SoylentNews is people
SoylentNews
Phoronix has an article up about some interesting ideas of Lennart Poettering about what could be a possible future for Linux:
Lennart Poettering of systemd and PulseAudio fame has published a lengthy blog post that shares his vision for how he wishes to change how Linux software systems are put together to address a wide variety of issues. The Btrfs file-system and systemd play big roles with his new vision. Long story short, Lennart is trying to tackle how Linux distributions and software systems themselves are assembled to improve security, deal with the challenges of upstream software vendors integrating into many different distributions, and "the classic Linux distribution scheme is frequently not what end users want."
This discussion has been archived.
No new comments can be posted.
New Linux Vision That Involves btrfs
|
Log In/Create an Account
| Top
| 99 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
McDonald's -- Because you're worth it.
(Score: 3, Informative) by cykros on Tuesday September 02 2014, @07:54PM
Installing software DOESN'T require privilege escalation. Nothing stops you from installing into your own ~/bin, ~/lib, etc.
Installing it system-wide, of course, does, and should, as system-critical files and directories require elevated privileges to write to them for a good reason.
(Score: 2) by tangomargarine on Tuesday September 02 2014, @08:24PM
Ah, yes, good point. I'm dimly aware there's some debate about where to install stuff to that I'm not privy to.
"Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
(Score: 2) by cykros on Monday September 15 2014, @09:01PM
It's less a matter of debate and more just something to consider when installing software. By installing system wide, you're generally aiming to make it available to more than one user on the system, whereas by installing in a home directory you're putting software in that is only to be used by that user (with normal permissions set up anyway). This makes it more suitable if you are using a multi-user system, such as a public shell server or shared work server. Furthermore, the decision can be impacted on your partitioning (or extra drives) scheme. In many cases, installing software into your /home partition means you'll retain it even if you choose reinstall your root system.