Live data from Hacker News

A Linux Evening

fabiensanglard.net

151–160 of 330 posts

Re: A Linux Evening

#151

Earlier quoted context omitted.

Hot-plugging Thunderbolt devices is hardly an edge-case on Macs, it's a heavily advertised feature. I had about weekly kernel panics or machine freezes (would not wake from sleep) while unplugging my Thunderbolt dock (with displays and lots of devices) all throughout the USB-C Intel Mac era, but they all went away when I got an M1 Pro machine, so I wonder how much is down to OS design vs drivers vs hardware (vs how s…

M1 machines don’t have bridgeOS at all, right?

If it can panic apparently they do have it.

https://en.wikipedia.org/wiki/BridgeOS says it runs the Touch Bar.

Re: A Linux Evening

#152
post #78

This is prototypical of the standard Linux experience, but I'd like to remark on just how much less common this sort of thing is. Modern Linux and modern Linux distributions have a much larger "just work" factor and it's getting better every year in my experience. Slowly and asymptotically, but it is improvement. This was driven home recently by my experience switching to NixOS. NixOS is brilliant in many ways, but b…

As user I would just return the device back and purchase a reliable USB based device. As a Mac-user would do? I guess a Windows-User would just rate [1/5] stars and don't even research. We should keep in mind: Linux users care a lot and do research. Most other will just say "nope" and leave it a issue for the manufacturer or keep turning it off and on again. What I don't know is if the initial situation is to blame u…

I wonder if this is why some of my monitors don't come back on after sleep. Is there a way to tell if macOS did the pause via the logs?

Re: A Linux Evening

#153

In my experience Linux is easy. Easy to install. Easy to upgrade. Never breaks. Never gets "infected". Fast. The absence of commercial bullshit is extremely nice too. (I like Debian) (Is it just me or is there a lot of FUD in this thread?)

> (Is it just me or is there a lot of FUD in this thread?)

Lots and lots of 'this is why I haven't used Linux for N years (and thus don't know what it's like)'.

I have to use Windows at work, and the system is way, way less predictable and reliable then any Linux system I've run for a decade. Shit changes out from underneath me (Windows Update, policy changes) in breaking ways all the time, and there's often no rest to inspect or reverse what causes breakage. For every 'evening of Linux' I've had on my life, I have a few 'afternoons of Windows' (mostly hopelessly, blindly turning things off and on again) every week.

When I ask colleagues who are my more accustomed to Windows than I am about how to solve issues, how to achieve particular configurations, or how Windows does certain things, it becomes clear that actually managing their workstations like comprehensible devices which are substantially under their own control is a foregone conclusion to them.

The reality for Windows users is not a system that actually 'just works', but a deeply internalized helplessness that manifests as conservatism (attempting little, assuming many reasonable configurations are not possible), superstition (attempting and advising reboots, constantly, without being able to articulate a real reason), and blindness to the outrageousness of the situation (e.g., thinking it's perfectly acceptable that their laptop can't handle an uptime of 4 days before it starts falling apart, or 'I always shut my laptop all the way down at the end of the day so it'll run better').

It's no wonder that people conditioned by this kind of usage pattern don't have a sense of what reliability or mastery look like in the Linux world, how frequently issues like this do or don't occur, how easy or hard they are to avoid, etc. They live on a different planet, where mastery in desktop computing is worthless because there's just no hope for a predictable, transparent system that doesn't change out from under your feet. It'll just break tomorrow anyway. And on their planet, it doesn't occur to anyone to research hardware compatibility ahead of time; they never need to. So of course the thought of spending an evening rooting out a hardware incompatibility issue strikes them as some mixture of futile, extremely burdensome, and unavoidable/common for those poor Linux users— even when none of those things are true.

Re: A Linux Evening

#154

Earlier quoted context omitted.

What is the point in having all of the drivers be open sourced and mainlined if we're not willing to fix them to support this?

Quoted post unavailable.

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

Re: A Linux Evening

#155

If OP used Windows exclusively, he'd have Windows evenings. There's tools that people complain about, and tools that people don't use.

Yeah. Anecdotally I once spent a "Windows Evening" trying to figure out why a game would freeze at the controls remapping menu. Found out that Windows' own game controllers menu was experiencing the same freeze. I went so far as to reinstall Windows entirely, only to find that the issue wasn't resolved. Started disconnecting devices out of desperation, only to find out that the issue was caused by the driver of a USB DAC I had connected...

Computers suck, in general. I have a hard time seeing an attempt to leverage blame on Windows or Linux as anything but an excuse to start a flame war.

Re: A Linux Evening

#157

Earlier quoted context omitted.

Linux is like driving a car with your hands in the engine

This contradicts my experience. I use Linux every day and I never touch the engine. I also set up Linux for computer-illiterate old ladies. They love it.

> I also set up Linux for computer-illiterate old ladies. They love it.

I think you're trying to say that they don't have problems with the browser, and maybe an email client. If they're computer-illiterate, they don't know enough about an operating system to have an opinion at all, other than being happy about it turning on and off when they want.

Don't mistake that for loving Linux, because it is not really praise of Linux, it is praise for a computer that works well enough to run a web browser, which is an extremely low bar.

Re: A Linux Evening

#158

Kernel parameters are usually documented in the kernel-parameters.txt file in the source. See https://github.com/torvalds/linux/blob/master/Documentation/... : hpbussize=nn The minimum amount of additional bus numbers reserved for buses below a hotplug bridge. Default is 1. The way to get from the error "No bus number available for hot-added bridge" at https://github.com/torvalds/linux/blob/master/drivers/pci/pr... t…

What's the approach used by OSes that "just work" for things like this? Is this due to the more monolithic kernel of Linux making more things required to be known up front than e.g. in Windows?

I always like this story about MacOs.

- Most OSes do a full dhcp look up when they connect to a network even if they have connected to the network before. Wifi saved networks is a good example of a network where you have some historical information on the connection

- MacOs however keeps track of the IP addresses that it saw for each of the networks it has connected to recently. If it sees a network it's been on before, it first tries to just use the old IP address. This is under the assumption that the lease is still tied to the user's laptop.

- In the best case, the laptop gets a working IP very quickly and in the worst case, you just do dhcp again

- From a user's perspective, if they walk into a meeting with a bunch of folks with non Mac laptops, it will seem like the Mac connects much faster than everyone else's machine

When I read this story, the author pointed out that many people say "Macs just feel like they work better!" and used this as an example. Granted, this partly comes from owning the ENTIRE stack from hardware to drivers to OS etc which is something only Mac can do.

Re: A Linux Evening

#159
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!

Re: A Linux Evening

#160

Earlier quoted context omitted.

There’re also real dual-SIM iPhones, but they’re market restricted (typically to China). Docs for SIM + eSIM: https://support.apple.com/en-gb/guide/iphone/iph9c5776d3c/io... Docs for dual physical SIM: https://support.apple.com/en-us/HT209086

I used to have a dual physical SIM iPhone X from China! However, when I sent it in to get (warranty) a local Apple repair shop screwed up and replaced it with a North American model. After much gnashing of teeth with Apple Support, I wound up with a new iPhone 12…but no dual physical SIM. Now my phone is still confused after restoring from backup and cannot see the eSIM. I’ve been filing feedbacks and radars to no av…

Not sure if this would help, but I recently learned about a product called iMazing[1] that lets you browse and edit iTunes backups.

You can't access the whole filesystem of a running iDevice with it, but you can access the whole filesystem of the backup. So I suspect it might be possible for you to clean-up the backup offline & then restore it. (At a minimum it should enable you to extract the valuable contents out of the backup and manually restore it on top of a clean iOS install.)

I've used it with some success to extract info from the photos database. I just wish they had a consumer-facing (read: more affordable/perpetually licensed) version of their CLI tool.

[1]: https://imazing.com/

Post reply on HN