At 10:28 PM 5/13/2000 +0200, Jeroen Ruigrok van der Werven wrote:
>-On [2513 22:08], Manfred Antar ([EMAIL PROTECTED]) wrote:
> >Which is the correct dev /dev/da0a , /dev/rda0a , or /dev/da0s1a to use
> >rda0a won't work. da0a works fine and I got rid of all the da0s1a,b,e,f,g ones ?
>
>The /
-On [2513 22:08], Manfred Antar ([EMAIL PROTECTED]) wrote:
>Which is the correct dev /dev/da0a , /dev/rda0a , or /dev/da0s1a to use
>rda0a won't work. da0a works fine and I got rid of all the da0s1a,b,e,f,g ones ?
The /dev/da0s1a would be the correct one to use, example:
# Device
In message <[EMAIL PROTECTED]>, Manfred Antar writes:
>>--- vfs_subr.c~ Sat May 6 00:08:38 2000
>>+++ vfs_subr.c Sat May 13 21:47:08 2000
>>@@ -1296,7 +1296,7 @@
>> return (error);
>> }
>> vp = nvp;
>>- vp->v_type = VBLK;
>>+ vp->v_type = VCHR;
>>
At 09:54 PM 5/13/2000 +0200, Assar Westerlund wrote:
>Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> writes:
> > -On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote:
> > >I get this in boot mesgs and I don't know how to fix it.
> > >Device char-major=13 minor=0 opened in block mode, c
> The following patch fixed the problem for me. For extra points,
> rename the function.
That fixed the problem for the me too. Thanks!
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the mess
Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> writes:
> -On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote:
> >I get this in boot mesgs and I don't know how to fix it.
> >Device char-major=13 minor=0 opened in block mode, convert to char mode
> >with /dev/MAKEDEV before 2000-07-01
>
> Actually I think this is an indication of really old boot blocks.
>
> The old bootblocks passed in a Bmajor number for the root device.
>
> Could you try to update your bootblocks with the disklabel
> program and see if that stops the warning Manfred ?
I can't speak for this case, but the one
At 09:18 PM 5/13/2000 +0200, Poul-Henning Kamp wrote:
>In message <[EMAIL PROTECTED]>, Jeroen Ruigrok van der Werv
>en writes:
> >-On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote:
> >>I get this in boot mesgs and I don't know how to fix it.
> >>Device char-major=13 minor=0 opened in b
In message <[EMAIL PROTECTED]>, Jeroen Ruigrok van der Werv
en writes:
>-On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote:
>>I get this in boot mesgs and I don't know how to fix it.
>>Device char-major=13 minor=0 opened in block mode, convert to char mode
>>with /dev/MAKEDEV before 200
> >I get this in boot mesgs and I don't know how to fix it.
> >Device char-major=13 minor=0 opened in block mode, convert to char mode
> >with /dev/MAKEDEV before 2000-07-01
>
> There is a bug somewhere in the rootmount code.
It's the following VFS_MOUNT call at line 215 of vfs_mountroot_try()
(
> >> No, I havn't tracked down the last couple of causes of this, but I
> >> will try to reproduce it as you describe it with some debugging added.
> >
> >How hard would it be to print the filename (or the device/inode) that
> >triggers the warning?
>
> Not at all (warning: cut&pasted patch, ta
-On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote:
>I get this in boot mesgs and I don't know how to fix it.
>Device char-major=13 minor=0 opened in block mode, convert to char mode
>with /dev/MAKEDEV before 2000-07-01
There is a bug somewhere in the rootmount code.
I just lack the e
On Tue, 9 May 2000, Sheldon Hearn wrote:
>
>
> On Mon, 08 May 2000 15:41:55 EST, Erik de Zeeuw wrote:
>
> > I ran MAKEDEV all, but the message still appear. The messages I found
> > about this on the archives says to do a 'ls -l /dev | grep ^b', and
> > to remake all devices listed, but there'
On Mon, 08 May 2000 15:41:55 EST, Erik de Zeeuw wrote:
> I ran MAKEDEV all, but the message still appear. The messages I found
> about this on the archives says to do a 'ls -l /dev | grep ^b', and
> to remake all devices listed, but there's no device listed when I'm
> doing the 'ls -l /dev | gr
In message <[EMAIL PROTECTED]>, Dan Nelson writes:
>In the last episode (May 08), Poul-Henning Kamp said:
>> In message <[EMAIL PROTECTED]>, Erik de Zeeuw writes:
>> >
>> >I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and
>> >when I first launch /stand/sysinstall after the sy
In the last episode (May 08), Poul-Henning Kamp said:
> In message <[EMAIL PROTECTED]>, Erik de Zeeuw writes:
> >
> >I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and
> >when I first launch /stand/sysinstall after the system has start, the
> >following message appears :
> >
>
In message <[EMAIL PROTECTED]>, Erik de Zeeuw writes:
>
>I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and
>when I first launch /stand/sysinstall after the system has start, the
>following message appears :
>
>... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get ri
On Mon, May 08, 2000 at 03:41:55PM -0500, Erik de Zeeuw wrote:
>
> I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and
> when I first launch /stand/sysinstall after the system has start, the
> following message appears :
>
> ... /kernel: WARNING: run /dev/MAKEDEV before 2000-
Yep, that's the ticket ! Thanks.
> Yes, that was an oversight on my part. Please let me know if the
> fix I committed solves this issue.
>
> Poul-Henning
>
> In message <[EMAIL PROTECTED]>, Brian Somers writes:
> >I've got an mfs /tmp too :-]
> >
> >> Hi,
> >>
> >> On 0, Ted Sikora <[EMAIL
In message <[EMAIL PROTECTED]>, John Polstra writes:
>The warning mentions the date 2000-06-01. What are you planning to
>happen on that date? Whatever it is, please make it tolerant.
My intention is to make the system whine even louder starting around
2000-05-01 and then I lean towards a sysc
The warning mentions the date 2000-06-01. What are you planning to
happen on that date? Whatever it is, please make it tolerant. I
don't care whether I can _use_ the old block devices, but I would
like to be able to ls them, dump them, restore them, etc., without
terrible consequences. (I woul
Yes, that was an oversight on my part. Please let me know if the
fix I committed solves this issue.
Poul-Henning
In message <[EMAIL PROTECTED]>, Brian Somers writes:
>I've got an mfs /tmp too :-]
>
>> Hi,
>>
>> On 0, Ted Sikora <[EMAIL PROTECTED]> wrote:
>> > After building a new kernel yest
I've got an mfs /tmp too :-]
> Hi,
>
> On 0, Ted Sikora <[EMAIL PROTECTED]> wrote:
> > After building a new kernel yesterday after a cvsup the following
> > appeared.
> >
> > Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
> > 2000-06-01 to get rid of block devices
> > I did
On Thu, 20 Apr 2000, Dirk Roehrdanz wrote:
[ snippage ]
> I get this message too whenever I mount a mfs filesystem.
> The line in /etc/fstab is:
> /dev/da0s1b /tmp mfs rw,async,-s327680 0
>
> The output of "ls -l /dev/*da0s1b" is:
> crw-r- 1 root operator 13, 0x00
Hi,
On 0, Ted Sikora <[EMAIL PROTECTED]> wrote:
> After building a new kernel yesterday after a cvsup the following
> appeared.
>
> Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
> 2000-06-01 to get rid of block devices
> I did a MAKEDEV all and the message still persists.
>
Hi,
> On Wed, 19 Apr 2000 12:33:44 +0100
> Brian Somers <[EMAIL PROTECTED]> said:
brian> I did the find, removed the bdevs in /compat/linux/dev and rebooted -
brian> no luck, the message is still there.
brian>
brian> I wonder if whatever's done on 2000-06-01 will leave the emulators
> Warner Losh wrote:
> > In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
> > : >Almost none. I don't actually mount nfs partitions until I type mount
> > : >foo:/bar /bar. There's no network card active at that time anyway...
> > :
> > : But does the nfs filesystems you mount have any
On 19 Apr, Peter Wemm wrote:
>> I've not mounted any filesystems when I get the message. I get it
>> when nfsd starts up in the boot process.
>
> Just a thought.. I got this message even though I thought I'd gotten rid of
> all bdevs.. It turned out there were some hidden in sub directories.
Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
> : >Almost none. I don't actually mount nfs partitions until I type mount
> : >foo:/bar /bar. There's no network card active at that time anyway...
> :
> : But does the nfs filesystems you mount have any bdevs on the
On Tue, 18 Apr 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Ted Sikora writes:
> : Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
> : 2000-06-01 to get rid of block devices
> : I did a MAKEDEV all and the message still persists.
>
> I get this message when the ou
On Wed, 19 Apr 2000, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Warner Losh writes:
> >In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
> >: In message <[EMAIL PROTECTED]>, Warner Losh writes:
> >: >In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
> >: >: At what t
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: >Almost none. I don't actually mount nfs partitions until I type mount
: >foo:/bar /bar. There's no network card active at that time anyway...
:
: But does the nfs filesystems you mount have any bdevs on them ?
I've not mounted any fil
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
>: In message <[EMAIL PROTECTED]>, Warner Losh writes:
>: >In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
>: >: At what time does the message come relative to the mounting of the
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: In message <[EMAIL PROTECTED]>, Warner Losh writes:
: >In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: >: At what time does the message come relative to the mounting of the
: >: root filesystem ? Before or after ?
: >
: >I get
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
>: At what time does the message come relative to the mounting of the
>: root filesystem ? Before or after ?
>
>I get mine when nfs starts up.
Any chance you have a bdev on one of the nf
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: At what time does the message come relative to the mounting of the
: root filesystem ? Before or after ?
I get mine when nfs starts up.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the bo
In message <[EMAIL PROTECTED]>, "David O'Brien" writes:
>On Tue, Apr 18, 2000 at 01:34:11PM -0600, Warner Losh wrote:
>>
>> I get this message when the output of ls -l | egrep ^b is empty.
>
>\begin{AOL mode}
>M To
>\end{AOL mode}
Hmm, that sounds weird...
At what ti
On Tue, Apr 18, 2000 at 01:34:11PM -0600, Warner Losh wrote:
>
> I get this message when the output of ls -l | egrep ^b is empty.
\begin{AOL mode}
M To
\end{AOL mode}
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
In message <[EMAIL PROTECTED]> Ted Sikora writes:
: Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
: 2000-06-01 to get rid of block devices
: I did a MAKEDEV all and the message still persists.
I get this message when the output of ls -l | egrep ^b is empty.
Warner
To Unsub
"Chris D. Faulhaber" wrote:
>
> On Tue, 18 Apr 2000, Ted Sikora wrote:
>
> > After building a new kernel yesterday after a cvsup the following
> > appeared.
> >
> > Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
> > 2000-06-01 to get rid of block devices
> > I did a MAKEDEV a
On Tue, 18 Apr 2000, Ted Sikora wrote:
> After building a new kernel yesterday after a cvsup the following
> appeared.
>
> Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
> 2000-06-01 to get rid of block devices
> I did a MAKEDEV all and the message still persists.
>
ls -l /
Did you install an updated MAKEDEV script?
I *think* the point is that you need to bet rid of block devices, and to
do so, you need a MAKEDEV script that doesn't make them...
Just a guess
On Tue, 18 Apr 2000, Ted Sikora wrote:
> After building a new kernel yesterday after a cvsup the fol
42 matches
Mail list logo
