[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How big will the 32-bit chroot end up being? What goes in these days?



On Fri, Jan 27, 2006 at 09:50:10AM +0100, Helge Hafting wrote:
> Thomas Steffen wrote:
> 
> >On 1/23/06, cmetzler@speakeasy.net <cmetzler@speakeasy.net> wrote:
> > 
> >
> >>So, as I understand it, the following stuff would need to go into the
> >>32-bit chroot (assuming one wants/needs these things):
> >>
> >>- Sun's J2RE
> >>
> >>- OpenOffice
> >>
> >>- Flash
> >>
> >>- RealPlayer/Helix/whatever
> >>
> >>- win32codecs + other misc A/V codecs one might scrounge up elsewhere
> >>
> >>- Any web browser that you want to be able to use Java/Flash/embedded
> >>AV stuff in
> >>
> >>- the Acrobat Reader
> >>
> >>- cdrecord/cdrdao plus whatever front end you're using to call them
> >>
> >>Is that correct?  Anything I'm missing?
> >>   
> >>
> >
> >Don't forget all the dependencies that all pulled in by these apps.
> >You might end up with nearly a typical Linux installation.
> > 
> >
> Not quite that bad.  There is no need for the xserver for example,
> as the 32-bit processes have no problem talking to the 64-bit server.
> And of course the chroot don't need any utilities, bootup scripts,
> window managers, printing subsystem, login software . . .

You will need the printing client software, however.  I discovered that
when I tried to print from OO the other day.

Cheers,

a



Reply to: