[Pkg-ltsp-devel] next upload

Vagrant Cascadian vagrant at freegeek.org
Mon Sep 4 09:49:42 UTC 2006


so, i'd like to push some things into pkg-ltsp main branch in
preparation for another upload...

http://llama.freegeek.org/~vagrant/bzr/ltsp/vagrant-main

  * ltsp-server:
    - prefer tftpd-hpa over atftpd, as it works out of the box
    - only run rc whitelisting code if something is whitelisted
    - ltsp-update-sshkeys:
      + only update directories with an /etc/ssh directory
    - bug reporting helper script to get package versions from chroot(s)
    - basic documentation of:
      + swap
      + plugins
      + anonymous workstation-style install
    - updated ltsp-build-client manpage:
      + removed ubuntu-centrism (Closes: #385885)
      + removed obsolete and distro-specific options
      + re-worded much of the text
  * ltsp-client:
    - bugfixes with /etc/hosts and /etc/hostname
    - man page for getltscfg
  * ldm:
    - merge localdev support from ubuntu
    - only enable ssh socket if localdev is configured
    - manpage for ldm

(in addition to the other things already in pkg-ltsp main)

i tested the localdev support today. it seems to at least partially
work, but it requires ltspfs/ltspfsd packages. i pulled the ubuntu
sources and built them on sid, and they seem to basically work.


i think we could upload new packages with just the above + pkg-ltsp
main, but consider these, too:

http://llama.freegeek.org/~vagrant/bzr/ltsp/features/vagrant-ltsp-plugins

this splits the load_plugins function out of ltsp-server into a file
that can be sourced, and moves the plugins into
/usr/share/ltsp/plugins/ltsp-build-client, to make it possible for other
scripts to start using the same plugins system.


http://llama.freegeek.org/~vagrant/bzr/ltsp/features/vagrant-ltsp-swap

includes support for encrypted swap with cryptsetup, NBD or local.
the one thing i don't like about this is that the nbd-client's init
script is ran after ours, so i manually called nbd-client from
ltsp-client's init script. we could possibly move ltsp-client's init
script to later in the process to implement it more properly.


http://llama.freegeek.org/~vagrant/bzr/ltsp/features/vagrant-ltsp-locale

plugin to set up the chroot with locales installed on the server. that
was pretty easy. still need to remove some of the hard-coded calls that
set LC_ALL before doing things in the chroot, as any that run after the
plugins stuff should be able to run with proper localization :)


also, currently our support for architectures other than i386, amd64,
powerpc, alpha and sparc is pretty poor. no kernels get installed, and
there's nothing that helps with creating network bootable images
installed. would this be the sort of thing to document in README.Debian?
(i also have theoretical patches for ia64 and hppa, based on:
http://bugs.debian.org/302638)


live well,
  vagrant



More information about the Pkg-ltsp-devel mailing list