Repair Your System Using BunsenLabs Live and Chroot

BLizgreat! · 2019-01-05 04:33:28

At the risk of sounding like I'm not the mega skilled Nix-ninja that everybody knows I clearly am.

Does someone really need the debootstrap package for this to work overall ? Regardless about to find out, as I have an experiment going and don't really care if the targeted install for it implodes anyway. However also thanks to Tknomanzr for keeping info on this topic in circulation. Xaos52 saved me so much time + pain with his chroot how-to, I feel indebted for life to him.

Also ... gladly admit I'm still Nix-retarded and probably doomed to remain so forevermore !

Last edited by BLizgreat! (2019-01-05 04:36:09)

BLizgreat! · 2019-01-05 04:38:50

Nobody has Hoas's sum total of tech knowledge. ( Truly not even him.) Because he's part cybernetic life-form and his attachments to the internet allow him to know and find such required info as and when needed.

BLizgreat! · 2019-01-05 05:36:05

INTERESTING:

Ok not trying anything off-topic'ish here but here goes.

Ok situation, had installed LM v19 Cinnamon. Still like Linux Mint and was dorking around for old times sake. Well oddly enough it doesn't come with out of the box support for my Broadcom wireless card, whereas BL does. So I used this cool how-to, to chroot the puppy from a BL usb and install the packages I needed to that Mint install. Typing on it now, I did install the binutils package but didn't need the debbootstrap ( or at least install it in my case and it worked.)

Also one thing may want to add to the OP, just reminding people to exit the chroot with Ctrl + D before reboot ? Anyway thanks again for a convenient reference.

Again not a hijack attempt, if you want I'll get rid of any offending posts just let me know. But here is what I posted about this in the LM forums, describing the situation, wireless card I was having issues with and just think there's some good general observations about the power and potential use of chroot. Plus of course linked to this how-to, so the author gets credit. Also thanks to BL in general, actually used a similar approach to get my minimal base netinstall of Debian to work. Bunsenlabs rocks ... supports hardware out-of-box even LM doesn't !!!!

VLC!!! ... no not the media player thingy, that's Viva la Chroot!

Last edited by BLizgreat! (2019-01-05 06:48:44)

DeepDayze · 2019-01-05 17:05:46

Good to see you posting again BLizgreat, and your comments are insightful (and humorous at times).

BLizgreat! · 2019-01-06 02:54:59

^ Thanks fellow nixer, is good to see you too.

BLizgreat! · 2019-01-29 07:34:40

Well owe tknomanzr another thanks for putting this how-to up. This has saved me mucho butt-aches and time. Straight forward, effective, is appreciated.

Just for the record, I also finally figured out why the BL.iso worked on LM 19.1 Cinnamon(32bit) but failed with the Mate version. Was due to the BL.iso being 32bit, the MATE install was 64b, supposedly someone can use this kickbutt live-session chroot goodness with a 64b iso to rescue a 32b OS but not the other way around. Am fairly sure there are ways to do it, multi-arch blahblah but just wanted to note this in case someone ends up running up against a similar situation.

Thanks Tknomanzr.

Last edited by BLizgreat! (2019-01-29 07:35:49)

BLizgreat! · 2019-10-30 08:51:47

Reason for visit, to kiss tknomanzr's cyber butt for putting this easy to follow chroot from live how-to up. Errrr, well going with shake his cyberhand or whatever but this tute has saved me mucho time and pain. Last few days wrapping up installing Buster, config'ed as I like it and it's been a real ordeal. In which this tute was heavily relied on to get the job done.

Also NUMEROUS thanks goes out to the BL team for including support for broadcom with b43 module. Even the dang Debian unofficial with nonfree netinstall iso, ... nope screw me. Could've taken other approaches ie: Chroot the damn thing from one of the Stretch-etc installs on the system that already have working wireless or even just download the packages and quickly transferred them to the non-net install + "dpkg -i *.deb" the stupid things but BL is kickarse for going the extra mile for us poor bastids afflicted by broadcom !

THANKS VERY MUCH Tknomanzr and BL team !!! YA'LL ROCK !

Last edited by BLizgreat! (2019-10-30 08:54:06)

BLizgreat! · 2019-11-12 04:03:33

Random note on this:

Couple of things I've noticed and have USED this tute a lot. :)

One issue someone may encounter when copying the BL's /etc/resolv.conf over, it'll complain about a dangling symlink on the target OS (depending) does so in Buster. Simple fix for it to rm - remove the resolv.conf file on that target system. I tend to do the whole process as root, making my user such in BL's live session with "sudo su", otherwise use sudo in below.

rm /mnt/chroot/etc/resolv.conf

Which is what it does, removes the file, then cp the /etc/resolv.conf file you're wanting and it'll succeed without danging symlink crappo. Also really think this should be scripted and built into the BL iso's too. Messing around with this and similar stuff. However my bash skills are somewhat lacking. I've had all manner of pdfs/bks on bash and using it in scripting on my system(s) forever. Though I must've been wrong, I thought if someone downloaded and kept bks on a subject long enough, the knowledge and info in them would seep through the hard drive, up the keyboard and into someone's brain, without need of reading them ? No ? Doesn't work that way ? Really ? Lmao. :D

It's on the 2-dork list though. Just stringing all necessary commands together, a pop-up which asks which partition/drive is to be mounted at /mnt/chroot and run/mount the rest of it a conditional thingy to check whether or not /mnt/chroot/etc/resolv.conf exists, if does run the remove (or back it up)command and then the cp command, otherwise just the cp one and whamo, proceed with script doing the chroot /mnt/chroot and ... JOY ! Also get complaints about /dev/pts not being mounted but don't much care or feel it's necessary in this to work.

Last edited by BLizgreat! (2019-11-12 06:17:10)

BLizgreat! · 2019-11-12 07:18:16

Pointless elaboration on the above, symlinking nonsense. Been griping in other threads about it, 900 progs now want to manage and/or overwrite resolv.conf ! Clearly on modern gnu/Nix, appears they like adding a symlink to control it too ! Check with ..

ls -l /etc/resolv.conf

Would show you what's linked to and fiddling with your resolv.conf file. Nothing comes back with the way this Stretch OS is config'ed anyway. However my other Buster does, it shows a symlink to resolvconf.service as griped about in other threads. Sheesh just leave my resolv.conf file ALONE DAMMIT !

Last edited by BLizgreat! (2019-11-12 07:19:32)

#21 2019-01-05 04:33:28

Re: Repair Your System Using BunsenLabs Live and Chroot

#22 2019-01-05 04:38:50

Re: Repair Your System Using BunsenLabs Live and Chroot

#23 2019-01-05 05:36:05

Re: Repair Your System Using BunsenLabs Live and Chroot

#24 2019-01-05 17:05:46

Re: Repair Your System Using BunsenLabs Live and Chroot

#25 2019-01-06 02:54:59

Re: Repair Your System Using BunsenLabs Live and Chroot

#26 2019-01-29 07:34:40

Re: Repair Your System Using BunsenLabs Live and Chroot

#27 2019-10-30 08:51:47

Re: Repair Your System Using BunsenLabs Live and Chroot

#28 2019-11-12 04:03:33

Re: Repair Your System Using BunsenLabs Live and Chroot

#29 2019-11-12 07:18:16

Re: Repair Your System Using BunsenLabs Live and Chroot

Board footer