"Andrey A. Chernov" wrote:
>
> On Tue, Nov 30, 1999 at 10:49:57AM -0500, Thomas Stromberg wrote:
> > [root@karma] dumpon> dumpon /dev/wd0s1b
> > dumpon: /dev/wd0s1b: must specify a block device
> > [root@karma] dumpon> dumpon /dev/rwd0s1b
> > [root@karma] dumpon>
> >
> > Bug or Feature?
>
> This message is confusing and means just opposite.
> I'll fix dumpon to accept both device types (to work with older kernels too)
> The bug is that you not rebuild your /dev
I thought all I needed to do was "./MAKEDEV all" in /dev after a
mergemaster (I also tried MAKEDEV drive) However, I guess this is not
the case. Evidentally if I makedev a drive or all, it does not MAKEDEV
the slices. I could of sworn it was supposed to.. alas! Learn something
new every day.
In any case the new 1.9 commit still acts strange (imho), I put some
output on the bottom. Thanks for your help btw! Nothing teaches you
better then a good screwup :)
[root@karma] /dev> uname -a
FreeBSD karma.afterthought.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue
Nov 30 09:03:33 EST 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/KARMA i386
[root@karma] /dev> ./MAKEDEV all
[root@karma] /dev> ls wd0s*
crw-r----- 1 root operator 3, 0x00020002 Nov 30 12:09 wd0s1
brw-r----- 1 root operator 0, 0x00020000 Nov 16 11:09 wd0s1a
brw-r----- 1 root operator 0, 0x00020001 Nov 29 18:06 wd0s1b
brw-r----- 1 root operator 0, 0x00020002 Aug 17 11:40 wd0s1c
brw-r----- 1 root operator 0, 0x00020003 Nov 16 16:48 wd0s1d
brw-r----- 1 root operator 0, 0x00020004 Nov 16 11:09 wd0s1e
brw-r----- 1 root operator 0, 0x00020005 Nov 16 11:09 wd0s1f
brw-r----- 1 root operator 0, 0x00020006 Nov 16 11:09 wd0s1g
brw-r----- 1 root operator 0, 0x00020007 Nov 16 11:09 wd0s1h
crw-r----- 1 root operator 3, 0x00030002 Nov 30 12:09 wd0s2
crw-r----- 1 root operator 3, 0x00040002 Nov 30 12:09 wd0s3
crw-r----- 1 root operator 3, 0x00050002 Nov 30 12:09 wd0s4
[root@karma] /dev> ./MAKEDEV wd0s1b
[root@karma] /dev> ./MAKEDEV wd0s1a
[root@karma] /dev> ls -la wd0s*
crw-r----- 1 root operator 3, 0x00020002 Nov 30 12:09 wd0s1
crw-r----- 1 root operator 3, 0x00020000 Nov 30 12:09 wd0s1a
crw-r----- 1 root operator 3, 0x00020001 Nov 30 12:09 wd0s1b
crw-r----- 1 root operator 3, 0x00020002 Nov 30 12:09 wd0s1c
crw-r----- 1 root operator 3, 0x00020003 Nov 30 12:09 wd0s1d
crw-r----- 1 root operator 3, 0x00020004 Nov 30 12:09 wd0s1e
crw-r----- 1 root operator 3, 0x00020005 Nov 30 12:09 wd0s1f
crw-r----- 1 root operator 3, 0x00020006 Nov 30 12:09 wd0s1g
crw-r----- 1 root operator 3, 0x00020007 Nov 30 12:09 wd0s1h
crw-r----- 1 root operator 3, 0x00030002 Nov 30 12:09 wd0s2
crw-r----- 1 root operator 3, 0x00040002 Nov 30 12:09 wd0s3
crw-r----- 1 root operator 3, 0x00050002 Nov 30 12:09 wd0s4
Output of the new 1.9 dumpon on block slices:
-------------------------------------------
[root@karma] /dev> ls -la wd0s1b
brw-r--r-- 1 root wheel 0, 0x00020001 Nov 30 12:17 wd0s1b
[root@karma] /dev> dumpon /dev/wd0s1b
dumpon: sysctl: kern.dumpdev: Device not configured
[root@karma] /dev> ./MAKEDEV wd0s1b
[root@karma] /dev> dumpon /dev/wd0s1b
[root@karma] /dev> sysctl -a|grep kern.dump
kern.dumpdev: { major = 3, minor = 131073 }
Still burps a wee bit. But after I looked at it again it's easy to tell
why. I guess a sysctl gets put into place (I'm still not sure from
where?) called kern.dumpdev that records the original device data
specified from /etc/rc.conf .. of course, when I last booted, mine was
set to /dev/rwd0s1b, which has those properties ..
I'm just wondering why it checks those properties rather then using the
properties of the specified file (/dev/wd0s1b in that case)..
--
======================================================================
thomas r. stromberg smtp:[EMAIL PROTECTED]
assistant is manager / systems guru http://thomas.stromberg.org
research triangle commerce, inc. finger:[EMAIL PROTECTED]
'om mani pedme hung' pots://1.919.380.9771:3210
================================================================[eof]=
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
