bios update
by Sebastian
Apologies if this has been discussed, I couldn't find it.
I have a single boot FC14 system on a Dell precision M6500 precision
notebook and wish to update the BIOS.
I go to the Dell download site, and for my machine select the closest match
to my operating system: RH Enterprise Linux 5.
This gives me the only option to download an EXE file: "M6500A06.EXE"
Is it possible to update my bios with this file given my current
installation?
I have windows Virtual Box under FC14, or,
Do I need to delete my installation, install windows and reinstall?
As I really don't want to do this, a final option to consider: could I
install windows via a USB drive (so as to not destroy my current system) and
then install bios?
Here is the link to the driver?
http://support.dell.com/support/downloads/driverslist.aspx?os=RHEL5&catid...
thanks for any help,
Sebastian
12 years, 11 months
rc.sysinit not being started
by Steve Searle
On my Fedora 15 installation I used yum to install initiscripts-legacy
because I wanted an /etc/rc.d/rc.sysinit. However this does not appear
to be run when the machine is booted up. Can anyone advise why this
should be, and what I should do to get it to be run. Or what I should be
doing instead of using rc.sysinit, I'm very lost with all this systemd
stuff.
Thanks
Steve
--
Website: www.stevesearle.com
Twitter: @ReddishShift
Facebook: www.facebook.com/steve.searle
21:04:04 up 6 days, 12:03, 2 users, load average: 0.00, 0.00, 0.00
12 years, 11 months
Selinux and Nvidia drivers
by Alexander Volovics
Wat is the reaction of selinux to the nvidia driver.
Does selinux try to prevent the nvidia driver from being loaded?
Alexander
12 years, 11 months
Today's GNOME3 funny
by Bill Davidsen
I was looking at gnome3.org today, and their FAQ says that "The traditional
GNOME 2 desktop will not disappear overnight, however: releases of GNOME 2 will
continue to be supported by distributions for years to come." so clearly they
don't imagine everyone will drop all their software and retrain all their users
overnight.
Ubuntu doesn't see to have that thought, either.
I was looking for a way to run fc15 in a VM, which worked in the alpha and
hasn't (for me) since. The FAQ says that's the case, no VM has a powerful enough
video emulation to handle the worthless eye candy. The Virtualbox people say
much the same, but their spin is that the video could do the job but GNOME
insisted on using some direct to hardware stuff they don't off. I freely admit I
didn't spend a lot of time deciding anything other than both of them imply the
fault is with the other.
My fc13 machines are moving to RHEL6.0 or a similar distribution, I'll be able
to keep them secure for a while and see which way the wind blows.
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
12 years, 11 months
OT: setting up a cluster - what is best practice
by Jamie Bohr
Sorry this is off topic.
I have been looking at setting up a compute cluster using blade servers with
a 10G connection to some high-end storage. I've been reading documents on
http://www.linux-ha.org but would like advice from people that have already
done this. What are the advantages of using MOSIX, openMosix, Kerrighed or
OpenSSI for kernel based clustering? What are the complications of
implementing such a system?
--
Jamie Bohr
12 years, 11 months
Selinux blocking denyhosts
by Kevin H. Hobbs
I tried to install and enable denyhosts on a fresh Fedora 15 install.
I did systemctl enable denyhosts.service. systemctl ran chkconfig.
When I started the service I got this in /var/log/messages:
May 29 07:49:33 murron setroubleshoot: SELinux is preventing
/usr/bin/python from read access on the lnk_file /var/lock. For
complete SELinux messages. run sealert -l
fc8b6153-e359-409b-9310-9f0f3b3a20c7
sealert says:
SELinux is preventing /usr/bin/python from read access on the
lnk_file /var/lock.
***** Plugin restorecon (94.8 confidence) suggests
*************************
If you want to fix the label.
/var/lock default label should be var_lock_t.
Then you can run restorecon.
Do
# /sbin/restorecon -v /var/lock
***** Plugin catchall_labels (5.21 confidence) suggests
********************
If you want to allow python to have read access on the lock lnk_file
Then you need to change the label on /var/lock
Do
# semanage fcontext -a -t FILE_TYPE '/var/lock'
where FILE_TYPE is one of the following: var_run_t, var_lock_t,
bin_t, cert_t, usr_t, device_t, devlog_t, locale_t, abrt_t,
etc_t, lib_t, proc_t, root_t, device_t, ld_so_t, proc_t,
denyhosts_t, textrel_shlib_t, rpm_script_tmp_t, var_run_t.
Then execute:
restorecon -v '/var/lock'
***** Plugin catchall (1.44 confidence) suggests
***************************
If you believe that python should be allowed read access on the
lock lnk_file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep denyhosts.py /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
12 years, 11 months
gnome 3 multiple monitors and alt-tab incorrect position
by Albert de Jongh
I am running Fedora 15, with two monitors. If I alt-tab the dialog is
always on the left (primary?) monitor - no matter where the mouse cursor
is. Is this an intentional design decision, or am I doing something wrong?
12 years, 11 months
What on earth is mounted?
by Tom Horsley
I was checking to see if I had everything mounted that I wanted
in a newly genned f15 system, and I see this insanity in
the output from running "mount":
/dev/sda2 on / type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=0,data=ordered)
/dev/sda2 on /tmp type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=0,data=ordered)
/dev/sda2 on /var/tmp type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=0,data=ordered)
/dev/sda2 on /home type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=0,data=ordered)
Where on earth do those /tmp /var/tmp and /home entries come from?
They certainly aren't all mounted on top of the same filesystem root.
There are no entries for them in /etc/fstab. What is going on?
They also all show up with identical free space entries in the
output from the df command.
This is just wayyyy confusing.
Can I make it stop somehow and leave them as ordinary subdirectories
as they have always been?
12 years, 11 months