From: Peter <peter.repliesignored@rimuhosting.com>
To: Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [patch 3/4] uml: remove most devfs_mk_symlink calls
Date: Tue, 23 Nov 2004 16:09:23 +1300 [thread overview]
Message-ID: <41A2A9E3.9070203@rimuhosting.com> (raw)
In-Reply-To: <200411222325.17269.blaisorblade_spam@yahoo.it>
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"? 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?
Regards, Peter
Blaisorblade wrote:
> I'd suggest to also stop using /dev/ubd/0 symlinks and going directly
> to /dev/ubd/disc.../disc (whatever), since the first one could soon go away
> (I've deferred that at least for now).
>
> Bye
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-11-23 3:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 1:13 [uml-devel] [patch 3/4] uml: remove most devfs_mk_symlink calls blaisorblade_spam
2004-11-22 14:43 ` [uml-devel] " Nuutti Kotivuori
2004-11-22 22:25 ` Blaisorblade
2004-11-23 3:09 ` Peter [this message]
2004-11-23 14:36 ` Nuutti Kotivuori
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=41A2A9E3.9070203@rimuhosting.com \
--to=peter.repliesignored@rimuhosting.com \
--cc=blaisorblade_spam@yahoo.it \
--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