I need help with following situation
OS: fedora 22
My root logical volume was full. As a result, I attempted to resize my home partition.
My physical volume :/dev/sda8
Logical volumes are:
Once, I resized volumes, I ran resizee2fs. However, system will not boot properly due to bad geometry.
To correct the situation, I ran mk2efs. This fix the geometry but, my /home/<user> is gone.
Now, I know data is there and I need to recover it.
I found a recovery point from 2014 in /etc/ LVM/archive. However, my problem is when I try to recover with
Pvcreate --uuid xxxx --restorefile file /dev/sda8
I get partition is already mounted error
Can someone help here please
Reading lines from 2 files in such a way that each iteration
lets me read the next line from each file so that the items
read from each file are in sync as far as line number is concerned.
Is this "doable"?
For a single file, indexing to next line is automatic, visa vis
while read line; do
done < some_file.txt
for when more than 1 file is involved, it is not so easy ...
Hypothetical (of course, non-working example):
while true do;
file_A_line=`read line$index` # Read from file A
file_B_line=`read line$index` # read from file B
[ x$file_A_line = x -o x$file_B_line = x ] && break
<do something withfile_A_line and file_B_line>
index=`expr $index + 1`
So how can the reading from 2 files be accomplished and keep the index
to next line in sync?
I know it is a no brainer with a C program.
I have a 3rd party app that use a Java GUI, so it won't run on a headless JVM. I had it working until I installed a different app using dnf. It overwrote my JVM with a headless one and now the Java GUI app is broken. Is there a way to install/register a non-headless JVM with Fedora so it won't keep installing the headless JVM?
I have filed the bug #1408997 about "xset m" commands having no effect on mouse speed. The lack of effect of the command also seems to mean that the GUI sliders in LXDE have no effect at all, and to cause inconsistent behaviour in XFCE4's settings.
The problem can be reproduced on at least two machines: in a VirtualBox VM (yes, the tablet emulation was disabled) and a real one.
I fail to find any info about the current situation of the command and it's possible replacement. Is the "xset m" command obsolete, or is there just a some kind of bug?
I tried to do an identical second install on the same machine, but the
installer Anaconda gives an error about being unable to set a root
The only difference compared with the first successful install is that
there is a bit less disk free space, and of course another F25 already
installed. Previous install was about 20GB in 60GB free space. Current
failed attempt is also 20GB in remaining 35GB space.
I'm trying to long-distance-coach a tech-challenged friend on using his
Samsung SmartTV's web browser to view content his Cable TV service
doesn't carry. (This is not trying to get around stuff without
paying--the content, out of area sports, FWIW, is freely available to
watch on his PC.)
When he tries to access the content with the Samsung-embedded browser,
he gets an immediate prompt to upgrade Flash. Following the offered
links allows access to what is labeled as "Linux" rpm and/or tgz
versions, neither of which will install on the TV. So, the content won't
While I've suggest he do a general upgrade of the TV firmware, in hopes
there's a usable Flash upgrade included, I'm thinking of pointing him in
a different direction--say, a ChromeCast.
Any other suggestions? Thanks.
Tim Evans |5 Chestnut Court
443-394-3864 |Owings Mills, MD 21117
I have a mount point definition in /etc/fstab for a NAS device
connected to my router via Ethernet that is specifying nfs interfacing.
When I first put this definition in place on F24 I was using the option
SEC=KRB5P which was working quite happily (I'm also not sure how long
ago it was that I put this definition in place). I found yesterday that
the mount point was no longer being mounted because of an invalid
option, when I removed all the options and added them back one at a
time, I found that the option that was being objected to was SEC=KRB5P.
I also found that SEC=KRB5 and SEC=KRB5I were also being rejected as
invalid even though looking at the MAN page for NFS says all three are
valid parameters. The only security option I could get to work was
SEC=SYS. The MAN page does hint at other configurations being required
to use Kerberos security, but if so, why is this required now?
How do I find out why the SEC specification I was using now no
longer works (I can't identify exactly when it stopped working) and why
the MAN pages are indicating that it is still valid?