David Howells:
>
> In a way, SCSI IDs and LUNs can change... When you do hot swapping of SCSI
> devices (may well be more likely than interface cards).
>
Hmm. I don't see anybody unplugging their SCSI disk w/ ID 0, rejumper it to
have ID 1, reattach it, and then expect the OS to recognize it as the same
disk.
> locked, the driver doesn't communicate with it's device, so that I can safely
with _its_ device... ;-)
> And the following to resume them all:
> cat <<EOF >/proc/cm/conf
> a scsidev0 1
> a scsidev1 1
> a scsidev3 1
> a scsidev7 1
> EOF
Currently, you cannot do that because the system tries to change the atime
for /bin/cat, and the shell wants to create a temporary file for the data,
not to mention swap in portions of /usr/bin/screen or /usr/sbin/telnetd.
Instant system hang... this needs a statically-linked standalone program
which calls mlock(MLOCKALL) and then waits a specified number of seconds
before automatically reenabling things.
-- Matthias Urlichs | noris network GmbH | smurf@noris.de The quote was selected randomly. Really. | http://www.noris.de/~smurf/-- I don't know why, but first C programs tend to look a lot worse than first programs in any other language (maybe except for fortran, but then I suspect all fortran programs look like 'firsts'). -- Olaf Kirch- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/faq.html