Yum update from live media??
by Beartooth
I have an F14 PC on which I'm currently running F15/xfce from a
live medium. Having had too little coffee, I tried (as root) telling it
"yum update."
It did it, or was about to. It got all the way to its "Is this
all right" question -- whereupon it was going to install fifteen things
and update four hundred-odd.
Would it have gone all the way? Would I then have an F15/xfce
machine, as if I had done preupgrade, with all my data still present? And
would that have been able to run preupgrade and get me to F16 when F16 is
released??
The machine in question is pretty well backed up; so I'm willing
to try the experiment, IF the knowledgeable think the odds are good, or
it would produce useful knowledge, or both.
--
Beartooth Staffwright, Not Quite Clueless Power User
I have precious (very precious!) little idea where up is.
12 years, 7 months
thunar instead of nautilus problem
by Leonardo Silveira
hello everyone.
I've installed XFCE and it works ok. But sometimes i go back to GNOME
and firefox keeps opening thunar instead of nautilus when i'm not on
XFCE.
Is there any way to make firefox open (open folder option) nautilus
when in GNOME and thunar when in XFCE? If not, where can i revert the
configuration?
thanks in advance.
12 years, 7 months
Installing F16 under VMWare Fusion
by SternData
Just a note to save you some time.... Uncheck "Use Easy Install" when
creating a F16 VM with VMWare Fusion. Anaconda will segfault very early
in the setup process.
--
-- Steve
12 years, 7 months
Re: Fun and games with 3TB hard drives
by R. G. Newbury
To Daniel Thurman
Why fight with physical hardware limitations?
Install Virtualbox (it's free) and create as many bootable virtuals as you want, each reachable without a physical hard-on-the-hardware re-boot. And from my experience the actual boot times of the virtuals are only about 50% of physical boot time for the same OS on the same hardware, ignoring BIOS initialization. Plus you can archive a copy of the vdi file for a near instant 're-install'.
Geoff
12 years, 7 months
VM qemu-kvm Shutdown question
by Cristian Sava
Hi,
I use F15 x64.
I installed a Win7 x32 in VM-qemu and shutdown does not work for me.
For the VM shutdown=restart and no way to change this behavior.
I want shutdown no FORCED OFF and no restart instead.
Am I missing something?
Cristian
12 years, 7 months
Problem with the gnome package updater
by Frode Petersen
Hi. I have got a problem that I hope someone could help me resolve:
The last few days I haven't been able to use gpk-update-viewer to
install updates. When started it dispalys an error message in a dialog
window:
Unable to get updates
Could not process requests
Opening 'More Details' reveals:
Unknown filter part: unknown
I've included the output from terminal running "gpk-update-viewer
--debug" at the end of this report.
I _can_ update packages through 'yum update' without problems.
gnome-packagekit 3.0.0-5.fc15 (x86_64)
This happens everytime now, whether starting the program through gui or
terminal. The problem started some days ago, but I don't have the exact
time. I reinstalled the package through 'yum reinstall
gnome-packagekit', but it didn't help.
Could this be some garbaged config files or caches? Is there a way to
reset everything that I could try?
Output from terminal:
$ gpk-update-viewer --debug
(gpk-update-viewer:7549): GnomePackageKit-DEBUG: ConsoleKit session ID:
/org/freedesktop/ConsoleKit/Session2
(gpk-update-viewer:7549): GnomePackageKit-DEBUG: using native mode: 700x600
(gpk-update-viewer:7549): GLib-GIO-CRITICAL **: This application can not
open files.
(gpk-update-viewer:7549): PackageKit-DEBUG: notify::backend-description
(gpk-update-viewer:7549): PackageKit-DEBUG: notify::version-major
(gpk-update-viewer:7549): PackageKit-DEBUG: notify::groups
(gpk-update-viewer:7549): PackageKit-DEBUG: notify::backend-author
(gpk-update-viewer:7549): PackageKit-DEBUG: notify::backend-name
(gpk-update-viewer:7549): PackageKit-DEBUG: notify::version-micro
(gpk-update-viewer:7549): PackageKit-DEBUG: notify::roles
(gpk-update-viewer:7549): PackageKit-DEBUG: notify::mime-types
(gpk-update-viewer:7549): PackageKit-DEBUG: notify::filters
(gpk-update-viewer:7549): PackageKit-DEBUG: notify::version-minor
(gpk-update-viewer:7549): PackageKit-DEBUG: notify::network-state
(gpk-update-viewer:7549): PackageKit-DEBUG: notify::distro-id
(gpk-update-viewer:7549): PackageKit-DEBUG: role now get-updates
(gpk-update-viewer:7549): GnomePackageKit-DEBUG: status finished
(gpk-update-viewer:7549): GnomePackageKit-WARNING **: Kunne ikke hente
oppdateringer: Unknown filter part: unknown
(gpk-update-viewer:7549): PackageKit-DEBUG: notify::connected
$
12 years, 7 months
F14, google-chrome won't launch after yum update
by Jackson Byers
$ uname -r
2.6.35.13-92.fc14.i686.PAE
after a recent 'yum update', google-chrome won't launch.
same response with updated 2.6.35.14-96.fc14.i686.PAE
$ ls -l /opt/google/chrome/chrome
-rwxr-xr-x. 1 root root 55207772 Sep 27 01:46 /opt/google/chrome/chrome
$ /opt/google/chrome/chrome: error while loading shared libraries:
cannot restore segment prot after reloc: Permission denied
Advice?
Jack
12 years, 7 months
anaconda: --rootPath obsolete. Any workaround?
by Kernel Guardian
For a long time I use diskless installations of Fedora/RHEL/CentOS
with readonly root. Recently, with changes in anaconda, --rootPath is
no longer supported.
I have to many different types of installations and initial
configuration. Until now i was using kickstart files for every type of
installation.
Installation dozens of installations and copying on NFS server is
worst case scenario. During copying i do not find useful way to keep
SELinux contexts.
So far i was run anaconda from command line with --rootPath option,
and any installation was have proper contexts.
Disabling selinux on clients is almost unacceptable, but it is only solution.
I'm open for any constructive suggestion.
Anyhow i have more then 100 diskless clients in my environment. They
choose on PXE boot which type and version of installed OS like to run.
On net i couldn't find any solution.
Is there any way I could preserve contexts when copying files?
Or anaconda have undocumented option, which would be the best solution?
Regards
12 years, 7 months
Fedora 15: a NFSv4 to glusterfs migration HOW-TO
by Dr. Michael J. Chudobiak
As detailed in another thread, we upgraded a few test machines on our
LAN to Fedora 15 (with gnome-shell and firefox), with user folders
served from a NFSv4 server (F14 originally, then F15).
It just didn't work. The F15 desktops would freeze frequently. And
worse, this would freeze ALL desktops on the LAN intermittently, as the
NFS server struggled with client flakiness.
When it did work, Firefox would lose authenticated logins randomly,
presumably due to corruption of its cookies.sqlite file. sqlite and NFS
seems to be a nightmare, for both NFSv3 and NFSv4.
Moving from a NFSv4 server to a glusterfs server solved all of these
problems, and sped up boot times significantly too. glusterfs looks
intimidating at first, because of all its fancy replicating features and
what-not, but it turns out to be trivially easy to set up a simple
server than will replace 95% of the NFS installations out there.
Luckily, you can easily point both the NFS daemon and the glusterfs
daemon at the same export folder, so you can migrate clients slowly over
time.
This HOW-TO is intended to document the process. There are other similar
HOW-TOs out there, but they are all a little out-of-date or don't show
how to enable locking correctly, which is critical for Firefox.
In this example, we export the server's /fileserver folder, and mount it
on /fileserver on the clients. In my server, /fileserver was already
being served by the NFSv4 server, which is fine.
--------------------------------------------
1. On the server:
- yum install glusterfs-server
--------------------------------------------
2. On each client:
- yum install glusterfs-fuse
- mkdir /etc/glusterfs/
- mkdir /fileserver
--------------------------------------------
3. On the server, edit the volume configuration file
(/etc/glusterfs/glusterfsd.vol) so that it looks like this:
volume raw
type storage/posix
option directory /fileserver
end-volume
volume brick
type features/posix-locks
subvolumes raw
end-volume
volume server
type protocol/server
option transport-type tcp
subvolumes brick
option auth.addr.brick.allow *
end-volume
The first stanza selects the basic folder to export.
The second stanza adds file locking to it. This is required to support
Firefox, and some other applications.
The third stanza authorizes everyone to access this file-locked export
over the network.
There is also a /etc/glusterfs/glusterfsd.vol file on the system, for
configuring the management interface. For this simple installation it
does not need to be modified.
--------------------------------------------
4. Restart the server services:
- service glusterd restart
- service glusterfsd restart
I believe the first service is a management service, and the second is
the actual file-export service.
--------------------------------------------
--------------------------------------------
5. On the client, create the /etc/glusterfs/glusterfs.vol configuration
file, which should look like this:
volume client
type protocol/client
option transport-type tcp
option remote-host 192.168.0.3 # use YOUR server IP here
option remote-subvolume brick
end-volume
--------------------------------------------
6. On the client, add this line to the end of /etc/rc.d/rc.local:
mount -t glusterfs /etc/glusterfs/glusterfs.vol /fileserver
--------------------------------------------
7. On the client, reboot, and check /var/log/messages for errors. On one
machine, we had an selinux problem that was flagged in the logs. We had
to manually create the logging file using:
touch /var/log/glusterfs/fileserver.log; reboot
--------------------------------------------
8. On the client, see if you can access the files in /fileserver. If
not, read the /var/log/glusterfs/* files on both the client and the server.
At this point, everything should work!
Weird things and gotchas:
A. You need the file-locking option to make Firefox work properly.
B. LibreOffice wouldn't start on one system, until we did:
rm ~/.libreoffice
rm ~/.openoffice.org
C. selinux prevented the creation of log files on one client, which
prevented the filesystem from mouting. The manual fix noted above fixed
that.
D. This HOWTO mounts the glusterfs from /etc/rc.d/rc.local, which is the
last step in the boot process. In theory, you can mount it from
/etc/fstab or using autofs. However, we found that autofs mounting just
didn't work - not sure why. fstab mounting didn't work either - I
suspect it occurred too early in the boot process. /etc needs to be up
and running so glusterfs can read the config file, and I don't think the
current init/systemd files handle this correctly. There are some Debian
bug reports about this that you can google.
I hope this is useful to someone, and that we can finally drive a stake
through the heart of NFS...
- Mike
12 years, 7 months
