Re: tazx problem

[Indigo <pointofavailability@xxxxxxxxx>]

Also, i don't see a problem with the way things work for package
configs.  I think it's more desirable to let each package create it's
own /home files for each user.  This would give a new user default
settings, rather than copying someone else's personal data - this is
especially true of programs like firefox, where you may not want a new
user to automatically get your bookmarks, for instance.  As far as I
know, there is no issue with packages creating their own configs on
first run.


On Fri, Nov 12, 2010 at 10:28 PM, Indigo <pointofavailability@xxxxxxxxx> wrote:
> /etc/skel is needed to install the system, as much as I wish it didn't
> have to exist.  It's also used to generate a new iso, though there
> might be better options there.  My thought is that /root should be
> populated with these files, and .xinitrc should not be created each
> time by tazx.  If slim were to default to using the /root directory,
> then .xinitrc could be a pre-installed system file, and it could take
> on the responsibility of copying the necessary config files, if they
> don't already exist, so that tazx and tazctrlbox would not have to
> both be run when a new user is created.  A new user, even using
> adduser, would not need to have any files in the /home directory to
> start -- tazx would only be responsible for installing/reconfiguring
> xorg, and tazctrlbox would only be responsible for global settings.
> This makes sense because the $USER variable persists (echo $USER is
> accurate before and after running tazx, just not during)... so, let
> tazx configure root only, let slim login_cmd='exec /root/.xinitrc',
> and let .xinitrc check to see what user is logging in and if any
> config files need to be copied.  This makes sense, also, because it
> would be easier to edit /root for global defaults, while still
> allowing configurations to be altered on a per user basis.  The only
> problem with this that I can think of is if /root files are changed,
> the changes wouldn't be reflected in pre-existing /home
> configurations... but that could be worked out, I'm sure.  Anyone have
> any thoughts on this idea?
>
>
> On Fri, Nov 12, 2010 at 9:46 PM, guilbault frederic
> <fredericguilbault@xxxxxxx> wrote:
>> hi
>> this discusion, make me think about why a skel in a live cd ?
>>
>> can we find a way to save some Ko of iso or ram space around it ?
>>
>>
>> fred
>>
>>> Date: Fri, 12 Nov 2010 12:19:30 +0100
>>> From: gokhlayeh@xxxxxxxxxx
>>> To: slitaz@xxxxxxxxxxxxxxxxxxx
>>> Subject: Re: tazx problem
>>>
>>> Hi all,
>>>
>>> We (indigo and me) already spoke about /etc/skel on IRC, here's what I
>>> remember :
>>>
>>> * /etc/skel doesn't contains all needed files. It's an issue when creating
>>> a new user.
>>> * /etc/skel is used only at user creation, this implies the following
>>> issue :
>>> * if you remove a config file in the home of an existing user, it's doesnt
>>> rollback to /etc/skel config, but to default config. I.e. : it's better to
>>> put the firefox default config in the system dir than in the /etc/skel
>>> because at launch time firefox use the system dir to get default config if
>>> no config exists.
>>> * if you install something which use /etc/skel (let's say
>>> slitaz-xfce4-config) it will be used to populate new users home but not
>>> existing users home.
>>>
>>> Solutions can be :
>>>
>>> • copy the /home]] files from another user (root or tux); there's an issue
>>> with this : it's doesn't use default config if the user modified his config
>>> files.
>>> • add some lines in tazpkg to force it to copy all files in /etc/skel to
>>> all users home at package installation time - solve the second issue.
>>> • add two options in users management - or one of theses two - to solve
>>> partially the first issue :
>>> * get default config : copy a new time /etc/skel in user home and
>>> reconfigure x with tazx.
>>> * reset config entirely : remove all config files and put the default one
>>> in user home.
>>>
>>> In addition, I want to say here that a new variable in receipt can be
>>> usefull in slitaz : USER_CONFIG_FILES="...". Storing the path of user config
>>> files can give us some new possibilities : remove package & config files,
>>> remove config files of deleted packages, reset config files per package,
>>> backup all user config files -or per package- and eventually populate
>>> /etc/skel with it. I know that adding this is a lot of work, so I just want
>>> to submit the idea; Maybe we can think about for a next SliTaz release (I
>>> don't know your opinion, adding this for 4.0 seems me difficult).
>>>
>>> So, I think that we need to use /etc/skel anyway to get default config of
>>> some apps, like openbox or pcmanfm etc.
>>>
>>> About adduser :
>>> Maybe we can user a wrapper : a little script instead of the adduser
>>> busybox. It can create the user with busybix adduser, then copy/paste the
>>> skel and setup the default config with tazx.
>>>
>>> Hope this help.
>>>
>>> P.S.: indigo, if you remember something else please tell us.
>>>
>>> --
>>> GoKhlaYeh <gokhlayeh@xxxxxxxxxx>
>>>
>>>
>>>
>>> ---
>>> SliTaz GNU/Linux Mailing list - http://www.slitaz.org/
>>>
>>
>

---
SliTaz GNU/Linux Mailing list - http://www.slitaz.org/