Date: Wed, 26 Apr 2000 02:18:11 GMT From: Salvo Bartolotta <bartequi@neomedia.it> To: freebsd-current@FreeBSD.ORG Subject: A positive data point ... and one question. Message-ID: <20000426.2181100@bartequi.ottodomain.org>
next in thread | raw e-mail | index | archive | help
Dear FreeBSD'ers, Although I had been reading negative news, I went ahead ruthlessly and I upgraded one of my 4.0-S slices to 5-CURRENT. My attempt was=20 successful. For the record, I had cvsup'ed -CURRENT on 25 April at about 9 GMT. However,I found a couple of curious things: 1) Albeit I had remade all the devices (including all the slices in use, sound devices etc.), this warning appeared: "WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices"; 2) while booting, I saw a bunch of "unknowns": bartequi /kernel: unknown: <PNP0400> can't assign resources bartequi /kernel: unknown: <PNP0501> can't assign resources bartequi /kernel: unknown: <PNP0501> can't assign resources bartequi /kernel: unknown: <PNP0700> can't assign resources bartequi /kernel: unknown0: <PNP0c01> at iomem 0-0x9ffff,0x100000-0x17ffffff,0xe8000-0xeffff,0xf0000-0xf3fff,0xf4000 -0 xf7fff,0xf8000-0xfbfff,0xfc000-0xfffff,0xfffe0000-0xffffffff on isa0 bartequi /kernel: unknown: <PNP0000> can't assign resources bartequi /kernel: unknown1: <PNP0100> at port 0x40-0x43 irq 0 on isa0 bartequi /kernel: unknown2: <PNP0b00> at port 0x70-0x71 irq 8 on isa0 bartequi /kernel: unknown: <PNP0303> can't assign resources bartequi /kernel: unknown3: <PNP0c04> at port 0xf0 irq 13 on isa0 bartequi /kernel: unknown4: <PNP0200> at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 bartequi /kernel: unknown5: <PNP0800> at port 0x61 on isa0 bartequi /kernel: unknown6: <PNP0a03> at port 0xcf8-0xcff on isa0 bartequi /kernel: unknown7: <PNP0c02> at port 0x290-0x297,0xe400-0xe43f,0xe800-0xe83f on isa0 bartequi /kernel: sbc0: <Creative SB AWE64> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 bartequi /kernel: sbc0: setting card to irq 5, drq 1, 5 bartequi /kernel: pcm0: <SB DSP 4.16> on sbc0 bartequi /kernel: joy0: <Generic PnP Joystick> at port 0x200-0x207 on isa0 bartequi /kernel: unknown8: <WaveTable> at port 0x620-0x623 on isa0 well, I had seen unknown8 before, but it was the ONLY unknown. Finally, I deinstalled the tcsh port and changed my shell to /bin/csh (ie /bin/tcsh). Apart from the above minor items, the upgrade seems to have been quite successful. Question. I had created the 4.0-S system that I would subsequently upgrade to -CURRENT via "make release". I ran "disklabel -B ad2" just to be safe (the OS, now -CURRENT, lives on ad2s1.) When I issued a "disklabel -r ad2", I got "disk: ad2s1". On the other hand, I issued a "disklabel -B ad1" for another 4.0-S system of mine, a 4.0-S system which lives on ad1s2 (/, /var swap) and ad2s2 (/usr). I had successfully upgraded this (former) 3.4-S to 4.0-CURRENT via cvsup and the procedure described in UPDATING; then I had upgraded it to 4.0-S. For this system, disklabel -r spits out "disk:wd1s2" (instead of "ad1s2"). What am I (yawn) missing ? Thanks in advance and best regards, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000426.2181100>