richard at reika.demon.co.uk
Sun Jan 28 06:09:51 PST 2001
Misquoted from Bryan Dumm:
> Subject: user profiles
> User profiles again.... I got some basic ideas below, and I
> would like to start building up a list of suggestions. One
> of the questions I have is how would General or Specific
> Preference xml structures look like or work????
> Anyways, looking for comments.
Please imagine the smiley of you choice in each paragraph ;-)
I tried keeping general information in a configuartion file. The
result quickly became too complicated. Think about how you would
generate the following files/links from a profile:
This is a subset of the files/links I have modified to my
taste. Perhaps you prefer BIND or procmail. Do you want to
support getting data from the profile to all the possible
I manage all this data with tarballs of configuration
files - one for each site, and one for each host. Alfs
could then manage all of the above from just the host
name, site name, and path to the tarballs - I keep
them in the same tree as my source code. Host specific
takes priority over site specific. Site specific takes
priority over application default.
The tarballs are made with three files - site_list
is a list of files to be packaged into the site tarball.
host_list packages stuff for any host, and does not care
about missing files. del_list deletes some clutter that
I do not use - eg /etc/access.conf.default from apache.
I did find four packages that could benefit from such
data, but I could now get that data out of /proc or
/dev with kernel 2.4.0
cdda2wav interface_type cdrom_dev_file cdrom_bus_id sound_dev
Target install directory
Place where packages are built. (I do not have much
space left for things in /usr/src, but my work partition
will be empty during an LFS build
list of (device, fstype) to make new file systems on before
starting to compile. I am not brave enough to add data for
list of (devives, fstype, mountpoint) to mount before starting
path to directory tree full of source code
Do you want some idea of whick packages installed which file?
How do you want to collect that data?
May be better off with soething like /etc/profile
LINGUAS, LANGUAGE, LC_ALL, LANG, CFLAGS, CPPFLAGS,...
List of stuff like:
localedef -i en_GB -f ISO-8859-1 en_GB
localedef -i en_US -f ISO-8859-1 en_US
The next thing to handle is a list of extra packages.
In the past I had difficulty keeping track of which
ones are not installed on a host because they are not
needed, and which ones are not installed because I
had not set up automatic installation last time I
updated that host.
My answer is for each host:
a list of packages to install
a list of packages to reject
And a global list of packages. It is trivial to remove
the packages in the first two lists from the third to
see what changes I should make to a hosts install lists.
This will get a bit more complicated with package groups
like kde or gnome.
Unsubscribe: send email to alfs-discuss-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message
More information about the alfs-discuss