Re: Atheros drirve
On Thu, 16 Jun 2005 12:05, Eitarou Kamo wrote: (B> Is there the Atheros wi-fi driver with WPA encryption. (B> Do I need WPA_supplicant like hack? (B (BI'd say you need to use wpa_supplicant but I don't see it as a hack.. (B (B (B-- (BDaniel O'Connor software and network engineer (Bfor Genesis Software - http://www.gsoft.com.au (B"The nice thing about standards is that there (Bare so many of them to choose from." (B -- Andrew Tanenbaum (BGPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpyA0XbVxESR.pgp Description: PGP signature
Atheros drirve
Hi, (B (BIs there the Atheros wi-fi driver with WPA encryption. (BDo I need WPA_supplicant like hack? (B (BEitarou (B (B (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS upgrading from 5.2.1->5.4
On 6/15/05, Scot Hetzel <[EMAIL PROTECTED]> wrote:
> On 6/14/05, Mars G. Miro <[EMAIL PROTECTED]> wrote:
> > > If the build machine and install machine were at the same -RELEASE
> > > number, I don't believe you would have come across this problem.
> > >
> > I'm not sure I get you but the purpose of making the world in FreeBSD
> > is ought to be able to upgrade across releases (some people even
> > report upgrading from major releases, e.g 4.X to 5.X), albeit minor
> > hurdles (like the one I've experienced).
> >
> Normally this would work, when the build machine and the install
> machine are the same computer. But when you NFS mount the the built
> sources on another system it may or may not work. For example you
> wouldn't build the sources on a 5.x system and then NFS mount the
> built sources to a 4.x system. The reason is that the build system
> custom tailors the build tools for the 5.x system, and they will most
> likely not run on the 4.x system.
>
True. But let's assume that we're not upgrading from major releases
(4.X to 5.X), as it's even discouraged to do so, but only from the
same minor release/branch (e.g. 5.2.1 to 5.4, or 4.4 to 4.10), I don't
think that NFS-mounting the built sources would not work, as the
build{kernel|world} stage only builds the kernel and world at
/usr/obj. In my own experience, it generally works, in fact, this
doesn't only work for NFS but for remote upgrades as well, I've done
something like building the kernel/world in a ultrafast box, tar
bzip'ing /usr/src and /usr/obj, uploading them unto a remote server
that desperately need to be upgraded and doing the install
kernel/world on that remote server.
> Scot
>
cheers
mars
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.4 SMP kernels now available via FreeBSD Update
Billy Newsom wrote: > Colin Percival wrote: >> It sounds like the SMP kernel I provided for FreeBSD 5.3 was quite >> popular [...] > > I'm curious how popular. Would you like to report some statistics here > on the list? As in, how many SMP downloads did you get, say, in > comparison to the GENERIC? Ok, I've gone through my log files, and it looks like the number of systems downloading SMP kernels is around 4% - 6% of the number of systems downloading GENERIC kernels. That said, I don't think this should be used as a measure of how popular SMP is on FreeBSD systems overall, since people with high-end SMP systems are more likely than average to build their own kernels rather than using those which I distribute and the availability of SMP kernels via FreeBSD Update wasn't very widely advertised. It is probably safe to conclude that _at least_ 5% of FreeBSD systems have more than one processor, but I suspect that the actual value is considerably higher than that. Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: carp run script
On Wednesday 15 June 2005 22:39, Dmitriy Kirhlarov wrote: > Hi, list > > How I can use CARP for failover? > I need run script from CARP, when machine status change from backup to > master? Take a look at net/ifstated from ports. As far as I understand devd can do something like this as well since the new dhclient is around. -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgp71DOtdnUJG.pgp Description: PGP signature
Re: FreeBSD 5.4 SMP kernels now available via FreeBSD Update
Colin Percival wrote: > It sounds like the SMP kernel I provided for FreeBSD 5.3 was quite > popular, so I've started building an SMP kernel for FreeBSD 5.4 as > well, in addition to the usual GENERIC kernel. To take advantage I'm curious how popular. Would you like to report some statistics here on the list? As in, how many SMP downloads did you get, say, in comparison to the GENERIC? I wonder just how popular SMP has become. I ran dual Pentium 120s on a 430HX motherboard once a long time ago. And I know SMP goes farther back to at least the Pentium 60. Back then, it was pretty unusual, but I wonder what it's like now. Thanks. BTW, nice idea you've got. I tried to use it back before you offered SMP kernels and was disappointed. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
carp run script
Hi, list How I can use CARP for failover? I need run script from CARP, when machine status change from backup to master? By. Dmitriy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.3-p16/i386 unknown reason console hang
Hello all, Recently, one of our 5.3-p16/i386 machine got frequenctly hang. Details, 1. I can switch vty, but can't login (after typing username, got hang) 2. can response to ping, but not other tcp/udp services 3. can break into ddb It's a IBM X236 (EM64T) with 2G memory, and running Postfix/Amavisd/clamav and mail/openwebmail with apache2. Sometime ago, I also reported similar hang on 5.4/amd64, in fact they are the same machines, but at that time, I have some non-default nfs mount options. But now, nfs mount options only includes -L and nodev, nosuid. I'm wondering if it is some kind of hareware problems, similar thins happens on 5.4/amd64, 5.3/5.4 i386. Anyway, I have kernel conf, loader.conf, dmesg, and two ddb output (ps, show lockedvn, show threads) at http://rafan.infor.org/tmp/236/. By the way, a strange thing is that sometims, after hang, I reboot the machine, after *foreground* fsck, when it enters multiuser, after the login prompt, I got another hang. But this time, I can't break into ddb.. only solution is the power cycle. If you need more informations, please let me know :-) Regards, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 380 G4
The 6i controller support is included in 4.11, so if you want to go with 4.x family, 4.11 is your best bet. I am also running 5.3 and 5.4 on G4s without any problem. -- Babak Farrokhi On 6/15/05, Philippe PEGON <[EMAIL PROTECTED]> wrote: > Palle Girgensohn a écrit : > > Hi! > > > > Just a quick check - a client is getting a Proliant 380 G4 with a "6i" > > Raid controller. Haven't used this hardware before. Will it work fine > > with FreeBSD? Which version will work best, 5.4 or 4.11? Any > > peculiarities or things to think about? > > > > Any input appreciated! > > we have 3 Proliant 380 G4 and hardware works fine. For your information, I > attach a dmesg of one of > them. I've just another problem, but I don't think that it comes from > hardware : > > http://lists.freebsd.org/pipermail/freebsd-stable/2005-June/015952.html > > > > > Thanks > > Palle > > -- > Philippe PEGON > > > Copyright (c) 1992-2005 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.4-STABLE #3: Thu May 19 20:35:36 CEST 2005 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NS1A > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3600.15-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 > > Features=0xbfebfbff > Hyperthreading: 2 logical CPUs > real memory = 2147430400 (2047 MB) > avail memory = 2095968256 (1998 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 6 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > ioapic2 irqs 48-71 on motherboard > ioapic3 irqs 72-95 on motherboard > ioapic4 irqs 96-119 on motherboard > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > pcib0: on acpi0 > pci0: on pcib0 > pcib1: at device 2.0 on pci0 > pci2: on pcib1 > pcib2: at device 0.0 on pci2 > pci3: on pcib2 > bge0: mem > 0xfdef-0xfdef irq 25 at device 1.0 on pci3 > miibus0: on bge0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge0: Ethernet address: 00:12:79:d8:a0:37 > bge1: mem > 0xfdee-0xfdee irq 26 at device 1.1 on pci3 > miibus1: on bge1 > brgphy1: on miibus1 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge1: Ethernet address: 00:12:79:d8:a0:36 > pcib3: at device 0.2 on pci2 > pci4: on pcib3 > ciss0: port 0x4000-0x40ff mem > 0xfdf8-0xfdfb,0xfdff-0xfdff1fff irq 51 at device 3.0 on pci4 > pcib4: at device 6.0 on pci0 > pci5: on pcib4 > pcib5: at device 0.0 on pci5 > pci6: on pcib5 > pcib6: at device 0.2 on pci5 > pci10: on pcib6 > uhci0: port 0x2000-0x201f irq 16 > at device 29.0 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0x2020-0x203f irq 19 > at device 29.1 on pci0 > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0x2040-0x205f irq 18 > at device 29.2 on pci0 > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub2: 2 ports with 2 removable, self powered > uhci3: port 0x2060-0x207f irq 16 > at device 29.3 on pci0 > usb3: on uhci3 > usb3: USB revision 1.0 > uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub3: 2 ports with 2 removable, self powered > pci0: at device 29.7 (no driver attached) > pcib7: at device 30.0 on pci0 > pci1: on pcib7 > pci1: at device 3.0 (no driver attached) > pci1: at device 4.0 (no driver attached) > pci1: at device 4.2 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x500-0x50f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > acpi_tz0: on acpi0 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse Explorer, device ID 4 > sio0: port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > sio0: type 16550A > fdc0: port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 > fdc0: does not respond > device_attach: fdc0 attach returned 6 > fdc0: port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 > fdc0: does not respond > device_attach: fdc0 attach returned 6 > orm0: at iomem > 0xee000-0xe,0xc8000-0xcbfff,0xc-0xc7fff on isa0 > pmtimer0 on isa0 > ppc0: parallel port not found. > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtua
Re: Proliant 380 G4
Palle Girgensohn a écrit : Hi! Just a quick check - a client is getting a Proliant 380 G4 with a "6i" Raid controller. Haven't used this hardware before. Will it work fine with FreeBSD? Which version will work best, 5.4 or 4.11? Any peculiarities or things to think about? Any input appreciated! we have 3 Proliant 380 G4 and hardware works fine. For your information, I attach a dmesg of one of them. I've just another problem, but I don't think that it comes from hardware : http://lists.freebsd.org/pipermail/freebsd-stable/2005-June/015952.html Thanks Palle -- Philippe PEGON Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-STABLE #3: Thu May 19 20:35:36 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NS1A Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3600.15-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 2147430400 (2047 MB) avail memory = 2095968256 (1998 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard ioapic3 irqs 72-95 on motherboard ioapic4 irqs 96-119 on motherboard npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci2: on pcib1 pcib2: at device 0.0 on pci2 pci3: on pcib2 bge0: mem 0xfdef-0xfdef irq 25 at device 1.0 on pci3 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:12:79:d8:a0:37 bge1: mem 0xfdee-0xfdee irq 26 at device 1.1 on pci3 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:12:79:d8:a0:36 pcib3: at device 0.2 on pci2 pci4: on pcib3 ciss0: port 0x4000-0x40ff mem 0xfdf8-0xfdfb,0xfdff-0xfdff1fff irq 51 at device 3.0 on pci4 pcib4: at device 6.0 on pci0 pci5: on pcib4 pcib5: at device 0.0 on pci5 pci6: on pcib5 pcib6: at device 0.2 on pci5 pci10: on pcib6 uhci0: port 0x2000-0x201f irq 16 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x2020-0x203f irq 19 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x2040-0x205f irq 18 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x2060-0x207f irq 16 at device 29.3 on pci0 usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib7: at device 30.0 on pci0 pci1: on pcib7 pci1: at device 3.0 (no driver attached) pci1: at device 4.0 (no driver attached) pci1: at device 4.2 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x500-0x50f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 acpi_tz0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse Explorer, device ID 4 sio0: port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A fdc0: port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 fdc0: port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 orm0: at iomem 0xee000-0xe,0xc8000-0xcbfff,0xc-0xc7fff on isa0 pmtimer0 on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master PIO4 da0 at ciss0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 135.168MB/s transfers da0: 34727MB (71122560 512 byte sectors: 255H 32S/T 8716C) da1 at ciss0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-0 device da1: 135.168MB/s transfers da1: 69455MB (142245120 512 byte sectors: 255H 32S/T 17432C) SMP
FreeBSD 5.4 SMP kernels now available via FreeBSD Update
It sounds like the SMP kernel I provided for FreeBSD 5.3 was quite popular, so I've started building an SMP kernel for FreeBSD 5.4 as well, in addition to the usual GENERIC kernel. To take advantage of this on your FreeBSD 5.4 SMP system, run the following commands as root: # touch /boot/kernel/SMP # freebsd-update fetch # freebsd-update install # echo 'bootfile="SMP"' >> /boot/loader.conf and reboot. You should now find that `uname -ri` outputs "5.4-SECURITY SMP". Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 380 G4
Palle Girgensohn <[EMAIL PROTECTED]> wrote: > Just a quick check - a client is getting a Proliant 380 G4 with a "6i" Raid > controller. Haven't used this hardware before. Will it work fine with > FreeBSD? Which version will work best, 5.4 or 4.11? Any peculiarities or > things to think about? > > Any input appreciated! It's not supported under 4.x: pci2: (vendor=0x0e11, dev=0x0046) at 1.0 irq 5 At a customer of ours we're currently forced to run Linux on the newer Proliants because of that problem (FreeBSD 5.x is currently not an option for that customer). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "[...] one observation we can make here is that Python makes an excellent pseudocoding language, with the wonderful attribute that it can actually be executed." -- Bruce Eckel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proliant 380 G4
On Wed, Jun 15, 2005 at 06:03:31PM +0200, Palle Girgensohn wrote: > Hi! > > Just a quick check - a client is getting a Proliant 380 G4 with a "6i" Raid > controller. Haven't used this hardware before. Will it work fine with > FreeBSD? Which version will work best, 5.4 or 4.11? Any peculiarities or > things to think about? > The card is listed as supported in the ciss(4) manpage. - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgptFW9Fbb9bm.pgp Description: PGP signature
Re: Proliant 380 G4
On Wed, Jun 15, 2005 at 06:03:31PM +0200, Palle Girgensohn wrote: > Hi! > > Just a quick check - a client is getting a Proliant 380 G4 with a "6i" Raid > controller. Haven't used this hardware before. Will it work fine with > FreeBSD? Which version will work best, 5.4 or 4.11? Any peculiarities or > things to think about? > > Any input appreciated! > > Thanks > Palle I run 5.3-Release on my DL380g3 with a SmartArray 6402, which is basicly the same controller as the 6i (just not embedded, it is a PCI-X card). No problems whatsoever. -- Regards, Ulf. - Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 You can find my resume at: http://seven.Alameda.net/~ulf/resume.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Proliant 380 G4
Hi! Just a quick check - a client is getting a Proliant 380 G4 with a "6i" Raid controller. Haven't used this hardware before. Will it work fine with FreeBSD? Which version will work best, 5.4 or 4.11? Any peculiarities or things to think about? Any input appreciated! Thanks Palle ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS upgrading from 5.2.1->5.4
On 6/14/05, Mars G. Miro <[EMAIL PROTECTED]> wrote: > > If the build machine and install machine were at the same -RELEASE > > number, I don't believe you would have come across this problem. > > > I'm not sure I get you but the purpose of making the world in FreeBSD > is ought to be able to upgrade across releases (some people even > report upgrading from major releases, e.g 4.X to 5.X), albeit minor > hurdles (like the one I've experienced). > Normally this would work, when the build machine and the install machine are the same computer. But when you NFS mount the the built sources on another system it may or may not work. For example you wouldn't build the sources on a 5.x system and then NFS mount the built sources to a 4.x system. The reason is that the build system custom tailors the build tools for the 5.x system, and they will most likely not run on the 4.x system. Scot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New Server - To 5.x or Not To 5.x
> > I've been running FreeBSD 4.x for eons now, mainly because of the fact > that she's "known" in our environment ... UNIONFS isn't perfect, but all > of the obvious/major bugs have been worked out of her, etc ... but, she's > also a dead branch, so any outstanding bugs, nobody is interested in > fixing them, let alone having reported ... > > I'm just in the process of putting together a new server, and based on > some stuff I've heard recently concerning work that has been done on > UNIONFS, I'm tempted to put 5.x onto this new server, to start bringing my > servers into the 'current age' ... > > Is there anyone out there using 5-STABLE and UNIONFS that are happy with > it, or is it still very problematic? > > Again, the key thing right now for me is UNIONFS, so I'm looking mainly > for feedback from ppl that *are* using it, not just reading the end of the > man page ... > > Thanks ... im using it, even with 6.0. im using it for my diskless (about 90% of our freebsd), to mount /etc kldload unionfs mount_md 4096 /conf/etc chmod 755 /conf/etc mount_unionfs /conf/etc /etc ls -R /etc > /dev/null touch /etc/.sentinel md_created_etc=created and all is fine. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CARP and VLAN interfaces (5.4)
On Tue, Jun 14, 2005 at 10:40:50PM +0100, Paul Civati wrote: P> Philippe PEGON <[EMAIL PROTECTED]> wrote: P> P> > > Has anyone tested this? P> > P> > yes, it doesn't work, carp with vlan aren't supported on FreeBSD. There is P> > a thread about that on freebsd-pf : P> > P> > http://lists.freebsd.org/mailman/htdig/freebsd-pf/2005-May/001033.html P> P> Thanks for the pointer, the patch listed below fixes the problem. P> P> http://lists.freebsd.org/pipermail/freebsd-net/2005-April/006997.html P> P> Could someone commit this to -STABLE, or is it not the 'correct' fix? Yes. It's not really correct. A correct approach is already commited to HEAD. Unfortunately, I can't MFC this because of ABI policy for RELENG_5 branch. I would advice you to stay with the patch, since it works for you. I'd also encourage you to move to 6.0-RELEASE, when first release candidates will be coming out. I am going to use carp(4) over vlan(4) in 6.0-RELEASE in production, so I will be testing this functionality when we will enter release candidate phase of release cycle. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Which driver for Soekris lan1641?
"Constant, Benjamin" <[EMAIL PROTECTED]> writes: > Is there a path to follow to request an update of the man page? man send-pr PR should be in category docs and class change-request, and ideally with a patch correcting sis(4) manpage attached. Éric Masson -- Salut, Je ne reçoit plus de messages de la mailing-list des nordistes. -+- SG in: GNU - Un ch'ti coup d'fufe pour la route ? -+- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Which driver for Soekris lan1641?
On Wednesday 15 June 2005 13:40, Constant, Benjamin wrote: > Thanks to all for the details... > > Soekris lan1641 is using chipset National Semicondutor DP83816 which > is not referenced in sis(4), that's why I was a bit confused. > > Is there a path to follow to request an update of the man page? send-pr(1). > Benjamin Constant > TI Automotive > > > -Original Message- > > From: Eric Masson [mailto:[EMAIL PROTECTED] > > Sent: mercredi 15 juin 2005 14:20 > > To: Constant, Benjamin > > Cc: freebsd-stable@freebsd.org > > Subject: Re: Which driver for Soekris lan1641? > > > > "Constant, Benjamin" <[EMAIL PROTECTED]> writes: > > > > Hi, > > > > > Ethernet chipset is National Semicondutor DP83816 but I > > > > can't find any > > > > > reference to it in the hardware notes for 5.4. I need to > > > > know if ALTQ > > > > > is available for this card. > > > > man 4 sis > > man 4 altq > > > > Éric Masson > > > > -- > > D'accord, mais si on se met à utiliser des arguments > > intelligents dans ce genre de débat, il devient impossible > > de discuter. > > Vous sombrez dans la facilité. > > -+- TS in GNU : La dialectique n'est plus ce qu'elle était. > > The information contained in this transmission may contain privileged > and confidential information. It is intended only for the use of the > person(s) named above. If you are not the intended recipient, you are > hereby notified that any review, dissemination, distribution or > duplication of this communication is strictly prohibited. If you are > not the intended recipient, please contact the sender by reply email > and destroy all copies of the original message. This communication is > from TI Automotive. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Which driver for Soekris lan1641?
Thanks to all for the details... Soekris lan1641 is using chipset National Semicondutor DP83816 which is not referenced in sis(4), that's why I was a bit confused. Is there a path to follow to request an update of the man page? Benjamin Constant TI Automotive > -Original Message- > From: Eric Masson [mailto:[EMAIL PROTECTED] > Sent: mercredi 15 juin 2005 14:20 > To: Constant, Benjamin > Cc: freebsd-stable@freebsd.org > Subject: Re: Which driver for Soekris lan1641? > > "Constant, Benjamin" <[EMAIL PROTECTED]> writes: > > Hi, > > > Ethernet chipset is National Semicondutor DP83816 but I > can't find any > > reference to it in the hardware notes for 5.4. I need to > know if ALTQ > > is available for this card. > > man 4 sis > man 4 altq > > Éric Masson > > -- > D'accord, mais si on se met à utiliser des arguments > intelligents dans ce genre de débat, il devient impossible > de discuter. > Vous sombrez dans la facilité. > -+- TS in GNU : La dialectique n'est plus ce qu'elle était. > The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. This communication is from TI Automotive. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.4 RC2 freezing
On Wed, Jun 08, 2005 at 09:08:11AM -0400, Matt Smith wrote: > pflog0: promiscuous mode enabled > > Do you want to be running this way? > This is normal operating mode for the pflog pseudo-interface. The function of the pflog pseudo interface is to collect packets which the "pf" packet filter dropped and log their contents for replay. If pflog is not in promiscuous mode it cannot catch these packets. -- chris -- Chris Hilton chris-at-vindaloo-dot-com "All I was doing was trying to get home from work!" -- Rosa Parks pgp5KhbCEeDmZ.pgp Description: PGP signature
Re: Which driver for Soekris lan1641?
"Constant, Benjamin" <[EMAIL PROTECTED]> writes: Hi, > Ethernet chipset is National Semicondutor DP83816 but I can't find any > reference to it in the hardware notes for 5.4. I need to know if ALTQ > is available for this card. man 4 sis man 4 altq Éric Masson -- D'accord, mais si on se met à utiliser des arguments intelligents dans ce genre de débat, il devient impossible de discuter. Vous sombrez dans la facilité. -+- TS in GNU : La dialectique n'est plus ce qu'elle était. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Which driver for Soekris lan1641?
On Wednesday 15 June 2005 13:57, Constant, Benjamin wrote: > Hello list, > > Does someone knows which driver is used for the Soekris lan1641 quad > ethernet card? > Ethernet chipset is National Semicondutor DP83816 but I can't find any > reference to > it in the hardware notes for 5.4. I need to know if ALTQ is available for > this card. As others have pointed out: sis(4) As for ALTQ: Yes, a pair of Soekris (4501 and 4801) were my main testbed for porting ALTQ - so I am pretty sure those chips work okay ;) > Thanks in advance! -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgpyIgA0NRzpC.pgp Description: PGP signature
Re: LOR: "ata state lock" and "user map"
on 09.06.2005 09:15 Andriy Gapon said the following: > > NOTE: CURRENT was run under qemu emulation, CDROM was emulated from iso > image on HDD. > > Got this LOR today with CURRENT built 3 days ago while trying to execute > a linux program located on a CD. Several days ago trying to do the same > on 5.4-RELEASE (without any debug options in kernel) on real hardware > caused a hardlock. > > System: > 6.0-CURRENT i386 > debug.mpsafevm=1 > > LOR message had this information: > 1st 0xc0eb44e8 ATA state lock ata-all.c:297 > 2nd 0xc0c1f344 user map vm_map.c:2997 > > Sources: > ata-all.c 1.252 > /vm_map.c 1.366 > > Interesting part of stack trace (not sure how useful it is): > #18 0x000c in ?? () > #19 0x0002 in ?? () > #20 0xc0455a15 in ata_pio_read (request=0xc107b0c8, length=2048) > at cpufunc.h:229 > #21 0xc045646c in ata_end_transaction (request=0xc107b0c8) > at /usr/src/sys/dev/ata/ata-lowlevel.c:393 > #22 0xc0447659 in ata_interrupt (data=0xc0eb4400) > at /usr/src/sys/dev/ata/ata-all.c:323 > #23 0xc04b5360 in ithread_loop (arg=0xc0eb9600) > at /usr/src/sys/kern/kern_intr.c:546 > #24 0xc04b46fd in fork_exit (callout=0xc04b51bc , > arg=0xc0eb9600, frame=0xc7b41d38) at /usr/src/sys/kern/kern_fork.c:789 > #25 0xc05df18c in fork_trampoline () at > /usr/src/sys/i386/i386/exception.s:208 > > Please let me know what additional information I can provide. > additional details - the problem is 100% percent reproducible with linux applications but is 0% producible with native applications. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Which driver for Soekris lan1641?
Constant, Benjamin wrote: Hello list, Does someone knows which driver is used for the Soekris lan1641 quad ethernet card? Ethernet chipset is National Semicondutor DP83816 but I can't find any reference to it in the hardware notes for 5.4. I need to know if ALTQ is available for this card. The DP83816 chip is handled by sis(4). /thn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Which driver for Soekris lan1641?
On 2005.06.15 13:57:10 +0200, Constant, Benjamin wrote: > Does someone knows which driver is used for the Soekris lan1641 quad > ethernet card? > Ethernet chipset is National Semicondutor DP83816 but I can't find > any reference to it in the hardware notes for 5.4. It's sis(4). > I need to know if ALTQ is available for > this card. It should be, though I haven't tested it. See http://www.freebsd.org/cgi/man.cgi?query=altq&manpath=FreeBSD+5.4-RELEASE -- Simon L. Nielsen pgp3wtmvq0KBq.pgp Description: PGP signature
Which driver for Soekris lan1641?
Hello list, Does someone knows which driver is used for the Soekris lan1641 quad ethernet card? Ethernet chipset is National Semicondutor DP83816 but I can't find any reference to it in the hardware notes for 5.4. I need to know if ALTQ is available for this card. Thanks in advance! Benjamin Constant TI Automotive The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. This communication is from TI Automotive. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CARP and VLAN interfaces (5.4)
Paul Civati a écrit : Philippe PEGON <[EMAIL PROTECTED]> wrote: I also tested it with em card and for me it only runs if I connect the network card after the boot, otherwise I have the INIT symptom on carp's interfaces. Did the patch apply cleanly? no I applied it to 5.4-REL sources, part of the code was already in there so I added the missing bits manually. Seems to work fine in my initial testing. I also added the missing bits manually, maybe I did a mistake... Actually I cannot test anymore, the firewall runs OpenBSD. -Paul- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Philippe PEGON ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/local/etc/rc.d/*.sh not working?
Hi, i have follows your trouble with rc-scripts. now im usind BSD for many years and i know! that *sh-ish rc-scripts should be supported. But this is not my interest. you have writte that the boxes with these behavior was updated from RELENG_4 to RELENG_5? right? if so double-check all these thinks you are doit to update reread the migration-guide and diff the rc-scripts and the binaries. my suggestion is somthing was going wrong with the update.. if the restly enviroment was leaved (profiles etc...) regards michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
