lkml.org 
[lkml]   [2000]   [Jul]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: RLIM_INFINITY inconsistency between archs
Date
Followup to:  <20000727223737.2722.qmail@t1.ctrl-c.liu.se>
By author: wingel@t1.ctrl-c.liu.se
In newsgroup: linux.dev.kernel
>
> In article <200007272122.RAA04791@tsx-prime.MIT.EDU> tytso@MIT.EDU wrote:
> >That certainly makes a lot of sense; I've alwyas thought it was a bit
> >odd that some stuff was in /lib/modules and Systemp.map and bzImage are
> >stored in /boot. My guess is this is because Linus doesn't use modules,
> >so he doesn't see this particular aesthetic fault. :-)
>
> There is one very good reason for putting the bzImage in /boot,
> older BIOS:es have trouble with cylinders >1024 so I've almost
> always but /boot on its own partition below 1024 cylinders and
> have made it as small as possible, so even putting System.map
> there is a mistake really, so I'd rather se System.map in
> /lib/modules/`uname -r`.
>

bzImage needs to be in /boot. System.map and vmlinux does *NOT* need
to be in /boot. Recent modutils support storing them in
/lib/modules/`uname -r`/kernel.

-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:57    [W:0.047 / U:0.656 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site