Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 07 Nov 1998 19:38:49 +0100
From:      Stefan Eggers <seggers@semyam.dinoco.de>
To:        Mikhail Teterin <mi@video-collage.com>
Cc:        current@FreeBSD.ORG, seggers@semyam.dinoco.de
Subject:   Re: same swap twice (was Re: The infamous dying daemons bug) 
Message-ID:  <199811071838.TAA07868@semyam.dinoco.de>
In-Reply-To: Your message of "Fri, 06 Nov 1998 21:04:48 EST." <199811070204.VAA10749@xxx.video-collage.com> 

next in thread | previous in thread | raw e-mail | index | archive | help

> =It may be interesting to know that mounting the same swap paritition
> =twice causes the exact same symptoms.
> 
> Some time back, I submitted a PR about ``swapon'' and/or underlying
> calls being not picky enough to prevent this sort of mistakes from

And how do you think shall it be prevented?  Making swapon know about
partitions and compatibility slice would be insane.

Maybe one could add functionality to the device drivers to allow
checking for "being the same thing" which gets callend whenever the
major device numbers are the same.  A driver not supporting this has
all the minors being "different things" by default.

The "thing" not necessarily being a partition of course as for example
the rewinding and non-rewinding minors of a tape device driver use the
same hardware and there this might get used for something, too.

> happening. One of the gods closed the PR promptly with "Don't do it
> then"...

Maybe you want to implement it the way suggested above and do the
testing?  A reasonably simple solution probably has a chance of
getting added.

W/o code such a PR hardly has a chance.  It's as if you complain about
config not preventing you from creating a non-compiling kernel config.
I once managed to do so by trying to exclude INET from a 2.2 kernel
which failed to compile and there are numerous other ways of doing
things wrong.

Or take another example.  Put "reboot" into /boot/boot.config and it
will be fun to watch the boot loader starting again all the time.
Shall code be added to prevent that?  Is it worth the investment of
time?  Probably not unless someone already has working code to do it.

Stefan.
-- 
Stefan Eggers                 Lu4 yao2 zhi1 ma3 li4,
Max-Slevogt-Str. 1            ri4 jiu3 jian4 ren2 xin1.
51109 Koeln
Federal Republic of Germany

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811071838.TAA07868>