Don't mind me, just read. 1-3 is about the Obarun installation process. I hope the formating is ok.

1: The options to select UTC or localtime.
2: Disabling of default services, hwclock in this case.

Sure, I can switch to localtime and then fix my BIOS time. It would be nice if I didn't have to.
Afterwards I don't see any point in the service hwclock. Nice if I could set these during install.

Of course, I could switch to a different tty. But at what point in time during install?
When would be a safe time to switch over n edit s6/66 files? Crit files in the mountpoints?
Sure I could experiment, or try harder, or maybe use a fake AUR PKGBUILD to break install (a similar trick I used to use with Ubuntu to break
installation so I could wurk from a fresh unpolluted base install).

Perhaps a switchable (ie --nobreaks --beerbreaks params) on obarun-install. Perhaps breaks between 'base' 'base-devel' 'base-obarun' etc.
Not sure when the best times would be, but it would be nice to have the option.

3: More control over user creation. Not everyone likes zsh.

Again, fixable. Just a conveniency. Get mad at myself when I forget 'cause I mutitask a bit and a reboot-update-chroot cycle is a waste of time.

4: It's Cristmas AND my birthday. I want script-fu.

What im thinking about here is some scripting that takes all updatable packages and verifies that Obarun repositories have the higher version number when doing an -Syu. Some pacman-db magic might be needed, I simply haven't gotten around to playing yet. Too much wurk, and my scripting is weak. Perhaps the wrapper could even cover -S.

Maybe using a wrapper is bad. Probly. Some db magic would be better. Some kind of 'check-all before you install or update' kind of thing.

Could even be useful during obarun-install; I remember one time I had a package from the wrong repo 'cause Obarun was a day behind. All sorts of probs.

--fin
Unless U like to read this was all word-salad. Thanks for your time iff u did read, n i will check this post again so feel free to shout back.
laters all,
b
To be honest I kinda got on a bit of a roll there. 1-3 belonged in 'installation' but I just couldn't stop. 4, talk about, no question. Anyone who bothers to check my command line parameters should understand, heh.

I'm having trouble getting a grip on s6/66 service management. The wiki is weak. No command I ever enter works. When Things Break(tm) I simply rebuild. Time for me to learn, perhaps.
In the beginning it was all changing so fast. I didn't even bother keeping up. Now I feel a bit noob-ish.

Sure, I could try harder. I'm busy, therefore I vamp.
laters
4 months later
1-3 Last I tried obarun-install on a machine at work, although the installation was complete, asked for user and root passwords, 66 was left without trees or services. It was all blank, user and root.
I suspect the cause was a faulty efi installation, which with win10 the totality of efi - wiki is useless. I don't have the liberty to remove win10 from the machine, boot is 100mb and it is not vfat, it is fat32, the wiki calls for a 500MB boot.

1-3 Even though you remove the syslinux choice the installer keeps trying to install syslinux, the reason being it is on the lists 2-3 times, so you can't escape installing the crappy abandoned for 10y software. But this is an old issue with obarun and it is a choice enforced by the dev.

4 This is a dangerous thing to do, having auto update/upgrade.
a script with
% sudo pacman -Suy --noconfirm 
will do what you want but eventually it may break your system and you wouldn't be able to know why, unless you hunt into /var/log/pacman.log
To run this from X you need something like gksu or doas, otherwise if sudo is not open without password check there will be no notification on X asking for pw. On console/terminal use sudo.
 % gksudo pacman -Suy --noconfirm 
Again this is not advisable, especially when obarun is based on two distributions for which obarun doesn't have ultimate control.
Again this is not advisable, especially when obarun is based on two distributions for which obarun doesn't have ultimate control
two distributions?? TWO distro?? which is?
Even though you remove the syslinux choice the installer keeps trying to install syslinux
default bootloader is configured at /etc/obarun/install.conf with BOOTLOADER="Syslinux"
This is a dangerous thing to do, having auto update/upgrade.
a script with
This is not, we talking about fresh installation here and we talk about automatic installation. Remove the --noconfirm option and you will understand the level of complexity to deal with error and making the script interactive after the launch of the installation process.
To run this from X you need something like gksu or doas, otherwise if sudo is not open without password check there will be no notification on X asking for pw. On console/terminal use sudo.
Sudo can be configured to ask for password on X.

Powered by Obarun