libc6

ioroboto · 2017-01-12 06:25:12

Hi everyone,

I was a long time user of CrunchBang until I ran into continuous libc6 issues. I'm sure that there may have been someone who had a similar problems and maybe these issues have been resolved since. However, when I gave up on it I decided to Install Debian with OpenBox and I copied a whole bunch of config files (with my person touch, of course) and essentially ended up with a similar system to what BunsenLabs is now. Even though it didn't exist then.

Since installing BL I haven't ran into this issue again (thankfully) even though I am using it much the same way I was before. I'm just trying to back track where this was fixed, if it was fixed, or what the issue may have been. For my personal knowledge as well as anyone else who may have ended up in a similar situation. I know you guys are doing fantastic work as I had been a disastrous Distro hopper for about 10 years until CrunchBang, then mimicking that system I ended up with one that didn't break for pretty the first time. I wouldn't have done this without the community support in #! and I had never even contributed to the forums, so Thank You.

But yeah, enough fanboyness, could someone please tell me what happened with libc6? (I searched the forums already, but if I missed it a link will do, I am in a rush 90% of the time).

Cheers Mates!

edit: I installed Debian+Gnome before BL this time after getting sick of W10(again). What a bloody disaster. Completely nonfunctional out of the box on my ThinkPad no less.

Last edited by ioroboto (2017-01-12 06:29:40)

Head_on_a_Stick · 2017-01-12 07:28:27

The whole libc6 thing was born out of users haphazardly upgrading parts of their system from foreign sources so that newer versions of programs, or programs only available from Ubuntu PPAs, could be installed.

As long as you follow the basic rules then you should be absolutely fine:

https://wiki.debian.org/DontBreakDebian

There are several "safe" methods of obtaining newer package versions that do not require a libc6 upgrade or mixed sources:

https://wiki.debian.org/Backports

https://wiki.debian.org/SimpleBackportCreation

https://wiki.debian.org/CreatePackageFromPPA

http://forums.debian.net/viewtopic.php?f=16&t=130057

http://forums.debian.net/viewtopic.php?f=16&t=38976

http://forums.debian.net/viewtopic.php?f=16&t=129390

http://flatpak.org/getting.html

Last edited by Head_on_a_Stick (2017-01-12 07:29:53)

ohnonot · 2017-01-12 07:32:29

libc6 is one of those pivotal libraries that most of the system depends on.
i suspect that you were trying to install software beyond wheezy on your crunchbang, maybe installing a newer version of libc, which ultimately broke your system:
https://wiki.debian.org/DontBreakDebian

so it is not a bug or something that needed to be fixed by BL devs - it happened on your system only.

oh, and welcome to the forums!

edit: HoaS, you're typing too fast! grrrrr!!!

Last edited by ohnonot (2017-01-12 07:33:15)

ioroboto · 2017-01-12 07:52:31

Haha, I guess the irony is by haphazardly breaking my linux I ended up with a stable one.

It's growing on me quickly that if I'm going to have a functioning computer and play with Linux again I 'might' need two computers. Even partitioning doesn't seem to be a safe way of protecting two systems on one device. Is there another form of Redundancy I could use? I travel constantly and carrying 2 computers is a hassle.

I want to keep breaking my Linux, there's not much I can do about it. I need a form of Redundancy that can be used preferably without the internet. Any ideas?

edit: To clarify I mean 1 computer, 2 operating systems, 1 or more forms of Physical Redundancy - is there a small device for this or is this a pipe dream? USB w/ some kind of software to back it up? (sorry I realize this is a new question)

Thank you and hello also!

Ps. I feel terrible, I actually wrote a script for a simplified version of Deb+OB which got lost in the ether. It was similar to BL's. I only want a toy to break so anything I learn from it can be given back to BL this time. No more being selfish.

Last edited by ioroboto (2017-01-12 08:09:25)

Head_on_a_Stick · 2017-01-12 08:06:22

I think that my last two links offer what you want — containerisation is a simple way of separating the dependency trees whilst allowing the disk & processor resources to be shared.

It is also possible to use virtualisation (but then the resources must be split) or dual-booting (but then the convenience is lost).

ioroboto · 2017-01-12 08:11:37

Genius. I assumed it was in there but it's quicker to find if it's pointed out (time restraints), i'll start looking into it. Thanks a bunch.

ohnonot · 2017-01-13 07:27:26

ioroboto wrote:

Even partitioning doesn't seem to be a safe way of protecting two systems on one device.

you mean dual-booting? why not?

ioroboto · 2017-01-14 11:28:05

It's not really dual if there's more than 2. I meant 2 as the minimum level of Redundancy on one ssd. Or more too the point I was looking for as much Redundancy as possible for my given situation. I generally use Cloud based but it's useless if I'm on a 14H flight.

(dual-boot won't save my system if the drive dies)

Last edited by ioroboto (2017-01-14 11:29:18)

KrunchTime · 2017-01-22 23:30:55

IMHO, virtualization is the way to go if you want to play around while avoiding hosing your actual day-to-day OS. Of course, that's assuming you have the proper resources (fairly up-to-date CPU and at least 8gb of RAM) to use virtualization. Another option is to install an additional hard drive if you have the open slot for doing so. If either of the aforementioned isn't an option, you can buy a new computer or multi-boot.

Last edited by KrunchTime (2017-01-22 23:32:00)

nobody · 2017-01-23 11:41:40

KrunchTime wrote:

IMHO, virtualization is the way to go if you want to play around while avoiding hosing your actual day-to-day OS. Of course, that's assuming you have the proper resources (fairly up-to-date CPU and at least 8gb of RAM) to use virtualization. Another option is to install an additional hard drive if you have the open slot for doing so. If either of the aforementioned isn't an option, you can buy a new computer or multi-boot.

To use different userlands, systemd-nspawn containers/Linux namespaces are a good way to go. For example, I have a debian unstable container with Debian userland , a BL container with debian jessie userland, and an Ubuntu 16.10 container with Ubuntu userland available instantly, with networking correctly set up, by running

sudo systemd-nspawn -D lib/vm/sid/
sudo systemd-nspawn -D lib/vm/jessie/
sudo systemd-nspawn -D lib/vm/yak/

#1 2017-01-12 06:25:12

libc6

#2 2017-01-12 07:28:27

Re: libc6

#3 2017-01-12 07:32:29

Re: libc6

#4 2017-01-12 07:52:31

Re: libc6

#5 2017-01-12 08:06:22

Re: libc6

#6 2017-01-12 08:11:37

Re: libc6

#7 2017-01-13 07:27:26

Re: libc6

#8 2017-01-14 11:28:05

Re: libc6

#9 2017-01-22 23:30:55

Re: libc6

#10 2017-01-23 11:41:40

Re: libc6

Board footer