Re: Fedora 20 Installation Problem
by Matthew Miller
On Thu, Feb 06, 2014 at 10:27:20AM +0000, L.G. wrote:
> [ 196.644920] dracut-initqueue[590]: Warning: /dev/root does not exist
> Starting Dracut Emergency Shell...
> Warning: /dev/root does not exist
[...]
> > First of all I have loaded a .ISO image on my USB pen drive, using very
> > useful UltraISO program. At this point I have restarted my PC and, after
^^^^^^^^^^
Ahha! Take a look at
https://www.happyassassin.net/2014/02/04/more-on-booting-a-practical-fedo...
I think maybe UltraISO is not as useful as it appears, unfortunately.
--
Matthew Miller mattdm(a)mattdm.org <http://mattdm.org/>
10 years, 3 months
Kontact, howto disable automatic replies on invitation?
by Corinna Vinschen
Hi,
for a long time I was using the Thunderbird/Lightning combination for
planning my appointments. Lately I tried Kontact instead and I think
I like it.
Except for one problem, which is a bit disturbing. When I get an
invitation, and I choose to add it to my Korganizer calendar, KMail
automatically sends a reply to the inviting person.
What if I don't want that? What if, for very good reasons, it's not a
good idea to send a reply, and the inviting person doesn't expect nor
wish a reply?
With Thunderbird/Lightning, when I add an invitation to my calendar,
a dialog pops up asking if it should send the mail, and at this point
I can choose myself whether to send a reply or not.
Is there a setting in Kontact/KMail/Korganizer to switch on such an
approval dialog for invitation replies?
This is F20 with KDE 4.11.5.
Thanks,
Corinna
10 years, 3 months
virtualization on f20
by Mike Wright
Hi all,
Just tried fedora 20 running off a 1G thumb drive and am impressed with
its speed. Looks like a lot of things are coming together. Good job.
I'm most interested in virtualization. yum didn't show any package
groups related to that and I didn't find much in the release notes.
Anybody know where that stuff is?
Thanks
10 years, 3 months
BTRFS/Rollback & Yum Snapshot Plugin
by Jorge Fábregas
Hi everyone,
I'm playing around with btrfs (this time on a Fedora 20 VM). I used the
default configuration for btrfs that Anaconda provides. Right after
installation I did:
#btrfs subvolume list /
ID 257 gen 102 top level 5 path root
ID 258 gen 102 top level 5 path home
I then installed the yum-plugin-fs-snapshot package to try it out. I
installed some updates and after it:
#btrfs subvolume list /
ID 257 gen 102 top level 5 path root
ID 258 gen 102 top level 5 path home
ID 278 gen 95 top level 257 path yum_20140130172422
ID 279 gen 97 top level 5 path home/yum_20140130172422
Fine. yum created the snapshots. I then wanted to rollback my system
(to the state prior to the updates) so I went ahead and changed the
rootflags=subvol... parameter in GRUB's kernel line in order to specify
the above snapshot for the root filesytem. (I also changed /etc/fstab
to point /home to the snapshot subvolume). After booting, everything
seemed right (I was running off the snapshot subvolumes).
Now, here's the thing. I wanted to permanently run off these snapshots
so I wanted to delete the parent "subvolumes" for these snapshots (e.g.
"commit" the snapshot) by doing:
# mount -o subvolid=5 /dev/vda3 /mnt
# btrfs subvolume delete /mnt/root
Delete subvolume '/mnt/root'
ERROR: cannot delete '/mnt/root' - Device or resource busy
I believe this is happening because the snapshots are being created
WITHIN the subvolume they're snapshotting against. That is, I can't
delete it because the currently running root snapshot,
yum_20140130172422, resides inside the "root" subvolume. Is this
theory correct? Can you modify the yum plugin so that it places its
snapshots within OTHER particular subvolume?
BTW, is there anyone out there using this plugin with btrfs?
Thanks!
Jorge
p.d. I know snapshotting /home doesn't make sense at all for yum updates
but I followed it along...
10 years, 3 months
2 TB Seagate Drive ??
by Mickey
Fedora 18.
Seagate Barracuda 2 TB HDD SATA 6 Gb/s NCQ 64MB Cache 3.5-Inch
Internal Bare Drive ST2000DM001
Has anyone had any experiernce with this hard drive on Linux.
10 years, 3 months
another systemd oddity: why is "syslog.socket" inactive when syslog is running?
by Robert P. J. Day
just another one of those little curiosities -- playing on my f20
system and the difference between:
$ systemctl list-sockets
$ systemctl list-sockets --all
is the single additional line:
> /run/systemd/journal/syslog syslog.socket rsyslog.service
which seems odd when syslog is clearly running:
# systemctl status syslog
rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled)
Active: active (running) since Sat 2014-02-01 17:44:36 EST; 3 days ago
Main PID: 654 (rsyslogd)
CGroup: /system.slice/rsyslog.service
└─654 /sbin/rsyslogd -n
... snip ...
#
so why would the syslog socket be classified as inactive while the
syslog service is running? is this another remnant from earlier
releases? still digging into systemd so it's entirely possible this is
a stupid question.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
10 years, 3 months
confused by "inactive dead" syslog.target on fedora 20
by Robert P. J. Day
just digging into systemd (so be prepared for several potentially
silly questions), and i was playing with some variations of listing
systemctl services, and i ran:
# systemctl list-units -t target --all
and everything looked fine other than this line:
syslog.target not-found inactive dead syslog.target
at the moment, syslog is running fine as a *service*, it seems ok
... so what does it mean that "syslog.target" is classified as
inactive and dead?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
10 years, 3 months
dual head issue
by Stephen Berg (Contractor)
My fedora 20 system on occasion gets the two monitors flipped around.
What used to be on the left will be on the right and vice-versa. I
notice it happens when I unlock the screen or when switching my kvm to
this box. It doesn't happen everytime, but often enough that it's
becoming a bit annoying. To fix it I run nvidia-settings, drag the
monitors back to the correct positions, hit apply and save to config.
All is well until it decides for whatever reason to do it again. Both
monitors are Dell 2408WFP's plugged into a Nvidia GeForce GT 330.
Is there any way to specify one monitor versus the other so nvidia will
know that monitor A is on the left, B is on the right and don't move
them ever again?
--
Stephen Berg
Systems Administrator
NRL Code: 7320
Office: 228-688-5738
stephen.berg.ctr(a)nrlssc.navy.mil
10 years, 3 months
Install and mirror issues on F20
by Mike Chambers
When using the boot.iso image and put on disk, does it have to be used
against an installable Fedora 20 tree, or can it be against just the
Packages/Repodata (Everything) tree where *all* the packages are
located?
Reason asking, is I mirror most of all Fedora most recent releases, to
include updates, testing, etc..But I mirror the release base against the
installable tree, not the *Everything* tree.
Well, using above, when I go to install other programs, from 3rd party
or even just what didn't come with the install, and the mirrored
installable tree doesn't have that package, I have to get it from the
*Everything* tree.
Hope I worded this right haha,
--
Mike Chambers
Madisonville, KY
"Best little town on Earth!"
10 years, 3 months
gnome-shell won't start
by Stephen Berg (Contractor)
I'm having a rather serious issue getting logged onto my system using
gnome. GDM starts, I put in user name and password and the login starts
but I never get a desktop loaded and usable.
Fedora 20
gnome-shell-3.10.3-2
Nvidia GT330
NVIDIA-Linux-x86_64-331.38.run compiled locally from geforce.com
I've tried the kmod and akmod drivers from RPM Fusion, no difference. I
can logon using KDE and everything works like I expect.
Tried the same thing on a very similar machine and got the same results.
The only significant differences are the second system has an Nvidia
GT210, and is using the akmod driver. The root account can get a
gnome-shell login working and everything works on both systems.
I deleted everything from my home directory that appeared to be gnome
related and tried again, still no luck.
Right now I'm not seeing a .xsession-errors file in my home directory so
kind of hard to troubleshoot. Is some some rc file that I can tweak so
gnome will log some more verbose status and/or errors? I don't mind
using KDE, but I managed to get to like gnome-shell and some of it's
features and would like to get it functional again.
--
Stephen Berg
Systems Administrator
NRL Code: 7320
Office: 228-688-5738
stephen.berg.ctr(a)nrlssc.navy.mil
10 years, 3 months
