Time to turn your laptop into a router! Let’s say you’ve got 2 network interfaces on your laptop, eth0 and wifi0. wifi0 is joined to your university WiFi as normal. Connect your iPad to your laptop via ethernet (with a USB-C adapter).
Rather than setting up a DHCP server or IPv6 stuff, I’d just configure the wired interfaces manually. Let’s use the network 192.168.69.0/24. Laptop will be 192.168.69.1, iPad will be at 192.168.69.2. On the laptop:
<span style="color:#323232;">ip addr add 192.168.69.1/24 dev eth0
</span>
On your iPad, go to Settings -> Ethernet:
address: 192.168.69.2
subnet mask: 255.255.255.0
router: 192.168.69.1
Curious to see if that works. We haven’t set up DNS or DHCP or done any sysctl for IP forwarding or any nftables.
How can we test if it works? We can set up a TCP listener using nc(1) on the laptop that the iPad’s web browser could hit. On the laptop:
Will I need a usb-c to rj45 adapter (or realistically, 2 since my laptop does not have an ethernet port)? I was planning to use my TB4 type c - type c cable and use an ethernet connection over usb.
I’ve been using PipeWire this year on my Void Linux laptop & desktop. It’s been mostly OK but has a few problems. For years I have been using plain ALSA (with no custom configuration) because pulseaudio causes me regular issues across multiple machines (mostly silently failing).
Pros:
I don’t have to use Chromium for my mic to work on online video conf (WTF Firefox)
“EasyEffects” lets me quickly fix crappy youtube audio (bad gain normalisation, way too much sibilance) with a minimum of effort.
Cons:
Sometimes breaks all audio until I manually restart it (hey, just like pulseaudio. This problem never happens when using ALSA straight)
First time setup is complicated, involving environment variables, dbus user session buses and multiple daemons (running just pipewire isn’t enough). Why can’t it handle this all itself? Surely it should notice if these things are missing and just fix it itself? Compare this to straight ALSA where you (1) do nothing and then (2) everything works (except Firefox mic support)
I can’t have multiple audio outputs all unmuted at the same time. Eg my headphone output and my rear speaker output. If I override this (using alsamixer) then it gets forgotten next boot anyway, it seems to be out of scope of PipeWire’s understanding.
Sometimes breaks all audio until I manually restart it (hey, just like pulseaudio. This problem never happens when using ALSA straight)
Well, how much lennart is in this thing? Not only can that predict how well it’s going to work, but also how soon it’ll be fixed, how responsive the ‘team’ will be to bug reports, how compatible it’ll be with other system components AND whether ‘compatibility’ will be achieved before the entire OS has been systematically imported into (and badly replicated by) the project.
If you check SystemD, its a HUGE step up, which is why everyone is using it now (whereas, the old scripts had race conditions, were a pain to write and other issues). Anyone who has written both can tell you how much better things are now…
The fact this issue is happening on both Pipewire and Pulseaudio also suggests it’s more likely a bug in the drivers… It might not be obvious on ALSA directly, but that doesn’t mean an issue doesn’t exist there…
And honestly, the situation before PulseAudio was awful. Audio not working was a common issue, and low latency audio was the least of anyone’s problems. Whereas, these days, because of Pulseaudio, even gaming is a thing now (back then, I even saw issues on tuxracer, and Unreal tournament back in the days).
In regards to setup, most distributions will handle that anyway I’m guessing. So not sure why the configuration process should matter unless you’re in Arch or Slackware? As long as the distribution handles it, it shouldn’t matter. It’d really a non-issue honestly.
I do a lot of middleware development and we’re regularly blamed by users for bugs/problems upstream too (which is why we’ve now added a huge amount of enduser diagnostics/metrics in our products which has made it more obvious the issues aren’t related to us). In practice, very few people have issues with Pulseaudio (I haven’t seen issues since launch). Sometimes as well, keep in mind it can be the sound interface (especially if its USB)
If you check SystemD, its a HUGE step up, which is why everyone is using it now
I think that’s a “winners write history” situation. There were other options at the time that might have been better choices. Everyone uses it now because of Redhat and Debian being upstream to most users, desktop and corporate. I was not surprised by Redhat adopting it (it’s their own product) but Debian was quite the shock.
Yes systemd is definitely a step up from traditional initscripts (oh god). In terms of simplicity, reliability and ease of configuration however it’s a step below other options (like runit). I don’t have distro management experience but, given the problems I’ve encountered with different init systems over the years, I suspect there would be less of a maintenance burden with the other options.
I’m very curious about the downvotes to this one. May I ask people’s thoughts? Perhaps I’m too vague? I can put a bigger story about my experiences with various init systems in production & research if people are interested.
The fact this issue is happening on both Pipewire and Pulseaudio also suggests it’s more likely a bug in the drivers… It might not be obvious on ALSA directly, but that doesn’t mean an issue doesn’t exist there…
I probably made the overlap unclear, sorry:
Pipewire issues: My 2023 desktop and 2016 laptop, very different hardware.
Pulseaudio issues: All of my pre-2023 desktops and several family laptops
I do a lot of middleware development and we’re regularly blamed by users for bugs/problems upstream too (which is why we’ve now added a huge amount of enduser diagnostics/metrics in our products which has made it more obvious the issues aren’t related to us).
Eep, that’s annoying. You also probably don’t have direct interaction with the users most of the time (they’re not your customer) which makes this worse, people in a vacuum follow each other’s stories.
In practice, very few people have issues with Pulseaudio (I haven’t seen issues since launch). Sometimes as well, keep in mind it can be the sound interface (especially if its USB)
There might be a bias here because these problems are not persistent, ie a reboot fixes them.
In regards to setup, most distributions will handle that anyway I’m guessing. So not sure why the configuration process should matter unless you’re in Arch or Slackware? As long as the distribution handles it, it shouldn’t matter. It’d really a non-issue honestly.
That’s potentially more things different distros can do differently and more issues your middleware will start getting blamed for.
Yes it’s not a problem for user-friendly distros, but why does the user friendliness problem exist anywhere anyway? It’s better to fix problems upstream, not downstream.
It works for me, I have KDE version. I have AUR apps, SNAP (VSC works better in snap than flatpak), official repo apps. I have not had any errors in the 6 months I have been using it.
Ubuntu 23.10 & Fedora 39, both running Gnome of all things (eye roll) run just fine on my late 2009 iMac (iMac 10,1)
nb : Fedora 39 has an installation bug. Installing Fedora 38 minimal then upgrading to 39 is the simplest solution. Kudos as usual to Canonical for shipping a trouble free install on Mac.
I am interested in tech, and also watched a lot of YouTube videos about different topics. Somehow I realised how much data windows sends. Since I was planning to buy myself a new pc(my old one was a Celsius W370 from 2009 that took 20 minutes to boot windows) I decided to not install Windows on this pc but to install Linux. I went the classic way and chose Mint with cinnamon.
That was about 1.5 years ago.
I wouldn say that I’m somehow obsessed with Linux and there’s definitely no way back. I got completely sucked into FOSS. My next phone will be a Google pixel where I will install Graphene OS on. Fuck big tech.
After having used Ubuntu LTS for 6 years, I find a little more peace with Debian. I do not like systems that break. Debian Stable is IMPOSSIBLY HARD to break, even more than Ubuntu LTS, which only broke once because of my stupidity of installing ProtonVPN client and using VPN killswitch through it. Switched to using OpenVPN/Wireguard config files.
Debian doesn’t break often because they don’t change things just for the sake of changing them. Nice and stable. Even if you do break something, a guide published 5 years ago describing how to solve the problem would probably still mostly work today.
u can use visual studio code instead of visual studio. about gaming - not that hard using wine+lutris, the future is here, we can install and run exe-s in linux!
You probably couldn’t game very much on a macbook. Maybe you could on the more expensive variants with Radeon Pro graphics, but those aren’t your typical gaming GPUs.
That’s Visual Studio Code vs VSCodium - I believe OP is referring to Visual Studio, the full blown IDE that’s been out for far longer than VS Code, which does have a completely different feature set.
Try playing Xonotic. It is FPS that runs natively and on dualcore celeron with iGPU it gives 60 fps on ultra and 120 on default. It runs mostly in single thread and you are likely to be GPU-bound.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.