I was trying to build a PC just to play internet radio on using Shortwave, and a 30€ thin client with 4 1,5Ghz cores and no active cooling, 4 gigs of ram and an 8gb ssd were more than enough for that
I think on a system like that you shouldn’t even run a GUI or a window manager at most. What is the service that is actually using though, it links to this https://www.radio-browser.info/ I guess I see you can play stations directly from that. It seems it makes more sense to use like lynx browser or something to just browse that website directly.
I’ve clicked like 10 of them they are all mp3 or aac. mpv or vlc can decode those on the command line and play it with using like 15-100mb of space on your storage. Like this random station for example https://stream-uk1.radioparadise.com/aac-320
all in all your total install should be like 400mb
It is not for me personally, but for a person who wants a gui. And a Touch screen. Also I need an on Screen Keyboard because he also does not want to use a keyboard or mouse.
I tried using a very simple compositor like cage to just start shortwave, but I couldnt get my Keyboard to work since it needs gnome accessibility runtime to automatically show when clicking a text field.
And also xfce is more than light enough not to take up more than 1-2 secs of the total boot time
The flatpak thing was just the jellyfin-media-player so I can play my music from jellyfin too, but I guess ill just set up DLNA so I can stream to the device from my Phone
nix collect-garbage, comrade! there’s also another command to clean up older generations. if you’re using git to version your nix config, you only really need to keep two generations: the current, and your last successful boot, since you can recover by git checkout.
Why the hell do you only have 8GB? Are you trying to install flatpaks on a smart fridge?
Sort of, actually
I was trying to build a PC just to play internet radio on using Shortwave, and a 30€ thin client with 4 1,5Ghz cores and no active cooling, 4 gigs of ram and an 8gb ssd were more than enough for that
this? https://gitlab.gnome.org/World/Shortwave
I think on a system like that you shouldn’t even run a GUI or a window manager at most. What is the service that is actually using though, it links to this https://www.radio-browser.info/ I guess I see you can play stations directly from that. It seems it makes more sense to use like lynx browser or something to just browse that website directly.
I’ve clicked like 10 of them they are all mp3 or aac. mpv or vlc can decode those on the command line and play it with using like 15-100mb of space on your storage. Like this random station for example https://stream-uk1.radioparadise.com/aac-320
all in all your total install should be like 400mb
It is not for me personally, but for a person who wants a gui. And a Touch screen. Also I need an on Screen Keyboard because he also does not want to use a keyboard or mouse.
I tried using a very simple compositor like cage to just start shortwave, but I couldnt get my Keyboard to work since it needs gnome accessibility runtime to automatically show when clicking a text field.
And also xfce is more than light enough not to take up more than 1-2 secs of the total boot time
The flatpak thing was just the jellyfin-media-player so I can play my music from jellyfin too, but I guess ill just set up DLNA so I can stream to the device from my Phone
oh you can run the https://github.com/jellyfin/jellyfin-mpv-shim and then just install MPV
Great, thanks
I didn’t even know ssd’s(nuts) that small existed
I just want you to know, I appreciated your deez nuts joke.
It was subtle. It was well-done. Roasted, even.
Maybe it’s an eMMC chip on an embedded device?
look into NixOS! there might already be a package for it. and NixOS can be very good about not duplicating dependencies.
I had a 200 gb ssd on my laptop and kept running out of space because all the old generations from nixos,
nix collect-garbage, comrade! there’s also another command to clean up older generations. if you’re using git to version your nix config, you only really need to keep two generations: the current, and your last successful boot, since you can recover by git checkout.For your use case, building from source might be more practical.