public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: sl@whiskey.fireplug.net (Stuart Lynne)
To: linux-kernel@vger.rutgers.edu
Subject: Re: RLIM_INFINITY inconsistency between archs
Date: 28 Jul 2000 13:56:40 -0700	[thread overview]
Message-ID: <8lss28$v2e$1@whiskey.fireplug.net> (raw)
In-Reply-To: Pine.LNX.4.21.0007280808460.73-100000@rc.priv.hereintown.net

In article <Pine.LNX.4.21.0007280808460.73-100000@rc.priv.hereintown.net>,
Chris Meadors <clubneon@hereintown.net> wrote:
>On Thu, 27 Jul 2000, Thomas Molina wrote:
>
>> No I'm not kidding.  Based on some comments by Linus earlier, he is
>> advocating putting the kernel source tree out of the way of glibc and
>> other "standard" development tools.  /usr/local seems a better fit to me
>> than /lib/modules.  According to FHS /lib is for essential shared
>> libraries and kernel modules.  It also says one of the uses of
>> /usr/local is for local source code.  It's also one of the few places
>> which shouldn't get clobbered in a system software upgrade.
>
>FHS also says that a distro should ship with nothing in the /usr/local
>tree.
>
>But the FHS also says you can't have things like /usr/apache.  But I find
>that most useful, as deleting one directory removes all traces of the
>program.  Large packages that would normally end up all over the place can
>be contained (like X, which FHS does allow to have its own place under
>/usr).

You can do that in /opt or /usr/local if you like. 

>> It was an opinion; I'm expressing my 'druthers, if you will.  I know
>> others don't agree.  I see where it looks as if Linus is leaning towards
>> /lib/modules anyway, so I'll adapt.  Or I'll be contrary and make
>> appropriate local changes in the source code.  As long as Linus keeps it
>> as a self-contained entity it won't matter anyway.
>
>/lib/modules seems good enough.  But as somone else said, it might make
>more sence to be /lib/kernel.  The one problem I see with this, is I
>usually have a small(ish) root partition.  On any installation I've done
>/lib has never had its own partition.  And on most, the root partition
>hasn't been big enough to hold an unpacked kernel tree.

/lib/modules is probably the easiest place to get some agreement. The
contents of that directory is not specified as of FHS 2.1. 

This discussion should probably be done on the FHS list so that the
results can written up in that document. It currently mandates that
(for example) /usr/include/linux points at /usr/src/linux/include/linux.

-- 
                                            __O 
Fireplug - a Lineo company                _-\<,_ 
PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 (_)/ (_) 88 EC A3 EE 2D 1C 15 68
Stuart Lynne <sl@fireplug.net>       www.fireplug.net        604-461-7532

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

       reply	other threads:[~2000-07-28 20:49 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0007280808460.73-100000@rc.priv.hereintown.net>
2000-07-28 20:56 ` Stuart Lynne [this message]
2000-07-28 20:13   ` RLIM_INFINITY inconsistency between archs clubneon
2000-07-31 17:31 Jesse Pollard
     [not found] <20000728112353Z160228-16385+645@vger.rutgers.edu>
2000-07-31 15:26 ` Kai Henningsen
2000-08-01  7:53   ` David Howells
2000-08-01 18:15     ` Kai Henningsen
2000-08-02  6:52     ` wingel
     [not found] <200007271459.KAA04701@tsx-prime.MIT.EDU>
     [not found] ` <200007271531.KAA89926@tomcat.admin.navo.hpc.mil>
2000-07-31 14:57   ` Kai Henningsen
2000-07-31 17:35     ` Richard B. Johnson
2000-07-31 20:06       ` Mike Galbraith
2000-07-31 21:15       ` Miquel van Smoorenburg
2000-07-31 21:49         ` Richard B. Johnson
2000-07-31 22:39           ` Miquel van Smoorenburg
2000-07-31 22:13         ` H. Peter Anvin
2000-07-31 22:33           ` Miquel van Smoorenburg
2000-08-01  0:17             ` H. Peter Anvin
2000-08-01  0:43               ` wingel
2000-08-01  1:00                 ` H. Peter Anvin
2000-08-01  2:06                   ` wingel
2000-08-01  9:36               ` Miquel van Smoorenburg
2000-08-01 17:03                 ` H. Peter Anvin
2000-08-01 21:50                   ` Miquel van Smoorenburg
2000-08-01  2:18           ` Mike Castle
2000-08-01  2:30             ` wingel
2000-08-01 23:55               ` Mike Castle
2000-08-02  0:18                 ` H. Peter Anvin
2000-08-02  9:28                   ` Miquel van Smoorenburg
2000-08-04  1:07                     ` H. Peter Anvin
2000-08-01 17:03             ` H. Peter Anvin
2000-08-01  2:11         ` Mike Castle
2000-08-01  9:38           ` Miquel van Smoorenburg
2000-08-01 23:44             ` Mike Castle
2000-08-02 18:16     ` peter swain
     [not found] <FyFI8n.IpM@spuddy.mew.co.uk>
2000-07-29 10:34 ` Stephen Harris
     [not found] <200007281315.OAA30398@flint.arm.linux.org.uk>
2000-07-29  1:09 ` David Howells
     [not found] <200007272122.RAA04791@tsx-prime.MIT.EDU>
     [not found] ` <m2hf9bnm95.fsf@euler.axel.nom>
     [not found]   ` <20000728162225.A4317@saw.sw.com.sg>
2000-07-29  0:51     ` Mike Castle
     [not found] <no.id>
2000-07-28 22:10 ` Adam Sampson
2000-07-28 22:20 ` Adam Sampson
2000-07-29 13:23   ` Miquel van Smoorenburg
     [not found] <3981ED0C.CBE0A0F9@transmeta.com>
2000-07-28 21:02 ` Khimenko Victor
     [not found] <E13HsBT-00033e-00@the-village.bc.nu>
     [not found] ` <200007281405.JAA101655@tomcat.admin.navo.hpc.mil>
2000-07-28 14:11   ` Jamie Lokier

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='8lss28$v2e$1@whiskey.fireplug.net' \
    --to=sl@whiskey.fireplug.net \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=sl@fireplug.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