Re: Strange networking problems after update 5.2.1-5.3
On Tue, 4 Jan 2005 06:30:26 +1100 Peter Jeremy [EMAIL PROTECTED] wrote about Re: Strange networking problems after update 5.2.1-5.3: PJ ed0: flags=108843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 PJinet 130.75.117.37 netmask 0x broadcast 130.75.255.255 PJether 01:d4:ff:03:00:20 PJ That's a multicast MAC address (the LSB of the first byte is 1). More Ok, I didn't know about this. Can you recommend any online resource where those special things are documented? PJ intelligent NICs will have an internal list of multicast MAC addresses PJ that they have been programmed to respond to and will ignore all other PJ multicast addresses (for dumber NICs, this checking should be in the PJ driver). This would explain the peculiar behaviour you are seeing. For sure. PJ Firstly, I presume you're not attempting to change the MAC address. Correct, I even don't know how to do this. ;-) PJ Secondly, the MAC address should be reported as part of the ed0 probe PJ message - can you have a look back through your messages file and PJ report the ed0 probe messages for both 5.2.1 and 5.3. Ok, 5.2.1 reported the following Dec 28 10:15:05 lonestar kernel: ed1: Dual Speed 10/100 Port Attached PC Card at port 0x100-0x11f irq 11 function 0 config 16 on pccard1 Dec 28 10:15:05 lonestar kernel: ed1: address 00:e0:98:a2:a7:33, type Linksys (16 bit) Dec 28 10:15:05 lonestar kernel: miibus0: MII bus on ed1 With 5.3 it says Dec 29 15:48:15 lonestar kernel: ed1: Dual Speed 10/100 Port Attached PC Card at port 0x100-0x11f irq 11 function 0 config 16 on pccard1 Dec 29 15:48:15 lonestar kernel: ed1: [GIANT-LOCKED] Dec 29 15:48:15 lonestar kernel: ed1: Ethernet address: 01:d4:ff:03:00:20 Dec 29 15:48:15 lonestar kernel: ed1: if_start running deferred for Giant Dec 29 15:48:15 lonestar kernel: type NE2000 (16 bit) I admit that I've got no clue where this new MAC is coming from. :) cu Gerrit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
fsck: broken file system with background check remains broken after bootup
Hi, I had following situation: Someone suddenly cut the power of a FreeBSD 5.3 PC, leaving the /usr filesystem in a very broken state. During next bootup, there was indeed the message telling 'not properly unmounted', but boot continued with background fsck after 60 seconds; although I have fsck_y_enable=YES in /etc/rc.conf. Because /usr was bad, the system hang immediately after bootup. I had to hit the power button (grump) to get a rebootcausing possibly more problems. I fixed it, by going into single user mode and do a manual fsck on all the filesystems. This way /usr got fixed and the system rebooted fine. This scared me. What if /usr was such broken that even single user mode would hang!?! Moreover, the main user of this PC is not a Unix guru and I hoped that the configuration setting in /etc/rc.conf of fsck_y_enable would do an automatic fix at bootup, like it used to do with 4.10. However, that apparently does not happen anymore. What can I do to enforce an immediate fix of the filesystems at bootup with FreeBSD 5.3, when a filesystem is not properly unmounted at shutdown? I suppose I should not change default background_fsck (YES). How about the background_fsck_delay? Should I set this to 0? Thanks, Rob. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
* Rob [EMAIL PROTECTED] [0123 10:23]: This scared me. What if /usr was such broken that even single user mode would hang!?! That won't happen, since /usr isn't mounted in single user mode. -- 'common sense is what tells you that the world is flat.' -- Principia Discordia Rasputin :: Jack of All Trades - Master of Nuns ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange networking problems after update 5.2.1-5.3
In message: [EMAIL PROTECTED] Robert Watson [EMAIL PROTECTED] writes: : I've CC'd Warner Losh on the general principle that if it's a problem with : a PCCARD ethernet adapter, he might be able to help (perhaps especially if : it's possible to ship him one of the cards). I think that I have one of the cards locally... Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange networking problems after update 5.2.1-5.3
In message: [EMAIL PROTECTED] Gerrit Kühn [EMAIL PROTECTED] writes: : Meanwhile I tried two further pcmcia cards which are 32bit (cardbus). Both : (Xircom CBE2-100 and D-Link DFE-690-TXD) result in : : cbb0: CardBus card activation failed : : It seems it's rather the pcmcia bridge that's broken than the driver for : the card itself. The notebook has a TI 1225 chip. The ed card issue is an ed driver. The TI 1225 chipset works fine in other systems, so it must be a resource issue with that specific machine. The 1225 is found typically in non-acpi machines, which have some known issues wrt memory allocation. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange networking problems after update 5.2.1-5.3
In message: [EMAIL PROTECTED] Gerrit Kühn [EMAIL PROTECTED] writes: : I will do so if it's the support for the cards that is broken. However, I : have tried 4 different cards now, and only one of them worked. So I'm : tending to put the blame on the pcmcia bridge and it's driver. Blame doesn't belong there, but elsewhere in the system. The second ed card is broken in the ed driver (people with other bridges have reported problems), while the cardbus activation issue almost certainly is a resource issue (because other people with TI-1225 bridge work). I'll be happy to help you track down that issue, however. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
problems with devfs amd /dev/fd/
Hi, trying to import foomatic-rip, I found great changes under /dev/fd/ going from RELENG_4 to RELENG_5. Seems that /dev/fd/3 is used by several pipe construct like foomatic-rip to get a free backwards error channel. Digging a bit, I found that now, I need mount fdescfs to get this. I think this is not well documented in release notes. Also, seems that support /dev/fd/3 in devfs may be a good idea. Add a sysctl to control how many /dev/fd/n devfs create will be even better. -- josemi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 4 Jan 2005 10:26:27 +, Dick Davies [EMAIL PROTECTED] wrote: That won't happen, since /usr isn't mounted in single user mode. Even if it were, there are always Live BSD CDROMs which should allow you to boot and then fsck your disk partitions. - -- G. Stewart - [EMAIL PROTECTED] The only person to get all of his work done by Friday was Robinson Crusoe -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB2nIXK5oiGLo9AcYRAremAJ4y79SBTaD47wUHIu7Q77zQ2u3htwCghB/m s59RUGwBo+b04fzZOiR8N54= =2/DX -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange networking problems after update 5.2.1-5.3
On Tue, 04 Jan 2005 03:36:53 -0700 (MST) M. Warner Losh [EMAIL PROTECTED] wrote about Re: Strange networking problems after update 5.2.1-5.3: MWL : I will do so if it's the support for the cards that is broken. MWL However, I : have tried 4 different cards now, and only one of them MWL worked. So I'm : tending to put the blame on the pcmcia bridge and MWL it's driver. MWL Blame doesn't belong there, but elsewhere in the system. The second MWL ed card is broken in the ed driver (people with other bridges have MWL reported problems), while the cardbus activation issue almost MWL certainly is a resource issue (because other people with TI-1225 MWL bridge work). I'll be happy to help you track down that issue, MWL however. Thank you very much in advance. Please tell me which information you need. cu Gerrit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BTX halted
Hi! On Tue, Jan 04, 2005 at 02:23:33AM -0500, kalin mintchev wrote: this is a few days old. i got a reply saying to try floppies but from the INSTALL.txt under the amd64/5.3-REL it says: 1.3 Floppy Disk Image Instructions Floppy disk based install is not supported on FreeBSD/amd64. like i said i played with bios settings and nothing really worked. can somebody help? thanks.. hi all... i'm trying to install 5.3 on an amd machine... i got the discs and they are ok but when i start the off the disk the boot stops with BTX halted no matter which boot mode i chose. i looked on google and i found a few posts about bios issues but non of that helped - i couldn't find how to disable DMA. the only location i saw the DMA mentioned was under PnP/PCI configurations = Resources Controlled by in the bios but there the setting is Auto(ESCD). i tried al the options there and it still stops at the same place... anybody can help?! thanks In similar circumstances (but with FreeBSD/i386) I succeeded by installing one of the previous releases and upgrading by sources. WBR -- bsam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
Godwin Stewart wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 4 Jan 2005 10:26:27 +, Dick Davies [EMAIL PROTECTED] wrote: That won't happen, since /usr isn't mounted in single user mode. Even if it were, there are always Live BSD CDROMs which should allow you to boot and then fsck your disk partitions. Thanks for your replies, but apparently I didn't make my point clearly. Let me try again: If the system ends with a bad filesystem, the background check may leave the system unusable after bootup. For a FreeBSD guru this is indeed easy to fix (single user mode, rescue floppies, live CDs bootup etc.). However, the main user of this particular PC is not at all a guru; on 4.10 I had rc.conf configured such that at bootup all filesystems would be automatically fixed with: fsck_y_enable=YES. With 4.10, this always worked nicely, whatever sudden power cut have happened. However, with 5.3, a recent powercut crippled the /usr filesystem such that X11 hanged. The user of this PC was convinced that FreeBSD was infected by a virus :(. An automatic fsck could have fixed the system (I eventually did it manually in single user mode), but the background check left the system broken. So I want to configure 5.3 similar to former 4.10: a full automatic fix of all filesystems at bootup, in case the system was not properly shutdown. How can I do that? Thanks, Rob. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange networking problems after update 5.2.1-5.3
On Tue, 2005-Jan-04 10:17:01 +0100, Gerrit Kühn wrote: PJ ed0: flags=108843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 PJ inet 130.75.117.37 netmask 0x broadcast 130.75.255.255 PJ ether 01:d4:ff:03:00:20 PJ That's a multicast MAC address (the LSB of the first byte is 1). More Ok, I didn't know about this. Can you recommend any online resource where those special things are documented? The definitive source is the IEEE 802.3 specifications which are available (free) from http://standards.ieee.org/getieee802/802.3.html If you're not trying to cure a bad case of insomnia, there are probably better overviews on the WEB but I can't quickly find them. PJ intelligent NICs will have an internal list of multicast MAC addresses PJ that they have been programmed to respond to and will ignore all other PJ multicast addresses (for dumber NICs, this checking should be in the PJ driver). This would explain the peculiar behaviour you are seeing. Upon reflection, my comments are wrong - the receiving NICs will be looking for (and typically ignoring) destination multicast frames. In your case, the source may[*] be multicast (though the response frames would be multicast). A more likely problem is that ARP packets generated by your system have the MAC address seen by the driver (as above) whereas the card is physically using it's correct address (as reported by 5.2.1) - and therefore remote systems will normally see the wrong address. You could confirm this by checking the ARP tables on some remote hosts within the same LAN and/or looking at tcpdump -es of some ARP packets. Ok, 5.2.1 reported the following Dec 28 10:15:05 lonestar kernel: ed1: address 00:e0:98:a2:a7:33, type Linksys (16 bit) This address looks sane. Dec 29 15:48:15 lonestar kernel: ed1: Ethernet address: 01:d4:ff:03:00:20 This address doesn't. Something in the driver is reading the wrong address. Off hand, I can't narrow it down right now. Unless someone recognizes the symptoms, you might need to look at the commits to the pccard and/or ed drivers between 5.2.1 and 5.3. [*] It's not clear whether the MAC address reported by ifconfig is actually the transmitted source MAC address. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Old version of bison
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ports cvsup'ed yesterday,
$ cat /usr/ports/devel/bison/Makefile
{snip}
PORTNAME= bison
PORTVERSION=1.75
PORTREVISION= 2
{snip}
Is there any particular reason why ports are sticking with this version when
1.875 was released 2 years ago almost to the day?
- --
G. Stewart - [EMAIL PROTECTED]
Always the dullness of the fool is the whetstone of the wits.
-- William Shakespeare, As You Like It
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (FreeBSD)
iD8DBQFB2n2kK5oiGLo9AcYRAvP1AJ94si7rV5CgrmHyudIprYhnHBNyMQCeN5SI
C62CGyfi6Fvg+xrZeuiihyM=
=C/hS
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
Hi! On Tue, Jan 04, 2005 at 08:25:20PM +0900, Rob wrote: So I want to configure 5.3 similar to former 4.10: a full automatic fix of all filesystems at bootup, in case the system was not properly shutdown. How can I do that? You already mention it -- backgroung_fsck=NO at /etc/rc.conf.local. Thanks, Rob. WBR -- bsam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
On Tue, Jan 04, 2005 at 08:25:20PM +0900, Rob wrote: An automatic fsck could have fixed the system (I eventually did it manually in single user mode), but the background check left the system broken. So I want to configure 5.3 similar to former 4.10: a full automatic fix of all filesystems at bootup, in case the system was not properly shutdown. How can I do that? Turn off background_fsck. Ceri -- Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-- Einstein (attrib.) pgpTKNUJOmsuS.pgp Description: PGP signature
Re: Old version of bison
On Tuesday 04 January 2005 03:27 am, Godwin Stewart wrote:
Ports cvsup'ed yesterday,
$ cat /usr/ports/devel/bison/Makefile
{snip}
PORTNAME= bison
PORTVERSION=1.75
PORTREVISION= 2
{snip}
Is there any particular reason why ports are sticking with this
version when 1.875 was released 2 years ago almost to the day?
If you have an uptodate port system you will find
Port: bison-1.875_4
Path: /usr/ports/devel/bison1875
Kent
--
Kent Stewart
Richland, WA
http://users.owt.com/kstewart/index.html
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
Ceri Davies wrote: On Tue, Jan 04, 2005 at 08:25:20PM +0900, Rob wrote: An automatic fsck could have fixed the system (I eventually did it manually in single user mode), but the background check left the system broken. So I want to configure 5.3 similar to former 4.10: a full automatic fix of all filesystems at bootup, in case the system was not properly shutdown. How can I do that? Turn off background_fsck. Thanks. Rob. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Old version of bison
Godwin Stewart wrote: Is there any particular reason why ports are sticking with this version when 1.875 was released 2 years ago almost to the day? From the first commit comment of devel/bison1875: Some grammars require the new version of Bison (such as PostgreSQL), however the new bison also breaks many many ports. Compromise with a new port. Installs as bison and _not_ bison1875 and should be mutually exclusive to the main bison port. Hopefully the bison authors will clean up their product and this port can disappear when the base bison port is updated in the future or enough ports are updated to work with newer versions of bison. http://www.freshports.org/devel/bison1875/ Regards Bjrn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: burncd freeze system
On Tue, 2005-01-04 at 18:10 +1100, Peter Jeremy wrote: On Tue, 2005-Jan-04 00:20:59 +0100, Norbert Augenstein wrote: i have tried to burn an iso of 26MB of size, and my system locks up so i have to reboot. /var/log/messages is unlikely to include the last 30 seconds or so of logging following a crash. Try running burncd from the console and see if there are any messages. Also, you might like to expand on locks up. Can you ping the system from another host? Switch VTYs? If you have DDB enabled, can you enter it? As i can burn it in Win, i am out of ideas. I presume this is Winbloze on the same host (dual-boot). I saw something similar with fixate a couple of days ago: http://lists.freebsd.org/pipermail/freebsd-stable/2005-January/010776.html -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Old version of bison
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 4 Jan 2005 03:55:42 -0800, Kent Stewart [EMAIL PROTECTED] wrote: If you have an uptodate port system you will find Port: bison-1.875_4 Path: /usr/ports/devel/bison1875 Indeed. That'll teach me to hit [tab] twice after typing /usr/ports/devel/bison Thanks. - -- G. Stewart - [EMAIL PROTECTED] QUARK: The sound made by a well-bred duck: -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB2ohlK5oiGLo9AcYRAvn+AKCnX5a9qhC7ywR0KEwGZ3KwIzOPdQCfRH3n s6Uh0PYkD0QrfFmHjR4ZCVU= =2EKn -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
Rob [EMAIL PROTECTED] writes: I had following situation: Someone suddenly cut the power of a FreeBSD 5.3 PC, leaving the /usr filesystem in a very broken state. During next bootup, there was indeed the message telling 'not properly unmounted', but boot continued with background fsck after 60 seconds; although I have fsck_y_enable=YES in /etc/rc.conf. That is the one that may cause problems. The default fsck settings are conservative so as to only make safe changes. fsck -y also makes more radical changes to your file system. OTOH, I am not convinced that fsck (particularly bgfsck) is bug-free, I have seen file system corruption on a FreeBSD 4.10 system that went with the write caches disabled. This scared me. What if /usr was such broken that even single user mode would hang!?! Don't worry as long as /usr is separate from /. Moreover, the main user of this PC is not a Unix guru and I hoped that the configuration setting in /etc/rc.conf of fsck_y_enable would do an automatic fix at bootup, like it used to do with 4.10. However, that apparently does not happen anymore. What can I do to enforce an immediate fix of the filesystems at bootup with FreeBSD 5.3, when a filesystem is not properly unmounted at shutdown? I suppose I should not change default background_fsck (YES). How about the background_fsck_delay? Should I set this to 0? Setting background_fsck=NO should be safe and cause the fsck to run in foreground - exactly your desire. I would avoid touching the background_fsck_delay. If, as you say, the main user of the PC is not a guru and shuts down the machine improperly, consider disabling the write cache. For ATA drives, place hw.ata.wc=0 into /etc/loader.conf.local and reboot, for SCSI drives, use camcontrol modepage da0 -m8 -e -P3 and change the figure on the WCE: line to 0, then save and exit; repeat for all further da* drives if you have more than one. That will limit the potential damage on the disk to one block rather than the whole of the cache, which is between 2 and 8 MB on the common drives sold today. -- Matthias Andree ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
Rob [EMAIL PROTECTED] wrote: [...] However, the main user of this particular PC is not at all a guru; on 4.10 I had rc.conf configured such that at bootup all filesystems would be automatically fixed with: fsck_y_enable=YES. With 4.10, this always worked nicely, whatever sudden power cut have happened. However, with 5.3, a recent powercut crippled the /usr filesystem such that X11 hanged. The user of this PC was convinced that FreeBSD was infected by a virus :(. I would strongly advise you to teach that user to properly shut down the machine instead of just pressing the power button, thus eliminating the real cause of the problem. (If you're suffering from frequent power outages, then a UPS should be installed.) By the way, you can map a key combination (Ctrl-Alt-Del or something else) to the »halt« or »power-down« functions, using kbdcontrol, so it's very easy and intuitive to shut down the machine properly. See the kbdmap(5) manpage for details. Apart from that, I suggest you simply disable background fsck. 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. We're sysadmins. To us, data is a protocol-overhead. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Old version of bison
On Tuesday 04 January 2005 04:13 am, Godwin Stewart wrote: On Tue, 4 Jan 2005 03:55:42 -0800, Kent Stewart [EMAIL PROTECTED] wrote: If you have an uptodate port system you will find Port: bison-1.875_4 Path: /usr/ports/devel/bison1875 Indeed. That'll teach me to hit [tab] twice after typing /usr/ports/devel/bison What I find handy is a perl script called portsearch. It is located in ports/Tools/scripts/ I moved it into a directory in my path. Then, I added an alias search'portsearch -n $1' You can do interesting things like search ^bison Where the port name begins with bison. There are a number of other interesting options. They are covered in a README. Make search does something similar but the output from portsearch is cleaner. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
Matthias Andree [EMAIL PROTECTED] writes: OTOH, I am not convinced that fsck (particularly bgfsck) is bug-free, I Make that fsck and ufs are bug-free... -- Matthias Andree ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
test
test ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: test
On Tue, 04 Jan 2005 16:41:35 +0200, podenok wrote test Please send these kind of e-mails to [EMAIL PROTECTED] There you can do all the testing you want :) Jorn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange networking problems after update 5.2.1-5.3
In message: [EMAIL PROTECTED] Gerrit Kühn [EMAIL PROTECTED] writes: : On Tue, 04 Jan 2005 03:36:53 -0700 (MST) M. Warner Losh [EMAIL PROTECTED] : wrote about Re: Strange networking problems after update 5.2.1-5.3: : : : MWL : I will do so if it's the support for the cards that is broken. : MWL However, I : have tried 4 different cards now, and only one of them : MWL worked. So I'm : tending to put the blame on the pcmcia bridge and : MWL it's driver. : : MWL Blame doesn't belong there, but elsewhere in the system. The second : MWL ed card is broken in the ed driver (people with other bridges have : MWL reported problems), while the cardbus activation issue almost : MWL certainly is a resource issue (because other people with TI-1225 : MWL bridge work). I'll be happy to help you track down that issue, : MWL however. : : Thank you very much in advance. : Please tell me which information you need. You've likely already sent this before... But can you send a full dmesg with hw.cbb.debug=1 and hw.cardbus.debug=1 (these are set in /boot/loader.conf) and a devinfo -r. I have a handle on the ed card showing up as NE-1000. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
On January 4, 2005 03:25 am, Rob wrote: Thanks for your replies, but apparently I didn't make my point clearly. Let me try again: If the system ends with a bad filesystem, the background check may leave the system unusable after bootup. For a FreeBSD guru this is indeed easy to fix (single user mode, rescue floppies, live CDs bootup etc.). However, the main user of this particular PC is not at all a guru; on 4.10 I had rc.conf configured such that at bootup all filesystems would be automatically fixed with: fsck_y_enable=YES. With 4.10, this always worked nicely, whatever sudden power cut have happened. However, with 5.3, a recent powercut crippled the /usr filesystem such that X11 hanged. The user of this PC was convinced that FreeBSD was infected by a virus :(. An automatic fsck could have fixed the system (I eventually did it manually in single user mode), but the background check left the system broken. So I want to configure 5.3 similar to former 4.10: a full automatic fix of all filesystems at bootup, in case the system was not properly shutdown. How can I do that? As with FreeBSD 4.x, all rc.conf options are listed in /etc/defaults/rc.conf. Read /etc/defaults/rc.conf and put the appropriate fsck options into /etc/rc.conf. What you want to do is disable background fsck, giving you the same behaviour as with 4.x, -- Freddie Cash, CCNT CCLPHelpdesk / Network Support Tech. School District 73 (250) 377-HELP [377-4357] [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange networking problems after update 5.2.1-5.3
On Tue, 04 Jan 2005 09:27:34 -0700 (MST) M. Warner Losh [EMAIL PROTECTED] wrote about Re: Strange networking problems after update 5.2.1-5.3: MWL : Please tell me which information you need. MWL You've likely already sent this before... But can you send a full MWL dmesg with hw.cbb.debug=1 and hw.cardbus.debug=1 (these are set in MWL /boot/loader.conf) and a devinfo -r. I'm taking this into private mail, or are there others being interested in this information? cu Gerrit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
MFC of src/bin/rmdir/rmdir.c
We are starting to migrate stuff to FreeBSD 5 and one of my shell scripts broke because rmdir -p doesn't work in 5.3. It would be really nice to have the fix from CURRENT merged to RELENG_5 and possibly even RELENG_5_3 if possible. Thanks. -- Christian Laursen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MFC of src/bin/rmdir/rmdir.c
Am 04.01.2005 um 19:34 schrieb Christian Laursen: We are starting to migrate stuff to FreeBSD 5 and one of my shell scripts broke because rmdir -p doesn't work in 5.3. It would be really nice to have the fix from CURRENT merged to RELENG_5 and possibly even RELENG_5_3 if possible. Appending /. to the path seems to work for me: $ find . . $ mkdir -p foo/bar/baz $ rmdir -p foo/bar/baz rmdir: foo/bar: Directory not empty $ find . . ./foo ./foo/bar ./foo/bar/baz $ rmdir -p foo/bar/baz/. $ find . . Stefan -- Stefan Bethke [EMAIL PROTECTED] Fon +49 170 346 0140 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPNAT IPv6
Hi, As far as I have tested pf(packet filter) on FreeBSD 5.3R, NAT function with IPv6 does not work well. Log says conversion is done. But source address is not translated. Though I asked about it in freebsd-pf mailing list, we have not had any reponses yet. Regard, Hideki Yamamoto From: Song Du [EMAIL PROTECTED] Subject: Re: IPNAT IPv6 Date: Mon, 3 Jan 2005 17:40:28 +0800 Message-ID: [EMAIL PROTECTED] but i want to do the data redirection transparently :( On Mon, 3 Jan 2005 09:25:11 +0100 (CET), Patrick M. Hausen [EMAIL PROTECTED] wrote: Hello! my original ipnat rule is rdr rl0 0.0.0.0/0 port 80 - 127.0.0.1 port 8000 tcp which redirect a priv port to a non-priv port but when i setup dual stack, i find it's unable to handle ipv6 connections. when i change 0.0.0.0 to ::0, ipnat complains it can't resolve it. even when i use domains instead of numeric format, still no help. so it seems that ipnat doesn't work with ipv6? any solution? Don't know if ipnat works with IPv6 or if ipfw/natd would do better, but you can always use netcat (/usr/ports/net/netcat) and inetd for incoming connections on a NAT gateway. HTH, Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de -- freewizard (at) gmail.com http://blog.tsing.org/freewizard/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
downgrading ports
Hi, I just upgraded to perl 5.6 using perl5 port. However some of my scripts are not working due to compatibility problems. How do I revert back to the system (base) version of perl that comes with 4.10. Tejas Kokje ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPNAT IPv6
On Wed, Jan 05, 2005 at 05:28:19AM +0900, Hideki Yamamoto wrote: As far as I have tested pf(packet filter) on FreeBSD 5.3R, NAT function with IPv6 does not work well. Log says conversion is done. But source address is not translated. Though I asked about it in freebsd-pf mailing list, we have not had any reponses yet. I don't think any of our packet filters really support IPv6 NAT at this point. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpIMScaGKnAO.pgp Description: PGP signature
Re: downgrading ports
Tejas Kokje wrote: Hi, I just upgraded to perl 5.6 using perl5 port. However some of my scripts are not working due to compatibility problems. How do I revert back to the system (base) version of perl that comes with 4.10. I think what you're looking for is /usr/local/bin/use.perl system Tejas Kokje Regards, RJ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: downgrading ports
Tejas Kokje wrote: Hi, I just upgraded to perl 5.6 using perl5 port. However some of my scripts are not working due to compatibility problems. How do I revert back to the system (base) version of perl that comes with 4.10. Tejas Kokje 1. Deinstall the perl 5.6 port 2. Type the command use.perl system Richard Coleman [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: downgrading ports
Richard Coleman wrote: Tejas Kokje wrote: Hi, I just upgraded to perl 5.6 using perl5 port. However some of my scripts are not working due to compatibility problems. How do I revert back to the system (base) version of perl that comes with 4.10. Tejas Kokje 1. Deinstall the perl 5.6 port 2. Type the command use.perl system Richard Coleman [EMAIL PROTECTED] Oops. My mistake. Reverse the order of these steps, since deinstalling the perl port will deinstall the use.perl command. Richard Coleman [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: downgrading ports
Hello, On Tue, Jan 04, 2005 at 12:32:32PM -0800 or thereabouts, Tejas Kokje wrote: I just upgraded to perl 5.6 using perl5 port. However some of my scripts are not working due to compatibility problems. How do I revert back to the system (base) version of perl that comes with 4.10. What kind of compatibility problems did you run into? Missing modules? Or? I think it was Matthew Seaman, who posted here nice guide of upgrading existing perl modules to be usable with new (port) version of perl. I will look into it... ah here it is: http://lists.freebsd.org/pipermail/freebsd-questions/2004-April/043400.html Also Kent Stewart (in reply to Matthew's posting) has mentioned that one has to upgrade also automake due to its need for perl. Anyway there is a command to revert to previous (system) version of perl. Just type use.perl system and you are good to go. Cheers, Martin -- martin hudec * 421 907 303 393 * [EMAIL PROTECTED] * http://www.aeternal.net Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws. Douglas Adams, The Hitchhiker's Guide to the Galaxy pgpJP9z2eFW77.pgp Description: PGP signature
Re: Old version of bison
On Tue, Jan 04, 2005 at 12:27:32PM +0100, Godwin Stewart wrote:
Ports cvsup'ed yesterday,
$ cat /usr/ports/devel/bison/Makefile
{snip}
PORTNAME= bison
PORTVERSION=1.75
PORTREVISION= 2
{snip}
Is there any particular reason why ports are sticking with this version when
1.875 was released 2 years ago almost to the day?
Yes, the bison developers apparently don't understand why a
widely-used build tool should need to remain backwards-compatible with
itself (see also: autoconf, automake developers).
Kris
pgpYhZH5kinPh.pgp
Description: PGP signature
Re: dump dumping core
In message [EMAIL PROTECTED], Mark Knight [EMAIL PROTECTED] writes With RELENG_5 from yesterday, as well from a week or so ago I'm finding that dump is failing. Must admit, this is the first time I've tried to run a backup since migrating from RELENG_4 to RELENG_5. fsck -f / marks the file system as clean. Any ideas? [EMAIL PROTECTED] dump -0a -b 512 -f - / /dev/null The -b 512 (or other large values), seems to be the key to making it crash (on various inodes). Sometimes the error is master/slave protocol botched instead. Until I find the cause, the workaround of don't do that then seems appropriate. At least it wasn't fs corruption ;) -- Mark A. R. Knight finger: [EMAIL PROTECTED] Tel: +44 7973 410732http://www.knigma.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
downgrading ports
Hi, Can anybody tell me how to downgrade the ports. I upgraded p5-GD port to 2.16 . However some of our applications require p5-GD 2.07 version. So I need to roll back to 2.07 from 2.16. Tejas Kokje ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: downgrading ports
On Tue, Jan 04, 2005 at 02:16:47PM -0800, Tejas Kokje wrote: Hi, Can anybody tell me how to downgrade the ports. I upgraded p5-GD port to 2.16 . However some of our applications require p5-GD 2.07 version. So I need to roll back to 2.07 from 2.16. This can be a slightly tricky business if there is a history of interdependent commits affecting the port, but you can try the portdowngrade port. Kris pgppKjvhUhIMx.pgp Description: PGP signature
Re: ports directories are broken again?
On Fri, Dec 31, 2004 at 05:28:48PM -0800, Kris Kennaway wrote: The port index under www.freebsd.org/ports *does* know that frontpage will not appear in packages, and doesn't provide a link to it. http://www.freebsd.org/ports/www.html I beg to differ http://www.freebsd.org/cgi/ports.cgi?query=frontpagestype=namerelease=5.3-RELEASE%2Fi386 -- Joe Rhett Senior Geek Meer.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports directories are broken again?
On Fri, Dec 31, 2004 at 05:22:00PM -0800, Kris Kennaway wrote: It provides a link to where the package would be if it exists. The web frontend has no knowledge of which packages are available at any given point in time because this set fluctuates on a daily basis, so the frontend is always going to have windows where it's out of date with respect to what's on the ftp site. I'm sorry, but clue me in here. You are saying that the online database of ports has no idea what is in the ports tree? We're not talking about daily or hourly fluctuation. We're talking about a package that hasn't been available for years for a version of the operating system that is less than 6 months old. One could imagine changing this with some hard work, or at least improving the documentation, but that's how things are today. You're welcome to submit a PR with your suggestion on how to change the documentation to annotate this. It's not a documentation issue, it's an accuracy issue. Is there a port or not? Is there a package for the port, or not? -- Joe Rhett Senior Geek Meer.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports directories are broken again?
On Tue, Jan 04, 2005 at 02:30:14PM -0800, Joe Rhett wrote: On Fri, Dec 31, 2004 at 05:22:00PM -0800, Kris Kennaway wrote: It provides a link to where the package would be if it exists. The web frontend has no knowledge of which packages are available at any given point in time because this set fluctuates on a daily basis, so the frontend is always going to have windows where it's out of date with respect to what's on the ftp site. I'm sorry, but clue me in here. You are saying that the online database of ports has no idea what is in the ports tree? No, it can't tell when a package failed to compile (or is otherwise missing from the ftp site) for an unexpected reason. It looks like the link I pointed you to does filter out 'expected' failures (of which frontpage is one), but the link you pointed me to does not. This is probably a simple omission in the affected scripts, so you should submit a PR pointing to both URLs and noting the difference. Thanks, Kris pgpaLYTlrnwcw.pgp Description: PGP signature
Re: ports directories are broken again?
On 2005.01.04 14:30:14 -0800, Joe Rhett wrote: On Fri, Dec 31, 2004 at 05:22:00PM -0800, Kris Kennaway wrote: It provides a link to where the package would be if it exists. The web frontend has no knowledge of which packages are available at any given point in time because this set fluctuates on a daily basis, so the frontend is always going to have windows where it's out of date with respect to what's on the ftp site. I'm sorry, but clue me in here. You are saying that the online database of ports has no idea what is in the ports tree? There is a port, just not a package. The issue is that the web pages uses INDEX (from ports/INDEX) to know which ports exists [1], but INDEX says nothing about packages. It's a while since I looked at the scripts, but there is some kind of mechanism to detect if a package exists for a port, but AFAIR that only works when searching for -STABLE/-CURRENT and not releases. Somebody (tm) would have to make the scripts know which packages exist for which releases to fix this. [1] Which btw. is going to fail for 4.11 since there is no INDEX in CVS... -- Simon L. Nielsen FreeBSD Documentation Team pgpi3hoPltekG.pgp Description: PGP signature
Re: fsck: broken file system with background check remains broken after bootup
0n Tue, Jan 04, 2005 at 02:01:22PM +0100, Oliver Fromme wrote: By the way, you can map a key combination (Ctrl-Alt-Del or something else) to the »halt« or »power-down« functions, using kbdcontrol, so it's very easy and intuitive to shut down the machine properly. See the kbdmap(5) manpage for details. This inspires me to ask this question: Is it possible to set up FreeBSD to do a clean shutdown upon a pressing the power button ? i.e. in the same fashion as Solaris does out of the box. Is this an ATX feature or a kernel feature in the PC world ? - aW ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
On Wed, Jan 05, 2005 at 01:59:01PM +1030, Wilkinson, Alex wrote: This inspires me to ask this question: Is it possible to set up FreeBSD to do a clean shutdown upon a pressing the power button ? i.e. in the same fashion as Solaris does out of the box. Is this an ATX feature or a kernel feature in the PC world ? Yes, in FreeBSD 5.3 if ACPI is enabled and working properly, pressing the power button will initiate a graceful shutdown (similar to shutdown -p). This feature is enabled by default if it is available, so you don't have to do anything special to get it. The usual if you have weird hardware there are no guarantees disclaimer applies, but I've never had a problem with the software controlled power button on any fairly recent hardware. Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
0n Tue, Jan 04, 2005 at 09:50:10PM -0600, Craig Boston wrote: Yes, in FreeBSD 5.3 if ACPI is enabled and working properly, pressing the power button will initiate a graceful shutdown (similar to shutdown -p). This feature is enabled by default if it is available, so you don't have to do anything special to get it. How can I confirm that ACPI has been setup to do this ? # acpidump -d | grep ??? - aW ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
On Tuesday 04 January 2005 9:57 pm, Wilkinson, Alex wrote: How can I confirm that ACPI has been setup to do this ? Hmm, well, the easiest thing to check is to run sysctl hw.acpi.power_button_state and see if that sysctl exists and if so, what it's set to (mine is S5, which IIRC is complete power-off). Also, check dmesg and see if you see a line similar to acpi_button0: Power Button on acpi0 If both of those show up, chances are that your ASL has a power button entry and it should do the right thing. Other than that, you could always wait until the system is idle and just try hitting the button to see what happens ;) Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: broken file system with background check remains broken after bootup
0n Tue, Jan 04, 2005 at 10:17:47PM -0600, Craig Boston wrote: On Tuesday 04 January 2005 9:57 pm, Wilkinson, Alex wrote: How can I confirm that ACPI has been setup to do this ? Hmm, well, the easiest thing to check is to run sysctl hw.acpi.power_button_state and see if that sysctl exists and if so, what it's set to (mine is S5, which IIRC is complete power-off). Also, check dmesg and see if you see a line similar to acpi_button0: Power Button on acpi0 If both of those show up, chances are that your ASL has a power button entry and it should do the right thing. Other than that, you could always wait until the system is idle and just try hitting the button to see what happens ;) Cool, thanks: #sysctl hw.acpi.power_button_state hw.acpi.power_button_state: S5 #grep acpi_button /var/run/dmesg.boot acpi_button0: Power Button on acpi0 - aW ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPNAT IPv6
On Tue, Jan 04, 2005 at 12:37:48PM -0800, Brooks Davis wrote: On Wed, Jan 05, 2005 at 05:28:19AM +0900, Hideki Yamamoto wrote: As far as I have tested pf(packet filter) on FreeBSD 5.3R, NAT function with IPv6 does not work well. Log says conversion is done. But source address is not translated. Though I asked about it in freebsd-pf mailing list, we have not had any reponses yet. I don't think any of our packet filters really support IPv6 NAT at this point. In IPv6, it is spelled NAP. See, http://www.ietf.org/internet-drafts/draft-vandevelde-v6ops-nap-00.txt NAT is eevul. Can we please, pretty please leave it with IPv4? -- Crist J. Clark | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
