OS wrote:

>Hello,
>
>I have mentioned before that Aurora is the wrong way around, but here is 
>another example:
>
>initscripts now asks if you wish to scan the disks if the system is not shut 
>down correctly (incidently, when I said NO to this the disks were still 
>scanned !). However, because Aurora only displays things AFTER the event this 
>prompt sits there hidden until it times out and the scan is performed. After 
>doing this the message "Do you want to ..." flashes extremely fast before 
>you. I think asking questions at boot time and Aurora just don't sit well 
>together !
>
>Owen
>
>
The problem in my mind is not with Aurora, but with initscripts.  This 
in not a new problem.  Aurora has been choking on kudzu for as long as 
Aurora has been around.  The solution is for initscripts to be 'Aurora 
aware'.  Initscripts needs to check if Aurora has been selected, and if 
it has select the appropriate switches which either skip the step 
(exercises like kudzu are rather meaningless under Aurora), or default 
the step (if a disk is not clean and Aurora is running, the disk should 
be audited, users who typically use Aurora won't be able to make an 
intelligent choice on this anyway, and could easily get themselves in 
trouble, audit the disk, OK?).  On the other hand, when booting in raw 
mode, all of the granularity should function with preciseness.  If I 
answer 'no' to a disk audit, the system should not insult me in typical 
Windows fashion and go ahead and perform the audit.

- George Mitchell



Reply via email to