4 ms·
Oddly enough, I had a lot of trouble getting my new laptop to boot, work and sleep properly. Not for lack of experience: I first installed linux in the summer o
by Arnt 12y ago
Oddly enough, I had a lot of trouble getting my new laptop to boot, work and sleep properly. Not for lack of experience: I first installed linux in the summer of 1992 using hlu's floppies and have used linux for daily work for about 20 of the 22½ years since then.
I can easily believe that someone used to windows with its mishmash of installers might have an unpleasant experience. Apt-get works wonderfully on a pristine system, but not so well if the system is halfway upgefucked with tarballs and rm -rf.
And particularly if systemd on ubuntu 14.04 supports his hardware as poorly as it supports my new laptop.
- zamalek 12y agoapt-get also only works extremely well for FOSS releases. If something is closed source (reality check) the developer will need to maintain the a build for each distro+release. The user will also need to add that apt repo and click through Linux's warnings about that. > What a pity they've decided to take a political position rather than a technological one. Ironically, it's the political (rather: religious) position of Linux that is getting in the way here. If you're not looking through the rosey colored RMS glasses it's very clear that the dev has taken the practical position. Don't get me wrong, I wish it was different. Linux has amazing potential, but it unrealistically hostile toward these guys. Maybe SteamOS will bring some uniformity to the situation.
- vetinari 12y agoIf you build your binaries against Ubuntu 12.04 (=glibc 2.15 symbols), chances are, that it will be extremely compatible with many distributions for years to come. Just make sure you know, what API you are really linking against. The resulting package can install the repo by itself - i.e. user downloads the package, install it and suddenly, he has repo for updates installed. Google Chrome does it, for example.
- zamalek 12y agoInteresting! I assume you would have to statically link all other libs? Distros often swap out e.g. libfoo for foolib and from my own experience that usually ends up being a rabbit hole of "make."
- vetinari 12y agoYou need to be able to make call, which libraries you are going to link dynamically. LSB libs, X11 and other parts of the infrastructure with staying history are safe, some random foo library is probably not.
- fit2rule 12y agoI'm with you - been running Linux since those days too, and I also think that the problem is entirely political in this case - he's already admitted that its not for any problem with the Linux host for C4 in particular, just that he's a frustrated Linux desktop user and wants nothing to do with Linux. But the Linux support is there and the C4 engine works on it .. so this is more of a political rant than anything else.
- Arnt 12y agoIn that case I expressed myself badly (possibly due to systemd-induced gritting of teeth). Sorry. I think it doesn't have to be political. The tiniest bit of ill will towards linux, a bit of windows-like behaviour (tar xf, rm -rf), and a bit of badly-supported hardware is quite enough to end up with an unworkable system and difficult-to-diagnode problems.
- digi_owl 12y agoThe basic problem with systemd is that its "dependencies" based design result in all manner of nondeterministic behavior. And i suspect this has little to do with the original complaint. I think that is more in terms of "lib version X-1 do not support the feature i need, X+1 breaks a different feature in a subtle way, and version X can't be found in any distro repo out there". Sadly the above is not a problem of Linux or libraries, but of distro package formats balking at having multiple lib versions installed at once.