Edit the boot manager
by Christopher Cornelius
Hello community,
Where do I go to edit the boot manager?
--
Christopher B. Cornelius
19 years, 7 months
noob sata question...
by Chris Tencati
Back when I had FC2 with the 2.4.x kernel, obviously there was no sata
support built-in, but I'm using a promise controller and they make their
drivers available for download/build, so everything worked fine. Now I'm
using an up to date (as of yesterday) version of FC2T2, and that's causing
some problems for me. SATA support is now built-in to the kernel, which is
great, but I can't figure out how to actually access the disk...with the old
driver I think it got reported as a scsi drive (which I swear is wrong) that
was then faked as a normal ide drive, and I could mount it normally as
/dev/hdc. Now though I don't have any scsi drives listed, udev made my
cdrom into /dev/hdc (which is lame, it's not an hd!) and there are no
addition hd* devices and nothing in general that looks correct. md0 is also
unmountable. The sata_promise module/driver and others are loaded, and the
system does recognize that there is a sata drive connected - KDE's hardware
browser lists it under RAID devices (it's not hardware raid though if that's
important), but I can't figure out any way to access it. I tried playing
with MAKEDEV but since I don't really know what to try with it, that didn't
help at all. /etc/fstab and /proc/partitions don't list anything except my
'normal' drives...
>From looking at all the stuff online about sata and linux and the new 2.6
kernels, it seems I'm missing something painfully obvious, but I really
can't think of what else to try. Promise doesn't have binaries or source
for independent modules that support the 2.6 kernels (which makes sense
since it's now included in the kernel itself), so I can't just do what I did
before either. So any idea what stupid thing I'm overlooking, so that I can
actually use this other drive?
FC2T2
kernel 2.6.8-1.541 (stock FC build)
Promise SATA 150 TX2plus controller
some Maxtor SATA drive
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
hthttp://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
19 years, 7 months
Pam problem
by Paul F. Johnson
Hi,
The first user to use the soundcard keeps it. No-one else can use the
soundcard.
Any ideas on how to fix the problem? It is a pam problem IIRC.
TTFN
Paul
--
Homer: Donut?
Lisa: No, thanks. Do you have any fruit?
Homer: This has purple stuff inside. Purple is a fruit.
19 years, 7 months
SELinux error with -584 kernel
by Michel Salim
Hi,
I get audit errors when booting up (and similar messages when shutting
down) with the -1.584 kernel:
audit(1095879279.586:0): avc: denied { read write } for pid=1701
exe=/sbin/minilogd name=console dev=tmpfs ino=993
scontext=user_u:system_r:syslogd_t tcontext=user_u:object_r:tmpfs_t
tclass=chr_file
(and lots of other messages like this one)
This does not happen under the -1.541 kernel that shipped with the
install media; is this normal, should I file a bug, and against the
kernel, selinux-policy-targetd, or mkinitrd?
Thanks,
--
Michel Salim 林智勇
http://salimma.livejournal.com
19 years, 7 months
Re: Pam problem
by sangu
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134426#c1
Poul's positng seems to be similar to #134426.
2004-10-03 (일), 13:03 -0400, Colin Walters 쓰시길:
> On Sun, 2004-10-03 at 17:20 +0100, Paul wrote:
>
> > Version 1.
> >
> > User 1 logs in, uses xmms, logs out
> > User 2 logs in, xmms reports soundcard blocked
> >
> > Version 2.
> >
> > User 1 logs in, uses xmms, logs into a couple of consoles (use
> > bittorrent, do an update and something else). Logs out
> > User 2 logs in, xmms reports soundcard blocked.
> >
> > What should happen is for version 1, user 2 should gain control over the
> > soundcard.
>
> Absolutely. If User 2 doesn't gain control that's a bug. Can you be
> sure that /var/run/console/console.lock doesn't exist after User 1 logs
> out?
>
> > Not sure what should happen for version 2, but I think once
> > user 1 has logged out of the X session, then user 2 should gain
> > permission.
>
> Yes, I think it would be best if user 2 gained permission as well, but
> unless the device supports hardware mixing you're going to lose anyways.
> In this case you need a sound server. But if you do have hardware
> mixing one nicer way to do this might be to modify pam_console to use
> ACLs on the devices instead of changing ownership.
>
>
> --
> fedora-test-list mailing list
> fedora-test-list(a)redhat.com
> To unsubscribe:
> http://www.redhat.com/mailman/listinfo/fedora-test-list
19 years, 7 months
Am I going mad?
by Paul F. Johnson
Hi,
My laptop has the 590 kernel on, this box has 584 on and currently on
the FC ftp site, it's on 581!
What gives?
Also, why can't I download and install RealPlayer? It was on the update
list a few days back.
TTFN
Paul
--
Homer: Donut?
Lisa: No, thanks. Do you have any fruit?
Homer: This has purple stuff inside. Purple is a fruit.
19 years, 7 months
SA - multiple instances
by Paul F. Johnson
Hi,
ISTR that under FC2, SA did not spawn instances for individual users (or
if it did, then the instances were killed after the end of email
checks). I have two sets running currently, one set for me and one set
as root.
Is this the correct behaviour?
TTFN
Paul
(Struggling with pam so that all users can have access to the scanner,
printer and soundcards)
--
Homer: Donut?
Lisa: No, thanks. Do you have any fruit?
Homer: This has purple stuff inside. Purple is a fruit.
19 years, 7 months
dbus-daemon-1. Is this right?
by Paul F. Johnson
Hi,
I'm looking at gnome-sys-monitor to see if I can see what's chomping the
processor and I'm seeing 15 instances of dbus-daemon-1 for user 'bev', 2
for user 'richard' and one for me and root.
Why should there be this many instances of dbus-daemon-1 running? If it
isn't, any ideas on what is causing this many of instances being created
so I can put something into bugzilla?
TTFN
Paul
--
Homer: Donut?
Lisa: No, thanks. Do you have any fruit?
Homer: This has purple stuff inside. Purple is a fruit.
19 years, 7 months
Login oddity
by Paul F. Johnson
Hi,
If I reboot and login, I get the original fc3t2 black with funny smokey
stripes desktop and lots of complaints of panel applets which have
failed. I am unable to logout via the redhat menu and have to do it with
ctrl alt backspace. Next time I login, everything is fine.
If have deleted myself and added myself with s-c-users as that sometimes
does the trick. It didn't.
When I installed FC3t2, I had one HD in. I then added my old drive with
the /home directories, altered fstab and rebooted. It looks like there
is a conflict between the /home on /dev/hda2 and the one on the other
drive.
Is there a simple way to cure the problem?
TTFN
Paul
--
Homer: Donut?
Lisa: No, thanks. Do you have any fruit?
Homer: This has purple stuff inside. Purple is a fruit.
19 years, 7 months
gnome-pilot question
by Eamonn Sullivan
Hi. I've been impressed enough with FC3T2 to attempt to connect by
wife's palmpilot (a USB-connected m500) to it. I have to admit this is
the very first time I've tried this, even though Linux and I go back
to the very first, painstakingly downloaded stack of Slackware
floppies... Anyway, I must be doing something very simple wrong.
When I hit the sync button, two (?) new links are created in /dev
ttyUSB0 and ttyUSB1. But when I use gnome-pilot, it just sits there
forever at the screen that asks me to press the HotSync button and
never sees the device.
What I've tried: starting the sync before opening gnome-pilot, press
the sync button only when asked to by gnome-pilot and tried telling it
to look at /dev/pilot, /dev/ttyUSB0, /dev/ttyUSB1. All to no avail.
My system logs look like this:
Oct 3 15:57:07 localhost kernel: usb 3-1: new full speed USB device
using address 15
Oct 3 15:57:07 localhost kernel: visor 3-1:1.0: Handspring Visor /
Palm OS converter detected
Oct 3 15:57:07 localhost kernel: usb 3-1: Handspring Visor / Palm OS
converter now attached to ttyUSB0
Oct 3 15:57:07 localhost kernel: usb 3-1: Handspring Visor / Palm OS
converter now attached to ttyUSB1
Oct 3 15:57:07 localhost udev: creating device node '/dev/ttyUSB1'
Oct 3 15:57:08 localhost udev: creating device node '/dev/ttyUSB0'
Oct 3 15:58:17 localhost udev: removing device node '/dev/ttyUSB0'
Oct 3 15:58:18 localhost udev: removing device node '/dev/ttyUSB1'
Oct 3 15:58:18 localhost kernel: usb 3-1: USB disconnect, address 15
What simple thing am I missing?
19 years, 7 months