I'm currently running FC5, will probably upgrade to F7 in a couple of months.
Unfortunately my CD/DVD rewriter appears to have died, before it's
even seen a dual layer disk :'(
SATA hard drives run without problems for me, but now that SATA
optical drives are starting to appear in the shops, would it be OK to
buy one of these and get rid of another wide ribbon cable?
Is anybody already running them with Fedora?
Thanks for any advice/experiences.
While preparing to upgrade to Fedora-37 (planned for mid-April), I noticed that my emergency tools are seriously out of date. Those are memtest, Fedora live, and rescue. memtest was dealt with in a thread earlier this month. Now I'm trying to update my Fedora live USB stick to Fedora-36. I used Fedora Media Writer to do that. I saw no hint of trouble while using that. But when I try to boot up from the stick (USB-3, if that matters), I get varying bad results. Two tries failed to complete the boot. One try appeared to succeed, but I couldn't launch any applications. The applications I tried were Firefox, a terminal, and I don't recall the other. The last application launch attempt locked up the workstation.
This workstation is 10 years old. It uses bios. I've attached a PNG screen capture of what Files says is on the stick at the top level. I do not have a cell phone or camera to capture the boot screen when the boot fails.
How do I make a Fedora-36 USB live stick that really works?
I can't find a tool on my workstation to check the stick. Disks, GSmartControl, and Disk Usage Analyzer don't do that, How can I check the stick itself? I actually tried 2 sticks for the Fedora Media Writer. They both failed when trying to boot.
On Tue, 2020-04-28 at 16:45 +0000, david richyad wrote:
> cisco ise helps safeguard your business. It lets you control access throughout your network, see the user and device details, and stop/contain any threats. You can also use it to enforce security policies throughout your network. As a result, it helps prevent any technical issues and strengthens your cybersecurity measures. In short, you can manage your network security with more ease. Everything can be handled in one place, as opposed to needing multiple different applications open at once.
Does this have anything to do with Fedora? Advertising is not
acceptable on this list.
I have 3 machines with clean F37 installs. One of the F37 machines has 4GB of RAM, and I maintain it as a backup and normally only log in via ssh and do dnf updates via command line. In the last few weeks this has become extremely difficult to do due to being automatically logged out, presumably by systemd-oomd. It happens even if I boot in multiuser, which ought to reduce memory use. From what little I've read and what experimentation I've done so far, it appears that being logged into a DE (maybe only GNOME or KDE?) protects against this, but non-DE logins (including ssh), and any commands running in them, are not protected. This goes against the expectation that non-DE access should be LESS likely to run out of memory, especially if there isn't even a DE running. How hard would it be for systemd-oomd to be configured to protect non-DE logins and anything running in them?
I've also read that configuring non-zram swap might be a cure. As I said, these are clean F37 installs, and if that's necessary for reasonable behavior when there's not enough RAM, the installer should be doing it automatically. In my case, I don't think that's the cause, since the free command suggests that I'm only using a fraction of both the memory and swap even when the automatic logging out is happening.
I am not able to login to cockpit, localhost:9090, as root. I can login as a normal user, but that isn't acceptable. Why would I even need cockpit as a normal user?
I have a fully updated Fedora instance. It may be related somehow to plasma as at the top of the login dialog I see "Fedora Linux KDE Plasma".
I suppose there is a configuration option to allow root logins. Note that sudo is not an option I am interested in using.
I have a caching server running. Other than digging
out my "forward" from /etc/named.conf to figure out
what my DNS server is, is there a way to use "dig"
or other to figure out what my actual DNS server is?