From: Kieran <kieran@ihateaol.co.uk>
To: Marco Gulino <rockman81@tin.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3: lilo warnings
Date: Wed, 18 Feb 2004 23:08:25 +0000 [thread overview]
Message-ID: <4033F069.1050206@ihateaol.co.uk> (raw)
In-Reply-To: <200402182353.41899.rockman81@tin.it>
Marco Gulino wrote:
> Hi! When i upgraded from linux kernel 2.6.2 to 2.6.3 i get these warnings when
> i run lilo... my system is all ok, however, i'm only reporting these
> warnings.
> My distro is GNU/Linux Slackware 9.1
> Thanks :-)
>
> bash-2.05b# lilo
> Warning: '/proc/partitions' does not match '/dev' directory structure.
> Name change: '/dev/ram8' -> '/tmp/dev.0'
> Warning: '/dev' directory structure is incomplete; device (1, 8) is missing.
> Warning: '/dev' directory structure is incomplete; device (1, 9) is missing.
> Warning: '/dev' directory structure is incomplete; device (1, 10) is missing.
> Warning: '/dev' directory structure is incomplete; device (1, 11) is missing.
> Warning: '/dev' directory structure is incomplete; device (1, 12) is missing.
> Warning: '/dev' directory structure is incomplete; device (1, 13) is missing.
> Warning: '/dev' directory structure is incomplete; device (1, 14) is missing.
> Warning: '/dev' directory structure is incomplete; device (1, 15) is missing.
> -
I also upgraded from 2.6.2 to 2.6.3 on Slack 9.1 today and received no
such warnings. What's in your lilo.conf?
next prev parent reply other threads:[~2004-02-18 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 22:53 2.6.3: lilo warnings Marco Gulino
2004-02-18 23:08 ` Kieran [this message]
2004-02-18 23:21 ` Marco Gulino
2004-02-18 23:08 ` Jens Bäckman
[not found] <1qIZy-6b9-25@gated-at.bofh.it>
[not found] ` <1qJsI-6Be-55@gated-at.bofh.it>
2004-02-18 23:56 ` Marco Gulino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4033F069.1050206@ihateaol.co.uk \
--to=kieran@ihateaol.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rockman81@tin.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox