Re: Patch for rc.d/devd on FreeBSD 9-current
On 06/26/10 13:29, Hans Petter Selasky wrote: > Hi, > > Sometimes utilities that are started by devd require libraries outside > /usr/lib. One example is the webcamd utility which is started by devd upon > USB > device insertion. What do you think about the following patch: > > --- devd(revision 209463) > +++ devd(local) > @@ -4,7 +4,7 @@ > # > > # PROVIDE: devd > -# REQUIRE: netif > +# REQUIRE: netif ldconfig > # BEFORE: NETWORKING mountcritremote > # KEYWORD: nojail shutdown ldconfig requires mountcritremote, so this patch would introduce a circular dependency. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: iSCSI boot driver version 0.1.1 for iBFT
Vincent Hoffman, wrote: Since I dont have a supported nic, would the iscsi support in gpxe (http://etherboot.org/wiki/iscsiboot) be enough? (might give it a try if i get time after the weekend.) Yes. gPXE + istgt can be used. I have confirmed with Windows before. Now I tested with FreeBSD 8.1+isboot0.1.3 (integrated). If you use integrated version, you can install FreeBSD to iSCSI target, mentioned in http://www.etherboot.org/wiki/sanboot/iscsi_install. There is the log of my old machine which have Intel Fast Ether onboard. (use gPXE1.0.0 FD + FreeBSD-8.1-RC1-i386-isboot-0.1.3.iso) gPXE 1.0.0 "Customize image configuration options" (static IP): --- #!gpxe ifopen net0 set net0/initiator-iqn iqn.2000-09.org.etherboot:gpxe-fbs8 set net0/ip 192.168.2.224 set net0/netmask 255.255.255.0 set net0/gateway 192.168.2.1 set net0/dns 192.168.2.1 set keep-san 1 sanboot iscsi:192.168.2.36iqn.2007-09.jp.ne.peach:isboot-gpxe --- istgt.conf: --- [InitiatorGroup97] Comment "Initiator Group97" InitiatorName "iqn.2000-09.org.etherboot:gpxe-fbs8" Netmask 192.168.2.0/24 [LogicalUnit97] Comment "iSCSI Boot Disk3" TargetName "iqn.2007-09.jp.ne.peach:isboot-gpxe" Mapping PortalGroup4 InitiatorGroup97 AuthMethod Auto UseDigest Auto UnitType Disk #QueueDepth 64 # FreeBSD 8.1 gPXE 1.0.0 LUN0 Storage /tank/iscsiz/istgt-boot-gpxe 16GB --- dmesg: --- iSCSI boot driver version 0.1.3 IS: Initiator name: iqn.2000-09.org.etherboot:gpxe-fbs8 NIC0: IP address: 192.168.2.224 NIC0: Prefix: 24 NIC0: Gateway: 192.168.2.1 NIC0: MAC address: 00:10:dc:55:5d:a1 TGT0: Target IP address: 192.168.2.36 TGT0: Target Port: 3260 TGT0: Target LUN: 0 TGT0: Target name: iqn.2007-09.jp.ne.peach:isboot-gpxe Boot NIC: fxp0 Configure IPv4 by NIC0 Attempting to login to iSCSI target and scan all LUNs. ... cut ... da0 at isboot0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 16384MB (33554432 512 byte sectors: 255H 63S/T 2088C) ... cut ... Boot device: da0 --- some results: --- # df Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/da0s1a507630 173014 29400637%/ devfs 1 10 100%/dev /dev/da0s1e507630 12 467008 0%/tmp /dev/da0s1f 12744762 705772 11019410 6%/usr /dev/da0s1d 1500046294 1379750 0%/var # camcontrol devlist at scbus0 target 0 lun 0 (da0,pass0) # diskinfo -v da0 da0 512 # sectorsize 17179869184 # mediasize in bytes (16G) 33554432# mediasize in sectors 0 # stripesize 0 # stripeoffset 2088# Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. 1097# Disk ident. # ifconfig -a fwe0: flags=8802 metric 0 mtu 1500 options=8 ether 02:10:dc:00:45:4e ch 1 dma -1 fwip0: flags=8802 metric 0 mtu 1500 lladdr 0.10.dc.56.0.0.45.4e.a.2.ff.fe.0.0.0.0 fxp0: flags=8843 metric 0 mtu 1500 options=2009 ether 00:10:dc:55:5d:a1 inet 192.168.2.224 netmask 0xff00 broadcast 192.168.2.255 media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 nd6 options=3 # netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.2.1UGS 01 fxp0 127.0.0.1 link#4 UH 02lo0 192.168.2.0/24 link#3 U 211391 fxp0 192.168.2.224 link#3 UHS 0 16lo0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%lo0/64 link#4U lo0 fe80::1%lo0 link#4UHS lo0 ff01:4::/32 fe80::1%lo0 U lo0 ff02::%lo0/32 fe80::1%lo0 U lo0 --- Notes: You have to configure DNS (/etc/resolv.conf) and hostname manually. Or must set exactly matched IP/mask/route in iBFT by sysinstall. This is current limitation. (sysintall breaks booted NIC parameter.) -- Daisuk
isboot (iSCSI boot driver) version 0.1.3
Updated isboot to 0.1.3. Try this. How to build/upgrade: # cd /usr/src # tar xvf /path/to/iscsi-2.2.4.tar.gz # tar xvf /path/to/isboot-0.1.3.tar.gz # make buildkernel # make installkernel or # cd /usr/src/sys/modules/iscsi/isboot # make obj # make depend # make all # make install After installation, please reboot the server to take effect. Confirm the log shows "iSCSI boot driver version 0.1.3". What's new?: * improve session recovery mode. * fix panic when socket is lost. Download links: http://www.peach.ne.jp/archives/isboot/isboot-0.1.3.tar.gz Download links(for testing purpose only): http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-amd64-isboot-0.1.3.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-i386-isboot-0.1.3.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC1-amd64-isboot-0.1.3.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC1-i386-isboot-0.1.3.iso http://www.peach.ne.jp/archives/isboot/demo/unionfs-mkisboot.sh I hope this helps you. Enjoy it. Daisuke Aoyama ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r209240 ia64 -> buildworld -> undefined reference to `lzma_physmem'
2010/6/25 Anton Shterenlikht : > On Thu, Jun 24, 2010 at 05:50:59PM +0200, Dag-Erling Smørgrav wrote: >> Anton Shterenlikht writes: >> > Dag-Erling Smørgrav writes: >> > > I expect this to produce the same error as before; if not, there is >> > > something seriously wrong. >> > the error is different... >> > >> > echo fsck_ffs: /usr/lib/libc.a /usr/lib/libufs.a >> .depend >> > cc -O1 -I/usr/src/sbin/fsck_ffs -I/usr/src/sbin/fsck_ffs/../mount >> > -DRESCUE -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k >> > -Wno-uninitialized -Wno-pointer-sign -c dir.c >> >> This is wrong. It shouldn't compile anything. Did you do anything at >> all to your tree (src or obj) after the failed buildworld? > > sorry, I probably misunderstood you again. > I did "rm -rf /usr/obj/*" before trying your > suggested commands. > > I guess now this is not what you wanted. > > So, just for me to be clear, I need to > proceed with the buildworld, until I get the > error, and then, without cleaning anything, do > > % cd /usr/src > % make buildenv > % cd rescue/rescue > % make > > Is that correct? > > sorry for the bother > and many thanks for your help Hi Anton, Sorry to jump in, but could you please copy your source tree on the failing machine elsewhere, run make clean cleandir, and try applying the patch attached to the post below [1] and see whether or not the issue is resolved? Thanks! -Garrett [1] http://lists.freebsd.org/pipermail/freebsd-hackers/2010-June/032202.html ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Patch for rc.d/devd on FreeBSD 9-current
On Sat, Jun 26, 2010 at 1:45 PM, Garrett Cooper wrote:
> On Sat, Jun 26, 2010 at 1:29 PM, Hans Petter Selasky wrote:
>> Hi,
>>
>> Sometimes utilities that are started by devd require libraries outside
>> /usr/lib. One example is the webcamd utility which is started by devd upon
>> USB
>> device insertion. What do you think about the following patch:
>>
>> --- devd (revision 209463)
>> +++ devd (local)
>> @@ -4,7 +4,7 @@
>> #
>>
>> # PROVIDE: devd
>> -# REQUIRE: netif
>> +# REQUIRE: netif ldconfig
>> # BEFORE: NETWORKING mountcritremote
>> # KEYWORD: nojail shutdown
>
> Funny since I was just monkeying around with this. This doesn't appear
> to be the only issue with devd:
>
> # devd
> devd: devd already running, pid: 430
> # pgrep 430; echo $?
> 1
> #
>
> Looks like /etc/rc.d/devd restart is broken :(...
This seems to fix that.
Thanks,
-Garrett
Index: devd.cc
===
--- devd.cc (revision 209530)
+++ devd.cc (working copy)
@@ -739,6 +739,7 @@
static void
event_loop(void)
{
+ bool warn_user_about_cleanup;
int rv;
int fd;
char buffer[DEVCTL_MAXBUF];
@@ -804,6 +805,17 @@
new_client(server_fd);
}
close(fd);
+ close(server_fd);
+
+ if (unlink(PIPE) == 0) {
+ cfg.remove_pidfile();
+ warn_user_about_cleanup = false;
+ } else
+ warn_user_about_cleanup = true;
+
+ if (warn_user_about_cleanup == true)
+ warn("cleanup failed");
+
}
/*
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Patch for rc.d/devd on FreeBSD 9-current
On Sat, Jun 26, 2010 at 1:29 PM, Hans Petter Selasky wrote: > Hi, > > Sometimes utilities that are started by devd require libraries outside > /usr/lib. One example is the webcamd utility which is started by devd upon USB > device insertion. What do you think about the following patch: > > --- devd (revision 209463) > +++ devd (local) > @@ -4,7 +4,7 @@ > # > > # PROVIDE: devd > -# REQUIRE: netif > +# REQUIRE: netif ldconfig > # BEFORE: NETWORKING mountcritremote > # KEYWORD: nojail shutdown Funny since I was just monkeying around with this. This doesn't appear to be the only issue with devd: # devd devd: devd already running, pid: 430 # pgrep 430; echo $? 1 # Looks like /etc/rc.d/devd restart is broken :(... Thanks, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Patch for rc.d/devd on FreeBSD 9-current
Hi, Sometimes utilities that are started by devd require libraries outside /usr/lib. One example is the webcamd utility which is started by devd upon USB device insertion. What do you think about the following patch: --- devd(revision 209463) +++ devd(local) @@ -4,7 +4,7 @@ # # PROVIDE: devd -# REQUIRE: netif +# REQUIRE: netif ldconfig # BEFORE: NETWORKING mountcritremote # KEYWORD: nojail shutdown --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Use of boot0cfg to set boot slice broke between r209459 and r209502
> > --qZLFzaLf2KECwqmh > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Sat, Jun 26, 2010 at 12:10:57PM +0300, Daniel Braniss wrote: > > ... > > what do you see when you type boot0cfg -v ...? > > gpart show? > > then try=20 > > gpart set -a active -i n aacd0 > > n will probably be 5. > >=20 > > bottom line, the MBR is NOT being updated by boot0cfg > > OK; here's what I see -- note that the /S1/usr/sbin/boot0cfg executable > is the one I built yesterday without the 2 lines from r209469: > > freebeast(9.0-C)[2] uname -a > FreeBSD freebeast.catwhisker.org 9.0-CURRENT FreeBSD 9.0-CURRENT #200 r2095= > 22: Fri Jun 25 06:11:00 PDT 2010 r...@freebeast.catwhisker.org:/usr/obj= > /usr/src/sys/GENERIC i386 > freebeast(9.0-C)[3] sudo boot0cfg -v aacd0; echo $? > Password: > # flag start chs type end chs offset size > 1 0x00 0: 1: 1 0xa5651:254:63 63 10474317 > 2 0x00652: 0: 1 0xa5 1023:254:63 10474380 10474380 > 3 0x00 1023:255:63 0xa5 1023:254:63 20948760 10474380 > 4 0x80 1023:255:63 0xa5 1023:254:63 31423140 40194630 > > version=3D1.0 drive=3D0x80 mask=3D0xf ticks=3D182 bell=3D (0x7) > options=3Dpacket,update,nosetdrv > default_selection=3DF4 (Slice 4) > 0 > freebeast(9.0-C)[4] sudo boot0cfg -v -s 2 aacd0 ; echo $? > boot0cfg: write_mbr: /dev/aacd0: Operation not permitted > 1 > freebeast(9.0-C)[5] sudo boot0cfg -v aacd0 ; echo $? > # flag start chs type end chs offset size > 1 0x00 0: 1: 1 0xa5651:254:63 63 10474317 > 2 0x00652: 0: 1 0xa5 1023:254:63 10474380 10474380 > 3 0x00 1023:255:63 0xa5 1023:254:63 20948760 10474380 > 4 0x80 1023:255:63 0xa5 1023:254:63 31423140 40194630 > > version=3D1.0 drive=3D0x80 mask=3D0xf ticks=3D182 bell=3D (0x7) > options=3Dpacket,update,nosetdrv > default_selection=3DF4 (Slice 4) > 0 > freebeast(9.0-C)[6] sudo /S1/usr/sbin/boot0cfg -v -s 2 aacd0 ; echo $? > # flag start chs type end chs offset size > 1 0x00 0: 1: 1 0xa5651:254:63 63 10474317 > 2 0x00652: 0: 1 0xa5 1023:254:63 10474380 10474380 > 3 0x00 1023:255:63 0xa5 1023:254:63 20948760 10474380 > 4 0x80 1023:255:63 0xa5 1023:254:63 31423140 40194630 > > version=3D1.0 drive=3D0x80 mask=3D0xf ticks=3D182 bell=3D (0x7) > options=3Dpacket,update,nosetdrv > default_selection=3DF2 (Slice 2) > 0 > freebeast(9.0-C)[7] sudo boot0cfg -v aacd0 ; echo $? > # flag start chs type end chs offset size > 1 0x00 0: 1: 1 0xa5651:254:63 63 10474317 > 2 0x00652: 0: 1 0xa5 1023:254:63 10474380 10474380 > 3 0x00 1023:255:63 0xa5 1023:254:63 20948760 10474380 > 4 0x80 1023:255:63 0xa5 1023:254:63 31423140 40194630 > > version=3D1.0 drive=3D0x80 mask=3D0xf ticks=3D182 bell=3D (0x7) > options=3Dpacket,update,nosetdrv > default_selection=3DF2 (Slice 2) > 0 > freebeast(9.0-C)[8] sudo gpart show > =3D> 63 71619471 aacd0 MBR (34G) > 63 10474317 1 freebsd (5.0G) > 10474380 10474380 2 freebsd (5.0G) > 20948760 10474380 3 freebsd (5.0G) > 31423140 40194630 4 freebsd [active] (19G) > 71617770 1764 - free - (882K) > > =3D> 63 143306919 aacd1 MBR (68G) > 63 143299737 1 freebsd [active] (68G) > 143299800 7182 - free - (3.5M) > > =3D> 0 10474317 aacd0s1 BSD (5.0G) > 0 30720001 freebsd-ufs (1.5G) >3072000 74023174 freebsd-ufs (3.5G) > > =3D> 0 10474380 aacd0s2 BSD (5.0G) > 0 30720001 freebsd-ufs (1.5G) >3072000 74023804 freebsd-ufs (3.5G) > > =3D> 0 10474380 aacd0s3 BSD (5.0G) > 0 30720001 freebsd-ufs (1.5G) >3072000 74023804 freebsd-ufs (3.5G) > > =3D> 0 40194630 aacd0s4 BSD (19G) > 0 30720001 freebsd-ufs (1.5G) >3072000 209715202 freebsd-swap (10G) > 24043520 74014724 freebsd-ufs (3.5G) > 31444992 87496386 freebsd-ufs (4.2G) > > =3D>0 143299737 aacd1s1 BSD (68G) > 0 209715202 freebsd-swap (10G) >20971520 671088644 freebsd-ufs (32G) >88080384 552193535 freebsd-ufs (26G) > > freebeast(9.0-C)[9]=20 if you look closely, changing the slice via boot0cfg does NOT change the active flag (0x80), so this is what I do - till the bug gets fixed: boot0cfg -s 3 ad0 gpart set -a active -i 3 ad0 btw, if you type on the console the selection at boot's prompt, the MBR gets updated. danny ___ fr
Re: [CFT] ZFS v16 with stat() speedup
Martin Matuska wrote: > As I have imported some more improvements to the ZFS v15 patch that also > target speed, > I am now calling for testing of v16 with mainly the following important > (post-v16) enhancement (and some related bugfixes): Thanks a lot. I've been only using it for a few hours so far, but I'll let you know if I run into any issues. I'm still booting from UFS, though, and I haven't looked at the python parts yet. Fabian signature.asc Description: PGP signature
Re: Use of boot0cfg to set boot slice broke between r209459 and r209502
On Sat, Jun 26, 2010 at 12:10:57PM +0300, Daniel Braniss wrote: > ... > what do you see when you type boot0cfg -v ...? > gpart show? > then try > gpart set -a active -i n aacd0 > n will probably be 5. > > bottom line, the MBR is NOT being updated by boot0cfg OK; here's what I see -- note that the /S1/usr/sbin/boot0cfg executable is the one I built yesterday without the 2 lines from r209469: freebeast(9.0-C)[2] uname -a FreeBSD freebeast.catwhisker.org 9.0-CURRENT FreeBSD 9.0-CURRENT #200 r209522: Fri Jun 25 06:11:00 PDT 2010 r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC i386 freebeast(9.0-C)[3] sudo boot0cfg -v aacd0; echo $? Password: # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xa5651:254:63 63 10474317 2 0x00652: 0: 1 0xa5 1023:254:63 10474380 10474380 3 0x00 1023:255:63 0xa5 1023:254:63 20948760 10474380 4 0x80 1023:255:63 0xa5 1023:254:63 31423140 40194630 version=1.0 drive=0x80 mask=0xf ticks=182 bell= (0x7) options=packet,update,nosetdrv default_selection=F4 (Slice 4) 0 freebeast(9.0-C)[4] sudo boot0cfg -v -s 2 aacd0 ; echo $? boot0cfg: write_mbr: /dev/aacd0: Operation not permitted 1 freebeast(9.0-C)[5] sudo boot0cfg -v aacd0 ; echo $? # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xa5651:254:63 63 10474317 2 0x00652: 0: 1 0xa5 1023:254:63 10474380 10474380 3 0x00 1023:255:63 0xa5 1023:254:63 20948760 10474380 4 0x80 1023:255:63 0xa5 1023:254:63 31423140 40194630 version=1.0 drive=0x80 mask=0xf ticks=182 bell= (0x7) options=packet,update,nosetdrv default_selection=F4 (Slice 4) 0 freebeast(9.0-C)[6] sudo /S1/usr/sbin/boot0cfg -v -s 2 aacd0 ; echo $? # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xa5651:254:63 63 10474317 2 0x00652: 0: 1 0xa5 1023:254:63 10474380 10474380 3 0x00 1023:255:63 0xa5 1023:254:63 20948760 10474380 4 0x80 1023:255:63 0xa5 1023:254:63 31423140 40194630 version=1.0 drive=0x80 mask=0xf ticks=182 bell= (0x7) options=packet,update,nosetdrv default_selection=F2 (Slice 2) 0 freebeast(9.0-C)[7] sudo boot0cfg -v aacd0 ; echo $? # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xa5651:254:63 63 10474317 2 0x00652: 0: 1 0xa5 1023:254:63 10474380 10474380 3 0x00 1023:255:63 0xa5 1023:254:63 20948760 10474380 4 0x80 1023:255:63 0xa5 1023:254:63 31423140 40194630 version=1.0 drive=0x80 mask=0xf ticks=182 bell= (0x7) options=packet,update,nosetdrv default_selection=F2 (Slice 2) 0 freebeast(9.0-C)[8] sudo gpart show => 63 71619471 aacd0 MBR (34G) 63 10474317 1 freebsd (5.0G) 10474380 10474380 2 freebsd (5.0G) 20948760 10474380 3 freebsd (5.0G) 31423140 40194630 4 freebsd [active] (19G) 71617770 1764 - free - (882K) => 63 143306919 aacd1 MBR (68G) 63 143299737 1 freebsd [active] (68G) 143299800 7182 - free - (3.5M) => 0 10474317 aacd0s1 BSD (5.0G) 0 30720001 freebsd-ufs (1.5G) 3072000 74023174 freebsd-ufs (3.5G) => 0 10474380 aacd0s2 BSD (5.0G) 0 30720001 freebsd-ufs (1.5G) 3072000 74023804 freebsd-ufs (3.5G) => 0 10474380 aacd0s3 BSD (5.0G) 0 30720001 freebsd-ufs (1.5G) 3072000 74023804 freebsd-ufs (3.5G) => 0 40194630 aacd0s4 BSD (19G) 0 30720001 freebsd-ufs (1.5G) 3072000 209715202 freebsd-swap (10G) 24043520 74014724 freebsd-ufs (3.5G) 31444992 87496386 freebsd-ufs (4.2G) =>0 143299737 aacd1s1 BSD (68G) 0 209715202 freebsd-swap (10G) 20971520 671088644 freebsd-ufs (32G) 88080384 552193535 freebsd-ufs (26G) freebeast(9.0-C)[9] Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpxzcqvxFsoo.pgp Description: PGP signature
Re: using cupsd instead of base lpr [was Re: [HEADS UP] Kernel modules don't work properly in FreeBSD 8.1-RC1 (solved)]
Gary Jennejohn wrote: > IMO if you're going to make the binaries in base non-executable > you might just as well delete them. The chmod is reversible without having to recover the base binaries from somewhere. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Use of boot0cfg to set boot slice broke between r209459 and r209502
> > --jr/gb2Ce1GM9KKZD > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Fri, Jun 25, 2010 at 08:37:36AM -0400, John Baldwin wrote: > > On Friday 25 June 2010 7:40:11 am David Wolfskill wrote: > > > Well, one one of my machines -- I realize that there are some > > > machines for which it's been problematic for a while. And all of > > > the machines I'm using run FreeBSD/i386. > >=20 > > 209469 perhaps? > > Apparently so. > > Here's what I did to test the above assertion: > > * Booted the build machine from slice 4 (usual "head" slice); cloned > that slice to slice 1; booted from slice 1. > > * In a "head" src working directory, I issued > > svn diff -c209469 > > and saw that r209469 merely added 2 lines to usr.sbin/boot0cfg/boot0cfg.c. > > * On the build machine's src working directory, I edited > usr.sbin/boot0cfg/boot0cfg.c to remove the lines in question. > > * Then (as root), I made /usr/src/usr.sbin/boot0cfg/ my current working > directory and issued: > > make && make install > > * I then issued > > boot0cfg -s 4 aacd0 && shutdown -r now > > then watched the serial console. > > * I noticed that the default boot slice -- which had been 1 -- was now > 4. > > * For grins, I then booted slice 4 (head) in single-user mode, mounted > the file systems, then invoked the boot0cfg executable from slice 1 to > switch the default to slice 2, then issued "halt -p". I waited a bit, > then powered the machine back up (WoL can be handy!) noted it was > booting from slice 2, brought it up in single-user mode, then issued > "halt -p" to reduce its power consumption and heat & nouse generation. > > All that said, it looks as if r209469 merely noticed an existing error > condition and tried to do something arguably sensible with it, rather > than merely ignore it. So it would seem that there's a more fundamental > issue at stake, here what do you see when you type boot0cfg -v ...? gpart show? then try gpart set -a active -i n aacd0 n will probably be 5. bottom line, the MBR is NOT being updated by boot0cfg danny ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
