Sell Cisco Systems equipment items
Hello, We have following original used and 100% compatible Cisco,Card,GBIC/SFP,WIC,console cable items for sale. If you are interested, pls feel free to contact us! example of the products: CWDM-SFP-1G 38dB (Ultra long-haul)--1510nm,1530nm,1550nm,1570nm,1590nm,1610nm WS-G5483, GLC-SX-MM SFP-GE-L WS-G5487, WS-G5484, WS-G5486, GLC-SX-MM, GLC-LH-SM, GLC-ZX-SM, GLC-T, .. NM-2FE2W-T1, NM-2FE2W-E1, NM-2FE2W-V2, WIC-1T, WIC-2T, WIC-2A/S, WIC-1B/ST, WIC-1ENET, VWIC-1MFT-T1, VWIC-1MFT-E1, VWIC-2MFT-T1, VWIC-2MFT-E1, VWIC-1MFT-G703, VWIC-2MFT-G703, VWIC-1MFT-T1-DI, VWIC-2MFT-T1-DI, NM-1E, NM-4E, .. WS-C2950-24, WS-C2950T-24, WS-C2950G-24-EI, WS-C2950G-48-EI, .. CONSOLE CABLE, CAB-STACK-1M/3M, CAB-V35MT, CAB-V35FC, CAB-SS-V.35MT, CAB-SS-V.35FC, CAB-SS-232MT, CAB-SS-232FC, CAB-232MT, CAB-232FC, CAB-SS-X21MT, CAB-SS-X21FC, CAB-X21MT, .. MEM-npe400-512MB, MEM-3660-128mb, MEM2600-32D, MEM2600-16FS, MEM2600XM-64D, MEM-S1-128MB, MEM-S2-256MB, MEM-S2-512MB, MEM-MSFC-128MB, MEM2801-256D, MEM3800-256D, MEM3800-512, MEM3745-256D, MEM1841-256D, MEM180X-256D, WS-X6K-MSFC2-KIT, and so on. Payment method: PayPal and Wire transfers are accepted. Warranty Information: All items come with 1-Year warranty. Regards Helen.Zhou NEWSTAR NETWORKING TECHNOLOGY www.nstnetwork.com MSN: [EMAIL PROTECTED] Email: [EMAIL PROTECTED] AOL helenxuezhou Icq 320-880-606 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
optimal CPUTYPE / arch for Intel T5600 ?
Hi, I have an Asus A6JE laptop which has an Intel T5600 CPU. It is currently configured as i386 with CPUTYPE=prescott. But after reading wikipedia, I get the idea that I have slightly underconfigured my box, i.e. that a better configuration is possible. dmesg says (7.0-release): CPU: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz (1828.77-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6f6 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 2 real memory = 2147287040 (2047 MB) avail memory = 2095947776 (1998 MB) ACPI APIC Table: AMIOEMAPIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 Version 2.0 irqs 0-23 on motherboard acpi0: _ASUS_ Notebook on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 7ff0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_ec0: Embedded Controller: GPE 0x1c port 0x62,0x66 on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 cpu0: ACPI CPU on acpi0 coretemp0: CPU On-Die Thermal Sensors on cpu0 est0: Enhanced SpeedStep Frequency Control on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 6130b2406000b24 device_attach: est0 attach returned 6 p4tcc0: CPU Frequency Thermal Control on cpu0 cpu1: ACPI CPU on acpi0 ACPI Warning (tbutils-0243): Incorrect checksum in table [SSDT] - 77, should be 2C [20070320] coretemp1: CPU On-Die Thermal Sensors on cpu1 est1: Enhanced SpeedStep Frequency Control on cpu1 p4tcc1: CPU Frequency Thermal Control on cpu1 Maybe some amd64 configuration is possible, since it the cpu has AMD features? Please cc me, I'm not subscribed. Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: optimal CPUTYPE / arch for Intel T5600 ?
On Fri, Jul 25, 2008 at 09:45:40AM +0200, Rene Ladan wrote: Hi, I have an Asus A6JE laptop which has an Intel T5600 CPU. It is currently configured as i386 with CPUTYPE=prescott. But after reading wikipedia, I get the idea that I have slightly underconfigured my box, i.e. that a better configuration is possible. dmesg says (7.0-release): CPU: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz (1828.77-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6f6 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 2 No it's configured correctly. See /usr/share/mk/bsd.cpu.mk Maybe some amd64 configuration is possible, since it the cpu has AMD features? If you want amd64, you should have installed the amd64 architecture. But remember that some ports (e.g. flash plugin) are only available for the i386 architecture. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp99wLv31Fw7.pgp Description: PGP signature
Re: optimal CPUTYPE / arch for Intel T5600 ?
2008/7/25 Roland Smith [EMAIL PROTECTED]: On Fri, Jul 25, 2008 at 09:45:40AM +0200, Rene Ladan wrote: Hi, I have an Asus A6JE laptop which has an Intel T5600 CPU. It is currently configured as i386 with CPUTYPE=prescott. But after reading wikipedia, I get the idea that I have slightly underconfigured my box, i.e. that a better configuration is possible. dmesg says (7.0-release): CPU: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz (1828.77-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6f6 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 2 No it's configured correctly. See /usr/share/mk/bsd.cpu.mk Maybe some amd64 configuration is possible, since it the cpu has AMD features? If you want amd64, you should have installed the amd64 architecture. But It seems to be amd64-capable: http://ubuntuforums.org/archive/index.php/t-649410.html Side-grading seems quite hard :( : http://lists.freebsd.org/pipermail/freebsd-amd64/2004-December/003008.html remember that some ports (e.g. flash plugin) are only available for the i386 architecture. Flash is available for amd64 if you use swfdec :) Probably not worth the hassle, maybe when 7.1 gets released. Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: optimal CPUTYPE / arch for Intel T5600 ?
2008/7/25 Rene Ladan [EMAIL PROTECTED]: 2008/7/25 Roland Smith [EMAIL PROTECTED]: On Fri, Jul 25, 2008 at 09:45:40AM +0200, Rene Ladan wrote: Hi, I have an Asus A6JE laptop which has an Intel T5600 CPU. It is currently configured as i386 with CPUTYPE=prescott. But after reading wikipedia, I get the idea that I have slightly underconfigured my box, i.e. that a better configuration is possible. dmesg says (7.0-release): CPU: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz (1828.77-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6f6 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 2 No it's configured correctly. See /usr/share/mk/bsd.cpu.mk Maybe some amd64 configuration is possible, since it the cpu has AMD features? If you want amd64, you should have installed the amd64 architecture. But It seems to be amd64-capable: http://ubuntuforums.org/archive/index.php/t-649410.html Side-grading seems quite hard :( : http://lists.freebsd.org/pipermail/freebsd-amd64/2004-December/003008.html remember that some ports (e.g. flash plugin) are only available for the i386 architecture. Flash is available for amd64 if you use swfdec :) Probably not worth the hassle, maybe when 7.1 gets released. I guess I would have to rebuild all ports after the upgrade, or is it possible to run i386 ports on an amd64 box? Because userland needs to be rebuilt... Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: optimal CPUTYPE / arch for Intel T5600 ?
cpu1: ACPI CPU on acpi0 ACPI Warning (tbutils-0243): Incorrect checksum in table [SSDT] - 77, should be 2C [20070320] coretemp1: CPU On-Die Thermal Sensors on cpu1 est1: Enhanced SpeedStep Frequency Control on cpu1 p4tcc1: CPU Frequency Thermal Control on cpu1 Maybe some amd64 configuration is possible, since it the cpu has AMD features? not maybe but indeed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
graid3
i read the graid3 manual and http://www.acnc.com/04_01_03.html to make sure i know what's RAID3 and i don't understand few things. 1) The number of components must be equal to 3, 5, 9, 17, etc. (2^n + 1). why it can't be say 5 disks+parity? 2) -r Use parity component for reading in round-robin fashion. Without this option the parity component is not used at all for reading operations when the device is in a complete state. With this option specified random I/O read operations are even 40% faster , but sequential reads are slower. One cannot use this option if the -w option is also specified. how parity disk could speed up random I/O? is there any description of how graid3 actually works? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: graid3
Hello, 1. I don't see such a thing on the weblink you gave (acnc) In my opinion, this rule is pure nonsense, as raid 3 just use a separate drive to store stripe parity. You just need at least 3 drives, one for parity, 2 for data. you can do raid 3 with how many drives you want. 2. because the raid controler/software thing can reconstruct the data with only n-1 of the n drives in the array. in random IO this can be quite usefull, while in sequential read, the parity drive is not that much of use. On Fri, Jul 25, 2008 at 11:46 AM, Wojciech Puchar [EMAIL PROTECTED] wrote: i read the graid3 manual and http://www.acnc.com/04_01_03.html to make sure i know what's RAID3 and i don't understand few things. 1) The number of components must be equal to 3, 5, 9, 17, etc. (2^n + 1). why it can't be say 5 disks+parity? 2) -r Use parity component for reading in round-robin fashion. Without this option the parity component is not used at all for reading operations when the device is in a complete state. With this option specified random I/O read operations are even 40% faster , but sequential reads are slower. One cannot use this option if the -w option is also specified. how parity disk could speed up random I/O? is there any description of how graid3 actually works? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: optimal CPUTYPE / arch for Intel T5600 ?
On Fri, Jul 25, 2008 at 11:16:02AM +0200, Rene Ladan wrote: CPU: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz (1828.77-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6f6 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 2 No it's configured correctly. See /usr/share/mk/bsd.cpu.mk Maybe some amd64 configuration is possible, since it the cpu has AMD features? If you want amd64, you should have installed the amd64 architecture. But It seems to be amd64-capable: http://ubuntuforums.org/archive/index.php/t-649410.html Side-grading seems quite hard :( : http://lists.freebsd.org/pipermail/freebsd-amd64/2004-December/003008.html The easiest way to update is to make a backup of your data and then reinstall the amd64 version. I guess I would have to rebuild all ports after the upgrade, Yes, that would be best. Make a list of all installed ports (e.g. with portmaster -L), delete all ports and install the so-called root ports (No dependencies, not depended on) and leaf ports (have dependencies, not depended on) again. or is it possible to run i386 ports on an amd64 box? It is possible, but I've never bothered trying it. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgptxQg6ztb5M.pgp Description: PGP signature
FreeBSD and ECC memory?
Hello, I am buying hardware for a FreeBSD server and me and my friend argue about whether or not to by ECC RAM for the server. It is a HP ProLiant ML110 G4 machine and currently it has 2 x 512 HP DDR2 ECC memory. My friend says buying ECC memory is not wise, because we would not profit from it since this server will not need very high availability (but still we'd like to make it a solid server). And also that ECC memory slows down memory operations by 2-3% all together. Also, we would profit from buying non-ECC memory because we already have 2 x 1GB non-ECC memory and if we: - buy extra 2 x 1GB non-ECC memory we'll have 4GB all together (4 x 1GB) - buy extra 2 x 1GB ECC memory we'll have 3GB all together (2 x 512MB + 2 x 1GB) 1. So, what would you base your decision on? Is getting ECC worth losing 1GB of non-ECC memory? 2. What are your experiences with ECC? 3. Did self-halt because of a memory error (having ECC memory) ever happen to someone here? 4. If there is non-ECC memory installed, how does FreeBSD recognizes (corrects?) memory errors? Thanks, Nejc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
setuid not working on directories, or am I doing something wrong?
$ whoami wmoran $ mkdir test2 $ sudo chown daemon:daemon test2 $ sudo chmod 6777 test2 $ ls -lah | grep test2 drwsrwsrwx 2 daemon daemon 512B Jul 25 07:40 test2 $ touch test2/testfile.empty $ ls -lah test2 total 8 drwsrwsrwx 2 daemon daemon 512B Jul 25 07:41 . drwxr-xr-x 59 wmoran wheel6.0K Jul 25 07:40 .. -rw-r--r-- 1 wmoran daemon 0B Jul 25 07:41 testfile.empty Shouldn't testfile.empty show up as daemon:daemon? or am I misunderstanding something about how setuid works? This is on FreeBSD 7, but I observe the same thing on 6.3 and 6.2. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ [EMAIL PROTECTED] Phone: 412-422-3463x4023 IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: [OT ? ] getting stats out of network capture
On Behalf Of Norberto Meijome On Thu, 24 Jul 2008 17:42:04 -0700 Chuck Swiger [EMAIL PROTECTED] wrote: Try something like this on the webserver or client machine: # tcpdump -ttt -q -n -A tcp port 80 Excellent, thanks Chuck. I haven't got access to the server, and the client has to run on a win32 ... so i'll figure out how to tcpdump on w32 or howto in wireshark gui. On MS-Windows, the easiest option is to download and install Wireshark 1.0, which will also install Winpcap. It gives you the option of installing Winpcap as a system service, which enables it for all users, even the non-admin types. When you use it, if possible, always tie it to the NIC, not the NDIS layer. A lot of traffic is sidetracked before it gets to NDIS. In some cases where the NIC is not supported, we have found that the only traffic Wireshark can capture is what is left after every other process has received theirs. Bob McConnell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and ECC memory?
Nejc Škoberne wrote: 4. If there is non-ECC memory installed, how does FreeBSD recognizes (corrects?) memory errors? By crashing or corrupting data, of course. Not doing this is what ECC is for :) Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and ECC memory?
Nejc Škoberne wrote: Hello, I am buying hardware for a FreeBSD server and me and my friend argue about whether or not to by ECC RAM for the server. It is a HP ProLiant ML110 G4 machine and currently it has 2 x 512 HP DDR2 ECC memory. My friend says buying ECC memory is not wise, because we would not profit from it since this server will not need very high availability (but still we'd like to make it a solid server). And also that ECC memory slows down memory operations by 2-3% all together. Also, we would profit from buying non-ECC memory because we already have 2 x 1GB non-ECC memory and if we: - buy extra 2 x 1GB non-ECC memory we'll have 4GB all together (4 x 1GB) - buy extra 2 x 1GB ECC memory we'll have 3GB all together (2 x 512MB + 2 x 1GB) 1. So, what would you base your decision on? Is getting ECC worth losing 1GB of non-ECC memory? My decision would be based upon what the server was going to be used for. Home use, or non mission critical I'd say non-ECC is just fine. At work for mission critical database, mail, etc I stick with ECC. Especially when it comes to Windows, as Windows has a nasty habit of trying to mask what's going on behind the scene. No way I'd run a large SQL database or Exchange server without ECC. I'd be more concerned with trying to buy all the memory at the same time so the sticks were all identical, especially with regard to timing and speed ratings. You can create a problem when you have stick(s) from one manufacturer then add in different ones later. IMHO, in this particular situation, my gut feeling from your description would be to go with the 4GB of non-ECC as it sounds like the scenario doesn't match the criteria I use for justifying ECC as a must have. 2. What are your experiences with ECC? 3. Did self-halt because of a memory error (having ECC memory) ever happen to someone here? If it does you have defective hardware that is in need of replacement. Yes, I have had bad RAM; whether it's ECC or non-ECC isn't the issue when it is simply defective. 4. If there is non-ECC memory installed, how does FreeBSD recognizes (corrects?) memory errors? Generally speaking this occurs more at the hardware level. Non-ECC RAM can correct single bit errors while ECC is capable of fixing multi-bit errors. However, should I become aware that ECC was fixing too many errors too often I would consider there to be defective hardware present. The purpose of these schemes is to compensate for the fact that in every so many (some large number) of memory transactions there may be a bit that gets flipped. If this is happening more often than (some large number) then there is a defect present. ECC just buys you uptime in the event there are more errors than there should be. In either case these bit flips should only happen extremely infrequently, if ever at all. Consider that these schemes are sort of a fallback to an extreme what if situation and really shouldn't come into play during most nominal operations. I would go with ECC for something that just had to stay up even in the face or errors. In either case I'd still replace the defective component(s), irregardless of whether they were ECC or not. I've seen thousands of machines with non-ECC RAM over the last 15 years that worked just fine. Just my $.02 here. YMMV and all other standard disclaimers apply. :-) -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and ECC memory?
4. If there is non-ECC memory installed, how does FreeBSD recognizes (corrects?) memory errors? it's not OS job, but hardware. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: setuid not working on directories, or am I doing something wrong?
Give me the output of 'mount' please. Thanks Subhro On Fri, Jul 25, 2008 at 5:15 PM, Bill Moran [EMAIL PROTECTED] wrote: $ whoami wmoran $ mkdir test2 $ sudo chown daemon:daemon test2 $ sudo chmod 6777 test2 $ ls -lah | grep test2 drwsrwsrwx 2 daemon daemon 512B Jul 25 07:40 test2 $ touch test2/testfile.empty $ ls -lah test2 total 8 drwsrwsrwx 2 daemon daemon 512B Jul 25 07:41 . drwxr-xr-x 59 wmoran wheel6.0K Jul 25 07:40 .. -rw-r--r-- 1 wmoran daemon 0B Jul 25 07:41 testfile.empty Shouldn't testfile.empty show up as daemon:daemon? or am I misunderstanding something about how setuid works? This is on FreeBSD 7, but I observe the same thing on 6.3 and 6.2. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ [EMAIL PROTECTED] Phone: 412-422-3463x4023 IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- WC Fields - A rich man is nothing but a poor man with money. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: setuid not working on directories, or am I doing something wrong?
In response to Subhro [EMAIL PROTECTED]: Give me the output of 'mount' please. In the example detailed below: $ mount /dev/ad4s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad4s1e on /tmp (ufs, local, soft-updates) /dev/ad4s1f on /usr (ufs, local, soft-updates) /dev/ad4s1d on /var (ufs, local, soft-updates) procfs on /proc (procfs, local) This was in my home directory, which is /usr/home/wmoran Again, the behaviour persists across at least three machines (this one with 7.0, and two others with 6.X). On Fri, Jul 25, 2008 at 5:15 PM, Bill Moran [EMAIL PROTECTED] wrote: $ whoami wmoran $ mkdir test2 $ sudo chown daemon:daemon test2 $ sudo chmod 6777 test2 $ ls -lah | grep test2 drwsrwsrwx 2 daemon daemon 512B Jul 25 07:40 test2 $ touch test2/testfile.empty $ ls -lah test2 total 8 drwsrwsrwx 2 daemon daemon 512B Jul 25 07:41 . drwxr-xr-x 59 wmoran wheel6.0K Jul 25 07:40 .. -rw-r--r-- 1 wmoran daemon 0B Jul 25 07:41 testfile.empty Shouldn't testfile.empty show up as daemon:daemon? or am I misunderstanding something about how setuid works? This is on FreeBSD 7, but I observe the same thing on 6.3 and 6.2. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ [EMAIL PROTECTED] Phone: 412-422-3463x4023 IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- WC Fields - A rich man is nothing but a poor man with money. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ [EMAIL PROTECTED] Phone: 412-422-3463x4023 IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pxe bootable freebsd rescue system?
Hello I try to setup a FreeBSD PXE bootable rescue image. I'm aware of the rescue mode on Disc1 on every FreeBSD CD. My goal is to setup a non interactive session. Boot via PXE, set a root password depends on the mac address, start ssh and allow remote login. Adrian Steinmann showed something similar at the Eurobsdcon 2005 in Basel with Single User Secure Shell, Installing small systems with FreeBSD using the Secure Shell RAMdisk environment He uses a ssh key, where i have to set the root password during the boot, depending on the mac adress. This is not a big issue with linux systems, where most rescue systems allow you to set password=xxx during the pxe boot. Maybe someone has already done this and wants to share some information with me :) Regards, Thomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and ECC memory?
On Fri, Jul 25, 2008 at 08:42:54AM -0400, Michael Powell wrote: Nejc ?koberne wrote: Hello, I am buying hardware for a FreeBSD server and me and my friend argue about whether or not to by ECC RAM for the server. It is a HP ProLiant ML110 G4 machine and currently it has 2 x 512 HP DDR2 ECC memory. My friend says buying ECC memory is not wise, because we would not profit from it since this server will not need very high availability (but still we'd like to make it a solid server). And also that ECC memory slows down memory operations by 2-3% all together. Also, we would profit from buying non-ECC memory because we already have 2 x 1GB non-ECC memory and if we: - buy extra 2 x 1GB non-ECC memory we'll have 4GB all together (4 x 1GB) - buy extra 2 x 1GB ECC memory we'll have 3GB all together (2 x 512MB + 2 x 1GB) 1. So, what would you base your decision on? Is getting ECC worth losing 1GB of non-ECC memory? My decision would be based upon what the server was going to be used for. Home use, or non mission critical I'd say non-ECC is just fine. At work for mission critical database, mail, etc I stick with ECC. Especially when it comes to Windows, as Windows has a nasty habit of trying to mask what's going on behind the scene. No way I'd run a large SQL database or Exchange server without ECC. I'd be more concerned with trying to buy all the memory at the same time so the sticks were all identical, especially with regard to timing and speed ratings. You can create a problem when you have stick(s) from one manufacturer then add in different ones later. IMHO, in this particular situation, my gut feeling from your description would be to go with the 4GB of non-ECC as it sounds like the scenario doesn't match the criteria I use for justifying ECC as a must have. 2. What are your experiences with ECC? 3. Did self-halt because of a memory error (having ECC memory) ever happen to someone here? If it does you have defective hardware that is in need of replacement. Yes, I have had bad RAM; whether it's ECC or non-ECC isn't the issue when it is simply defective. 4. If there is non-ECC memory installed, how does FreeBSD recognizes (corrects?) memory errors? Generally speaking this occurs more at the hardware level. Non-ECC RAM can correct single bit errors while ECC is capable of fixing multi-bit errors. No, non-ECC RAM cannot detect or correct any errors at all. (Old parity-RAM could detect, but not correct, single-bit errors.) ECC is generally capable of detecting multi-bit errors and fixing single-bit errors. (There are different ways of implementing ECC. Some of them might well be able to fix multi-bit errors too.) However, should I become aware that ECC was fixing too many errors too often I would consider there to be defective hardware present. The purpose of these schemes is to compensate for the fact that in every so many (some large number) of memory transactions there may be a bit that gets flipped. If this is happening more often than (some large number) then there is a defect present. ECC just buys you uptime in the event there are more errors than there should be. Note that random, spontaneous bit flips can happen (infrequently) even in perfectly good RAM. (Due to cosmic rays, radioactive decay in surrounding material, and similar stuff. (No, I am not joking.)) ECC will handle such errors just fine, and that is the main reason why I would want ECC. You can also get defective memory modules, but such can usually be detected by running memtest86 or similar. ECC can usually handle memory modules that have some bits more or less permanently wrong, but such modules should be replaced as soon as possible. In either case these bit flips should only happen extremely infrequently, if ever at all. Consider that these schemes are sort of a fallback to an extreme what if situation and really shouldn't come into play during most nominal operations. I would go with ECC for something that just had to stay up even in the face or errors. In either case I'd still replace the defective component(s), irregardless of whether they were ECC or not. I've seen thousands of machines with non-ECC RAM over the last 15 years that worked just fine. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and ECC memory?
Michael Powell wrote: [snip] 1. So, what would you base your decision on? Is getting ECC worth losing 1GB of non-ECC memory? Oh - and the other criterion I forgot to mention. If the box in question is only being used by 1 or 2 people and can have downtime to fix defects whenever you want, non-ECC is a consideration. That being said, if it is a box depended upon by many people and expected to be reliable I'd spend the money on 4GB of ECC from the outset. The difference being I need to put up a box and move on to other things. Having to return and muck with complaints is a counter productive waste of time that could be better spent with new projects. [snip] Just my $.02 here. YMMV and all other standard disclaimers apply. :-) -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: setuid not working on directories, or am I doing something wrong?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bill Moran wrote: | $ whoami | wmoran | $ mkdir test2 | $ sudo chown daemon:daemon test2 | $ sudo chmod 6777 test2 | $ ls -lah | grep test2 | drwsrwsrwx 2 daemon daemon 512B Jul 25 07:40 test2 | $ touch test2/testfile.empty | $ ls -lah test2 | total 8 | drwsrwsrwx 2 daemon daemon 512B Jul 25 07:41 . | drwxr-xr-x 59 wmoran wheel6.0K Jul 25 07:40 .. | -rw-r--r-- 1 wmoran daemon 0B Jul 25 07:41 testfile.empty | | Shouldn't testfile.empty show up as daemon:daemon? or am I | misunderstanding something about how setuid works? | | This is on FreeBSD 7, but I observe the same thing on 6.3 and 6.2. | Hi Bill, ~From what I've read, you have to take some extra steps to get this to work. First, visit this page and search for suiddir: http://www.freebsd.org/cgi/man.cgi?query=mountsektion=8apropos=0manpath=FreeBSD+7.0-RELEASE I believe you have to run a kernel with the SUIDDIR option enabled, and then you have to mount your filesystem with the suiddir option, as described in the mount man page above. Let us know if that works for you or not. Best regards, Greg - -- Greg Larkin http://www.sourcehosting.net/ http://www.FreeBSD.org/ - The Power To Serve -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIics70sRouByUApARAnZbAJ9UK/3OA6Q9m4TIk6vnzT8Hrx4P+wCgnkw2 JaLLa7Lp7Y8v2Jm04qSWC1I= =WC5T -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: setuid not working on directories, or am I doing something wrong?
In response to Greg Larkin [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bill Moran wrote: | $ whoami | wmoran | $ mkdir test2 | $ sudo chown daemon:daemon test2 | $ sudo chmod 6777 test2 | $ ls -lah | grep test2 | drwsrwsrwx 2 daemon daemon 512B Jul 25 07:40 test2 | $ touch test2/testfile.empty | $ ls -lah test2 | total 8 | drwsrwsrwx 2 daemon daemon 512B Jul 25 07:41 . | drwxr-xr-x 59 wmoran wheel6.0K Jul 25 07:40 .. | -rw-r--r-- 1 wmoran daemon 0B Jul 25 07:41 testfile.empty | | Shouldn't testfile.empty show up as daemon:daemon? or am I | misunderstanding something about how setuid works? | | This is on FreeBSD 7, but I observe the same thing on 6.3 and 6.2. | Hi Bill, ~From what I've read, you have to take some extra steps to get this to work. First, visit this page and search for suiddir: http://www.freebsd.org/cgi/man.cgi?query=mountsektion=8apropos=0manpath=FreeBSD+7.0-RELEASE I believe you have to run a kernel with the SUIDDIR option enabled, and then you have to mount your filesystem with the suiddir option, as described in the mount man page above. Let us know if that works for you or not. That explains it, Greg. Thanks for the feedback. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ [EMAIL PROTECTED] Phone: 412-422-3463x4023 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and ECC memory?
Erik Trulsson wrote: [snip] No, non-ECC RAM cannot detect or correct any errors at all. (Old parity-RAM could detect, but not correct, single-bit errors.) Actually quite true. The old parity bit functionality that was removed from RAM and then called non-ECC actually migrated to the memory controller. So yes, it isn't the RAM that does it. Poor choice of wording on my part. ECC is generally capable of detecting multi-bit errors and fixing single-bit errors. (There are different ways of implementing ECC. Some of them might well be able to fix multi-bit errors too.) These cost lots of money. Common on Big Iron. In fact, non-ECC as an option isn't even offerred on B.I. [snip] The purpose of these schemes is to compensate for the fact that in every so many (some large number) of memory transactions there may be a bit that gets flipped. If this is happening more often than (some large number) then there is a defect present. ECC just buys you uptime in the event there are more errors than there should be. Note that random, spontaneous bit flips can happen (infrequently) even in perfectly good RAM. (Due to cosmic rays, radioactive decay in surrounding material, and similar stuff. (No, I am not joking.)) ECC will handle such errors just fine, and that is the main reason why I would want ECC. Especially true in satellites. The RAM in a satellite, or other spacecraft must be radiation hardened to be usuable at all. And yes, it is no joke but the truth what you say. For me the dividing line is when lots of people depend on a box 24/7 it must be ECC. A storage server in someones basement doesn't necessarily fit into this category. You can also get defective memory modules, but such can usually be detected by running memtest86 or similar. ECC can usually handle memory modules that have some bits more or less permanently wrong, but such modules should be replaced as soon as possible. I agree - I was kind of harping on the defective idea. If it's defective the manufacturer owes me a replacement, as in yesterday. [snip] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and ECC memory?
If you can afford it, always buy the ECC. Saves your bacon more often than not in the long run. My Mac Pro personal desktop has it. It developed an issue in one of the sticks. The system detected that many errors were getting corrected, and disabled the whole stick. Sure I lost 2GB but the system did not go down. I can shut it down and replace the memory at my leisure. A Solaris 10 server I run has a memory stick creating many errors. System is still up and I can replace the stick when I can without a hard crash. ECC cannot necessarily protect you from every memory issue but it can protect you from many sorts of memory issues and can keep you from having hard crashes and allow you to fix problems on your schedule instead of in a panic. First time you have a hard crash due to memory issues you will wish you had ECC. (And a motherboard that supports ChipKill) Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Motherboard FAN Speed control
Hi friends, I have a motherboard for Intel Core2Duo CPU using the Q35 chipset. How can I read out the speed of the Fan's connected to the Motherboard and control the speed? I would like to do that from console and later directly in my application. I tried to find something in sysctl but without success. David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and ECC memory?
On Fri, Jul 25, 2008 at 09:28:11AM -0400, Michael Powell wrote: Erik Trulsson wrote: [snip] No, non-ECC RAM cannot detect or correct any errors at all. (Old parity-RAM could detect, but not correct, single-bit errors.) Actually quite true. The old parity bit functionality that was removed from RAM and then called non-ECC actually migrated to the memory controller. So yes, it isn't the RAM that does it. Poor choice of wording on my part. Not quite. Old parity-RAM usually had an extra parity bit for every 8 data bits. By computing the parity (odd or even number of 1s) in the data bits and comparing it with the value of the parity bit (which got set when you wrote to memory) you could see if any single bit had been flipped. (ECC also uses these extra bits, but uses them in a smarter way.) Non-ECC RAM (as well as older non-parity RAM) does not have these extra bits and therefore you cannot detect any spontaneous bit-flips inside the RAM, since you have nothing to compare the data read against. (The reason non-ECC RAM is more common than ECC RAM is simply that these extra bits require extra chips on the memory module and therefore cost more money - money which most people are not prepared to pay.) (If you count the number of chips on a non-ECC memory module you will find that the number of chips on it is usually a multiple of 8, while on ECC- or parity-RAM it is usually a multiple of 9.) Many modern memory controllers do have parity checking (or even ECC) on the busses between controller and RAM and between controller and CPU. This lets you detect (or even fix) any errors may happen as data is transferred from RAM to CPU. It does not let you detect random errors inside the RAM, which parity or ECC can let you do. ECC is generally capable of detecting multi-bit errors and fixing single-bit errors. (There are different ways of implementing ECC. Some of them might well be able to fix multi-bit errors too.) These cost lots of money. Common on Big Iron. In fact, non-ECC as an option isn't even offerred on B.I. [snip] The purpose of these schemes is to compensate for the fact that in every so many (some large number) of memory transactions there may be a bit that gets flipped. If this is happening more often than (some large number) then there is a defect present. ECC just buys you uptime in the event there are more errors than there should be. Note that random, spontaneous bit flips can happen (infrequently) even in perfectly good RAM. (Due to cosmic rays, radioactive decay in surrounding material, and similar stuff. (No, I am not joking.)) ECC will handle such errors just fine, and that is the main reason why I would want ECC. Especially true in satellites. The RAM in a satellite, or other spacecraft must be radiation hardened to be usuable at all. And yes, it is no joke but the truth what you say. For me the dividing line is when lots of people depend on a box 24/7 it must be ECC. A storage server in someones basement doesn't necessarily fit into this category. It depends also on what kind of data is stored on the server. One of the really nasty problems that can occur with random bit-flips in non-ECC RAM is that important data can get silently corrupted. You can get an error in your database or spreadsheet or payroll data or whatever without noticing until it is too late (by which time all your backups will probably have this wrong data too.) Depending on the data this can be VERY bad, even if it is a system that is only used occasionally by a few people. Memory errors which cause the computer to crash can be quite disruptive, but they are at least easily noticed, and can then be handled. You can also get defective memory modules, but such can usually be detected by running memtest86 or similar. ECC can usually handle memory modules that have some bits more or less permanently wrong, but such modules should be replaced as soon as possible. I agree - I was kind of harping on the defective idea. If it's defective the manufacturer owes me a replacement, as in yesterday. Yes, and in the (luckily fairly uncommon) case that one of the chips on a memory module suddenly decides to stop working, then ECC can serve the same purpose as RAID does for disks - it allows the system to keep going until you have time to replace the broken part. (Which should be done ASAP since if you get random bit-flips in addition to a broken chip, ECC will not be able to correct those bits.) -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Motherboard FAN Speed control
On Fri, Jul 25, 2008 at 03:44:12PM +0200, Vonarburg, David wrote: Hi friends, I have a motherboard for Intel Core2Duo CPU using the Q35 chipset. How can I read out the speed of the Fan's connected to the Motherboard and control the speed? You can read it with the sysutils/mbmon port. I don't think you can set it. The CPU clock speed is managed by powerd(8) with the cpufreq(4) driver. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpiblnPIskZW.pgp Description: PGP signature
what is hostuuid, hostid (for)?
I just setup a new server with 7.0-RELEASE and saw the following lines for the fist time when booting the system: Setting hostuuid: 2231232f-4000--2333-aafbb88a88ca. Setting hostid: 0x89e3310b. What exactly are those for? Is it a unique string based on my hardware based on a certain component? CPU maybe? Is it something that could be determined under lets say Linux as well? I am asking because this could become handy as a unique identifier for a piece of equipment (for putting it on stock, re-using, inventory database, ...). Sandra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what is hostuuid, hostid (for)?
On Fri, Jul 25, 2008 at 04:26:21PM +0200, Sandra Kachelmann wrote: I just setup a new server with 7.0-RELEASE and saw the following lines for the fist time when booting the system: Setting hostuuid: 2231232f-4000--2333-aafbb88a88ca. Setting hostid: 0x89e3310b. What exactly are those for? Is it a unique string based on my hardware based on a certain component? See http://en.wikipedia.org/wiki/UUID and /etc/rc.d/hostid. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpgOMW4x9OWV.pgp Description: PGP signature
Re: optimal CPUTYPE / arch for Intel T5600 ?
2008/7/25 Roland Smith [EMAIL PROTECTED]: On Fri, Jul 25, 2008 at 09:45:40AM +0200, Rene Ladan wrote: Hi, I have an Asus A6JE laptop which has an Intel T5600 CPU. It is currently configured as i386 with CPUTYPE=prescott. But after reading wikipedia, I get the idea that I have slightly underconfigured my box, i.e. that a better configuration is possible. dmesg says (7.0-release): CPU: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz (1828.77-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6f6 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 2 No it's configured correctly. See /usr/share/mk/bsd.cpu.mk Maybe some amd64 configuration is possible, since it the cpu has AMD features? Hmm, according to CPU pages the T5600 is 64-bit capable (see http://forums.anandtech.com/messageview.aspx?catid=29threadid=2067695enterthread=ySTARTPAGE=2), but according to the 7.0 hardware notes it is not: 2.1 amd64 ... * Intel Pentium(R) 4 Processor supporting Intel EM64T (Prescott). This is fabricated on 90nm process technology, uses FC-LGA775 package, and operates with 3.20F/3.40F/3.60F GHz and Intel 925X Express chipsets. The corresponding S-Spec numbers are SL7L9, SL7L8, SL7LA, SL7NZ, SL7PZ, and SL7PX. Note that processors marked as 5xx numbers do not support EM64T. Yes, there are only two x's in the last sentence. Does that refer to another processor type? Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: optimal CPUTYPE / arch for Intel T5600 ?
On Fri, Jul 25, 2008 at 06:03:46PM +0200, Rene Ladan wrote: Hmm, according to CPU pages the T5600 is 64-bit capable (see http://forums.anandtech.com/messageview.aspx?catid=29threadid=2067695enterthread=ySTARTPAGE=2), but according to the 7.0 hardware notes it is not: ... * Intel Pentium(R) 4 Processor supporting Intel EM64T (Prescott). This is fabricated on 90nm process technology, uses FC-LGA775 package, and operates with 3.20F/3.40F/3.60F GHz and Intel 925X Express chipsets. The corresponding S-Spec numbers are SL7L9, SL7L8, SL7LA, SL7NZ, SL7PZ, and SL7PX. Note that processors marked as 5xx numbers do not support EM64T. Yes, there are only two x's in the last sentence. Does that refer to another processor type? Yes. The T5600 _does_ support x86_64/amd64/EM64T: http://processorfinder.intel.com/details.aspx?sSpec=SL9SP Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpk2BfdxDI5G.pgp Description: PGP signature
IP alias/routing question
This strikes me as a noob question but in 10 years of freebsd, I've never wrapped my brain around it and it seems to be causing me problems this time. I have many aliases on many servers. Some services listening on an alias address seem to return the packets out the alias address as shown in netstat -i in the Opkt column. Others seem to return packets back out the first address specified on the system. This has not bothered me before because it seems to work and I figured I was just confused on how netstat shows the In and Out packet counts. I assumed that local lan traffic would be listed on the appropriate line and anything headed out the WAN would go to default gateway thus appear on the line with the initial address. I've noticed it on ssh often, connect in on a second or third IP yet the packets show as going out through the first configured IP in netstat. I'm now setting up a bind server in which the third alias is the address for incoming DNS queries. It appears it's responding but even though the queries come in on the third alias, they go out through the primary address or more specifically, the packet count is incremented in the Opkts total for the IP address first attached to the interface via ifconfig (without an alias). My problem appears to be that the packets really are coming from the first IP as the source and are getting blocked by my firewall as they should (the first address is not supposed to be answering DNS queries). Am I conceptualizing what I'm seeing incorrectly and have a different config error, or is it true that some services respond with a different source IP other than the what they came in on if multiple aliases are specified on a single interface and wire. In other words, is the Opkt count on the IP irrelevant to the addressing of the packet? Please let me know if this should instead go to FreeBSD-Net. Supporting info: here is an example of the netstat, in this example, dns is listening on 192.168.0.18, the first interface ifconfig'd is 0.12. If I read it correctly, it goes out the default gateway which is somehow tied to the 0.12. This machine is not a gateway, has no FWDs in ipfw, and isn't running natd. $ netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll rl01500 Link#1 00:10:b5:76:ce:20 631 0 1 0 0 rl01500 192.168.252.0 192.168.252.11 0 - 0 - - rl11500 Link#2 00:14:2a:02:bd:6422628 0 7833 0 0 rl11500 192.168.0.0 192.168.0.12 11 - 7450 - - rl11500 192.168.0.11 192.168.0.11 1482 - 278 - - rl11500 192.168.0.18 192.168.0.18 1243 -0 - - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Dell Wireless 350 Bluetooth Internal Card
I am using a Dell Latitude D520 with the GENERIC kernel on FreeBSD 7.0.I am not able to fully utilize all of the devices available on this model. However, the most concerning issue is the Dell Wireless 350 Bluetooth Internal Card. I am not able to find the device or the device name on the boot log or on any forums on the web. Background information: This internel device is a combination Wi-Fi and Bluetooth and is fully customizable for one interface or the other. It’s built into each Dell Latitude D520 by default without any installation required. I suspect if I add the device name to a custom kernel and rebuild, it will recognize it. Any help is deeply appreciated.Sincerely,Harrison King.Resident Design. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IP alias/routing question
Chris Pratt wrote:
I'm now setting up a bind server in which the third alias
is the address for incoming DNS queries. It appears
it's responding but even though the queries come in
on the third alias, they go out through the primary
address or more specifically, the packet count is
incremented in the Opkts total for the IP address first
attached to the interface via ifconfig (without an alias).
My problem appears to be that the packets really are
coming from the first IP as the source and are getting
blocked by my firewall as they should (the first address
is not supposed to be answering DNS queries).
Carefully not answering the 'why do these packets come from the
wrong address' question, but just pointing out that BIND is
actually rather more configurable in this respect than most
software.
You can control what IPs BIND will communicate on for various
purposes using the following statements in the options { } section
of named.conf:
listen-on {
127.0.0.1;
12.34.56.78;
};
listen-on-v6 {
::1;
1234:5678:9abc:def0::1;
};
query-source address 12.34.56.78 port *;
query-source-v6address 1234:5678:9abc:def0::1 port *;
transfer-source12.34.56.78 port *;
transfer-source-v6 1234:5678:9abc:def0::1 port *;
notify-source 812.34.56.78 port *;
notify-source-v6 1234:5678:9abc:def0::1 port *;
Note the 'port *' stuff -- due to the recent security problem with
the DNS protocol publicised by Dan Kaminsky, it is imperative that
the /source/ port on DNS traffic is allowed to be randomised. See
http://www.kb.cert.org/vuls/id/800113
http://security.freebsd.org/advisories/FreeBSD-SA-08:06.bind.asc
and make sure you install a patched version of BIND.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Re: IP alias/routing question
On Jul 25, 2008, at 10:12 AM, Matthew Seaman wrote:
Chris Pratt wrote:
I'm now setting up a bind server in which the third alias
is the address for incoming DNS queries. It appears
it's responding but even though the queries come in
on the third alias, they go out through the primary
address or more specifically, the packet count is
incremented in the Opkts total for the IP address first
attached to the interface via ifconfig (without an alias).
My problem appears to be that the packets really are
coming from the first IP as the source and are getting
blocked by my firewall as they should (the first address
is not supposed to be answering DNS queries).
Carefully not answering the 'why do these packets come from the
wrong address' question, but just pointing out that BIND is
actually rather more configurable in this respect than most
software.
You can control what IPs BIND will communicate on for various
purposes using the following statements in the options { } section
of named.conf:
listen-on {
127.0.0.1;
12.34.56.78;
};
listen-on-v6 {
::1;
1234:5678:9abc:def0::1;
};
query-source address 12.34.56.78 port *;
query-source-v6address 1234:5678:9abc:def0::1 port *;
transfer-source12.34.56.78 port *;
transfer-source-v6 1234:5678:9abc:def0::1 port *;
notify-source 812.34.56.78 port *;
notify-source-v6 1234:5678:9abc:def0::1 port *;
I am not using those latter three but only the listen-on.
I will experiment. I am still curious if what I see with
bind, ssh and some others is actually returning on the
first address or if netstat just makes it look that way
because of the default gateway.
Note the 'port *' stuff -- due to the recent security problem with
the DNS protocol publicised by Dan Kaminsky, it is imperative that
the /source/ port on DNS traffic is allowed to be randomised. See
This is good to know. I assumed going to the current
patched cvs was enough.
Thank you very much.
http://www.kb.cert.org/vuls/id/800113 http://security.freebsd.org/
advisories/FreeBSD-SA-08:06.bind.asc
and make sure you install a patched version of BIND.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Is it Better to Wait until the 6.3 Upgrade to build bind?
Several 6.2 systems are about to be upgraded to FreeBSD6.3. They run bind which also must be upgraded to the new patched version. Should I wait to build the new bind port until after the systems are upgraded or does it matter? Thank you. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Network Operations Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is it Better to Wait until the 6.3 Upgrade to build bind?
On Jul 25, 2008, at 11:32 AM, Martin McCormick wrote: Several 6.2 systems are about to be upgraded to FreeBSD6.3. They run bind which also must be upgraded to the new patched version. Should I wait to build the new bind port until after the systems are upgraded or does it matter? Either way, you should not wait to update bind. :-) If you upgrade to 6.3-STABLE, you should be updating to a 9.3 version of which includes the patch, but it's reasonable to install a later version from ports if you so prefer. If you compile this under 6.2, it would run fine if you later upgrade to 6.3... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is it Better to Wait until the 6.3 Upgrade to build bind?
Chuck Swiger writes: Either way, you should not wait to update bind. :-) It's like 72 hours away.:-) On Monday, I will actually do the cvs-based upgrades for all the systems in question and will also upgrade bind so that when they are rebooted, bind only has to go down for one time. If I needed to wait until 6.3 is built, then each system would get rebooted and then bind would have to be stopped once more to install the new bind. We are running bind9.3xso we need the upgrade quickly and I just wanted to do it all with as little disruption as possible. It sounds like I can build the new bind first and then do all the cvs upgrades so all that is needed in the wee hours of the morning is a reboot. Many thanks. Martin McCormick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: new vanilla system fails to install many packages/ports
Steve Franks wrote: On Thu, Jul 24, 2008 at 4:56 PM, Kevin Kinsey [EMAIL PROTECTED] wrote: Steve Franks wrote: I must be missing something obvious. About 25% of my dependencies fail to install with errors like: install-info: /usr/local/info/dir: empty file pkg-add: command 'install-info --quiet /blah.info' failed system is 7.0/i386 Steve info is GNU-related. Any reason that GNU-stuff, esp. info, wouldn't have been installed/built thus far? (I dunno, but, maybe a csup with the GNU stuff rejected or commented out ...) All I did was a developer (not x developer) sysinstall off 7.0 disk 1. No tweaking, hacking, or extra packages until I got a clean boot onto the new disk. I'm somewhere between user and power user. I have 5 running freebsd systems under my belt, and was going to do my laptop (I've given up on it several times already - bloody compaq). And anything these ports have in common (assuming they're all GNU for starters). They aren't Linuxolator stuff? Seems to me, they all use gnuinfo instead of manpages? I don't even know what gnuinfo is, nor linuxulator. Right, GNU programs may have manpages, but they also have info pages which were developed by GNU as a replacement for the UNIX manual (I'm assuming based on past reading ... memory ain't all it used to be). Linuxulator or however it's spelled is just a colloquialism for the FreeBSD linux emulation. I've got few guesses for ya. Developer package has documentation, correct? Or not? What's ls -ld /usr/local/info give? (!) Bison won't even install (makes fine, but install fails), and that's pretty darn basic, no? Steve Yup, 'tis. Tho' I figure someday BSD'ers would like to have their own implementation. Again, just a guess. KDK -- When all else fails, EAT!!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IP alias/routing question
On Fri, Jul 25, 2008 at 10:12 AM, Matthew Seaman [EMAIL PROTECTED] wrote: Chris Pratt wrote: I'm now setting up a bind server in which the third alias is the address for incoming DNS queries. It appears it's responding but even though the queries come in on the third alias, they go out through the primary address or more specifically, the packet count is incremented in the Opkts total for the IP address first attached to the interface via ifconfig (without an alias). My problem appears to be that the packets really are coming from the first IP as the source and are getting blocked by my firewall as they should (the first address is not supposed to be answering DNS queries). Carefully not answering the 'why do these packets come from the wrong address' question, but just pointing out that BIND is actually rather more configurable in this respect than most software. Deliberately addressing the question of 'why do these packets come from the wrong address' question which Mr. Seaman avoided (hello again, Mathew!), I'll add my two cents. Run netstat -rnfinet and examine what's in the 'Netif' column. If there was some inter-host traffic, you'll see a host entry for each of your aliases with a value of 'lo0'. Correlate all the entries in the routing table and you'll be able to determine what exits where. I'm not sure why this question doesn't come up more frequently as it can be problematic, especially in regards to jails (which are implemented using IP aliasing). I started a discussion some weeks ago on the subject that you may find interesting. To recap briefly, if a jail host sends traffic to a jail, the traffic will transit the lo0 interface, exit the jail's interface using the jail's IP address, and connect to the jail on its IP address. The end result? Traffic with identical source and destination IP addresses! Using your numbers, if named was running in a jail (192.168.0.18) and a query was made on the host (192.168.0.12), instead of seeing 192.168.0.12.3450 - 192.168.0.18.53 192.168.0.18.53 - 192.168.0.12.3450 you'd see the following on lo0: 192.168.0.18.3450 - 192.168.0.18.53 192.168.0.18.53 - 192.168.0.18.3450 You're not using jails, but what I'm describing isn't a jail issue, or a general IP aliasing issue, but a routing issue. Modifying the routing table is, of course, possible. But the results, I've found, are less than satisfactory. If you force traffic out an actual interface, the return traffic will probably still have to occur over loopback and you're back to where you started, but with some new problems. Note also that the above seems to apply irrespective of the number of network cards or networks. Tthe moral of the story? Configure named appropriately, and don't ask any more questions. ;-) On the other hand, if you insist on thinking immoral thoughts as I do, and find a more thorough explanation of any of the above, please do let me know. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
crontab mails
Hello On freebsd7.0, my crontab sends many mails about its jobs. I want crontab not to send these mails How can I do that ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IP alias/routing question
On Jul 25, 2008, at 4:05 PM, David Allen wrote: On Fri, Jul 25, 2008 at 10:12 AM, Matthew Seaman [EMAIL PROTECTED] wrote: Chris Pratt wrote: I'm now setting up a bind server in which the third alias is the address for incoming DNS queries. It appears it's responding but even though the queries come in on the third alias, they go out through the primary address or more specifically, the packet count is incremented in the Opkts total for the IP address first attached to the interface via ifconfig (without an alias). My problem appears to be that the packets really are coming from the first IP as the source and are getting blocked by my firewall as they should (the first address is not supposed to be answering DNS queries). Carefully not answering the 'why do these packets come from the wrong address' question, but just pointing out that BIND is actually rather more configurable in this respect than most software. Deliberately addressing the question of 'why do these packets come from the wrong address' question which Mr. Seaman avoided (hello again, Mathew!), I'll add my two cents. Run netstat -rnfinet and examine what's in the 'Netif' column. If there was some inter-host traffic, you'll see a host entry for each of your aliases with a value of 'lo0'. Correlate all the entries in the routing table and you'll be able to determine what exits where. I'm not sure why this question doesn't come up more frequently as it can be problematic, especially in regards to jails (which are implemented using IP aliasing). I started a discussion some weeks ago on the subject that you may find interesting. To recap briefly, if a jail host sends traffic to a jail, the traffic will transit the lo0 interface, exit the jail's interface using the jail's IP address, and connect to the jail on its IP address. The end result? Traffic with identical source and destination IP addresses! Using your numbers, if named was running in a jail (192.168.0.18) and a query was made on the host (192.168.0.12), instead of seeing 192.168.0.12.3450 - 192.168.0.18.53 192.168.0.18.53 - 192.168.0.12.3450 you'd see the following on lo0: 192.168.0.18.3450 - 192.168.0.18.53 192.168.0.18.53 - 192.168.0.18.3450 You're not using jails, but what I'm describing isn't a jail issue, or a general IP aliasing issue, but a routing issue. Modifying the routing table is, of course, possible. But the results, I've found, are less than satisfactory. If you force traffic out an actual interface, the return traffic will probably still have to occur over loopback and you're back to where you started, but with some new problems. Note also that the above seems to apply irrespective of the number of network cards or networks. Tthe moral of the story? Configure named appropriately, and don't ask any more questions. ;-) On the other hand, if you insist on thinking immoral thoughts as I do, and find a more thorough explanation of any of the above, please do let me know. Thanks for the very detailed explanation. I'm hot on the named configuration so that should quiet the questions. But ;-), how about the multiple route table implementation recently introduced in HEAD. Perhaps there is a solution there in the future! I stay with the current RELEASE so I haven't even researched, just watched the talk. Thanks again to both you and Matthew, Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: crontab mails
Yavuz Maslak [EMAIL PROTECTED] wrote: On freebsd7.0, my crontab sends many mails about its jobs. I want crontab not to send these mails How can I do that ? This is somewhat of a FAQ; see: http://lists.freebsd.org/pipermail/freebsd-questions/2004-March/038638.html -- Sahil Tandon [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
upgrade from 6.3 to 7.0
Hi I ve got 6.3 stable database server. Can i directly upgrade my server from 6.3 to 7.0 *default release=cvs tag=RELENG_6 *default release=cvs tag=. and also may i add ZFS to my server if such kind of update succsessfull. is it possible or not and advantage and disadvantage. -- Share now a pigeon's flight Bluebound along the ancient skies, Its women forever hair and mammal, A Mediterranean town may arise If you rip apart a pigeon's heart. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade from 6.3 to 7.0
You should not do the upgrade, though you can. ZFS is still experimental on FreeBSD though you can certainly use zfs pools on your existing system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade from 6.3 to 7.0
On Friday 25 July 2008, tethys ocean wrote: I ve got 6.3 stable database server. Can i directly upgrade my server from 6.3 to 7.0 Sure. Be prepared to rebuild and/or reinstall all your ports/packages and follow the other guidelines in src/UPDATING and other documentation. *default release=cvs tag=RELENG_6 That's 6-STABLE.. *default release=cvs tag=. ..and that's 8-CURRENT. You probably want tag=RELENG_7 (7.0-STABLE) or RELENG_7_0 (7.0-RELEASE + security fixes). and also may i add ZFS to my server if such kind of update succsessfull. is it possible or not and advantage and disadvantage. Since ZFS in FreeBSD is still experimental you should do a lot of testing and otherwise keep that in mind. For many loads and with the right tuning (see the wiki) it works fine. Advantages and disadvantages are many but a useful response depends on your goals. Why do you think ZFS would be a good thing for this server? JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade from 6.3 to 7.0
tethys ocean wrote: Hi I ve got 6.3 stable database server. Can i directly upgrade my server from 6.3 to 7.0 *default release=cvs tag=RELENG_6 *default release=cvs tag=. and also may i add ZFS to my server if such kind of update succsessfull. is it possible or not and advantage and disadvantage. It's quite possible to go from RELENG_6 to 7.0-RELEASE via the traditional csup/buildworld cycle. Take a backup, as *always*. If the machine is remote, have someone prepared to go there ASAP if there is a problem. Be sure and mergemaster -p. However, I don't recall much trouble ... aside from rebuilding all ports. In some cases, 'twas easier to make deinstall and then rebuild or even pkg_add. Kevin Kinsey -- Lee's Law: Mother said there would be days like this, but she never said that there'd be so many! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
