What linux should i use

Hi i want to replace windows 7 with some lightweight linux because my computer is pretty i use it mainly for gaming so my specs are these
RAM: 1.84GB
CPU: INTEL CORE DUO 2.50GHZ
GPU: INTEL EXPRESS CHIPSET Q43/Q45
can you suggest me a smooth linux where i can game because windows 7 use a lot of ram thanks

https://redd.it/bsew7b
@r_linux

monitor network usage per browser tab

Hi,
I am looking for a software or Chrome add on that will monitor internet usage per browser tab.
I googled a lot (days) and didn't find a real solution for this.
I want to see a list of browsertabs orderd by total downloaded data.
ntop can probably do it, but do I realy have to learn and configure a complicated program do achieve this?

https://redd.it/bsg9zn
@r_linux

Ubuntu feels bloated...or is it just me?
https://redd.it/bsglhq
@r_linux

Space Station welcomes free-flying, Ubuntu-powered autonomous robots
http://linuxgizmos.com/space-station-welcomes-free-flying-ubuntu-powered-autonomous-robots/

https://redd.it/bsh25g
@r_linux

The T-Shirt my GF offered me
https://redd.it/bshi1k
@r_linux

Before Ubuntu existed, what distro was considered the easiest, most beginner-friendly one?



https://redd.it/bshtje
@r_linux

Weekend Fluff / Linux in the Wild Thread - May 24, 2019

Welcome to the weekend! This stickied thread is for you to post pictures of your ubuntu 2006 install disk, slackware floppies, on-topic memes or more.

When it's not the weekend, be sure to check out r/WildLinuxAppears or r/linuxmemes!

https://redd.it/bsjhw3
@r_linux

LOT Polish Airlines and SUSE Linux - A Customer Success Story
https://www.youtube.com/watch?time_continue=1&v=rAhRSLqyXcA

https://redd.it/bsiehq
@r_linux

Please don't theme our apps
https://stopthemingmy.app

https://redd.it/bska96
@r_linux

Am I crazy for thinking about changing a new employer again after a few months should they continue their path to a more Microsoft based ecosystem?

I just started at a new employer a few months, ago because they pay really good compared to my city's average salary and offered a job I wanted because I developed a new passion towards Linux the last years in my life. I used Windows 20 years of my life, but about 5 years ago I fully switched to Linux at home and abandoned Windows and also Google services from my phone. Let's just say the NSA scandal made me think a looooot.

Last year I said to myself that I do also not want to work with Windows anymore (it was also that the salary was wayyy BELOW our city's average and we had to travel a lot and after 3.5 years there they did not want to take away my junior noscript.) and follow a mostly non closed-source, non telemetry, non big five (Google, Amazon, Apple, Facebook, Microsoft)-corporate path.

In my freetime I love to code, but since Linux related jobs are 90% admin jobs I took a new job at a local company. People are great, we are a big family etc etc. However, we are say 2.5 admins that have to do a SHITLOAD of work. 2 of us including me are new and one is part of the company for longer.

What they did not tell me is that about a year ago they did a fusion with a company from a neighboring country which of course uses a similar core service software for their core business that serves the same purpose. Ours is Linux based, theirs is windows based. Somehow in discussion they decided to go with the windows based software in the future and in the far future they will merge both softwares into a new one which will also be windows based.

Due to that fact we already had to install Windows machines the last 2 weeks, when we are really focusing on a much more important project. Learning the windows ecosystem is not of my interest, especially not enterprise-whise. I cannot do it in consensus with my leisure time skill, professional skill, philosophical, political or what-so-ever interest.

Thing is if it stayed at being just 10% of my work that would be OK and it will become wayyy more. The CEO (now our second CEO) from the company we fused with already talked with me about certificates related to Microsoft. My mind went immediately into alarm mote and I though: "I have to get out of here. Using anything but unixoid systems and open source" is plain wrong and utterly stupid.

Now my dilemma is. I just went into a Linux job for a first time and it would probably look bad as F in my CV if I changed an employee after a few month (because of that, because I will tell my reasons in all honesty to the next job interviewer!).

What would you guys do?

https://redd.it/bsj13e
@r_linux

Another open source / open hardware Linux phone: Dragonbox Pyra phone version teaser
https://youtube.com/watch?v=X3Su8LJnmd4&t=14m04s

https://redd.it/bskxrw
@r_linux

KTextEditor/Kate Bugs - Help Appreciated
https://cullmann.io/posts/ktexteditor-kate-bugs-help-appreciated/

https://redd.it/bsj4ob
@r_linux

Plasma is a breath of fresh air

I feel that Free Software should not only about the license, but also about empower me as a user, allow me to use my computer how I want it to be used.

Say what you want about Plasma and the KDE ecosystem, there might be some bugs and problems, like all software has.

But using KDE seems like the developers really want you to be in command.
Want a theme? There is an easy way to search and install themes inside Plasma.

Want bigger buttons or smaller buttons? No problem.
Want to remove noscript bars? No problem, there is an easy way to install Arc KDE.

I find this attitude refreshing, look at Krita it ships with different themes by default.

Say what you want about the design and problems, for me KDE is great because I feel like I can control my system to be however I want it to be. They don't even push me for reliance on some technologies like flatpak or systemd.

But it also works great out of the box, simple and intuitive. No wheels reinvented or designs meant for tablets or phones.

Thanks to all the Plasma and KDE developers for your awesome works!!!

https://redd.it/bsmbo7
@r_linux

Full-disk encryption Arch linux installation guide feat. encrypted GRUB and Evil Maid hardening
https://gist.github.com/huntrar/e42aee630bee3295b2c671d098c81268

https://redd.it/bskio0
@r_linux

There's a lot of nostalgia behind old WinXP profile pictures. What are some classic Linux images?



https://redd.it/bskt8c
@r_linux

All of the talks from Day 1 of the openSUSE conference are already online!
https://www.youtube.com/playlist?list=PL_AMhvchzBaeJiFMaZ3WsH7wt5ZXchUQ0

https://redd.it/bsmusf
@r_linux

Emulator basics: a stack and register machine
http://notes.eatonphil.com/emulator-basics-a-stack-and-register-machine.html

https://redd.it/bsmmy4
@r_linux

You probably hate systemd because you think it's all about "boot fast no bash" - but it can do so much more you probably had no idea about.

This is a bit of a rant, a bit of an educational post, and really came about because I'm just tired of how much flak systemd got and still gets based on obscure philosophical "issues". That's not to say I fully disagree, I'm just a pragmatist. I think it's better in a lot of ways. But when someone comes in to defend systemd, what do they usually have to offer? What improvements justify that philosophical sacrifice? "Uh, it boots fast. And BASH is annoying." Cool. Clearly that's convinced some people, but it doesn't really give any *compelling* reasons for why it's "better".

The documentation for systemd is utter crap, and finding out everything about what it can do involves slogging through pages and pages of boring documentation with no examples. Even those who have been using systemd for years probably have no idea of half of what it can do.

So I'm here to tell you about a couple *really cool features* that you probably never heard about, that might change your mind about systemd, at least in a practical sense. If they don't, that's fine. But at the very least, if you're stuck with it in every major distro, you can at least know some neat features that might be useful to you!

# #1 - Seriously, `service` units are great.

This one does come up a lot as a defense, but I'd be remiss not to repeat it. Boilerplate BASH SysV initnoscripts are crap. They're fragile, they're annoying to read, they're annoying to write, and half the time they're just calling `start-stop-daemon` anyways, which is a half-assed service manager at best. Systemd units are clean, concise, and powerful. They're worth a look on their own merits if you've ever written an initnoscript and hated every moment of it. You can auto-restart failed units, you can delay the restart, you can do actions... so much power, no BASH knowledge necessary.

# #2 - [Email yourself (or do whatever you want) on a service failure.](https://serverfault.com/a/701100/188250)

This is a cool little feature of units. You can specify an `OnFailure` entry in your unit to execute *another* arbitrary unit if the service fails. For example, a `oneshot` unit that sends you an email. Or perhaps starting a secondary daemon to do something else. Really anything you want.

# #3 - `ExecPreStart`/`ExecPostStart` and similar `Stop` commands

OK, yea, you can do this in BASH initnoscripts too, but Systemd just makes it so... accessible. Want to `git pull` before starting a service? Want to remove a cache directory on exit? Easy peasey. Add `ExecPreStart = /path/to/mynoscript` to execute `mynoscript` before starting the main `ExecStart`. And systemd will fail the whole unit if the `Pre` command fails. If you don't want that, you [can make them optional as well](https://unix.stackexchange.com/questions/404199/documentation-of-equals-minus-in-systemd-unit-files) by adding a `-` before the path.

# #4 - [Mount units](https://oguya.ch/posts/2015-09-01-systemd-mount-partition/)

This is a biggie. You may have heard of them in the context of `fstab`, how Systemd "destroys" it. But this is incredibly short-sighted. First, editing fstab programmatically (looking at you, Ansible) is a pain in the ass and fraught with dragons. Mount units let you create mount definitions atomically. Second, you can depend anything on them! Imagine you have an NFS filesystem and a Free Software Media server (shameless /r/jellyfin plug). You don't want that server to start if your filesystem isn't mounted, because bad things would happen if you do. What can you do? `mount -a` is a hack. No - use a `.mount` unit for your NFS volume, and then `Requires = my-mount.mount` in the service! Now you're safe.

There is one major caveat though: if you have a `-` in your mount directory target, you're going to have a *very bad time*, since the unit is named `path-to-mountpoint.mount` with the `-` replacing the filesystem `/` separator, and escaping the dashes almost never works. Otherwise, though, the

y're incredibly powerful.

# #5 - [Simple overrides with `unit.d` directories](https://unix.stackexchange.com/a/468067)

Have a unit installed by an operating system package, but you want to do some interesting things to it? The first thing everyone thinks is to just edit the `/lib/systemd/system/my-unit.service` file and go wild. But, this will be overwritten on an upgrade. OK, you might read a bit, and then copy it from `/lib` into `/etc`. That won't be overwritten. But now you've duplicated the unit, and won't get nice improvements from your packages. The solution? `/etc/systemd/system/my-unit.service.d/`! Using this directory, you can override small components of the unit file with your own values, for instance adding an `ExecPreStart` or a `Requires`. The above example uses the `systemctl edit` function, which automatically creates these overrides, but you can drop these files in manually too using your configuration management of choice.

# #6 - Targets - group services, mounts, etc. together

Target units are another really cool feature of Systemd. You've probably seen stuff like `Reached multi-user.target` in your boot logs, but you can of course create your own `targets` as well. Simply put, they group other units together. If two services and a mount are part of a target, the target won't be reached until all of them start, and you can, with a few modifications to the units - using `PartOf = mytarget.target` in the `[Unit]` section of the services/mounts - control all the services by stopping or starting the target itself, in the right order. Depend other services on targets as well for maximum control of the startup sequence. There's a ton of power here.

# #7 - `systemctl enable` and `systemctl disable`

This is a really basic one, but want to turn off a service or mount for a bit? Disable it! Want a service that is installed by default (such as `nginx`), but want to start it with `supervisord` instead and are getting a conflict? Disable it!

# #8 - PIDFile

A nice thing about Systemd is that you don't ever have to worry about PID files, including weird stale PIDfiles lying around and messing with your service startup. But still want one? You can still add one with `PIDFile=`.

# #9 - Sockets units can replace [x]inetd

The old style, "run a noscript on a socket connection" tool inetd and its modern successor xinetd can be replaced by [systemd `.socket` units](https://www.linux.com/blog/end-road-systemds-socket-units), bringing the ease of use and control of Systemd to your inetd services!

Those are the first 9 I can think of right now, but if you have any of your own cool systemd tricks, I'd love to hear them too!

https://redd.it/bsqar4
@r_linux

The Wine development release 4.9 is now available.
https://www.winehq.org/announce/4.9

https://redd.it/bspobe
@r_linux

Dear Ubuntu: Please Stop Packaging Epiphany If You Won’t Do It Properly
https://blogs.gnome.org/mcatanzaro/2019/05/24/dear-ubuntu-please-stop-packaging-epiphany-if-you-wont-do-it-properly/

https://redd.it/bsqvrw
@r_linux