Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A Linux Evening

fabiensanglard.net

Post reply on HN
Print view View original

181–190 of 330 posts

Re: A Linux Evening

#181

Post by hackeraccount »

vid wrote: post #22

Someone should tell the author about the great lshw, it lists full details of the system board (and everything else) without having to go to a GUI display. azalp description: Desktop Computer product: B660M AORUS PRO AX DDR4 (Default string) vendor: Gigabyte Technology Co., Ltd. version: -CF serial: Default string width: 64 bits capabilities: smbios-3.4.0 dmi-3.4.0 smp vsyscall32 configuration: boot=normal chassis=de…

This. I generally have few problems with the people I work with one exception is when they start posting screenshots on Slack. If it's some gui and you can't get a good export then I understand the frustration - but this will be a screen shot of terminal.

Why? I mean do you hate the future? Did a month from the present beat you up as a child? Perhaps when you were 10 years old 2 years from now kicked sand in your face and now you're going to punish it. I don't know. But they need to get over it for everyone's sake.

Re: A Linux Evening

#182

Post by nortonham »

vehemenz wrote: post #116

1. If you don't encounter any trouble daily driving GNU/Linux, that is actually a sign of inexperience . That or you're doing nothing interesting. 2. If principles mattered more than convenience, most Linux users would be on FreeBSD or OpenBSD instead of GNU/Linux. Either follow your arguments to their conclusions, or understand that Windows/macOS users are doing the same thing as you—making practical tradeoffs. 3. U…

Point 2: What makes you say that, and what principles specifically are you assuming every gnu/linux user has that would lead them to Free/OpenBSD (and not dragonfly or net)?

Re: A Linux Evening

#183

Post by ur-whale »

> When I emerge from these "Linux evenings", I wonder if the real problem is my attitude.

It isn't. I mostly use Linux and sometimes (work) have to use windows.

The exact same thing happens with windows if you try to do anything remotely techy on it.

The difference though is that "Windows evening" often end in failure because at some point, you hit the wall of a binary blob whose source code isn't online.

Re: A Linux Evening

#184

Post by hackeraccount »

The saddest thing of all (I think there's some XKCD referencing this) is when you have a technical problem like this and you find some post from a year or two years ago exactly describing the problem. And there's no reply.

Empathy isn't the word. It's feeling like you're trapped on a deserted island in a vast empty sea - suddenly realizing that there's another S.O.B. who's been right next to you the whole time and also knowing that neither of you has the faintest idea how to get off the island.

Re: A Linux Evening

#185

Post by arghwhat »

jodrellblank wrote: post #154
blueflow wrote: post #62

Earlier quoted context omitted.

Quoted post unavailable.

You are free to comment on the question raised, instead of a dismissive empty ad-hom.

While tongue in cheek, the answer is accurate: open source does not mean "free service contract", it means that you can take the code and modify yourself (and preferably upstream the fix).

Patches come both from vendors and users experiencing an issue. Vendors take care of most things, but for esoteric problems you might only have a handful of people experiencing it. The vendor is unlikely to care, so if you do not write the patch or pay someone to do it, who will?

Still better than the competition, where such problems will never be fixed unless it generates sufficient bad PR...

Re: A Linux Evening

#186

Post by nortonham »

vehemenz wrote: post #116

1. If you don't encounter any trouble daily driving GNU/Linux, that is actually a sign of inexperience . That or you're doing nothing interesting. 2. If principles mattered more than convenience, most Linux users would be on FreeBSD or OpenBSD instead of GNU/Linux. Either follow your arguments to their conclusions, or understand that Windows/macOS users are doing the same thing as you—making practical tradeoffs. 3. U…

1) Yes for quite some time I only do fairly basic/uninteresting things. That being said, gnu/linux has become far easier to use than it was, say 20 years ago.

Re: A Linux Evening

#187

Post by reshie »

diego_sandoval wrote: post #165
markus_zhang wrote: post #85

Earlier quoted context omitted.

Thanks, but I actually wanted to learn low level stuffs, or I thought I wanted. Anyway I'll see what happens. So far nothing really clicks for me but if that's it then that's it.

People say "Arch makes you learn how Linux really works", but I don't think that's a good way to put it. Arch teaches you about the most boring parts of how linux works: the specific idiosyncrasies and configuration minutiae of a ton of libraries and programs (GNU coreutils, systemd, udev, mesa, glib, X11, Xlib, xdg, dbus, etc.) Arch will usually not teach you the really interesting "low level" things about Linux: Ho…

gentoo gets pretty close for a full OS system.

Re: A Linux Evening

#188

Post by II2II »

_justinfunk wrote: post #44

I used to hear "Linux is only free if you don't value your time." - this article seems to validate that this is still the case. Am I getting the wrong impression?

It really depends upon what you are doing with your machine.

If you're dealing with new hardware, situations like the one described in the article may pop up since vendors will focus their testing on Windows (and possibly macOS) so there is a good chance that it will work on the commercial operating systems but not the open source ones. That is going to be especially true to more exotic hardware since there will also be less testing by the open source community.

On the other hand, I find managing a Linux system significantly more time efficient. Some of it is because of the nature of open source. For example: installing, updating, and removing software is much easier since the licensing model allows distribution maintainers to create a universal software management tool. In other cases, it is simply because of the approaches typically taken by open source developers. For example: it is usually easy to copy configuration files from one system to another.

Re: A Linux Evening

#189

Post by dkozel »

fabiensanglard wrote: post #159
dkozel wrote: post #138

Hi folks. :) I'm so glad that my hit-and-run post has been so useful. After seeing Fabien's blog post I did a quick search and it turns out that the solution has spread fairly broadly to other forums. My choice of 0x33 was arbitrary so makes a nice canary for seeing it spread out. I'm thrilled. Sharing experiences and solutions is so essential to learning. I've benefited enormously from the generosity of open source…

The internet is amazing! The way it allows people to connect, help each other and sometimes also reconnect is heartwarming. If you have a PayPal account, I will gladly contribute to your microscope fund! Thank you again, and happy end of year!

Thanks Fabien!

Also I love all your retro work. I have a NeXTStation Turbo Color that's my retro pride and joy. Have you seen or been involved in any of the Demoscene activities? It's amazing the graphics that people are able to squeeze and abuse out of older hardware.

Off topic, but folks might enjoy Poems for Bugs, a talk where Linus Åkesson talks about cycle accurate coding to exploit GPU bugs in the C64. https://www.linusakesson.net/programming/poems-for-bugs/inde...

Re: A Linux Evening

#190

Post by bscphil »

vehemenz wrote: post #116

1. If you don't encounter any trouble daily driving GNU/Linux, that is actually a sign of inexperience . That or you're doing nothing interesting. 2. If principles mattered more than convenience, most Linux users would be on FreeBSD or OpenBSD instead of GNU/Linux. Either follow your arguments to their conclusions, or understand that Windows/macOS users are doing the same thing as you—making practical tradeoffs. 3. U…

> If principles mattered more than convenience

What principles? Is this another BSD vs GPL licensing turf war you're trying to start here? I think there are obviously coherent sets of principles on which it makes sense to prefer the latter.

Post reply on HN