I'm trying to setup snmpd on a newly updated F35 system. So far I
cannot get any response and port 161 remains closed. I've checked that
firewalld is not running. No iptables. There's no hosts.allow or
hosts.deny to cause this. The daemon is running. The port is listening
according to
On 5/8/20 10:11 AM, Thomas Schmitt wrote:
Hi,
Steve Berg wrote:
I've got some data saved to blu-ray BD-R disks that won't read.
[...] I'm positive it's a BluRay drive [...]
Anyone have any idea what could cause this?
You should try to find out whether it is a problem of medium and drive
On 5/8/20 9:21 AM, Tom Horsley wrote:
On Fri, 8 May 2020 09:10:22 -0500
Steve Berg wrote:
Anyone have
any idea what could cause this?
Linux shouldn't need any extra software to read a BD-R data
disk, so the drive dying or the disk dying over time are
the most likely issues.
I've tried 5
I've got some data saved to blu-ray BD-R disks that won't read. Loading
a video DVD works, the system mounts it and I can see the files. But
when I pop in one of these BD-R disks nothing, the system doesn't see
the media at all. I'm positive it's a BluRay drive, pretty sure it's
the same
Is there anyway to get a dual head system to use the two monitors as two
different consoles? I got a dual head setup working nicely in F25 and
Gnome, but when I switch to the console the two monitors are mirrored.
Can they be set up to be two different consoles as well as the virtual
Just tried using fedup to get a 17 system upgraded to 18. Went through
the fedup --network process, rebooted, let it boot to the System Upgrade
option in grub and it seemed to start doing it's thing. The fancy
graphic appeared with the progress bar so I walked away. Came back an
hour or so
Got a couple of F17 systems that I'm a little wary of re-installing with F18. Both are setup with two drives, GPT partitioned and running RAID1 with a couple of LVM volume groups. From what I've read it seems that the anaconda in F18 will not be able to deal with this setup like previous
Try nethogs. It may give you exactly what you need. It's kind of like
iftop, but tells you the name of the process involved as well.
That's handy! Thanks, I never knew of that app before but I can see it's
potential.
--
* Stephen Berg *
* sb...@mississippi.com *
* Sinners
On 03/17/2012 12:45 PM, Dave Ihnat wrote:
Well, playing_Advocatus Diaboli_, what if some moneyed software company
claims Open Source software being hosted for download is violating their
copyrights, and uses this excuse to shut down archives?
Wouldn't that be similar to folks wanting to shut
I just attempted using preupgrade on a Fedora 11 system. It ran fine on
the system, downloaded all the packages, set up grub.conf and all the
other things it normally does. I rebooted into the upgrade kernel and
then it tells me that it can't upgrade the system because it's too old.
You can
On 10/11/10 12:57, Steve Berg wrote:
If preupgrade is smart enough to know that limitation once the upgrade
starts, why isn't it smart enough to warn me about that before it
downloads and sets everything up?
Maybe it figured you would do that yourself in advance.
--
Regards,
Frank
Hi,
Im trying to do automated installation with Fedora 14 kickstart and the
configuration [2] shown at
the end of this message. The installation never runs through. Anaconda
still displays these screens
and waits for user input:
Here's a sanitized version of my kickstart. I do pxeboot
Meant to send this to the list in case any one is curious about possible
solutions.
On 11/05/2010 03:39 PM, Robert Myers wrote:
Maybe I'm missing something:
From a computer with ssh and an X-server:
$ssh -X 192.168.xxx.yyy
$...@192.168.xxx.yyy: su
#r...@192.168.xxx.yyy: preupgrade
So far I've had very good luck with preupgrade for 12 to 14 and 13 to 14
systems. There's one annoyance that is causing me some headache. I have
a couple of systems that are headless and remote that I'd like to do a
preupgrade on but I can't seem to get things started without some local
keyboard
http://forums.fedoraforum.org/showthread.php?t=253668
Quoting the relevant bit:
Update - apparently this issue is related to the GTK theme in use. The
default (Fedora, or Clearlooks, or a few others) results in this slow
behaviour. Other themes, like Nodoka and a few others perform fine.
I've tried on two different systems, both recent clean installs of Fedora
13 x86_64. Open K3B (V1.91.0), pull in files that I'd like to have an
archive of, total size is just under 40GB. Load up a blank BD-R dual
layer and tell K3B to burn.
It sees the blank BD-R as having 46.6GB space. K3B
16 matches
Mail list logo
