I followed instructions in https://wiki.obarun.org/doku.php?id=uefi and finished the installation several days ago without any problem.
It's great. It has necessary, precise and latest information just needed. I really like the word about bootloader. I haven't understood why grub is needed in UEFI for a long time.
By contrast, the arch wiki contains TOO MUCH information. More and more got infected by systemd.
Thanks for your work!

Second, I want to share a quote:
Well-designed components are easy to replace. Eventually, they will be replaced by ones that are not so easy to replace.
- Sustrik's law
There are many reason for the popularity of systemd, but I didn't find a technical one until I discovered this quote.

Best regards
Welcome, just in time you got in and the Introduction to 66 was published (66 for begginers)
https://wiki.obarun.org/doku.php?id=66intro

It would be of great help to let all of us know what you think and whether it helps or not, suggest what is missing and if it is too much for an introduction.
Welcome to the club, glad to see you here. I've personally become less aggressive towards being against systemd in specific but s6 is just such a breeze that I don't see why it wouldn't get more adoption (well of course I do see why but still...). In fact I think it should be the de facto standard to manage low level computing in the 21st century. Just think about embedded devices, mobile etc. Feel free to comment every little nitpick you may have with s6, 66 or Obarun in general, Eric's very dedicated to comments. Have fun with a very stable system (with occasional breaks from being Arch to begin with [let's be honest here, you don't go rolling distro for the stability factor] :P)
fungalnet wroteWelcome, just in time you got in and the Introduction to 66 was published (66 for begginers)
https://wiki.obarun.org/doku.php?id=66intro

It would be of great help to let all of us know what you think and whether it helps or not, suggest what is missing and if it is too much for an introduction.
Just read it and I have some ideas to make it more useful:

Separates "read only"/"query" operations from others

For example, use sudo:
$ 66-intree
$ sudo 66-tree -nE net
or use different command prompt:
$ 66-intree
# 66-tree -nE net
In section 9, makes the relationship between commands and explanations more clearly

For example, use COLON:
Create a (n)ew tree for booting (default boot) and enable the standard boot bundle of services (boot-66serv) as a single special service:
# 66-tree -n boot

enable boot in tree boot (again boot-66serv is a special bundle of services specifically for booting an arch system, such as obarun):
# 66-enable -t boot boot
Horizontal bar or more blank lines between groups may also be helpful.

Use some harmless examples.

Will the boot related commands make the system not bootable?
Can I use virtual console to execute tty related commands safely?
Can I enable wpa_supplicant when networkmanager is enabled?

I'm not sure so can not try these examples.

httpd, tty3 and sshd(at different port) may be better examples.
marianarlt wroteHave fun with a very stable system (with occasional breaks from being Arch to begin with [let's be honest here, you don't go rolling distro for the stability factor] :P)
A kid destroyed my Windows partition in 2013. I booted into the Linux partition, tried to repair it and failed.
After that I asked myself, why do I need repair or reinstall Windows instead of just using Linux? Emacs, Chrome, Firefox and Conkeror(a keyboard driven browser) work the same(or better) as Windows. Many development tools in Linux are MUCH better than Windows. And drivers(horrible stories in early days) for wifi and card work out of box. So I just use Linux only.
In fact, I can't use Windows "efficiently" again after I discovered tiling window manager.
Another good news is no one can use my computer again.

This Linux distribution was Ubuntu 12.04. And it is still Ubuntu 12.04. Why I do not upgrade my system? I cann't remember the exact reasons.
Maybe I'm seeking a non-systemd distribution. Ubuntu 12.04 uses upstart. It's not clear which one it will use in next TLS.
Maybe I'm just lazy.

The system itself is stable. But the world isn't. More and more secure protocols deprecate SSL in favour of TLS. More and more websites(gmail, github, gitlab/framagit, etc.) don't support old browsers.
I have learned, the hard way, that there is no stable(unchanged) system if I want to use it to interact with the changing world. Only large changes occasionally or small changes frequently.
As a developer, I suffers from outdated softwares and I'm not so scared when something breaks. So rolling release mode make more sense to me.
marianarlt wroteI've personally become less aggressive towards being against systemd
While I'm seeking and waiting non-systemd distributions, more and more major distributions adopt it. So I migrated one of my laptop and some servers to arch one month ago and tried to live with it:
  • manage my services using my favorite supervisor
  • start supervisor by rc.local(to avoid wasting time to learn unit files)
  • write small wrappers for shutdown, reboot, poweroff, ...
systemd works until it doesn't.
I just wish it won't fail me too quickly before I get familiar with arch. The fact is, it does, in the beginning.
journald use 100M memory after boot. It's 20% of the total memory on a $5 vultr instance. It's almost the 100% memory used by processes after boot. It's insane.

After a quick google search I gave up. I don't know how to fix it, or it could be fix at all.
I don't want to invest my time to learn this bloatware which treats users like idiots(The most responses from developers are "you measure your memory usage wrong").
As consequence, make system comprehensible is not a goal of them: "You are not capable to manage your system, so we do it for you."

So I gave up living with it and gave obarun a try. Thanks for your installation guide.
ownwaterloo wroteSo I gave up living with it and gave obarun a try. Thanks for your installation guide.
Thanks for the hints, I agree on all counts.
About playing with 66 and bricking your system:
You delete all trees # 66-tree -R treename
# 66-tree -n boot
# 66-enable -t boot boot
# reboot
You at least have tty12 to work on (ctrl-shift F12 or vm-hotkey F12), very low ram use :)
Runit sells simplicity and ease of maintenance. Try to beat this simplicity mrRunit or mrsBusybox.
Then make a tree called froot # 66-tree -cnE froot and # 66-enable -t froot -S tty@ tty9, most intruders will give up after 6 or 7 :) and start your i3 or awesome on tty9 then make an other tree and add networking or whatever else you REALLY need.

Obarun simply takes the world's most advanced init/svc.mgmt system and hands it to the world. Is the world ready for it? The world has been handed free and great ideas for more than a century, but "the world is not ready for anything better than what they get".

Now I am going cycling till my knees collapse, I am done with my 3hr work day :P
I'm tweaking the new laptop. I will do these experiments on old laptop after that.
Fungal is right, tty12 seems to be such a minor thing, but is has saved my ass several times when I played around with services and their structures and directories to get to know the system.
Also s6 is so simple it's awkward. That's probably it's main design flaw in a philosophical sense. A lot of people might think there's "missing" something in so much simplicity, that in our overcrowded digital devices there needs to be that super complex initialization process or it's not "good enough". Won't be able to do all what is necessary.

If you're server admin @ ownwaterloo I think you'll love Obarun and even more so the latest 66 suite. It's a breeze to organize daemons in a meaningful way and have them at hand when YOU want them to be there. Care should be taken when your pacman update includes system libraries though, I'd advise to always check Forums first.
The simplicity of daemontools and related softwares are very important to me. It make me confident: when something goes wrong, I can understand what's going on and fixing it. They just have several hundred/thousand lines of code.
When some bloatware goes wrong, good luck to read their million lines of code. Or contact them for their "supports".
Ok, I will check forums and do it on test machine first before upgrade.

Powered by Obarun