From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net,
stefano.melchior@openlabs.it
Cc: Mattia Dongili <malattia@linux.it>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] [RFC][PATCH] include /usr/lib/uml in PATH
Date: Wed, 19 Apr 2006 11:52:10 +0200 [thread overview]
Message-ID: <200604191152.10992.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20060409125221.GB7503@SteX>
On Sunday 09 April 2006 14:52, Stefano Melchior wrote:
> On Fri, Apr 07, 2006 at 06:52:05PM +0200, Mattia Dongili wrote:
> Dear all,
> > > > > #define UML_LIB_PATH ":/usr/lib/uml"
> > > > what about a config option instead? CONFIG_UML_NET_PATH
> > > Don't think so, that's not supposed to be changed according to any
> > > config option or I can't see that. Unless on 64-bit system that's
> > > /usr/lib64/uml, and in that case it makes sense to have CONFIG_XXX =
> > > "/usr/lib/uml" (without :, add them only in the source, i.e. insulate
> > > details away).
> > Yes, that was what I meant. However it's probably not worth the effort
> > yet.
> > Description:
> > append /usr/lib/uml to the existing PATH environment variable to let
> > execvp search uml_net in FHS compliant locations.
>
> at this point, is it the case to have also this patch for the
> uml-utilities in order to install uml-net directly on the FHS complaint
> path (uml-net):
It is likely a correct patch (didn't proof-read, seems very reasonable) but:
a) make sure it can work on amd64 (/usr/lib or /usr/lib64?)
b) I'll do this in at least 6 months from now, or users will scream - or I'll
add a compatibility symlink in /usr/bin for a while.
Debian did it the hard way IIRC (don't remember if only for the default
location of uml_switch socket or also for this), and problems resulted for
people with self-compiled kernels.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
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:[~2006-04-19 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 17:34 [uml-devel] [RFC][PATCH] include /usr/lib/uml in PATH Mattia Dongili
2006-04-02 18:29 ` Geert Uytterhoeven
2006-04-02 19:54 ` Mattia Dongili
2006-04-04 0:39 ` Blaisorblade
2006-04-05 21:11 ` Mattia Dongili
2006-04-07 6:45 ` Blaisorblade
2006-04-07 16:52 ` Mattia Dongili
2006-04-09 12:52 ` Stefano Melchior
2006-04-19 9:52 ` Blaisorblade [this message]
2006-04-19 19:07 ` Mattia Dongili
2006-04-21 18:34 ` Blaisorblade
2006-04-21 21:18 ` Blaisorblade
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=200604191152.10992.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=geert@linux-m68k.org \
--cc=jdike@addtoit.com \
--cc=malattia@linux.it \
--cc=stefano.melchior@openlabs.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