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

[debian-knoppix] Feature ideas/suggestions



	I've been playing around with some slightly different Knoppix uses
lately, and came up with these ideas which I think will work well in the
official version.  I could probably do most of these myself, but some of
them are pretty easy to implement too.

---

Compressed hd installation mode:

	I set up knoppix on a 1GB CF for my firewall/terminal server
machine, and hence I had to keep the knoppix filesystem compressed.  I was
able to use this partition scheme:

	hda1 - 2MB FAT partition with the contents of the boot 'floppy'
image.  syslinux.cfg modified to scan for config and home.  I used
syslinux to make this bootable.

	hda2 - 768MB ext2 filesystem, which has my remastered knoppix
(regular knoppix would work in this setup too - I took 5/20 and updated
the debian packages and added transcode, ffmpeg, and mplayer)

	hda3 - ~180MB ext3 persistent home, in non-file mode.

	hda4 - ~20MB ext3 filesystem with config files.  This is a bit of
an overkill and could be merged with a slightly larger hda1, since the two
files' names would work in vfat, presumingly.

	If this installation setup could be scripted, it would be good for
knoppix terminal servers and machines with 1-2GB of hard drive space, or
1GB CF cards.

Persistent home:

	- Perhaps it should use the -j option to add journaling (ext3)
with mke2fs, which would make recovering from an unclean reboot much
faster.  It's easy enough to run "tune2fs -j" later, however.  (got this
idea from the forum)

	- Make scanning work with direct filesystems.  This could be done
by adding a .knx_persistanthome file to the top directory of the
partition. 

Other features:

	- Ability to easily disable auto-reboot once the X session is
closed.  My remaster accidently did this by having a S99kdm init file,
although since the default does not have passwords assigned it's slightly
awkward - however I use saved configs and persistent home on the terminal
server clients anyway.

	- Perhaps home=scan and myconfig=scan should be default for
terminal server clients?  Then a user could easily use an external flash
device for such.  Handling network configuration might be a bit dicey,
however.

	- Terminal server init could make files in /etc/rc[5?].d so that
it would automatically come up if someone saves the config.  I've noticed
that the terminal server config would be saved along with /etc.

---

	Thanks for making such a useful package,

	- Chad
	

_______________________________________________
debian-knoppix mailing list
debian-knoppix@linuxtag.org
http://mailman.linuxtag.org/mailman/listinfo/debian-knoppix


Reply to: