Thoughts on running Xubuntu and ZFS on root
https://distrowatch.com/weekly.php?issue=20191028#xubuntu

https://redd.it/do1ivu
@r_linux

Linux Experiences/Rants or Education/Certifications thread - October 28, 2019

Welcome to r/linux rants and experiences! This megathread is also to hear opinions from anyone just starting out with Linux or those that have used Linux (GNU or otherwise) for a long time.

Let us know what's annoying you, whats making you happy, or something that you want to get out to r/linux but didn't make the cut into a full post of it's own.

For those looking for certifications please use this megathread to ask about how to get certified whether it's for the business world or for your own satisfaction. Be sure to check out r/linuxadmin for more discussion in the SysAdmin world!

_Please keep questions in r/linuxquestions, r/linux4noobs, or the Wednesday automod thread._

https://redd.it/do3vpz
@r_linux

HTTPDirFS - a filesystem which allows you to mount HTTP directory listings, and servers which support Subsonic API.
https://github.com/fangfufu/httpdirfs/

https://redd.it/do34s5
@r_linux

Google Snap: a Microkernel Approach to Host Networking
https://ai.google/research/pubs/pub48630/

https://redd.it/do3ypr
@r_linux

Smart Platforms Article
https://pclite.net/manifesto

https://redd.it/do68sc
@r_linux

GraphQL Foundation Launches Interactive Landscape and Welcomes New Members from Open Source Summit Europe
https://wire.mpelembe.net/graphql-foundation-launches-interactive-landscape-and-welcomes-new-members-from-open-source-summit-europe/

https://redd.it/do6l90
@r_linux

Sell me on identifying disks based on UUIDS over Labels.

Why on earth would it be best practice to meaningfully identify a disk based on uniquely generated garbage?

Bad practice to use /dev/sda1 etc in fstab as it can change on you without notice so use a UUID?

Okay, why not identify via the label field? Human settable and meaningful data entry and still just as computationally static as a UUID field until manually manipulated. More accessibly changed yes but UUID is not immuteable either so is that really a argument that can stand?

Accidental conflicts are more likely to arise? Not if naming schemes are followed, regardless a malicious user is perfectly capable of changing the UUID on their USB thumb drive aswell so UUID doesnt even remove that risk.

Identifying via label makes certain processes significantly easier to understand by design aswell, migrating disks for example, provided you label correctly the fstab file won't require regeneration.

https://redd.it/do74qp
@r_linux

How many of your know about "sudo !!"?

I recently took up a teaching job and demonstrated to a class how to setup a security module. I forgot that I was in a user account and when I ran a command it gave out the permission denied message.

I typed "sudo !!" which runs the previous command as root. They were all like, woah! what was that command you did? They've all used Linux before and were quite familiar with it but they were just so amazed that they had not known about that simple command.

I spoke to some other IT teachers afterwards and they too had not known about this command. At this point I was quite surprised. So I thought I'd post here to let you all know about it, in case you weren't aware.

​

EDIT: To clear up any confusion as noted by u/bjrn: The '!!' element is used to refer to the previous command. It can be used in conjunction with anything really. It just saves you typing out the last command. The 'sudo' part is logically placing 'sudo' before '!!' which is the previous command.

https://redd.it/do7ocx
@r_linux

Linux Networking From Go
https://tomdnetto.net/post/linux_networking_from_go_nftables

https://redd.it/do8woi
@r_linux

Video by a former director explaining the context and importance of fighting off the Rothschild patent troll (even if you don't use GNOME or Shotwell), in terms anyone can understand
https://invidio.us/watch?v=OacaptJDj1I

https://redd.it/doa2cd
@r_linux

How to remove duplicate lines from files with awk without sorting or changing their order
https://opensource.com/article/19/10/remove-duplicate-lines-files-awk

https://redd.it/dob3hq
@r_linux

Humble Book Bundle: Linux & BSD Bookshelf by No Starch Press
https://www.humblebundle.com/books/linux-bsd-bookshelf-2019-books

https://redd.it/dod8af
@r_linux

A new home for KernelCI
https://www.collabora.com/news-and-blog/news-and-events/a-new-home-for-kernelci.html

https://redd.it/do98is
@r_linux

Unbox Therapy shows off Gnome without realising

[Unboxing Edward Snowden's Favorite Laptop](https://www.youtube.com/watch?v=hVcJgCvFuWo)


Interesting to see someones first impression.

https://redd.it/dof39l
@r_linux

Is Slackware a good distro for learning Linux ?

I was wondering if Slackware was a good distro for a learning tinkerer that likes to study, change and break stuff, while also being a main workstation.

I believe that such a distro should be :

* Well documented
* Stable, meaning that:
* It doesn't break easily
* It doesn't change all the time, it's not a rolling release
* Has a friendly and experienced userbase

I don't care about being supported or having recent packages, mainly because I only use free software and compiling exist.

So, would Slackware be a wise choice for me ?

And while you're at it, what are your thoughts on Slackware as a whole ?

Thank you for your time and have yourself a nice day :)

https://redd.it/dofrnv
@r_linux

Distributions Devroom Call for Participation - FOSDEM 2020

This isn't a spam. I am not affiliated with the event in any way except that I hope to speak there.

\---


\# FOSDEM 2020 - Distribution Devroom Call for Participation


The Distributions devroom will take place Sunday 2 February 2020 at
FOSDEM, in Brussels, Belgium at the Université Libre de Bruxelles.


As more and more workloads are being considered for containerization in
the future and are finally landing in virtualized environments today,
distributions remain a critical success factor and are more important
than ever. Containers, like virtual machines, are not magical and
rely on piles of software being assembled in a way that is repeatable,
reliable, and functional. This is at the very heart of the problem that
distributions have always solved.


Each distribution is responsible for building, testing, and releasing
software as well as managing the lifecycle of each application in the
collection. Additionally, distributions do very important work in ensuring
that various versions of upstream software work well together and can
co-exist. Distributions are also, often responsible, for "de-vendoring"
upstream software so that security fixes can be applied more quickly.


We welcome submissions targeted at contributors interested in issues
unique to distributions, especially in the following topics:


\# Topics and Areas of Focus


\## Focus Areas


\- The ways that distribution technologies can be leveraged to allow
  for easier creation of a multi-verse of artifacts from single source
  trees. This includes the increasing move toward self-contained
  applications and providing multiple non-parallel installed versions
  of software.


\- Efforts being made in shared environments around Build/Test/Release
  cycles.


\- Topics related to the delivery problem as it impacts updates in
  terms of both size and rollback/reliability are expected to be featured.


\## Additional Topic Ideas


\- Distribution and Community collaborations, eg: how does code flow from
  developers to end users across communities, ensuring trust and code
  audibility


\- Automating building software for redistribution to minimize human
  involvement, eg: bots that branch and build software, bots that
  participate as team members extending human involvement


\- Cross-distribution collaboration on common issues, eg: content
  distribution, infrastructure, and documentation


\- Growing distribution communities, eg: onboarding new users, helping
  new contributors learn community values and technology,  increasing
  contributor technical skills, recognizing and rewarding contribution


\- Principals of Rolling Releases, Long Term Supported Releases (LTS),
  Feature gated releases, and calendar releases


\- Distribution construction, installation, deployment, packaging and
  content management


\- Balancing new code and active upstreams verus security updates, back
  porting and minimization of user breaking changes


\- Delivering architecture independent software universally across
  architectures within the confines of distribution systems


\- Effectively communicating the difference in experience across
  architectures for developers, packagers, and users


\- Working with vendors and including them in the community


\- The future of distributions, emerging trends and evolving user demands
  from the idea of a platform


Ideal submissions are actionable and opinionated. Submissions may
be in the form of 25 or 50 minute talks, panel sessions, round-table
discussions, or Birds of a Feather (BoF) sessions.


Dates
\------
Submission Deadline: 01-Dec-2019 @ 2359 GMT
Acceptance Notification: 6-Dec-2019
Final Schedule Posted: 14-Dec-2019


How to submit
\--------------
Visit [https://penta.fosdem.org/submission/FOSDEM20](https://penta.fosdem.org/submission/FOSDEM20)


1.) If you do not have an account, create one here
2.) Click 'Create Event'
3.) Ente

r your presentation details
4.) Be sure to select the Distributions Devroom track!
5.) Submit


What to include
\---------------
\- The noscript of your submission
\- A 1-paragraph Abstract
\- A longer denoscription including the benefit of your talk to your target
  audience, including a definition of your target audience.
\- Approximate length / type of submission (talk, BoF, ...)
\- Links to related websites/blogs/talk material (if any)


Administrative Notes
\----------------
We will be live-streaming and recording the Distributions Devroom.
Presenting at FOSDEM implies permission to record your session and
distribute the recording afterwards. All videos will be made available
under the standard FOSDEM content license (CC-BY).


If you have any questions, feel free to contact the
devroom organizers: [distributions-devroom@lists.fosdem.org](mailto:distributions-devroom@lists.fosdem.org)
([https://lists.fosdem.org/listinfo/distributions-devroom](https://lists.fosdem.org/listinfo/distributions-devroom))


Cheers!


Brian Exelbierd (twitter: @bexelbie) and Brian Stinson (twitter:
@bstinsonmhk) for and on behalf of The Distributions Devroom Program
Committee

https://redd.it/doey2a
@r_linux

Sooo is the future of Btrfs in question with Ubuntu seemingly putting ZFS on future roadmaps?

Given that Canonical is allowing experimental adoption of ZFS by incorporating it into the installer options, I'm wondering if that will mean Btrfs will see less adoption moving forward? Also:

1. What advantages does ZFS provide over Btrfs currently given all the development that's being done with Btrfs?

2. Why is OpenSuse still the only major distribution who has settled on Btrfs as their de facto standard?

Thanks everyone!

https://redd.it/dobifs
@r_linux

Electron Packaging: What can be done to reduce the package sizes?

I've seen this online a lot that people complain about the huge package sizes of Electron apps (and RAM usage, but let's ignore that for a second), and it's because most (all?) of the apps distribute their own chromium runtime.

1. Why have we not got to the model of having a distro's electron package being a dependency for all electron apps reducing the eventual package sizes to around a few MBs each?

2. Are their any efforts in this direction? If so, what are the major hurdles left to cross?

https://redd.it/dohsnz
@r_linux

Recordings made a Ubucon Europe 2019 are now availlable

All talks and workshops made at [Ubucon Europe 2019](https://sintra2019.ubucon.org/) were recorded whenever the speaker authorized, now all those recordings that have enough quality (likely all) are being published on the [Ubucon Europe Youtube channel](https://www.youtube.com/channel/UCLCZ80HI7OJaMEGTTsEDDpA/).

https://redd.it/do8hb3
@r_linux

Smart or Outdated design?

One of my personal biggest flaws with Linux (and I'm not a huge Linux person, so you don't need to bust my ass over this), is that, from what I've seen, there is no way to install software to another drive/partition. Now, some software I've downloaded, I've noticed is self contained, it doesn't need to be installed, and can be run from seemingly any location.

But is there a reason we can't, for example: sudo apt install some\_software --dest /someDrive
(And yes, I'm aware the 'sudo apt install' command is not universal, and is only the method of installing software on certain distros, but that's besides my point).

Does it come down to some oudated design philosphy? Or are there actually very good reasons why this can't be done/isn't done?

https://redd.it/doiqnc
@r_linux