[Grml-devel] About the new grml direction

[Christian Hofstaedtler]

* Marc Haber <mh+grml-devel at zugschlus.de> [120101 23:45]:
> On Sun, Jan 01, 2012 at 11:10:40PM +0100, Ulrich Dangel wrote:
> > * Marc Haber wrote [01.01.12 22:33]:
> > > Loading an 350 MB image to RAM takes considerably more time than an
> > > 130 MB image. 
> > 
> > You can load the image into ram after you started it via the command
> > grml2ram. This means you can copy it to ram while already working.
> 
> Nice idea. How about an option to copy to ram in the background?
> 
> What do I do on old systems that only have 512 MB RAM?

Use an old release.

> > > Additionally, on my typically 1 GB large boot, I was
> > > able to place to grml-small images in addition to the normal /bot
> > > contents. I was already forced to resize /boot on my notebook because
> > > of grmls size increase.
> >  
> > As i said before you can place the grml iso images on a dedicated LVM lv
> > or on raid and use that for mounting the isos. Stacked setups will work
> > also (LVM on raid)
> 
> That doesn't help too much for systems that are already installed.

1GB is enough for kernels, initrds and Grml.
Also, nothing forces you to put Grml into /boot. Choose something
else if you can.

Generally speaking, having /boot seperate from / is one of those
legacy errors that need to die.

  -ch

-- 
christian hofstaedtler