yello mates

actually i had wrote some post installation wiki but dont have time and forget to share it on the past. i upload it on my pagure now.
it still not complete but already contains guides to set up full featured graphical desktop environment (xserver, sndio, doas, dhcp etc etc..)
it needs review and correction, and maybe include or refer it in hyperbola post installaion beginner guide

you can open it in browser:
https://pagure.io/hyperbola_wiki/blob/m … /guide.txt

or use git:
git clone https://pagure.io/hyperbola_wiki.git
cd hyperbola_wiki
nano guide.txt

goodnight

This will be good, till HyperbolaBSD is at least at beta level and has the packages we have now here or better.

Which, I don't know when it will happen, but always be prepared, am I right?

Aka, till it arrives, have it as  backup, also... not sure what will change at this time.

Either way, thanks and have a good one!

actually i had wrote some post installation wiki but dont have time and forget to share it on the past. i upload it on my pagure now.
it still not complete but already contains guides to set up full featured graphical desktop environment (xserver, sndio, doas, dhcp etc etc..)
it needs review and correction, and maybe include or refer it in hyperbola post installaion beginner guide

you can open it in browser:
https://pagure.io/hyperbola_wiki/blob/m … /guide.txt

or use git:
git clone https://pagure.io/hyperbola_wiki.git
cd hyperbola_wiki
nano guide.txt

goodnight

Hello,

I managed to install latest milkyway ISO , everything seems to be working fine but upon boot system is stuck at starting sndiod , I am unable to reach to tty to login to openbox by startx , so what am I missing ?

This is the screenshot of my Hyperbola screen

https://imgur.com/a/0pSQjJB

Are you able to press ctrl alt f2 to switch to a terminal? if so, log into root and then you may need to install some new things.

PS, I am currently using sndio with no issues, the only thing I am guessing, is that if sndio doesn't work for you, its possible there are some bugs in the ISO for specific architectures, or some other weird problem.

I can only speculate, so don't take my word for it yet. But yeah, try crtl alt f1-f12

basically crtl + alt and one of the function keys  that I mentioned above.

If this doesn't work, then chrooting via a live iso, is the only fix available.

I'd recommend first to disable sndio. For that the following steps:

1. Mount the system with the downloaded ISO (on USB or DVD) again.
2. Get into your installation-partition with arch-chroot [DEVICE] /mnt
3. Do the following command: rc-update del sndiod default

It could be also something more than sndio itself. But first thing is to get the point of the problem on your installation.
You can always use ALSA only first and later add sndiod again. Nevertheless there could be óther problems like missing network-connections for dhcp. But as said: Needed to consider the point. So also the question: What kind of hardware is base for the installation? More details would help here.

I managed to install latest milkyway ISO , everything seems to be working fine but upon boot system is stuck at starting sndiod , I am unable to reach to tty to login to openbox by startx , so what am I missing ?

This is the screenshot of my Hyperbola screen

https://imgur.com/a/0pSQjJB

OK, I'm in. The annoying part is over, and now the hard work starts.

I intend to write guides for installation of the graphical environment and other 'bits' that many users would like.

When they're complete, I'll send them your way and you can see what you think of them.

Thanks for the help!

I hope I won't have too many questions, now that I can have the browser to search for answers in the same workspace as the terminal I'm grappling with! (previous to now I was having to logout and reboot from antiX USB every time I wanted to post on these forums or look for help)

Take care

If you want an ultra lightweight setup, I recommend, jwm.

Also, if you know how to set jwmkit up, its even easier, gives you a menu and a way to a poweroff easily, or via pressing a few keys at the same time.

only thing you need to do, is make sure, you change doas.conf to change the part of doas.conf to include these new two lines:

## Allow members of group wheel to execute any command
permit persist :wheel

## Same thing without a password
#permit nopass :wheel

## Allow tedu to run procmap as root without a password
permit nopass localuser as root cmd /sbin/poweroff
permit nopass localuser as root cmd /sbin/reboot
permit nopass localuser as root cmd /usr/sbin/s2ram

## Allow members of group power to execute power commands
permit nopass :power cmd openrc-shutdown
permit nopass :power cmd runit-halt
permit nopass :power cmd runit-shutdown
permit nopass :power cmd halt
permit nopass :power cmd poweroff
permit nopass :power cmd reboot
permit nopass :power cmd shutdown

## Allow root user to execute any command
#permit nopass root

Btw, you may notice a third line, right?

aka, s2ram as well,

However, there is no point, unless you have installed this:

uswsusp

also, when installed, it has a few steps for you to do, before iI think it would be to its maximum effectiveness.

that being said,

I detracted somewhat, from my original reply,

but there is one GOOD reason, you should use jwm...

JWM, uses the least cpu power, of any of the window managers that are still maintained, have a taskbar and even an application menu.

Thus, it is awesome for me, for darn sure, but you can feel free to do things however you like.

I just thought I would let you know this...

If you want, something more flashy, Lumina Desktop is also an option.

Hope this helps!

I'm happy than for reading your notes and guide, will give you also feedback. Thanks for the questions and the additions so we can make Hyperbola and the project bit by bit better.

I intend to write guides for installation of the graphical environment and other 'bits' that many users would like.

When they're complete, I'll send them your way and you can see what you think of them.

Thanks for the help!

I hope I won't have too many questions, now that I can have the browser to search for answers in the same workspace as the terminal I'm grappling with! (previous to now I was having to logout and reboot from antiX USB every time I wanted to post on these forums or look for help)

Take care

Regarding starting the x-server (xenocara): It is your choice either to use some login-manager like slim or xorg-xdm, alternative using startx-command itself from the terminal. Besides to check again the posting earlier: https://forums.hyperbola.info/viewtopic … 4593#p4593

Your user should be in the corresponding groups for having no further trouble. If you prefer startx as command:

doas pacman -S xenocara-xinit

The most important thing is: HOW DO I START X ?

Surely I am now only one step away

Since I seem to be close to getting a bootable graphical system, I would thank you for your help, but I would also raise a point that you so far seem to be missing:

In order for a person to properly test your OS, they need to boot into a graphical environment and then play around with it (assuming you want graphical users at all?)

So expecting them to learn all of the above just puts an unnecessary barrier to entry, IMO

I'm persisting because my will is strong, but others will not be

You didn't comment about the Obarun script I mentioned

I don't see at all why Hyperbola could not develop something like that

It just prompts people to choose their locale, choose their window manager, etc, and does all the other stuff, like interacting with init system, automated

If you confirm for me that Hyperbola is ONLY for ADvanced users, then fine, but then I simply cannot evaluate it.

It's a shame. If your distro was a TINY bit more user friendly you would attract a lot more support, I think

I hope you'll consder my feedback as trying to be helpful and not just negative

I've been using Linux since 2013, and experimenting with Systemd-free distros for around a year, so I'm not a recent Windoze convert or something

If I can do my bit to bring Hyperbola to more people, I would be happy

Isn't that what you want?

boot
default

As written already you can add services to those runlevels like this:

doas rc-update add dhcpcd detault

This will execute the service at default-runlevel (recommended). You can review all installed services under:

/etc/init.d/

And the configuration-files under:

/etc/conf.d/

Beware: Not all services need a configuration there at all as those are only used for start-configurations and elementary parts of the services. To remove a service from a runlevel:

doas rc-update del dhcpcd default

This will remove dhcpcd then from default-runlevel.

Same to do when x-server is installed further and you want to execute it at startup, example with slim:

doas rc-update add slim default

I hope this is giving you a first idea how the service-framework is working. You can also look here for more: https://wiki.gentoo.org/wiki/OpenRC

You need to start dhcpcd for getting a correct connection, either direct as root or via service on the default-level:

doas rc-update add dhcpcd default

WordsOfPower wrote:

This is tiresome, honestly

Sorry, but is impossible to create a complete free and libre system with a full flavored environment at startup. The previous version of Hyperbola GNU/Linux-libre had also dbus included. But we don't distribute that any longer. Yes, it is harder and not that kind of user-friendly. But there is no bloat left. You need to understand the service-framework hyperrc (openrc) and therefore also how services work for getting further. I try to do my best getting through with you, noting where we can add more details for a better installation-guide.

Ok what other steps might I need to perform between the end of your installation guide and the actual booting of a GUI ?

I assume I will only have to start DHCP once and after that it's part of the init process?

Stuff like Trackpad and Keyboard Backlight and screen light I can handle once I'm in and able to play around, but can you think of anything else that is gonna stop me from moving further?

doas rc-update add dhcpcd default

Sorry, but is impossible to create a complete free and libre system with a full flavored environment at startup. The previous version of Hyperbola GNU/Linux-libre had also dbus included. But we don't distribute that any longer. Yes, it is harder and not that kind of user-friendly. But there is no bloat left. You need to understand the service-framework hyperrc (openrc) and therefore also how services work for getting further. I try to do my best getting through with you, noting where we can add more details for a better installation-guide.

This is tiresome, honestly