Which will work best ...
by Jonathan Allen
Hi All,
Which is likely to work best out of the box with Fedora ...
1. AMD Dual Core 4200 on an Nvidia 6100S motherboard/chipset and graphics
2. Intel Pentium Dual Core 925 on an Intel 946GZ Chipset MicroATX
Motherboard and
Intel GMA 950 PCI Express Graphics
3. Intel Pentium Dual Core E2140 on an Intel 946GZ Chipset MicroATX
Motherboard
and Intel GMA 950 PCI Express Graphics
Your opinions welcomed
Jonathan
16 years, 3 months
selinux, sendmail, and services
by SternData
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
For two days, I've been receiving notices from setroubleshooter about
sendmail and "unknown file". Today, after the pam update, I rebooted
and saw sendmail fail to start due to a problem with "services".
Feb 26 06:55:50 sds-desk setroubleshoot: #012 SELinux is preventing
the /usr/sbin/sendmail.sendmail from using potentially mislabeled files
(<Unknown>).#012
Feb 26 07:04:35 sds-desk setroubleshoot: #012 SELinux is preventing
the /usr/sbin/sendmail.sendmail from using potentially mislabeled files
(/etc/services).#012
I used
~ grep sendmail /var/log/audit/audit.log | audit2allow -M sendmail
to generate a policy to fix this. Was this the right thing to do? And
what caused sendmail and selinux to suddenly have a problem?
sendmail.te:
module sendmail 1.0;
require {
~ type initrc_tmp_t;
~ type rpm_script_tmp_t;
~ type system_mail_t;
~ type unconfined_home_t;
~ type sendmail_t;
~ type unconfined_home_dir_t;
~ type var_t;
~ class process setrlimit;
~ class dir { getattr search };
~ class file { write getattr read ioctl };
}
#============= sendmail_t ==============
allow sendmail_t initrc_tmp_t:file { read write getattr ioctl };
allow sendmail_t rpm_script_tmp_t:file read;
allow sendmail_t self:process setrlimit;
allow sendmail_t unconfined_home_dir_t:dir { getattr search };
allow sendmail_t unconfined_home_t:file { read getattr };
allow sendmail_t var_t:file { read write };
#============= system_mail_t ==============
allow system_mail_t rpm_script_tmp_t:file read;
- --
~ Steve
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHxBKueERILVgMyvARAvE6AJ49qi30dYDaPPmEWAcXZCK3Sf+i+ACeLgYa
GsbDrhehWXwG+MMxAEoNHXc=
=uKfC
-----END PGP SIGNATURE-----
16 years, 3 months
Keyboard configuration problem
by ALBERTO VIEIRA FERREIRA MONTEIRO
I got a weird problem when upgrading from FC4 to FC6.
My keyboard is brazilian, abnt2. It worked fine in FC4. But, after the
upgrade, it behaves strangely. And the behaviour can't get fixed by
system-config-keyboard or any other trivial method.
In resume, for some accounts, it works fine, as abnt2. For other accounts
under KDE (but not under Gnome) it works as an USA keyboard. And for
other accounts, the keys are misinterpreted.
I suppose there must be something wrong down in the .kde tree, and
I think I could fix it if I could delete some files. But I have no idea which
(until now, I haven't done anything irreversibly destructive...). Any ideas?
Alberto Monteiro
16 years, 3 months
"driver=" entry in /proc/bus/usb/devices??
by Robert P. J. Day
from the user manual for VirtualBox related to accessing USB
devices:
"On Linux hosts, VirtualBox accesses USB devices on Linux through the
usbfs file system. Therefore, the user executing VirtualBox needs read
and write permission to the USB file system. Most distributions
provide a group (e.g. usbusers) which the VirtualBox user needs to be
added to. Also, VirtualBox can only proxy to virtual machines USB
devices which are not claimed by a Linux host USB driver. Please refer
to the driver= entry in /proc/bus/usb/devices to see which devices are
claimed."
my questions:
1) what means this "driver=" entry in /proc/bus/usb/devices? never
heard of it. it certainly doesn't appear to exist on fedora. did it
ever?
2) i also see no evidence of a "usbusers" group on fedora. in any
event, since standard USB access seems to be working, i'm guessing
those two issues aren't relevant WRT fedora. should i care?
thoughts?
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================
16 years, 3 months
How to install KDE4 on Fedora 8?
by Zhongxing Xu
Hi,
I wish I could use KDE4 on my Fedora 8. Can I use yum to install it? What
configuration is needed? My run level is 5.
16 years, 3 months
OT, way OT
by Gene Heskett
Greetings all;
I just installed firefox3b3 here, separately from the fedora issue, and wow,
is it fast & only one hiccup in a carload, but that hiccup is making it
difficult to use it as a default browser.
The hiccup is: Anytime you have to enter data in a web sites data requestor
box, from the keyboard, the text line, which is white, stays white, no
cursor, nothing, UNTIL you take the focus away from this entry line, and then
you can see what you typed.
FF-2.0.0.12 doesn't have this problem, and neither does the official F8
version the last time I checked.
Does anyone have any idea what I should check out in the about:config (or
prefs) that might effect that, like a background and text color the same
$FFFFFF or ??
This new version is MUCH faster, and if I could fix that I'd never go back to
Camels. :)
Many Thanks for any hints rolled my way.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Superior ability breeds superior ambition.
-- Spock, "Space Seed", stardate 3141.9
16 years, 3 months
Enable compiz-fusion after kernel update
by Doctor Who
I had compiz-fusion working on my Fedora 7 machine with nvidia
graphics card. I have recently updated my kernel and now I'm booted
to a console due to X failing.
What must be done to get compiz fusion back. In other distros, I've
had to rebuild my kernel sources, but I'm not sure of the process with
Fedora yet.
Thanks for any help.
16 years, 3 months
attempt to access beyond end of device
by Michael D. Berger
My minimal FC7 box has 125M ram, 20G hard drive, 400 MHZ. I have been
successfully using it for a web server. Suddenly it began doing
the sort of thing shown below. I know neither what starts in nor how
many there are, but my /var/messages file exceeds 1G. I am guessing
that there is some limit parameter somewhere that I can set.
Any suggestions?
Thanks,
Mike.
Feb 24 18:40:43 mbrc20 kernel: device-mapper: ioctl: 4.11.0-ioctl
(2006-10-12) initialised: dm-devel(a)redhat.com
Feb 24 18:40:43 mbrc20 kernel: attempt to access beyond end of device
Feb 24 18:40:43 mbrc20 kernel: sda: rw=0, want=40017743, limit=39062500
Feb 24 18:40:43 mbrc20 kernel: attempt to access beyond end of device
Feb 24 18:40:43 mbrc20 kernel: sda: rw=0, want=40017743, limit=39062500
Feb 24 18:40:43 mbrc20 kernel: attempt to access beyond end of device
Feb 24 18:40:43 mbrc20 kernel: sda: rw=0, want=39923925, limit=39062500
Feb 24 18:40:43 mbrc20 kernel: Buffer I/O error on device dm-1, logical
block 131056
Feb 24 18:40:43 mbrc20 kernel: attempt to access beyond end of device
Feb 24 18:40:43 mbrc20 kernel: sda: rw=0, want=39923925, limit=39062500
Feb 24 18:40:43 mbrc20 kernel: Buffer I/O error on device dm-1, logical
block 131056
Feb 24 18:40:43 mbrc20 kernel: attempt to access beyond end of device
Feb 24 18:40:43 mbrc20 kernel: sda: rw=0, want=40017743, limit=39062500
16 years, 3 months