On 02/22/2015 09:00 AM, Jens Neu wrote:
Dear list,
maybe since 2 weeks (close to upgrade to Twenty_One), my nfs shares are
no longer mounted at boot. Claims that the nfs server is not resolvable,
but it clearly is. Raised the timeo to 200, but no luck. Hints? Bugworthy?
Dear all,
iIssue is re
Tried to install all xmms packages.
# yum -y install bluecurve-xmms-skin.noarch collectd-xmms.x86_64
gkrellxmms2.x86_64 gxmms2.x86_64 logjam-xmms.x86_64 nyxmms2.x86_64
purple-plugin_pack-pidgin-xmms.x86_64 xmms.x86_64 xmms-acme.x86_64
xmms-adplug.x86_64 xmms-arts.x86_64 xmms-crossfade.x86_64
I've had a few different laptops over the last few years doing VGA out
to my Vizio TV. It took quite a bit of experimenting, but I figured out
a modeline that worked and put the following
in /etc/X11/xorg.conf.d/40-monitor.conf:
Section "Monitor"
Identifier "VGA1"
# Vizio Manufacturer's modeli
On 02/28/2015 11:53 AM, Patrick Dupre wrote:
ls -l /dev/sdc*
brw-rw. 1 root disk 8, 32 Feb 28 10:14 /dev/sdc
brw-rw. 1 root disk 8, 33 Feb 28 10:14 /dev/sdc1
brw-rw. 1 root disk 8, 34 Feb 28 10:14 /dev/sdc2
brw-rw. 1 root disk 8, 35 Feb 28 10:14 /dev/sdc3
brw-rw. 1 root disk
On 02/28/2015 05:36 AM, Angelo Moreschini wrote:
Hi
I tried with e2fsck -f /dev/sdc1
but I got the message:
WARNING!!! The filesystem is mounted. If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.
Of curse I didn't continue...
How I have to do this test ?
Have I to boot t
ls -l /dev/sdc*
brw-rw. 1 root disk 8, 32 Feb 28 10:14 /dev/sdc
brw-rw. 1 root disk 8, 33 Feb 28 10:14 /dev/sdc1
brw-rw. 1 root disk 8, 34 Feb 28 10:14 /dev/sdc2
brw-rw. 1 root disk 8, 35 Feb 28 10:14 /dev/sdc3
brw-rw. 1 root disk 8, 36 Feb 28 10:14 /dev/sdc4
brw-rw. 1 root
ls -l /dev/sdc*
Depending on how the application is opening it having a partition on
it seems to block certain apps from opening the underlying device. It
likely depends on how the application is opening it. dd always works
in my experience, but other tools appear to be unhappy when they
detect a
Hello,
When I try to benchmark a hard drive
(from the Disk applicaton), I get:
Error opening /dev/sdc: Device or resource busy (udisks-error-quark, 0)
This disk work fine (from GsmartControl).
What do I miss?
Thank.
===
On Fri, 27 Feb 2015, jd1008 wrote:
On 02/27/2015 03:15 PM, Max Pyziur wrote:
Greetings,
I decided to begin making the leap from F18 to F21. My reluctance in
upgrading with each new release was due to all of the problems that were
reported with upgrades, and not wanting to go through a d
On Fri, 2015-02-27 at 21:07 -0800, Mike Wright wrote:
> I'd like to see it stay open. The OP was not trolling and is
> obviously
> in desperate need of a solution. I'm sure every one of us has lost
> critical data at one time or another.
The strictures against cross-posting are there for a rea
On Feb 28, 2015 3:37 AM, "Angelo Moreschini"
wrote:
>
> Hi
>
> I tried with e2fsck -f /dev/sdc1
> but I got the message:
Buried in my long first reply:
"booting with parameter rd.break=cmdline"
Chances are it's not sdc1 damaged. It's lv-root.
>
> WARNING!!! The filesystem is mounted. If you
Hi
I tried with e2fsck -f /dev/sdc1
but I got the message:
WARNING!!! The filesystem is mounted. If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.
Of curse I didn't continue...
How I have to do this test ?
Have I to boot the computer using some utility that didn't need the
12 matches
Mail list logo