You are not logged in.
We need the ability to (optionally) create a new User within AIF "procedures"/"Modules"/...:
Is there a method to add/create a new User (with a /home dir, ...) within an AIF install, so that upon completion, and reboot, of a successful AIF, the new user is properly setup. ?
And/or if not, how about adding the User info by hacking in the (passwd, shadow, gshadow) files. ?
For example, I tried several times within "worker_scripts, chrooting,... "? and concatenating the respective new User info to passwd, shadow, gshadow, ...,as mentioned in the line above,
BUT, unfortunately, none of these worked. ?
All I got was "Seg faults" when trying to use chroot -> useradd...?
So, let me re-clarify here; ie, the "disk-configurator" during an "aif -p automatic -c ...." requires those "mandatory" disk values be edited in already.
Ok, then, optionally, how about a "USER-configurator" (with $username_aif, $passwd_aif, $groups_aif, $....) variables that we could also just plug-in within that script, ... ?
...and yes, I have also been trying to search the arch-releng mailing-lists but maybe I'm missing somethin' here...? sry.
-please don't get me wrong, and any suggestions are welcome.
Other than that, AIF is very good. -and, I also would just like to thank the Author and company, at this time, for it.
Regards,
Rick.
Last edited by scjet (2012-03-02 11:56:46)
The "BSD" things in life are "Free", and "Open", and so is "Arch"
Offline
I do believe that whatever can be done from the live system manually isn't desirable to be a part of aif, it goes against the rule of simplicity. It's obviously just my personal viewpoint, but I don't think we'll see that option in aif anytime soon. But I'm a bit surprised that adding user from within chroot segfaulted, what exactly happened there?
Running arch is like raising a puppy - if you spend a bit of time with it each day and do just a bit of training you'll end up with the most loyal partner you could want; if you lock it in a room and don't check on if for several days, it'll tear apart your stuff and poop everywhere.
Offline
Hi @meph, and thx for reply.
I'm beginning to agree with the reasonable sentiment of simplicity, aka Live vs (automated)Netinstall, otherwise, I'm sure AIF would have implemented an "add_user" ability within AIF a long time ago.
As far as seg faults, I read somewhere in the past that I would also have to mount /proc,... and some other's to get a more full functionality, again , I'm not completely sure about this either yet.
Example:
If I try to run a useradd, (witin my automated script), I notice that the "useradd" command (as used by the booted netinstall image is purposely lacking a "-R" switch ? , preventing me from referencing it within /mnt/home/<Username> ...?
Again, I don't get much info after the "Seg fault" even with debug on. It craps out.
I like "Netinstall" simply becuase I get a fully up-to-date, pristine Install.
Bascially, AIF (within the aif -p automatic ...) does everything else that I possibly need, except, adding user(s) with /home(s),....
I guess that is too bad.
Last edited by scjet (2012-03-01 23:57:36)
The "BSD" things in life are "Free", and "Open", and so is "Arch"
Offline
@scjet
maybe you should try sai(simple arch installer), which is written by me.
it is semi-auto but you need to provide 1. a list of packages to install 2. your script to setup
here is the script example. you get full control of your automated install.
https://github.com/taylorchu/march/blob … sai_config
"After you do enough distro research, you will choose Arch."
Offline
@scjet
maybe you should try sai(simple arch installer), which is written by me.
it is semi-auto but you need to provide 1. a list of packages to install 2. your script to setuphere is the script example. you get full control of your automated install.
https://github.com/taylorchu/march/blob … sai_config
Thanks very much for the link, and nudge !
It made me see my own mistakes.
The "BSD" things in life are "Free", and "Open", and so is "Arch"
Offline