[Pkg-ltsp-devel] 0.82debian2 - what's coming?

Vagrant Cascadian vagrant at freegeek.org
Tue Mar 7 19:20:41 UTC 2006


On Tue, Mar 07, 2006 at 02:03:06PM -0300, Gustavo Franco wrote:
> On 3/7/06, Otavio Salvador <otavio at debian.org> wrote:
> > "Gustavo Franco" <gustavorfranco at gmail.com> writes:
> >
> > > revno: 251
> > > committer: Gustavo Franco <stratus at debian.org>
> > > branch nick: ltsp--stratus
> > > timestamp: Tue 2006-03-07 11:34:10 -0300
> > > message:
> > >   add ltsp-client depends on hwinfo, latest xdebc does that but it's
> > > needed for debian sarge
> >
> > Well, I think hwinfo isn't need for detection. Of course it improve
> > the overall detection but isn't a requirement.
> 
> I had the same opinion, but once xdebc in sid is depending on hwinfo
> why we shouldn't add it now? Keep in mind that we can end in a
> scenario that ltsp in a sid chroot will guess the hardware properly
> and with sarge won't, and the fault will be because the hwinfo is
> missing. Yes, i know that it can happen due to others reasons.
 
i want to avoid any dependencies that aren't absolutely necessary.
i'd actually like to move towards a "ltsp-client-core" package, to
provide the absolute basic diskless client functionality, and other
things like X and sound and such are either packages or
commandline/configuration options to ltsp-build-client. the default
could very well be to install everything, but there should be a way to
get a more basic diskless client.

> - The "root=/dev/nfs ip=dhcp" thing:
> It wasn't added in the 'default' file, i grepped the latest ltsp and
> it seems to be there, but i need to read the code carefully and see if
> i did something wrong. The fact is that i upgraded from a older ltsp
> package, i will do from scratch soon.

i think this is part of ltsp-update-kernels, so re-running that should
overwrite and obliterate any changes you have made. i don't
particularly like this behaviour :(

live well,
  vagrant



More information about the Pkg-ltsp-devel mailing list