KGMD 2.0

[Tamminen Eero <t150315@students.cc.tut.fi>]

> 	0) Provide an "upgrade script" that will back-up a current users
> 	configuration to floppy (eg) for use in installing KGMD 2.0 -
> 	basically files in /etc, /usr/local/lib (for pine, lynx, etc),
> 	/var/spool/mail/*, and anywhere else _WE_ identify. OBVIOUSLY, it
> 	will be up to the user to back up their own personal stuff (you
> 	don't already...??!!!)

The backup script should IMHO be provided only as an example.  I think
users' configurations vary too much for it to be of help without fiddling
(They are installing KGDM to get stuff into standard locations :)).

IMHO a backup script that fails confuses new users more than no backup.
Better let the script rename every file it would overwrite, like this:

filelist = <files to upgrade>
for i in filelist
do
	if [ -e $i ]
	then
		mv $i $i.orig
	fi
done
tar -zxvf /a/upgrade.tgz

If users wants to backup the files later, something like this could
be used:  tar -zcvf /a/backup.tgz -C / `find -name *.orig -print`
when user will have the tools to do this (find etc).


> 	1) FHS documentation states that the various filesystem
> 	(partition) components be kept to a reasonable size. Ideally,
> 	this means, as part of this new distribution, the opening
> 	(instruction) documentation should instruct the user to create
> 	various partitions on a hard disk. Many users will not want to do
> 	this (I expect), so an alternate method will be provided. But many
> 	will, so suitable partition sizes will need to be determined, eg
> 	(completely random figures - plucked from the air about me) 5Mb
> 	for the root filesystem, 20Mb for /home, etc, etc...
> 
> 	2) root.tgz - this will be the bare bones for booting ONLY: /bin,
> 	/sbin, /etc, /root will contain binaries and configuration files
> 	as layed out by the FHS documentation.

After you got the packages made, you'll know how much at least is needed ;-)


> 	Q a. Should inetd and friends reside in /sbin?

/sbin is on the root partition where should be only the files needed
for booting the system up (in different configurations) and fixing
errors (fsck).  Inetd offers services *to* network so the answer
would be no.


> 	Q b. Should there be provision for an alternate hostname during
> 	single user boot?

?

> 	8) (Probably more important than I've numbered it) Multilingual
> 	support. I believe the man pages/documentation could be done as
> 	deutsch.tgz, english.tgz, francais.tgz, italiano.tgz, etc...

I doubt we got enough/interested people for translating man pages.  That
should IMHO be left for the larger freeware/GPL communities. Translating
the most important installation documents (MiNT, MiNTNet, FHS etc)
would be good though if there just are volunteers.


	- Eero