Heh, if you think Lenovo is bad and mac vs Lenovo is a bad choice to have to make…
…what do you put forth as the shining beacon of laptop mfgs? Cos it ain’t Dell, and it sure isn’t HP.
Who else is there?
Heh, if you think Lenovo is bad and mac vs Lenovo is a bad choice to have to make…
…what do you put forth as the shining beacon of laptop mfgs? Cos it ain’t Dell, and it sure isn’t HP.
Who else is there?
That’s what most laptop OEMs do.
Dell is just “rebranded” Compal, Quanta, Clevo…
That’s not a bad thing and the ODM/OEM system is not anything new.
Sometimes the difference is just the badge, sometimes it’s firmware changes too, sometimes it’s completely customized to the OEM specifications.
It has varied a lot over time and mostly depends on how big the OEM is and proportionally how much time/effort/expense they want to throw at a particular design.
For screenshots I recommend Greenshot. Simple to use and good annotation tools.
I think you might have a different understanding of support than most. Nobody’s saying that the code to run this 30-year-old hardware should be enabled by default nor that distros should have them included by default.
That’s very different from whether the code is in the kernel in case someone wants to compile a custom kernel that does support it. Source code that’s disabled doesn’t add bloat to running systems.
/srv is for “site-specific data which is served by this system.”
How to interpret that is up to for debate, but it seems clearly to be “user files” as opposed to “system files”. “Served” is a bit ambiguous but I don’t think it really requires that it be made accessible with a network service.
Basically I’d treat this as a location to mount/store your non-personal data such as music, videos, etc that should be accessible to anyone using your system. It could be network-exported as well but doesn’t have to be.
/net is for files imported from the network.
There’s intel as well. Probably a few other small players. Is Matrox still around?
What a confusing headline.
Is there any reason this 5% number still holds true? Back in the days of 40 MB hard drives it made sense to make sure the system didn’t totally run out while root was fixing the low disk situation … but these days even 1% is still several gigabytes of space, not likely to run out that quickly.
Yes… I’d classify context as a reboot of latex.
I’d say only open/libreoffice fits that.
Edit: maybe Tex/latex/lyx too, but context is not.
There are many instances like that. Systemd vs system V init, x vs Wayland, ed vs vim, Tex vs latex vs lyx vs context, OpenOffice vs libreoffice.
Usually someone identifies a problem or a new way of doing things… then a lot of people adapt and some people don’t. Sometimes the new improvement is worse, sometimes it inspires a revival of the old system for the better…
It’s almost never catastrophic for anyone involved.
Probably, yeah. Depends on a few other things (drive age, SMART test results, how risk-averse you are…)
But at least it’s worth thinking about.
There’s a lot of options for which key to use for compose. And you can set right-alt to be that key very easily.
laser printers can print color but it’s a bit expensive up front.
Semi-embedded removed like this is always astoundingly outdated.
How so?
Beginning to conscript women as well as men does not equate to abolishing the military, or am I missing something?
Binning a sexist conscription system is not anything close to “binning the military”
What the removed is a labtop?
Also a testament to how much of a benefit it is when the vendors just get out of the way and don’t feel the need to add their own Special SauceTM to the drivers.