From: Blaisorblade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Peter <peter@rimuhosting.com>
Subject: [uml-devel] About DevFS
Date: Tue, 23 Nov 2004 19:00:40 +0100 [thread overview]
Message-ID: <200411231900.40463.blaisorblade_spam@yahoo.it> (raw)
On Tuesday 23 November 2004 04:09, Peter wrote:
> How will this affect existing UML setups? Does it mean they would need
> to change if we started them up with a new UML kernel after /dev/ubd/0
> "goes away"?
The other name (see the FAQ on my page to know which one, linked in my
signature) - is available also in the old instances (both 2.4 and 2.6).
> That would mean quite a disruption to operations (i.e.
> making changes on lots of UML instances). Is there a way to acheive
> what you're doing in a backwards-compatible manner?
The other name always exists, even on older instances, so the new syntax is
backward compatible.
However, I hope the removal of /dev/ubd/0 symlinks can be deferred, so that
you don't need to rush on this (I'm not sure of this - I don't care, but
there are other developers complaining). At least, I need to update the Uml
page.
That said, DevFS is unstable (not in UML, but in general), so people should
start switching away from it.
Using devfsd probably helps the transiction (i.e. you start using the
"standard" non-devfs names without removing access to the DevFS ones until
you complete the transiction).
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
reply other threads:[~2004-11-23 17:58 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=200411231900.40463.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=peter@rimuhosting.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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