Re: [Ltsp-discuss] LTSP GUI GSOC project status and meeting minutes June week 3

jam <[email protected]>
Newsgroups gmane.linux.terminal-server.devel
Message-ID <[email protected]>
On Sunday 29 June 2008 03:00:53 ltsp-developer-request-5NWGOfrQmneRv+LV9MX5uv+2+P5yyue3@public.gmane.orgt 
wrote:
> > My client (a via EPIA) dies [utterly dead] during the initrd
> >    I took the initrd and vmlinuz from a working ubuntu
> >         it works but chokes on the squash image
> >    I took the squash image from my ubuntu and it works
> >
> > I not sure about this: Dies after
> > ...
> > Free unused kernel memory ...
> > Write protect kernel data ...
> > input: PS/2 mouse etc
> > ------------------------------ dead [no key led, no keyboard, no net
> > activity]
>
> Someone has reported this before in a VIA TC, unfortunately none of
> the hardwares we've tested has this problem, so we cannot debug it.
> The TC has to be minimum 128M RAM, ideally 265M, and supported by i586
> kernel.

The TC has 512M. I don't know what level of x86 the VIA cpu is. I CANNOT build 
ubuntu (Fiesty Gutsy or Hardy) on those machines but SuSE10.3 installs fine.

> > I've not downloaded the DVD, but I can't find WHAT kernel or how the
> > initramfs is built on KIWI-anywhere (I've looked at repos and opensuse
> > from the .ymp files)
>
> Run kiwi-ltsp-setup without any arguments, it will list all the
> switches available, there are a couple of switches for building
> initrd. You'd need i586 DVD if you intend to build images.
>
> See /usr/share/kiwi/image/netboot/suse-11.0/config.xml and
> suse-linuxrc there, that description is used for creating the initrd.
>
> > Is there enough info to guide an-old-fart like me through the initramfs
> > build for kiwi-ltsp so I can debug what is wrong?
> >
> > Question <a la Warren <smile>>
> > Why has KIWI made such a mess in /srv/tftboot
> > surely at least a ltsp maybe even ltsp/i386 ?
>
> Check out /usr/share/doc/packages/kiwi/kiwi.pdf for the structure of
> /srv/tftpboot used by KIWI.
>
> KIWI-LTSP is in /srv/kiwi-ltsp and /srv/kiwi-ltsp-nfs, openSUSE puts
> all services together in /srv, easier to find that way, and "more" FHS
> compliant ;)

> > Also that would make the dhcpd.conf filenames the same.
>
> Why would anyone want it another?

I have ubuntu machines [everybody served by my central DHCP server]. Filenames 
are /pxelinux.0 for suse and /ltsp/i386/pxelinux.0 on ubuntu, but I also use 
TC-mythtv http://www.linpvr.org/ so it's nice to keep some order 
in ..tftpboot ie ltsp myth etc.

All very minor, as I contemplate how I might use this

Again many thanks, I'll feedback what I can find re Via
James

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.