After downgrading lilo to 1:22.8-3.1 (sept. 2007) andexecuting lilo -v, the bug still persists. So it seems this has nothing to do with lilo??

--
Eugen



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to