Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
dd 1m zero on the drive and rerun the 8.0Beta4 DVD. Created two slices S1 and S2, and did auto labling (unix partiton) on S1, hit W, the problem persists. Boot system with freeBSD 6.4, and 6.4 sees two slices (MBR partitions) S1 and S2, but no any Unix partition (ad0s1a, ad0s1b etc) on S1. Boot back to 8.0-Beta4, it still sees not Slice created. At this point, it is obviously that 8.0 looks in a wrong MBR location -- 8.0 created slices can be seen by 6.4 but not 8.0 itself. --- On Mon, 9/14/09, Thierry Thomas thie...@freebsd.org wrote: From: Thierry Thomas thie...@freebsd.org Subject: Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b To: Jin Guojun jguo...@sbcglobal.net Cc: b...@freebsd.org, freebsd-stable@freebsd.org, curr...@freebsd.org Date: Monday, September 14, 2009, 10:06 PM Le Lun 14 sep 09 à 23:08:53 +0200, Jin Guojun jguo...@sbcglobal.net écrivait : I do not enve know how to make dangerously dedicated disk, and the 8.0 may do this sliently. No, I don't think so! But such a problem may arise if your disk had been installed as dangerously dedicated in a former version. Unfortunately, previous versions of sysinstall have created uncorrect labels, and the new gpart in 8.0 does not see them. In that case, you have to boot kernel.old and wipe out the bad label. If you reboot with a 7.2 kernel, can you see your missing partitions? -- Th. Thomas. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
panic: UMA: page_free used with invalid flags 4
Hello, My server was using FreeBSD-7-Stable and performing a mail server. Software I used is postfix 2.6.3 and dovecot 1.2.4. The hardware is IBM blade server HS-21 CPU: dual Intel E5335 @ 2.00GHz MEM: 3G HD: onboard LSI RAID controller with 2 73G SAS HD. (mpt0: LSILogic SAS/SATA Adapter) The system is very stable until last week. After csup the FreeBSD-7-STABLE source to around 2009/09/10, it will halt randomly around every several hours. The error message I saw on console was the following: panic: UMA: page_free used with invalid flags 4 cpuid = 0 Uptime: 3h1m14s Physical memory: 3064MB Dumping 1544MB: 1529 1513 1497 Reading freebsd-stable mailing shows there is some vm related modfication during the first week of Sep. (the panic: vm_phys_paddr_to_vm_page: paddr 0x series) So, I csup my src back to 2009/09/01, the problem disappeared, and system comes back with stable state. Today, I csup my src to latest 7-STABLE (2009/09/15) and problem comes again. It seems the problem is still there and not be solved yet. Would you please help to fix it? Thanks very much. Sincerely, Tim Chen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
Hi! I had the same problem with beta4: http://lists.freebsd.org/pipermail/freebsd-current/2009-September/011470.html and I tried this fix, and it did not solve the problem. It might be related with the number of slices and partitions one is creating ? I'll try this again today. Tested it, no, it does not solve the problem. Is there anything I can do to debug this ? I think I can provide remote console access if necessary. I'll try the LiveCD, too. -- p...@opsec.eu+49 171 310137211 years to go ! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
Hi! I had the same problem with beta4: [...] My previous tests were with 8.0-beta4-amd64. I now tested with 8.0-beta3-i386, this time installation and partitioning worked. I'll try to partition using a i386 boot cd and install using the amd64 boot cd 8-) It seems to be a bug with the amd64 code ? -- p...@opsec.eu+49 171 310137211 years to go ! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: problem with link aggregation failover
On 2009-Sep-13 12:11:45 +0200, Maciej Jan Broniarz gau...@gausus.net wrote: I have configured the same mac on both cards. This should be done automatically by lagg. When I disconnect the cable from xl0, the network connection dies, and my lagg0 looks like this: lagg0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9RXCSUM,VLAN_MTU ether 00:01:02:20:24:ef inet 192.168.1.104 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect status: active laggproto failover laggport: fxp0 flags=4ACTIVE laggport: xl0 flags=1MASTER What might be the problem with that setup? Both sides of a lagg need to co-operate to pass packets. You need to configure the switch to failover as well. -- Peter Jeremy pgpMQ4Rr2dl4y.pgp Description: PGP signature
Re: problem with link aggregation failover
Hello, What might be the problem with that setup? Both sides of a lagg need to co-operate to pass packets. You need to configure the switch to failover as well. A simple LACP configuration should do? mjb ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
Hi, * Kurt Jaeger li...@c0mplx.org [090915 09:34]: I had the same problem with beta4: [...] My previous tests were with 8.0-beta4-amd64. I now tested with 8.0-beta3-i386, this time installation and partitioning worked. I'll try to partition using a i386 boot cd and install using the amd64 boot cd 8-) It seems to be a bug with the amd64 code ? a few days ago I installed a new system using the amd64 bootonly iso and didn't have any problems with partitioning. Hardware is atapci1: Intel ICH7 SATA300 controller port 0xd080-0xd087,0xd000-0xd003,0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on pci0 ad4: 476940MB Hitachi HDP725050GLA360 GM4OA5CA at ata2-master SATA150 On installation I had a different BIOS configuration though that caused the SATA disk to be found as ad0, maybe that makes a difference. Wolfgang ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.0 Install Failure
Installing 8.0 Beta 4 on an i386 machine from disc 1. IN the Extracting ports: Panic: initiate_write_inodeblock_ufs2: already started cpuid=0 KDB: enter: panic [thread pid 19 tid 100045 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why I did a where but its way too much to type accurately by hand. This is an older system, but it does boot disc 1 where some of the previous releases it would not boot disk 1 but had to use the live file system. I'll try it again without adding the ports. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0 Install Failure
On 15 Sep 2009, at 10:52, Doug Hardie wrote: Installing 8.0 Beta 4 on an i386 machine from disc 1. IN the Extracting ports: Panic: initiate_write_inodeblock_ufs2: already started cpuid=0 KDB: enter: panic [thread pid 19 tid 100045 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why I did a where but its way too much to type accurately by hand. This is an older system, but it does boot disc 1 where some of the previous releases it would not boot disk 1 but had to use the live file system. The same thing happened to me under VMWare Workstation, when I installed FreeBSD 8.0-BETA4 on a (virtual) disk connected to a (virtual) LSI SAS adaptor. Installing on a IDE disk worked around the problem. It happened with the i386 as well as the amd64 version. Thomas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0 Install Failure
On 15 September 2009, at 01:52, Doug Hardie wrote: Installing 8.0 Beta 4 on an i386 machine from disc 1. IN the Extracting ports: Panic: initiate_write_inodeblock_ufs2: already started cpuid=0 KDB: enter: panic [thread pid 19 tid 100045 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why I did a where but its way too much to type accurately by hand. This is an older system, but it does boot disc 1 where some of the previous releases it would not boot disk 1 but had to use the live file system. I'll try it again without adding the ports. Well, now it no longer boots disc 1 but does boot the live fs. Reinstalled, but now I am getting a bunch of disk errors (SCSI) so I suspect the problem is hardware. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: problem with link aggregation failover
On 2009-Sep-15 09:50:49 +0200, Maciej Jan Broniarz gau...@gausus.net wrote: What might be the problem with that setup? Both sides of a lagg need to co-operate to pass packets. You need to configure the switch to failover as well. A simple LACP configuration should do? Yes. I use LACP at $work. See lagg(4) for other options. -- Peter Jeremy pgpuoDPA53s7j.pgp Description: PGP signature
Re: problem booting FreeBSD 8-Beta4 on Soekris net5501
Le Sat, 12 Sep 2009 14:57:16 +1000, Graham Menhennitt gra...@menhennitt.com.au a écrit : I'm upgrading a Soekris net5501 from FreeBSD 7-Stable to 8-Beta4 (via source). I've done a buildworld, buildkernel, and installkernel. When I try to boot the new kernel, it stops very early on in the boot sequence. The serial console shows: ... Does anybody have any clues please? No. I can only say that it works for me (tm) The only change I remember was to change /etc/ttys with ttyu[0..3] instead ttyd[0..3] on 7.2 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
Kurt Jaeger writes: I had the same problem with beta4: [...] My previous tests were with 8.0-beta4-amd64. I now tested with 8.0-beta3-i386, this time installation and partitioning worked. It seems to be a bug with the amd64 code ? That might be. I have tried this with: 1) amd64 beta3 and beta4 using the downloaded DVD images 2) 7.1/7.2 using the installation CD from the set sold by FreeBSD Mall. I also tried on several sets of hardware: SCSI, IDE, SATA. The number of disks and number of slices and partitions per disk had no effect. (1) always failed; (2) succeeded. (Fruitlessly, since the specification was for a clean install of 8.0 code and I had to wipe and try (1) again.) Robert Huff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
Jin Guojun writes: I do not enve know how to make dangerously dedicated disk, and the 8.0 may do this sliently. I was told in private conversation dangerously dedicated mode is currently broken (at least with regards to installation), and that it was removed as an option between beta3 and beta4. Robert Huff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.0 rc.d scripts less verbose?
Hi, Since I run 8.0 the rc.d scripts are less verbose. I have some problems with them, but the default output gives me no information anymore. In the 8.0-TODO wiki there is a mention about verbosity of the rc.d scripts at the bottom. Is there a way for me to increase the verbosity? Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
newsyslog can't execute command?
Hi. Have I overlooked something, or is it not possible with newsyslog to run a certain command after log rotation? :-( It looks like the patch mentioned here http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2006-06/msg00575.html never made it into the FreeBSD distribution? Bummer ... -- Ferdinand Goldmann Johannes Kepler University Linz - Server Systems/Information Management Mail: ferdinand.goldm...@jku.at Phone: 00437024689398 Fax: 00437024689397 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0 rc.d scripts less verbose?
Ronald Klop wrote: Hi, Since I run 8.0 the rc.d scripts are less verbose. I have some problems with them, but the default output gives me no information anymore. In the 8.0-TODO wiki there is a mention about verbosity of the rc.d scripts at the bottom. Is there a way for me to increase the verbosity? You can use rc_debug or rc_info in your rc.conf rc_debug (bool) If set to ``YES'', enable output of debug messages from rc scripts. This variable can be helpful in diagnosing mistakes when editing or integrating new scripts. Beware that this produces copious output to the terminal and syslog(3). rc_info (bool) If set to ``NO'', disable informational messages from the rc scripts. Informational messages are displayed when a condition that is not serious enough to warrant a warning or an error occurs. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0 rc.d scripts less verbose?
On Tue, 15 Sep 2009 16:59:46 +0200, Miroslav Lachman 000.f...@quip.cz wrote: Ronald Klop wrote: Hi, Since I run 8.0 the rc.d scripts are less verbose. I have some problems with them, but the default output gives me no information anymore. In the 8.0-TODO wiki there is a mention about verbosity of the rc.d scripts at the bottom. Is there a way for me to increase the verbosity? You can use rc_debug or rc_info in your rc.conf rc_debug (bool) If set to ``YES'', enable output of debug messages from rc scripts. This variable can be helpful in diagnosing mistakes when editing or integrating new scripts. Beware that this produces copious output to the terminal and syslog(3). rc_info (bool) If set to ``NO'', disable informational messages from the rc scripts. Informational messages are displayed when a condition that is not serious enough to warrant a warning or an error occurs. Rc_info gave me 1 line extra about kld green_saver being loaded. I still have to try rc_debug. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Source level upgrade from 4.9 to CURRENT..
Hi folks. Need help in doing the following, but first want to check and see if it is feasible with the latest Release, or if I'm just going to be spinning my wheels on this one. The Objective. == I have a FreeBSD 4.9-RELEASE system which I want to upgrade to 7.X from the source level. Had a bunch of problems installing 7.1-RELEASE from the CD distribution I got from freebsdmall.com. Several problems that could not mount the CD at the time of installation causing sysinstall to halt. So, 4.9 is installed and working, is there a source level backward compatibility issue between 7.x and anything older than 6.0 ? In other words, upgrading from the sources with such an old distribution is a doable task ? Your response is greatly appreciated. Many thanks. --Rom a_romolo at hotmail (dot) com _ Ready for Fall shows? Use Bing to find helpful ratings and reviews on digital tv's. http://www.bing.com/shopping/search?q=digital+tv'sform=MSHNCBpubl=WLHMTAGcrea=TEXT_MSHNCB_Vertical_Shopping_DigitalTVs_1x1___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Source level upgrade from 4.9 to CURRENT..
Hi, Reference: From: Rom Albuquerque a_rom...@hotmail.com Date: Tue, 15 Sep 2009 17:38:16 + Message-id: snt114-w81d034e5efd1695113d57ed...@phx.gbl Rom Albuquerque wrote: Hi folks. Need help in doing the following, but first want to check and see if it is feasible with the latest Release, or if I'm just going to be spinning my wheels on this one. The Objective. == I have a FreeBSD 4.9-RELEASE system which I want to upgrade to 7.X from the source level. Had a bunch of problems installing 7.1-RELEASE from the CD distribution I got from freebsdmall.com. Several problems that could not mount the CD at the time of installation causing sysinstall to halt. So, 4.9 is installed and working, is there a source level backward compatibility issue between 7.x and anything older than 6.0 ? In other words, upgrading from the sources with such an old distribution is a doable task ? Your response is greatly appreciated. Many thanks. --Rom a_romolo at hotmail (dot) com I recently upgraded lots of hosts from 4.10 4.11 5 6 to 7.2, So many to keep track I needed my http://www.berklix.com/~jhs/txt/upgrade.html I `just' moved in the binaries from CD alongside, flipped the directory contents, rebooted, then built new custom kernels make world rebuilt ports. But I didnt do some cross compile from 4 to 7, too much like hard work that! So quite possible to upgrade without repartitioning disc reloading data. But you might want a bigger root. You might want a newer FFS for performance (can't remember when that came in). ... there'll doubtless be a few other `Gotchas' so if you have problems/ not enough experience/ get stuck. the safe way is a back up, reinstall. Well, a back up's not exactly a foolish precaution anyway ;-) Good luck. Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail ASCII plain text not HTML Base64. http://asciiribbon.org Virused Microsoft PCs cause spam. http://berklix.com/free/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0 rc.d scripts less verbose?
On 2009-09-15 16:37, Ronald Klop wrote:
Since I run 8.0 the rc.d scripts are less verbose. I have some problems
with them, but the default output gives me no information anymore.
In the 8.0-TODO wiki there is a mention about verbosity of the rc.d
scripts at the bottom. Is there a way for me to increase the verbosity?
Nope, this was removed, apparently. A pity, since this was very useful
information during boot time. However, setting rc_debug will give you
enormous gobs of useless info (unless you're debugging rc scripts), and
rc_info doesn't seem to add much anymore, if anything.
To restore the old behaviour, apply the following patch (I have this in
my local repository for ages now):
Index: etc/rc.subr
===
--- etc/rc.subr (revision 196888)
+++ etc/rc.subr (working copy)
@@ -680,7 +680,7 @@ run_rc_command()
# setup the full command to run
#
- [ -z ${rc_quiet} ] echo Starting ${name}.
+ echo Starting ${name}.
if [ -n $_chroot ]; then
_doit=\
${_nice:+nice -n $_nice }\
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-BETA-4: no mouse or keyboard in X.
On Tue, Sep 15, 2009 at 01:24:37PM +1000, Dave Hardman wrote: On Sun, Sep 13, 2009 at 12:40:52PM +0200, Patrick Lamaiziere wrote: Le Sun, 13 Sep 2009 15:29:58 +1000, Dave Hardman d...@hardman.name a écrit : I upgraded from 7.2 to 8.0-BETA4. Now X will not receive input from either the mouse or keyboard. [...] You need to rebuild hal and to remove the old libusb port. libusb is now part of the base system in 8.X and you must use this version. You should rebuild all that depend on the old port libusb (at least). I rebuilt all the ports (portupgrade -afc), during the upgrade and there was no indication of any failures. I tried again (portmanager -u -f -l). hal-0.5.11_26 failed. See below. I also noticed the fuse.ko will not load, reporting Exec format error. Did you rebuild this module too? It rebuilt when I ran portmanager. I also tried to remove the libusb, as another responded suggested. However pkg_delete refused as it was required by other packages. Mostly gnome by the look of it eg, gnucash gnumeric. Best Dave gmake[5]: Entering directory `/usr/ports/sysutils/hal/work/hal-0.5.11/hald/freebsd/probing' cc -DHAVE_CONFIG_H -I. -I../../.. -DPACKAGE_SYSCONF_DIR=\/usr/local/etc\ -DPACKAGE_DATA_DIR=\/usr/local/share\ -DPACKAGE_BIN_DIR=\/usr/local/bin\ -DPACKAGE_LOCALE_DIR=\/usr/local/share/locale\ -DPACKAGE_LOCALSTATEDIR=\/var\ -I../../.. -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -I/usr/local/include -DHAVE_CK_0_3 -O2 -pipe -fno-strict-aliasing -Wall -Wchar-subscripts -Wmissing-declarations -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -MT probe-hiddev.o -MD -MP -MF .deps/probe-hiddev.Tpo -c -o probe-hiddev.o probe-hiddev.c probe-hiddev.c: In function 'main': probe-hiddev.c:81: error: 'USB_GET_REPORT_ID' undeclared (first use in this function) probe-hiddev.c:81: error: (Each undeclared identifier is reported only once probe-hiddev.c:81: error: for each function it appears in.) gmake[5]: *** [probe-hiddev.o] Error 1 gmake[5]: Leaving directory `/usr/ports/sysutils/hal/work/hal-0.5.11/hald/freebsd/probing' gmake[4]: *** [all-recursive] Error 1 gmake[4]: Leaving directory `/usr/ports/sysutils/hal/work/hal-0.5.11/hald/freebsd' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/sysutils/hal/work/hal-0.5.11/hald' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/sysutils/hal/work/hal-0.5.11/hald' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/sysutils/hal/work/hal-0.5.11' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/sysutils/hal. *** Error code 1 Stop in /usr/ports/sysutils/hal. ! sysutils/hal (hal-0.5.11_26) (compiler error) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Source level upgrade from 4.9 to CURRENT..
On Tue, Sep 15, 2009 at 05:38:16PM +, Rom Albuquerque wrote: to halt. So, 4.9 is installed and working, is there a source level backward compatibility issue between 7.x and anything older than 6.0 ? In other words, upgrading from the sources with such an old distribution is a doable task ? It's doable, in that many of us have indeed upgraded through those control points with source, but it can't necessarily be done in one step. Is it worth trying to do in multiple steps? Maybe not: you'll almost certainly want a larger root partition, and may very well want to change to UFS2, both of which mean that you're going to have to dump to backup, repartition, reformat and restore at some stage (and that stage is one of the intermediate stops, because you don't have UFS2 in 4.9). So: you're going to need to be able to boot from the 7.2 (or whatever) kernel+fixit combination to do the reformat anyway, so why not go the whole hog and reinstall directly to 7.2 (or so) at the same time? That's what I did when I hit the UFS2 barrier, and I'm otherwise a died-in-the-wool source upgrader. If you're having trouble getting 7.1 to boot from CD, then try 7.2 or otherwise sort out that problem, because not having a bootable CD fallback position is not a comfortable place to be, anyway. Cheers, -- Andrew ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
