# passwd -a <your-user> <some-group-name> 

is used to

.

This command is incorrect. According to the man page,

# passwd -a

.

It does not in any way add your user to the group. In fact, used as shown in the wiki it only outputs the --help information for the passwd command, since that command only accepts two arguments, [OPTIONS] and [LOGIN].

Edit:
All references to the passwd command in this context should be changed to

# groupmems -a <your-user> -g <some-group-name>

.

we were noted in IRC that both articles about encrypted installation have severe flaws and do not fully work. Listing them here:

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

As consequence and regarding lack of time for our small team we will now archive them. But not without the question if there is interest to write completely now ones so we also archive them as pads for review:

Encrypted installation, excluding boot
https://pad.riseup.net/p/sjmKVqsWaEW1FrTNhs_1-keep

Encrypted installation, including boot
https://pad.riseup.net/p/Q8M6jURLL2eglCyYqRK1-keep

You can edit the pads as you like for sure and / or give within this thread feedback. As for the time being the forum-user and community-member jim have some further guides provided:

https://forums.hyperbola.info/viewtopic.php?id=934
https://forums.hyperbola.info/viewtopic.php?id=920
https://forums.hyperbola.info/viewtopic.php?id=933

within this thread we want to document the changes around the website and the wiki of the Hyperbola-project. This includes for sure also partwise debates on missed out information needed to be added.

For the moment to leave as newest addition: Hyperbola is independent and not only with the focus on GNU/Linux-libre!
We have therefore modified the Social Contract with point 6. The original point 9 about "Arch GNU/Linux and Debian" was removed (remember as Hyperbola is independent) and a newly created point 12 (original point 13) was added.

When HyperbolaBSD is going further into the alpha-phase point 7 and point 8 will be also removed. The reasoning here is that we no longer provide GNU/Linux in any form at a point in the future and we also do not need "deblobbed kernels" as our own operating-system and its infrastructure is following our ruleset and does therefore surely not contain non-free blobs.

There will be a FAQ coming in the near future, so we can hand out a list about facts and information for HyperbolaBSD, clearing up common misunderstandings. And within the next days we rework also the information-site for Hyperbola.

In the #Setting_up_the_kernel_modules part I had an error about encrypt hook missing. Although I have installed cryptsetup earlier in the installation as mentioned in the #Initial_setup section. What solved the issue was installing it again with

pacman -S cryptsetup

before doing

mkinitcpio -p linux-libre-lts

In the #Install_video_package_(depending_brand_of_your_video_card) I installed my brands package AND #Xenocara_components. I propose this to be better documented.

In the #Install_`xenocara-input-synaptics`_only_on_laptops I would like to propose to add only in laptops that have touchpad, because in laptops like x200 this package is not needed.

Othet than the above minor comments, this guide is an excellent improvement . Many thanks to everyone that made it possible.

https://pagure.io/hyperbola_wiki/blob/m … /guide.txt
git clone https://pagure.io/hyperbola_wiki.git

im posted it here for sharing and archive purpose

The issue I had when trying to register on the wiki - there was a database error of some sort, and I never received the activation email, so now I seem to be in limbo. If this could be fixed, that would be great. My email address is paul .at. teulu dot org. By all means delete the account there if that's the easiest approach, and I can try again.

Thanks!

usermod -aG adm USER

doas pacman -S postfix

doas rc-service postfix start

doas nano /etc/postfix/aliases

-->root : USER

doas newaliases

echo test mail localhost | mail -s "mail test" root

To read the messages

mail

or

mutt -f /var/mail/USER

rc-service

doas rc-update add postfix default

That probably is the harder question above, but I also wonder if anyone knows how to make this work with an external solid state drive connected remotely and of course made them interchangeable more or less whenever they are both connected or act normally when the other one is disconnected.

Just curious...

However, it looks a bit outdated and not that detailed. I am trying to compile in my system without success. So far, I have this:

git clone https://github.com/RealityRipple/UXP.git
cd UXP && mkdir applications
cd applications
git clone https://git.hyperbola.info:50100/software/iceweasel-uxp.git
cd ..
echo 'ac_add_options --enable-application=iceweasel-uxp' >> .mozconfig
echo 'ac_add_options --disable-pulseaudio' >> .mozconfig
echo 'ac_add_options --disable-debug' >> .mozconfig
echo 'ac_add_options --enable-strip' >> .mozconfig
echo 'ac_add_options --disable-sync' >> .mozconfig
echo 'ac_add_options --disable-updater' >> .mozconfig
echo 'ac_add_options --disable-crashreporter' >> .mozconfig
echo 'ac_add_options --disable-maintenance-service' >> .mozconfig
echo 'ac_add_options --disable-tests' >> .mozconfig
echo 'ac_add_options --disable-ipdl-tests' >> .mozconfig
echo 'ac_add_options --disable-verify-mar' >> .mozconfig
./mach build
...
./mach run

Unfortunatelly, after some checks I get:
unknown project iceweasel-uxp

Of course, not hurry, just in case you have an idea about the missing steps.
Regards

obviously you need to install console-tdm, xinit and dialog (if you want the gui)

But here are the steps to getting it to run properly.

1: do this in your  non root account:
tdmctl init
tdmctl add yourwindowmanager /usr/bin/yourwindowmanagerEXECUTABLE 

2: Then edit your .bash_profile and add:

tdm && exit

if you want to logout automatically when the window manager is closed, add exit so no one can use your comp till you put your password and login in.

3:  Make a file called .xinitrc and put it in your /home/user folder. 

tdm --xstart

IT should work after this, otherwise scroll below to my warning:

WARNING though, not dangerous just ANNOYING! and it RARELY happens anyways:

If it refuses to start after all this, there might be some sort of an error.

I had this on my x230 laptop for some reason where you would have to disable-xrunning-check

meaning automatic login was not able to be setup.

Which means one you logged in you had to type in something before you logged in like this:

tdm 

Then your gui or text mode options would appear

Just don't put the --disable-xrunning-check option into .xinitrc or .bash_profile to fix this problem.

If you want to fix it, I recommend looking into .config/tdm/

and checking to see if the problem is there.

or,  doas nano /usr/bin/tdm  (not recommended unless you need automatic login and it wont work any other way!)

and work from there!

BEFORE YOU SCROLL DOWN... BE EXTREMELY CAREFUL! I WOULD PREFER NO ERRORS COME FROM THIS! okay? anyways look below now:

IF you do this, make a backup config file with cp -r  of your /usr/bin/tdm

in case something goes screwy...

then I suppose you could disable xrunning-check, I am not sure if this will fix it. But you can try if you wish.

NOTE! I should add this wasn't needed on my T430 at all.

Both have a version/fork of  coreboot and intel me is disabled on it. 

It is also possible something was screwy with my X230, so maybe this is a 1% chance of being a problem.

Just mentioning cause it happened to me on one comp once. 

MAJOR EDIT! THERE IS IN FACT ONE OTHER WAY besides the smplayer method!

mpv --audio-device=sndio + whatever mp4 file you wish to play!

Hope this helps some people!

The below still works, but its really the inferior way I think...

You cannot use pure mpv if you are using sndio, or the video is out of order and the sound moves faster than the video...

smplayer is required until someone figures out how to make this an easy default within regular mpv or at least feasible.

Anywho, for sndio to work with smplayer on mp4 videos:

Go to Options/preferences/General and enable the following:

Audio/Video Auto synchonization and make the audio output sndio.

I am not sure if this is an issue with other video/audio files, but if you don't do these two things, the video and audio aren't properly in sync.

Just thought I should mention this.

g4jc told me about this once, if I recall correctly.

Long story short, I feel like this should be mentioned in both the wiki and the forums as a sticky.

I was told by one of the devs moments ago that I should post here even if the other 3 don't respond back to me.

Hope this helps someone!

Peace!

Small side-note, don't change the A/V auto synchronization factor from 100 to any other number.  I think that might cause problems. 

openrc user should set hostname in /etc/conf.d/hostname instead

https://wiki.parabola.nu/Beginners%27_Guide#Hostname

how dangerous is it ?
- it mess up your network, especially network manager
- it mess up your X11 and block your apps,  "error cannot open display 0" if you trying an network connection