I will. But first there is a need to find the bug wich removed every
single removable storage from my fstab ;)
CC'ing to fedora-devel, since there is where the discussion started...
I have now created a bug report on the new problem - that every
removable storage thing is nuked. When that is fixed, ill see if i can
reproduce the original error.
Maybee ask for imput from fedora-test-list? There might be somebody who
has had the same troubles.
man, 27.09.2004 kl. 14.16 skrev Jeff Spaleta:
> On Mon, 27 Sep 2004 11:30:48 +0200, Kyrre Ness Sjobak
> <kyrre(a)solution-forge.net> wrote:
> > => probably not a gnome problem.
> > How the fstab etc. looked when i had 3 floppy disks, i dont know. But
> > since it seems like gnome is telling the truth, i think there must have
> > been 3 fstab entries.
> That is an absolutely horrible assumption to make. I have run into
> bugs with gamin in the past which left devices listing in my computer
> even though fstab was being propoerly updated. You need to attempt to
> reproduce this and you need to narrow it down for the bugreport to
> have any meaningful value.
The Fedora Core 3 freeze is coming soon, so it's time again for the
frantic activities of a Bug Week. This time with community participation.
The idea is to fix as many bugs as possible in the week from Sunday,
September 26th till Friday, October 1st. Yes, it starts this weekend...
The goal of Bug Week is to fix as many of the annoying bugs out there
as possible, so Fedora Core 3 ends up being a nice distribution without
rough edges. We're going for quantity here, trying to fix all the
easily fixable bugs that annoy users. Of course, if you have a fix for
a harder to resolve problem, you're more than welcome to contribute it!
Developers: you can help by fixing bugs and reviewing the proposed
fixes that other people mail to the fedora-patches-list,
or that get attached to bugzilla. Packaging bugs are
another category where we can use your help.
Testers: you can help by verifying whether old bugs are still present
in rawhide, as well as by testing proposed fixes sent in by
Bug triagers: you can help by gathering information on NEEDINFO bugs, as
well as by helping assess the importance of bugs.
Everybody: this is a chance to get the bugs fixed that you care about!
Developers from all engineering groups in Red Hat are standing by
to fix bugs together with you, to apply submitted bug fixes and to
make test RPMs available on the Bug Week repositories.
To participate in Bug Week, you can use the normal channels of
- For discussion: fedora-devel-list, fedora-tools-list, fedora-test-list
- For proposed patches: fedora-patches-list (so others have a chance
of reviewing the proposed patches and verifying that they are ok)
- For verified patches: bugzilla (to keep track of the patch)
- IRC: #fedora-bugweek on irc.freenode.net
If you want to nominate a bug for being fixed this Bug Week, please
send an email to me (riel(a)redhat.com) and the owner of the bug that
you want to nominate for the Bug Week must-fix list. Note that bugs
will only be accepted for the Bug Week must-fix list if there is a
realistic chance of fixing them this week.
More information will be available soon, on:
Developers, remember to subscribe to fedora-patches-list:
You can track our progress on the FC3 Bug Week Tracker bug:
Just wondering about something:
When i plugged in my camera (which is a usb mass storage device),
mountpoints are automatically created (one for /dev/sda and another for
/dev/sda1), and /dev/sda1 is mounted. (so why is sda1 created? sda is
nothing...) Great work. (but why are they named floppy? My camera isn't
a floppy - and who hotplugs scsi floppy disks using the mass storage
driver on the usb port?!?)
But then, when i decide "enough", i pull the plug (which is ok, since it
is mounted with "sync"), and it gets umounted. So far, so good.
But the mountpoints are still there - so according to gnome's "my
computer" - i now have tree floppy discs.
So i decided to upgrade hal and dbus, just to see if anything happens.
"yum upgrade hal" and "yum upgrade dbus". Done. Log in (i was doing this
over ssh) to see the effects. Quite astonishing - it had "cleaned up"
all of my removable media stuff - ie. my cdrom, floppy, and all the
extra floppys are gone. Okay... So i try to "hotplug" a cd into the
drive. It spinns up for about a minute, and nothing happens. I then try
to connect the camera. The usb activity light flashes a bit, but no new
mountpoints... Thats... bad.
Maybe kudzu could make a difference. So i start kudzu. And all it tries
to do, is to remove the printer which are conected to the paralell port
(it is switched of. I hate that behaviour - made me deactivate kudzu in
the past. But it has'nt pestered me during boot due to the printer been
switched off. Thats good!)
So what to do? "yum update kudzu" is the answer. Or not. Reboot then,
and see what happens. No. No luck... And no dbus/hal messages in the
console when plugging in the camera - just that the device was found and
Arg. I smell bugs...
echo mkdmnod | /sbin/nash
rc.sysinit runs the above command to create /dev/mapper/control. Now that we
have udev managing /dev we have no need to have nash do that.
Is it time to remove that line from rc.sysinit? I ask because it requires
undesirable access to be granted in the SE Linux policy.
Also in rc.sysinit we have "echo raidautorun /dev/md0 | nash", but in that
case /dev/md0 does not already exist. Can we change things such that udev
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
Just a note that gqview just got removed from rawhide. It has the same
mission statement as gthumb and uses raster code internally. Yes, I
know there are people who use it still. I suggest this can move over to
Fedora Extras if people really want it.
I have always before been able to run dnsmasq on my smoothwall, and if i
then put a host in its /etc/hosts, all (Linux - it has never worked for
my fathers laptop, so he has to use ip adresses...) computers wich use
that as a dns-server will get it.
F.ex. i have a host called "kyrre". If i want cups to be able to print
to the printer shared on that machine, i have to have a dns lookup for
"kyrre" - either on the local /ets/hosts, or in DNS. So the smoothwalls
hosts file look like this:
And it works great. On all my fc2 (and earlier) linux-computers, i am
able to f.ex type "ssh kyrre", and it looks up kyrre from dns, dnsmasq
on the smoothwall reads the hosts file on the smoothwall, and returns
"192.168.0.200". And i am able to start my evolution over encrypted X,
or print my document (much printing today :-) ) from the laptop.
But with fc3t2, which has a hosts and resolve file which are identical
to the fc2 laptops, this dont work. That means - "host kyrre" returns
the correct IP, but "ssh kyrre" or printing on kyrre dont work
(acctually, hitting "print test page" in the cups web-interfafe just
gives me a google seach for "kyrre").
I would call this a bug. But where should i post it? Which component
does handle DNS lookups?
We haven't had any rawhide reports for a day or two now. Is the build
system hung up again?
Is there a URL for checking the status of the build system?
G.Wolfe Woodbury `- -'
The Line Eater is a boojum!