On Thu, 29 Mar 2001 [EMAIL PROTECTED] wrote:
> On Thu, 29 Mar 2001, David Douthitt wrote:
>
> > Charles Steinkuehler wrote:
> >
> > > The
> > > technique I'm using to run LRP off a HDD root partition is to acutally run
> > > the LRP startup scripts in a chrooted environment, creating a root
> > >
On Sat, 31 Mar 2001 [EMAIL PROTECTED] wrote:
> Well, if you look at the top quote, the suggestion was that it
> has been folded into the main kernel tree; and I don't use
> slack-provided kernels, I download plain kernels from
> kernel.org...not that I think slack patches their kernels
> anyhow.
On Fri, Mar 30, 2001 at 09:03:15PM -0500, George Metz scribbled:
> > > It would appear from discussion here and a search that proconfig was
> > > folded into 2.4; in any case, the most recent versions at the web site
> > > are:
> >
> > I couldn't find it in menuconfig, nor by a recursive, case
> >
On Fri, 30 Mar 2001 [EMAIL PROTECTED] wrote:
> On Fri, Mar 30, 2001 at 08:41:52AM -0600, David Douthitt scribbled:
> > It would appear from discussion here and a search that proconfig was
> > folded into 2.4; in any case, the most recent versions at the web site
> > are:
>
> I couldn't find it in
George Metz wrote:
>
> On Fri, 30 Mar 2001, David Douthitt wrote:
>
> > This wouldn't be the "proconfig" patch would it? With this patch, you
> > can type "cat /proc/config" and it will give you a list of features
> > set, in the form of a Config file for the running kernel.
> > > Fairly neat,
On Fri, 30 Mar 2001, David Douthitt wrote:
> This wouldn't be the "proconfig" patch would it? With this patch, you
> can type "cat /proc/config" and it will give you a list of features
> set, in the form of a Config file for the running kernel.
I honestly am not sure. SuSE doesn't list anywhere
[EMAIL PROTECTED] wrote:
> On Fri, Mar 30, 2001 at 08:41:52AM -0600, David Douthitt scribbled:
> > It would appear from discussion here and a search that proconfig was
> > folded into 2.4;
> I couldn't find it in menuconfig, nor by a recursive, case
> insensitive grep for 'proconfig' in my 2.4.2
On Fri, Mar 30, 2001 at 08:41:52AM -0600, David Douthitt scribbled:
> It would appear from discussion here and a search that proconfig was
> folded into 2.4; in any case, the most recent versions at the web site
> are:
I couldn't find it in menuconfig, nor by a recursive, case
insensitive grep fo
[EMAIL PROTECTED] wrote:
>
> On Fri, Mar 30, 2001 at 06:49:48AM -0600, David Douthitt scribbled:
> > This wouldn't be the "proconfig" patch would it? With this patch, you
> > can type "cat /proc/config" and it will give you a list of features
> > set, in the form of a Config file for the running
Charles Steinkuehler wrote:
> > Um... not quite. You are talking about bootable CDROMs with a
> > configuration disk; I am talking about booting from floppy disk and
> > using the CDROM as a data disk. Your ideas are much more
> > revolutionary than mine.
>
> Actually, I want both to work. My
On Fri, Mar 30, 2001 at 06:49:48AM -0600, David Douthitt scribbled:
> This wouldn't be the "proconfig" patch would it? With this patch, you
> can type "cat /proc/config" and it will give you a list of features
> set, in the form of a Config file for the running kernel.
>
> > Fairly neat, if not
> > The key to making this happen is getting a linuxrc that's smart (or
> > flexible) enough to deal with whatever is required. The other missing
piece
> > is a way to communicate with the CD-ROM boot scripts.
>
> That would be syslinux.cfg; what is needed (sounds like) is a way to
> shift the en
Charles Steinkuehler wrote:
> The chroot thing is a one-time deal to build a root image on the HDD. The
> part you're missing is I'm running LRP WITHOUT a ramdisk, more like
> conventional linux...hopefully I won't be burned at the stake.
A Now I understand. Jeff was so gentle about it
George Metz wrote:
> Perfect example is a feature I found while compiling a 2.4.2 kernel for my
> SuSE server last night. It's an option that I don't ever recall seeing in
> any of the kernels, that stores the kernel's configuration in the kernel
> image itself - at a cost of 1-4k of size - so th
> > The
> > technique I'm using to run LRP off a HDD root partition is to acutally
run
> > the LRP startup scripts in a chrooted environment, creating a root
> > environment that is then simply mounted at the next boot (linuxrc is
> > modified to just exit after loading bootstrap modules if root i
On Thu, 29 Mar 2001 [EMAIL PROTECTED] wrote:
> no patch required. That's the ability that makes LRP kernels different
> from anybody else's kernels [with the possible exception of RH, which,
> AFAIK, has some of their own kernel patches...yuck!].
To the best of my knowledge, the majority of the
On Thu, Mar 29, 2001 at 02:19:09PM -0800, [EMAIL PROTECTED] scribbled:
> probably doesn't make sense. However, there was a post awhile back by
> someone who figured out how to run an unpatched kernel with LRP, so it
An unpatched kernel that would work on a regular LRP ramdisk-root setup?
Obviou
On Thu, 29 Mar 2001, David Douthitt wrote:
> Charles Steinkuehler wrote:
>
> > The
> > technique I'm using to run LRP off a HDD root partition is to acutally run
> > the LRP startup scripts in a chrooted environment, creating a root
> > environment that is then simply mounted at the next boot (l
Charles Steinkuehler wrote:
> The
> technique I'm using to run LRP off a HDD root partition is to acutally run
> the LRP startup scripts in a chrooted environment, creating a root
> environment that is then simply mounted at the next boot (linuxrc is
> modified to just exit after loading bootstra
Well, I'm working on documenting how to run LRP 2.9.8 with root on a HDD,
and it got me thinking about my CD booting images. One of the main things I
can't change on the CD is the size of the ramdisk, since that's a kernel
parameter, and I can't change kernel paramaters on a bootable CD without
r
20 matches
Mail list logo
