![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Did you take a little journey into the BIOS yet? Is definitely firmware, the question is if you can just change a setting there. Otherwise, somebody already mentioned dummy HDMI plugs.
Did you take a little journey into the BIOS yet? Is definitely firmware, the question is if you can just change a setting there. Otherwise, somebody already mentioned dummy HDMI plugs.
Relied on an AUR package for building and signing my unified kernel image… one day it was outdated and geberating the image failed, I noticed that by the fact that the system refused to boot my OS. Fixing it was done in a few minutes but boy, that was a shock :D
Guess who also checks the exact output of the kernel rebuild now before rebooting!
Might be the case but is this really a problem to solve? To my knowledge, all modern boards support wol.
Not just Dell… bought an HP Elite x360 in 2018 and it had to go back twice too; first time because they jammed a physical blocker for non-LTE models into my sim slot (then sent it back after removing it and putting the same blocker back in, afterwards gave me free on-site repair for this issue, fucked up my board during that and came back next day with a replacement board) and second time because the keyboard died after a year. Solid ever since, still running perfectly but these initial issues should not happen with a 2500€ device.
Vim supports editing files through scp as well, no reason to cry here xD
I second this. If you want people to help you tell us
Meaning what did you type, what did you expect it to do and what is the error. Copy the code ideally, alternatively send a screenshot. Once you provide this, we will be happy to help.
Okay, then it simply has an issue with the addresses you are providing, as someone pointed out already, the issue likely is the 192.168.100 network. Find out where exactly you define localhost and 192.168.100.1 as addresses to listen to and change them to e.g. 0.0.0.0 and 127.0.0.1 instead (or ideally just 0.0.0.0 as this includes localhost as well). Restart the container afterwards, see if it works. Of course make a backup of your config first so you can go back.
I don’t see anything like that in this thread. If you want people’s help, help them help you and provide sufficient information about your problem.
Yes, have it running and it works well. Nextcloud setup is sth that I will still have to set up but the only problem I see there is certificates.
To debug Nebula, simply try executing it by hand, e.g. nebula --config /path/config.yml
and see what the error message is. Or check your journalctl of course. Share the message here and we can have a look!
When you issued the netstat command, were the containers up or down? Issue it again after docker-compose stop
. If you moved or renamed the compose file, the old conrainers would still run in the old context.
For me, two main aspects: I do not have to move my hands from the keyboard and I can pipe things from one tool into others, significantly speeding up many tasks
Very nice! I am running an HC4 (I think; the toaster) now since last month and so far, it’s running much better than I thought! So yes, check that one first, then see if you have to upgrade and if you do, go for aarch64 or traditional x64 but not 32 bit arm
Alternatively, there are also some options from pine64.com, maybe scroll through there! Same for odroid.nl
Native tool, not the web. So far, I have not felt the need to use anything else; calibre does decent management and connects to my koreader installations on ebook readers, while the abs app handles all interactions with phones. The latter has good wife-approval but the syncing through calibre to readers is complex and not super reliable, so it still requires “admin intervention”
Yes. Let me give you an example on why it is very nice: I migrated one of my machines at home from an old x86-64 laptop to an arm64 odroid this week. I had a couple of applications running, 8 or 9 of them, all organized in a docker compose file with all persistent storage volumes mapped to plain folders in a directory. All I had to do was stop the compose setup, copy the folder structure, install docker on the new machine and start the compose setup. There was one minor hickup since I forgot that one of the containers was built locally but since all the other software has arm64 images available under the same name, it just worked. Changed the host IP and done.
One of the very nice things is the portability of containers, as well as the reproducibility (within limits) of the applications, since you divide them into stateless parts (the container) and stateful parts (the volumes), definitely give it a go!
I’m currently using Calibre and Audiobookshelf, where the latter is basically just using the folder structure of Calibre with and additional folder for some audiobooks. Works okay but is not the greatest solution. The calibre library web interface is quite nice (not the weird VNC-style admin panel, the one on other port). People also mention lazylibrarian a lot but I never tried it.
By that logic, upvoting posts is equally as “repressive” as downvoting as it decreases the relative visibility of all other comments, I hope that angle shows the stupidity of that argument. I think we have a fundamental difference in understanding censorship, freedom of speech and intolerance here. If you want to play the self-victimization game, please do so on Reddit and not in the linux community on this platform.
“Do folks in here are really that needy of self-validation, even if it means seeking such from something completely insignificant like internet points?”
But… is that not exactly the description of somebody who complains about downvotes?? As said by others; they should be considered exactly as valid as upvotes. If you feel like they prohibit you from voicing an opinion, I personally feel like that is a you-problem. Ask yourself of the content you posted is crap, if you feel it is not, simply ignore the downvotes and move on, they are just pixels.
Edit: I checked your posts, most downvoted ones seem to be clickbaity or images that you posted to the linux community. This is not something that vibes with that type of community, I would have downvoted that too. The ones on your technical questions seem unjustified however. Posting a code snippet asking people to execute it… I think that crap should even have been deleted by mods.
Great question, from my understanding, notifications through private nextcloud or ntfy instances should be safe but I just started looking into this a month ago, so let’s wait for someone more knowledgeable to join in here.
Well yes but I am not sure that this is the main problem with flatpak containers.
I’d rather point out that this approach creates a bigger attack surface since the containers tend to ship with outdated versions of libraries, frameworks and tools that the actual application relies on because it is now that specific app developer’s problem to update them inside of the container. So with this, even an up to date system is not really up to date and might suffer from severe vulnerabilities. I’d say it depends on your application, use case and threat scenario; containerization can make sense but is not the holy grail.