arch-chroot -> hyper-chroot
pacstrap -> hyperstrap

For sure: Before release 0.4.5 we will also enhance the installation-guide. And there I would like to invite: If you like, let's go through step by step so your questions and unclear points can be reworked. Taking that as invitation for doing.

Sorry, but this is not going to work like and being honest I do not have any clue how I can start with answering any kind of question with that much of quotes in it and filtering out what you exactly want to ask about. You are also mixing here several layers not working together:

Sorry about having many questions in one post.

I thought I saw somewhere on this website a picture of OpenBSD's installer, so I thought Hyperbola may use something like that one also as HyperbolaBSD's installer.

At

https://web.archive.org/web/20230810230 … stallation

I saw

and later I also saw

So I thought root was mounted twice.

Thank you for this information. I'm mostly used Trisquels graphical installer, so I did not see as many possibilities with the default graphical installer recommendation on Trisquel.

I also did not use Trisquel's command line installer.

Though I do like that the Hyperbola installer shows there are many ways to install Hyperbola.

I was not demanding anything, I was just glad you are making HyperbolaBSD.

I saw Richard Stallman showed in text at
https://www.gnu.org/philosophy/is-ever- … ogram.html

I just likened it to maybe not "participating in small ways in some evil activity" but instead not trying to use non-free things for a long time to get rid of non-free things.

Though I also see you are making a hard fork, and I did not know what a hard fork was before.

And I see

So I'm glad HyperbolaBSD will not have non-free things in it but only libre programs.

This was not criticism, I just am glad you found a way to make HyperbolaBSD.

I did not know how to do that without using something like Ben Eater's breadboard computer design and maybe using a hexeditor like hexedit to somehow get that working on a breadboard.

I'm very glad you found a faster and likely better way than I thought of.

https://en.wikipedia.org/wiki/Simple-As … e_computer

Thank you for explaining what fork types, like hard and soft, are.

https://forums.hyperbola.info/viewtopic … 7623#p7623

I think you answered all my questions.

Question 1 answered.

Pacman on Hyperbola 0.4.4 can still be used like the

https://wiki.hyperbola.info/doku.php?id … stallation

page shows
.

Question 2 answered.

I do not mount root twice. Or boot twice.

Question 3 answered.

arch-chroot is not anything "Arch GNU/Linux" related in the

https://wiki.hyperbola.info/doku.php?id … stallation

HyperbolaBSD with its HyperBK is a "hard fork". HyperbolaBSD has no ties towards OpenBSD. We have done therefore a tremendous amount of work before with auditing the licenses and review of them (thanks to rachad and bUst4gr0 supporting and doing that amount work and engagement).

Also to clear up: We have at the moment two parts and systems.

1. Hyperbola GNU/Linux-libre: This is our current independent system-distribution and is meant as transition-helper towards HyperbolaBSD. We have reconstructed that system-distribution from the ground up in 2020 and after with releasing finally 0.4 and beyond to be complete independent. Before Hyperbola followed a comparable approach with reworking packages and using a snapshot from Arch GNU/Linux.
2. HyperbolaBSD: This is our operating-system as complete new and independent BSD-descendant. Meant the same minimalistic and as most possible near to the Unix-philosophy.

Both systems are ...

... independent ...
... free and libre designed and meant ...
... constructed from scratch ...
... using only a base for the initial construction (HyperbolaBSD first OpenBSD, Hyperbola GNU/Linux-libre Arch GNU/Linux)

So I hope this clears again up.
Further examples of "hard forks":

(NetBSD before v1.0)
UNIX
↳4.3BSD
↳386BSD
↳NetBSD

(NetBSD since v1.0)
4.4BSD
↳NetBSD

(OpenBSD)
BSD
↳NetBSD
↳OpenBSD

(FreeBSD before v2.0)
UNIX
↳BSD
↳386BSD
↳FreeBSD

(FreeBSD after v2.0)
4.4BSD
↳FreeBSD

All of them reference each other and I have now not included DragonflyBSD:

BSD
↳FreeBSD
↳DragonFly BSD

All of them are in the result hard forks, developed further in their own ways. And HyperbolaBSD is going something like this:

(HyperbolaBSD)
BSD
↳NetBSD
↳OpenBSD
↳HyperbolaBSD

We have cut ties since version 7.0 and developing and porting from there. Making our Hyperbola as Unix-derivate, minimalistic and free, libre.

1. HyperbolaBSD never was on any FSF-related site as the FSF has up until now never recognized any BSD-descendant system as "free and libre" or FSDG-compliant.
2. There is no dedicated "HyperbolaBSD"-installer for the moment and sidewise we are not on that point.
3. As announced hyperman (source) is a drop-in replacement for pacman. This means you can and should use the new as the old one. It is done out of two main reasonings: Cutting ties once and for all towards anything "Arch GNU/Linux" related, because Hyperbola is NOT "Arch GNU/Linux" and also NOT "Parabola". Second: Development tie-in for HyperbolaBSD.

To underline also: The reference-installation mentions several times that you should use the commands - for example connecting WiFi - as template and not as it stands there. So you need to replace things like:

wpa_supplicant -B -i wlp2s0 -c <(wpa_passphrase "The_WiFi_name_I_wish_to_connect_to_here" "It's_password_here")

The_WiFi_name_I_wish_to_connect_to_here = The SSID of your WiFi-connection
It's_password_here = The password for your WiFi-connection

Also the way you like to create your partitions is the same: It is your decision to be done, only one possible recommendation on how to use and do. You can also create only one boot-partition with all on it, including your $HOME-folder. But with this be sure: When you want to reinstall you will also remove all of your data in your $HOME.

Yes, the reference-installation is a point of perspective. Cannot be fitting at once for everyone. But also to underline: HyperbolaBSD will not be easier to install. So you can go through and tryout. If you have issues, try again. Experience is the sum of failures and learned information.
Aside: Please ask one question at a time so it is possible to explain and solve. You can do that in this thread for example. But I cannot answer this posting above without having big question-marks above my head same as I do not understand the mix you are using and I also do not read many more questions out of as now.

Besides this here ...

Just does not work. You demand indirect that we wait for a free, libre made BSD-like system and make comparisons not working same way. A free, libre system has to start at a point and this is for sure OpenBSD. If you are not okay with this working, please recommend another but also: GNU/Linux-libre and OpenBSD are NOT compliant and it is NOT possible to build a BSD-system out of nothing. Pointing on the FAQ: https://wiki.hyperbola.info/doku.php?id … olabsd_faq

HyperbolaBSD is NOT OpenBSD just with removed parts and consists of ...

1. its own kernel (HyperBK)
2. its own libc-implementation (HyperBLibC)
3. its own userspace
4. a dedicated defined init-system (runit)
5. two repositories (core for BSD, extra for the rest)

And just now the compilation of the kernel and the userspace (incluing the libc) works and needs to be tied up into first images. When this is done and working, we work with our first real image (pre-alpha) and construct the rest so we can create the rest now with complete free, libre software. You can't just build out of "void" (nothing). So if this is criticism: I either do not understood the point or you should repeat that point more specific. We are not using OpenBSD to remove non-free things here. We are building a system from scratch! Same as Hyperbola 0.4 also: This is really done from scratch, not just taking OpenBSD and removing some parts of it - if this is the point you thought of. Hyperbola is a free, libre and independent system! Even now it is a hard-fork and will be the same with HyperbolaBSD. We do not just pull some package from "upstream", we evaluate and build it on our own, including our patches to make it work and including also the perspective getting as close as possible towards original Unix-philosophies.

So we just used until now our own pacman-version, rest is complete our own (also that exact pacman-version with our own fixes and enhancements). With version 0.4.5 we are making it official and use our already in development stated hyperman.

Will Hyperbola 0.4.4 still be able to use pacman with it's operating system installer?

Also I do not yet know if some of the things in this are set once or twice. Or if I may do this in the right order.

(End of main questions)

I saw some things after looking at
https://wiki.hyperbola.info/doku.php?id … stallation
with

than saw wifi network names.

Than I also used the

things, though that is not the name and password I used.

and saw

and

though I do not know why there are 2 "Primary" things.

So maybe this means the first one is set things in the "graphical partitioning table" to the swap type and the other is set as Boot, I think.

though the sda1 above looks like swap and sda2 looks like Boot. I do not know if that order matters or not.

But than I saw

though I do not yet know how to do that with Hyperbola as I set up things on Trisquel's graphical installer, so maybe not using these will not be a large problem.
Unless these can somehow improve security for a computer against remote cracking.

I also saw

and also things about setting the keyboard. I do not know if the above mounts root or boot. Though I do not think I need to type

So next I may need to type

Than this is also

I thought is was mounted already with

as shown above.

But maybe it needs to be mounted again. For some reason. Or maybe somehow that is a "Boot" mount and not "root" mount.

And also there was

before. So that was just to activate swap than, I think.

I do not see a command to mount a swap.

So maybe

could work, though it is already an "Activate swap" without being mounted, I think.

So mount the "Activated swap" swap thing than.

A note here, on Trisquel I typed with the Mate Terminal lsblk and saw in part

But this was made with Trisquel's graphical installer, so I mostly just clicked on things without learning how to do this with a command line.

So if it looks like that, to get a "home" also I may need to type something like I did with swap. Maybe like

and

Note I think I mixed up some thing here after twice mounting a root or boot. Or at least looking at the

https://wiki.hyperbola.info/doku.php?id … stallation

page when typing this.

Was sda2 a Boot partition that showed in the text under

so a Boot and not a "mount the root than" maybe, though I do not know.

Also does this mean that swap does not have a file system, as swap is, likely at if I saw right, in or at a

?

Okay so this may be how to set system time, I think.
First see a date with

At least two ways to set it if it is not correct.

For 6:44:32 PM on the 13th of November 2013.
Or whatever time is has to be set as.
Or

So maybe like

I think I will use the other one, if needed.

There is also

though if pacman is being changed will the Hyperbola 0.4.4 still work for installing Hyperbola 0.4.4? I do not know if

is only in pacman.

Than

because I need a password for the wifi.

I than saw

I can try to "Generate an fstab" even though I did not know what a "fstab" is. So I looked a little at
https://en.wikipedia.org/wiki/Fstab

You may also look there.

The next thing may be this.

So does Hyperbola use arch somehow?
Or is this just a program?

I hope the Hyperbola installer shows when to set the hostname.

I think HyperbolaBSD may have a more easy way to setup the system, if I remember right from a page I may have saw on the Hyperbola website.

So than

than

somehow saving it with a program likely called nano.

Than

So unless it shows a way to see more "Zone and Subzone" areas my time will be the same as Athens' time, even though I do not live there.

I can likely use the time that was set before, but if I need to use this time also I may have Athens' time. I may be able to reset it later.

Than I can set a language.

Uncomment (remove the #) like

than

Than set keymaps.

Than use

again, I think.

Set time again, this time hopefully not in Oslo.

Now setting a root password like this

and a user to a group. Though is this a user account or root as a user?

I do not know where the user's password will be set at.

pacman may work in Hyperbola 0.4.4 but maybe not.

This section?

Maybe I need some sort of bootloader that is not somehow on an external drive I need to

or more like

or

So I will likely need to remember what the names of all the partitions I made, or maybe use lsblk and type each one in at a time.

I do not know how to use umount to search for all things to unmount.

Than

so the other user for that group was not likely a user account.

I think I saw a HyperbolaBSD installer on a page also showing

https://www.gnu.org/philosophy/is-ever- … ogram.html

I do not remember where that was, but the HyperbolaBSD installer looks like it may be more easy for me to use.

And Hyperbola may only have been using OpenBSD to remove the non-free things.

Like using a magnifying glass with a very (bad handle)/(non-free things) on it, to start a fire to burn the bad handle off of the magnifying glass, so a better (magnifying glass without a bad handle)/(operating system without non-free things) may be made.

I can also look at

https://forums.hyperbola.info/viewtopic … 7482#p7482

where a user called jim typed