search for: le0

I have tried to set up Samba on my Solaris 2.5.1 with 2 interfaces (le0, le0:1 - one network card with two IP addresses). But all I could see is throught the default ports 137 and 139. In my /etc/inetd.conf, I have: netbios-ns dgram udp wait root /opt/samba/bin/nmbd nmbd -s/opt/samba/lib/kes.smb.conf netbios-ssn stream tcp nowait root /opt/samba/bin/smbd smbd -...

...mat -- Cats land on their feet. Toast lands jellyside down. A cat glued to some jelly toast will hover in quantum indecision perl -e'$_=q#: 13_2: 12/o{>: 8_4) (_4: 6/2^-2; 3;-2^\2: 5/7\_/\7: \ 12m m::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' Yes, of course it's the right cabl [le0: NO CARRIER] -------------- next part -------------- A non-text attachment was scrubbed... Name: part Type: application/pgp-signature Size: 190 bytes Desc: not available Url : http://lists.xiph.org/pipermail/icecast/attachments/20040422/f6b77ab4/part.pgp

Hi, I am getting this log entry in the nmb.log file. Any ideas why I am getting it? query_name_response: Multiple (2) responses received for a query on subnet 9.36. 220.43 for name WHITE<1d>. This response was from IP 9.36.223.255 Thanks Chip

...eet. > Toast lands jellyside down. > A cat glued to some jelly toast will hover in quantum indecision > > perl -e'$_=q#: 13_2: 12/o{>: 8_4) (_4: 6/2^-2; 3;-2^\2: 5/7\_/\7: \ > 12m m::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' > > Yes, of course it's the right cabl [le0: NO CARRIER] > -- Jappe Reuling jappe@parcproductions.com Parc Productions Waalsteeg 4-6 1011 ER Amsterdam Tel: +31 (0)20-4892456 Fax: +31 (0)20-4892458 Http: http://www.parcproductions.com Http: http://www.parchosting.com The information in this document can be confidential. It...

Hi, I'm running 1.9.18p7 on a Solaris 2.5 box with two interfaces. I have 2 class-C networks that are divided up with a 26-bit netmask (255.255.255.192) into 4 subnets, each. This is what the interfaces look like: le0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 38.253.161.130 netmask ffffffc0 broadcast 38.253.161.128 ether 8:0:20:77:34:b3 le1: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500...

Is it possible to somehow meter and log the bandwidth used by individual mountpoints? I'm using mrtg to monitor the whole server, but I'd like to know which mountpoints are creating the most traffic so I can offer better-priced streaming packages to users who really aren't using all that much bandwidth. And also to be able to charge more for users who use way much more bandwidth than

Here's another easy rsync question (I am trying to make sense of some stuff): Let's say I have this burp file, which I set the follow uid/gid: raub@kushana-13>ls -l burp -rw-r--r-- 1 nobody4 noaccess 44800 Feb 18 13:07 burp raub@kushana-14> When I move it to katri, since it does not have those uid/gid defined, it just spits them out as the appropriate numbers (that were

Hello! I have two problems. One is, that I cannot ping a DomU from Dom0 (or any other host in my local network) and the second one is, that I cannot ping the same site (eg. www.suse.com) from two DomU''s at the same time. I have a fresh installation of openSuse 11.0 with Kernel 2.6.25.20-0.1-xen and my box has two physical ethernet cards. As far as I have investigated, eth0 is the one

...he factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those parameters here. #device an # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pseudo-device ether # Ethernet sup...

...ry default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those parameters here. #device an # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? disable port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? disable port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? disable port 0x280 irq 10 drq 0 #device cs0 at isa? disable port 0x300 #device sn0 at isa? disable port 0x300 irq 10 # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pse...

...tory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those parameters here. device an # The probe order of these is presently determined by i386/isa/isa_compat.c. device ie0 at isa? disable port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? disable port 0x300 irq 5 iomem 0xd0000 device lnc0 at isa? disable port 0x280 irq 10 drq 0 device cs0 at isa? disable port 0x300 device sn0 at isa? disable port 0x300 irq 10 # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pseudo...

...67bd2 100644 --- a/arch/x86/crypto/glue_helper-asm-avx2.S +++ b/arch/x86/crypto/glue_helper-asm-avx2.S @@ -67,7 +67,7 @@ vmovdqu (iv), t2x; \ vmovdqa t2x, t3x; \ inc_le128(t2x, t0x, t1x); \ - vbroadcasti128 bswap, t1; \ + vbroadcasti128 bswap(%rip), t1; \ vinserti128 $1, t2x, t3, t2; /* ab: le0 ; cd: le1 */ \ vpshufb t1, t2, x0; \ \ @@ -124,13 +124,13 @@ tivx, t0, t0x, t1, t1x, t2, t2x, t3, \ xts_gf128mul_and_shl1_mask_0, \ xts_gf128mul_and_shl1_mask_1) \ - vbroadcasti128 xts_gf128mul_and_shl1_mask_0, t1; \ + vbroadcasti128 xts_gf128mul_and_shl1_mask_0(%r...

...t the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those paremeters here. #device an # Xircom Ethernet #device xe # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pseudo-device ether # Ethernet sup...

Changes: - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce

Changes: - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

Changes: - patch v3: - Update on message to describe longer term PIE goal. - Minor change on ftrace if condition. - Changed code using xchgq. - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends