Stories
Slash Boxes
Comments

SoylentNews is people

posted by on Wednesday February 22 2017, @09:56AM   Printer-friendly
from the it's-already-perfect-is-not-the-right-answer dept.

We all know about Microsoft's latest OS, so I won't rehash. A lot of us intensely dislike it, to put it politely. Those of us who can, use other operating systems. This is Soylent, so let's focus on the one that is the most important to us: Linux.

I have been using Windows as my OS since right after Atari times. A few years ago I bought an ARM (ARMHF/ARMv7) netbook and put Lubuntu on it. I had problems with my first Linux experience, mainly in the area of installing software: missing packages in Synaptic, small dependency hells, installing a package at a time by hand, some broken stuff. I put it down mainly to the architecture I have been using, which can't be supported as well as x86-64.

Now, we all know that no software is perfect, and neither is Linux, even though it is now my main OS. We support it in spirit and financially, but there is always room for improvement.

So, the question is: What are your problems with Linux and how can we fix them? How do we better it? Maybe it's filesystems, maybe it's the famous/infamous systemd. Let's have at it.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Wednesday February 22 2017, @01:00PM

    by Anonymous Coward on Wednesday February 22 2017, @01:00PM (#470134)

    linux is damn f#cking awesome. until it is not. but that's still better then winblows : )

    example: sometimes you have to configure some network device that came straight from the box.
    it has a default IP you connect to via (mostly) IExplorer.exe (bleh) and you cahnge the ip address of the winblows box.
    after config, you connect the device to the overall network-lan and then you go about changing the ip of the winblows back.
    sometimes you are not happy, reset the device (for example). do this "ip-of-windows-changing" thing a few times without a
    reboot in between and it just craps out. no more ping, no more loading of the config-webpage of the device. only a reboot will "fix" it.

    with linux i can tell it a new ip-address and it swallows it with a big gulp and a smile. it can do this all day long : )

  • (Score: 2) by J053 on Thursday February 23 2017, @02:19AM

    by J053 (3532) <reversethis-{xc. ... s} {ta} {enikad}> on Thursday February 23 2017, @02:19AM (#470563) Homepage
    A neat trick for this use case:
    • Connect the new device to your LAN (supposing, of course, that your LAN doesn't have the same network as the new device - that could get confusing if you already have a 192.168.2.10 or 10.10.0.1 or whatever).
    • On your Linux box, use "ip addr add" to just add an address on that net to your Ethernet device:ip addr add 192.168.2.100/24 dev eth0, for example.
    • Use Chrome or Firefox to get into the new device and set up its networking correctly.
    • Use "ip addr del" to get rid of the temporary address from the Linux box.

    Viola!