Installing BunsenLabs Helium-dev

dobl · 2017-12-24 21:14:55

, for ext4! forgot to add...

Yes, I know the basics. In fact I'm adjusting parameters (such as lazy or commits) for my flash drive emergency install but have started with main install defaults. So rw,noatime,data=ordered and I really dont remember from where is this data=ordered and for...

Head_on_a_Stick · 2017-12-24 21:31:32

dobl wrote:

I really dont remember from where is this data=ordered and for...

See ext4(5), in the "Mount options" section:

in the default data=ordered mode, the data blocks of the new file are forced to disk before the rename() operation is committed. This provides roughly the same level of guarantees as ext3, and avoids the "zero-length" problem that can happen when a system crashes before the delayed allocation blocks are forced to disk.

So whatever it does, it is the default setting and so does not need to be added to /etc/fstab

Head_on_a_Stick · 2017-12-24 21:41:34

dobl wrote:

flash drive emergency install

I would recommend using f2fs rather than ext4 if this is for a flash drive installation:

https://www.kernel.org/doc/Documentatio … s/f2fs.txt

https://packages.debian.org/stretch/f2fs-tools

dobl · 2017-12-24 22:05:34

thanks for first link. I find it now really very strange that one can always find (by find I mean with good keywords and results near the top) Ubuntu docs page via google and it is not possible with Debian which is having superb documentation btw.
Yes, looks like data=ordered is default so not needed. But should I exchange it adding 'defaults' instead?

Regarding flash drive: f2fs or nilfs2.
However I'm using rEFInd as my boot manager everywhere and really don't want to create separate boot partitions. rEFInd doesn't have included drivers for those file systems, they exists from third-party but at least f2fs driver didn't work for me during one trial.
So as for now I have ext4 without journal but I'm checking other possibilities...
It looks there is no special support for those filesystems, many limitations like shrinking not possible and so on...
EDIT: also btrfs with compression is possibly good candidate

Last edited by dobl (2017-12-25 14:18:07)

vinzv · 2017-12-26 17:41:47

Head_on_a_Stick wrote:

For the first step, it is possible to use the Debian stretch netinstall ISO image (with the non-free firmware already included):
https://cdimage.debian.org/cdimage/unof … ch/iso-cd/

That URL changed due to Debian point release 3:
https://cdimage.debian.org/cdimage/unof … ch/iso-cd/

Head_on_a_Stick · 2017-12-26 17:45:16

^ Thanks!

OP changed.

lowrider · 2018-01-05 17:19:26

Did a netinstall + installscript in virtualbox. Install worked very smooth without errors. Everything worked so far.
To get full resolution in virtualbox i did:

sudo apt install build-essential module-assistant linux-headers-$(uname -r)

congrats @team

scrot or it didn't happen

Head_on_a_Stick · 2018-01-06 12:25:54

^ Nice

Update for all Helium-dev users: the KTPI patch has been applied to the Debian stretch kernel so please upgrade ASAP:

sudo apt update && sudo apt upgrade

Reboot and then test with:

grep TABLE_ISOLATION /boot/config-$(uname -r)

Which should return:

CONFIG_PAGE_TABLE_ISOLATION=y

Thanks!

Last edited by Head_on_a_Stick (2018-01-06 15:16:12)

vinzv · 2018-01-06 15:01:20

Hi,

thanks for the heads-up!

Last kernel update I got was 4.9.0-5-amd64 (4.9.65-3+deb9u2) dating from 2018-01-04. This is the same as listed on packages.d.o but sudo dmesg | grep isolation tells me:

Kernel/User page tables isolation: enabled

Any idea if I did something wrong?

Head_on_a_Stick · 2018-01-06 15:03:35

vinzv wrote:

Any idea if I did something wrong?

Erm, no, that's me, I think :8

I was copy&pasting the output from another forum 'cos I'm booted in OpenBSD atm and I must have made an error, sorry!

I will edit my posts...

EDIT: my stretch system says "disabled" so I'm a bit confused here, give me a bit.

EDIT2: my stretch system is on an AMD laptop, that's why O:)

Last edited by Head_on_a_Stick (2018-01-06 15:20:09)

Head_on_a_Stick · 2018-01-06 15:11:11

OK, definitive test:

grep TABLE_ISOLATION /boot/config-$(uname -r)

Patched output:

CONFIG_PAGE_TABLE_ISOLATION=y

Last edited by Head_on_a_Stick (2018-01-06 15:13:16)

vinzv · 2018-01-06 15:22:31

vinz@hobbes:~$ grep TABLE_ISOLATION /boot/config-$(uname -r)
CONFIG_PAGE_TABLE_ISOLATION=y

Phew, what a relieve. Thanks for your help!

devnull · 2018-01-22 12:40:59

Just as a feedback: had it on my brand new laptop (hp x360) for a month now. This helium is awesome, no troubles whatsoever and I have to say, gorgeous. I set up few things to have the touchscreen working nicely and it's smooth to be used even as a tablet

Thanks everybody for the great job!

bigbenaugust · 2018-01-22 21:32:00

I just committed some science and added the helium-dev repos to an antiX VM and installed the openbox and theme bits to see how a systemd-free BL-alike could be achieved. I am not disappointed with the results so far.

nederpils · 2018-01-25 21:51:18

Hello

Just because i can't update my Vuescan to the latest version due to a outdated libc in current Jessie based BL i thought i'll give Helium-dev a test drive ...

I chose Virtualbox and installed the recommended Stretch netinstall iso. All went fine until i tried to run the netinstall script. Error - can't use sudo ... So i had to install sudo first and add my user to sudo before i was able to successfully launch the script.

Head_on_a_Stick · 2018-01-25 22:11:40

^ Thanks for the feedback!

nederpils wrote:

I chose Virtualbox and installed the recommended Stretch netinstall iso. All went fine until i tried to run the netinstall script. Error - can't use sudo ... So i had to install sudo first and add my user to sudo before i was able to successfully launch the script.

This is because you chose to enter a root password when running the Debian stretch ISO.

BunsenLabs ships with the root account locked so if you had chosen not to enter a root password then the first user would have been added to the sudo group (and the package installed) automatically.

This is actually covered in the README for the bunsen-netinstall script, see the first point in the "Debian Netinstall Hints" section:

1) At the "Set up users and passwords" screen,
do NOT enter a password for root.
Type nothing and press "continue".
Do this again at "Re-enter password to verify".
Enter your own name and password as normal.
You will then be given 'sudo' permissions,
which will be needed in the script.

https://raw.githubusercontent.com/Bunse … ter/README

nederpils · 2018-01-25 22:40:05

Uuups - my fault - of course - i almost never, ever read read-me's - instead i just followed what i have read in the relevant thread here in the forum ;-) apologize - maybe i am the only one not reading read-me's ... thx. for the explanation.

grobister · 2018-01-30 08:33:20

I used this method twice in the past two days, really happy with Helium so far.
Good work!

cloverskull · 2018-01-30 17:25:39

I just tried this today in VMWare and hit a few snags.

First off, debian stretch doesn't trust github, so I had to wget the bunsen installers with the --no-check-certificate flag.

Second, it looks like there are some issues with the BL helium repos. I get the following error logs:

Err:9 https://kelaino.bunsenlabs.org/~johnraff/debian helium/main amd64 Packages
  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

It's worth mentioning that this is the 9th "Ign:" line, and it tries the 9th/10th/11th/12th over and over again (the BL repos) and then eventually ends up with:

Reading package lists...
W: The repository 'https://kelaino.bunsenlabs.org/~johnraff/debian helium Release' does not have a Release file.
E: Failed to fetch https://kelaino.bunsenlabs.org/~johnraff/debian/dists/helium/main/binary-amd64/Packages . server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
E: Some index files failed to download. They have been ignored, or old ones used instead.

I'm trying to set up a new dev environment in VMWare using BL as my desktop and any help soon-ish would be appreciated

Head_on_a_Stick · 2018-01-30 17:37:44

cloverskull wrote:

First off, debian stretch doesn't trust github, so I had to wget the bunsen installers with the --no-check-certificate flag.

Check your system time, the certificates don't work if the clock is wrong

#181 2017-12-24 21:14:55

Re: Installing BunsenLabs Helium-dev

#182 2017-12-24 21:31:32

Re: Installing BunsenLabs Helium-dev

#183 2017-12-24 21:41:34

Re: Installing BunsenLabs Helium-dev

#184 2017-12-24 22:05:34

Re: Installing BunsenLabs Helium-dev

#185 2017-12-26 17:41:47

Re: Installing BunsenLabs Helium-dev

#186 2017-12-26 17:45:16

Re: Installing BunsenLabs Helium-dev

#187 2018-01-05 17:19:26

Re: Installing BunsenLabs Helium-dev

#188 2018-01-06 12:25:54

Re: Installing BunsenLabs Helium-dev

#189 2018-01-06 15:01:20

Re: Installing BunsenLabs Helium-dev

#190 2018-01-06 15:03:35

Re: Installing BunsenLabs Helium-dev

#191 2018-01-06 15:11:11

Re: Installing BunsenLabs Helium-dev

#192 2018-01-06 15:22:31

Re: Installing BunsenLabs Helium-dev

#193 2018-01-22 12:40:59

Re: Installing BunsenLabs Helium-dev

#194 2018-01-22 21:32:00

Re: Installing BunsenLabs Helium-dev

#195 2018-01-25 21:51:18

Re: Installing BunsenLabs Helium-dev

#196 2018-01-25 22:11:40

Re: Installing BunsenLabs Helium-dev

#197 2018-01-25 22:40:05

Re: Installing BunsenLabs Helium-dev

#198 2018-01-30 08:33:20

Re: Installing BunsenLabs Helium-dev

#199 2018-01-30 17:25:39

Re: Installing BunsenLabs Helium-dev

#200 2018-01-30 17:37:44

Re: Installing BunsenLabs Helium-dev

Board footer