This occurs because swapon is called twice, first in S10checkroot.sh,
then in S35mountall.sh. Ideally I guess some smarts to detect swap files
that are now available but have not yet been activated, rather than
simply trying to remount all swap filesystems a second time would be
helpful, as this error message has the ability to unnerve the unwary.
Stu
--
>From the prompt of Stu Teasdale
"With molasses you catch flies, with vinegar you catch nobody."
-- Baltimore City Councilman Dominic DiPietro
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
