From: "werner" <w.landgraf@ru.ru>
To: linux-kernel@vger.kernel.org, mjt@tls.msk.ru
Subject:
Date: Fri, 13 Jul 2012 20:49:45 -0400 [thread overview]
Message-ID: <web-769674809@zbackend1.aha.ru> (raw)
Since years I use the same routine for compile / link /
package the kernel. Until now, rdev gave and wrote always
the boot device in the form /dev/... , not as the bios
number. This problem starts now only. So I suppose there
was anything changed, either on the kernel or in one of
the kernel-near basic routines (such as, rdev itself)
I agree that the bios device numbers are not good for
identify installations or devices, as they can change, if
one change the BIOS boot order, or if one only change via
F12 the actual boot order, or even if one stick in an usb
key before booting; specially it changes after one install
Linux from an USB key. Just because of this I use the
/dev/... names for lilo and for the kernel command line.
rdev may be obsolete, but it's one of the oldest functions
and used in many install systems, so that for
compatibility it should be kept, nor be changed.
---
Professional hosting for everyone - http://www.host.ru
reply other threads:[~2012-07-14 0:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=web-769674809@zbackend1.aha.ru \
--to=w.landgraf@ru.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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