Pixel wrote:
> Borsenkow Andrej <[EMAIL PROTECTED]> writes:
>
>
>>This may be considered devfsd bug ... but to fix it means major design change.
>>And we must do something for 8.1.
>>
>
> In fact, i'd say it's a kernel bug triggered by devfsd. The change causing all
> this is unlink'ing before symlink'ing.
>
Sorry? Are you sure we are speaking about the same problem?
In scenario I described there is no unlinking in the first place. When
you start, you have no link (e.g. /dev/sda4) and no module for your
removable drive. Then you plug in your drive and do 'mount /dev/sda4
/mnt/hd). It triggers LOOKUP event and module loading, let's say ppa.
ppa creates canocical device /dev/scsi/... It triggers REGISTER. As
result devfsd creates link /dev/sda4 -> /dev/scsi/../part4. For kernel
it just another user application, so it results in CREATE action being
triggered and link is copied into /lib/dev-state.
Where is this "unlinking" you speak about?
Then you reboot. The link /lib/dev-state/sda4 is copied back into /dev.
After some time you come, plug in your removable drive, do 'mount
/dev/sda4 /mnt/hd' ... and nothing happens. Because /dev/sda4 already
exists, so no LOOKUP event is generated, no module is loaded.
Very simple. Again, where is this "unlinking" you speak about?
> the solution fredl is currently "implementing" is just removing the warning
> when the existing file is the same symlink as the one we want.
>
What warining? I do not care a *** about these warnings. I do care that
I cannot simply do urpmi and have to do
rm /dev/sda*
every time after reboot. I just modified /etc/rc.d/rc.sysinit as
described and this problem went away.
-andrej
