Re: Simplist way to boot only to a shell

Hello,

I had this working in early January.  Now for some
unknown reason I get an error from cpio
about not enough space.  All I changed in
the building dist area was a small shell script
by perhaps 200 bytes size.

I run:
# pxesconfig -c my.conf -i my.initrd --initialize
--dontreadconfiguration --druid=0
Initializing ram disk.
Fatal error:
cpio: write error: No space left on device

Looking at /tmp/pxes.initrd size it is 17 MB
If I mount it, it does show 100% full.  What can
I use to configure the initialized size?

I tried some values for INITRD_FSSIZE=
in my.conf but it didn't seem to make
a difference.

My temporary workaround was to uncompress
my last good my.initrd, mount it, and copy in
my new shell script.  That worked OK.
But I'd like to better understand what is
doing wrong with doing it the normal way.

One other change is that my system kernel
(not used by PXES) is changed to a newer one,
but still in 2.4 land.  Is there any thing in my
kernel environment that could impact this?
It is mainly a make oldconfig build, compared
to the previous, from what I remember.

I'm working with pxes-0.9 .  pxesconfig v 1.36 2004/08/06 04:01:54 diego

--Donald Teed

On Mon, 27 Dec 2004 14:04:56 -0300, Diego Torres Milano <[email protected]> wrote:
> There are other ways of obtaining this but I would do:
> 
> # pxesconfig -d my.conf
> 
> # vi my.conf
> # set this
> CUSTOM='/bin/sh'
> SESSION_CUSTOM='1'
> SESSION_DEFAULT='custom'
> WINDOW_MANAGER=''
> # check also that X_SESSION_* is set to 0
> # disable other thins you don't want to be included
> 
> # pxesconfig -c my.conf -i my.initrd --squashed=my.squash --initialize
> --dontreadconfiguration --druid=0
> 
> Voila !
> A 3.8 MB image.
> 
> 
> On Thu, 2004-12-23 at 16:02, Donald Teed wrote:
> > I only want the PXES to bring up a shell enivironment, no special clients
> > or graphical interfaces.  Rather than tracing the logics of the init.d area
> > I thought I'd ask here...
> >
> > What is the cleanest way to get PXES to boot only to a shell?
> >
> > Is there a point in the rcS where is it safe to place an 'exit' and
> > arrive in a shell, or is there another way to approach this?
> >
> > I don't need any services running on ths client, nor printer or sound
> > support.  I just need network and local hard drive support.
> >
> >
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real users.
> > Discover which products truly live up to the hype. Start reading now.
> > http://productguide.itmanagersjournal.com/
> > _______________________________________________
> > pxes-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/pxes-devel
> --
> Diego Torres Milano <[email protected]>
> PXES Universal Linux Thin Client
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> pxes-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pxes-devel
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click