John on S8

[John]

Matt Zimmerman wrote:

>On Sun, Sep 12, 2004 at 09:22:08PM +0800, John wrote:
>
>  
>
>>I think hiding the grub menu a mistake, and I thought the default delay 
>>a little short.
>>    
>>
>
>We've increased the timeout once already (from 2 seconds to 3 seconds), and
>while I agree that _when you want it_ a longer timeout would be nice, most
>users will never know that the grub menu exists, and a longer delay just
>slows down their boot process.
>
>I believe you can hold down the escape key rather than waiting for the
>prompt to appear.
>
>  
>
There is that message, but the I was dead lucky to get it first time. 
Second time I missed it and booted what might have been the wrong 
kernel, and certainly without the opportunity to add kernel parameters.

>>I think hiding the menu a mistake because I've sometimes recognised that 
>>the default was wrong.
>>    
>>
>
>Can you be more specific?
>  
>

When I'm booting, the Grub menu provides affirmation that it's going to 
boot the kernel _I_ want. Most times (but not always) it's the last one 
I booted.

If I don't see the menu I don't have that confidence.

>  
>
>>User account
>>I accidently typed "Summer" meaning "summer," and the "error" was not 
>>reported to me until after I had supplied the password.
>>
>>I'm not sure that "Summer" really is invalid. I can imagine it would 
>>cause problems with email, but I think it should work aside from that. 
>>Certainly, useradd is fine with it:
>>    
>>
>
>It's not invalid, but it would be rather confusing to the uninitiated, since
>the tools are case-sensitive. I agree; suggesting it imprudent and asking for confirmation would be sufficient. Saying it's wrong....
>
>Yes, the error should be reported immediately, rather than after reading the
>password as well.  Please file a bug (severity minor) about that.
>  
>

I cannot at present easily report bugs from that system, it's not on the 
LAN. I hope to have Wireless by week's end.

>  
>
>>However, that's a minor point; what irritated me was its description as an
>>error.
>>    
>>
>
>Perhaps you can suggest alternate text for the error.  We won't be changing
>it for the Warty release because it would be disruptive for the translated
>messages, but we will certainly be considering these issues for Hoary.
>
>  
>
>>The assumption computers clocks are set to UTC is unsound.
>>    
>>
>
>The defaults are oriented toward a system where Ubuntu is the only installed
>operating system (hence the "erase entire disk" default as well), where UTC
>is a reasonable choice.
>  
>

All the computers I've bought have had the clocks set to local time. 
except possibly the Suns. If Ibuy or build a peecee I see these scenarios:
1. Clock unset. User sets it to watch time.
2. Clock set by manutacturer. Probably Taiwan (same as ours in this 
instance).
3. Set by importer. Probably (Australia) EST (Sydney/Melbourne).
4. Set by vendor. Same as 3 for name vendors (who are mostly located in 
Sydney or Melbourne). Local watch time for local PC shops.

I recently installed a new mobo; I didn't norice the time so it probably 
fell into 2. Certainly, _I_ didn't set it, but Sarge might have when it 
booted.

>  
>
>>Why ask about configuring ppp during boot? We're installing from CD.
>>    
>>
>
>Agreed, we shouldn't be asking this question when installing from CD.
>Colin, is this trivial to fix?
>
>  
>
>>First login.
>>I logged in with my own account and had a look around.
>>Screen res is 1024x768 which suits Mrs S (but not me).
>>    
>>
>
>Is your hardware capable of higher resolution?  If so, that would imply that
>the autodetection probe was not successful, and there may be a bug report in
>  
>
the Acter 77c? CRT. As I said, the Gateway was driving my 20" Sun at 
1600x1200. This monitor probably does 1280x1024 at 60 with some flicker. It 
won't suit everyone; my wife and eldest daughter would complain (S 
because everything's too small, Rebekah because it flickers).

>it.  I'm attaching instructions for how to test.  Is this a CRT or an LCD?
>
>  
>

That's not going to happen until I have wireless running in it.

> ------------------------------------------------------------------------
>
> Subject:
> Notes on how to debug X autodetection.
> From:
> Fabio Massimo Di Nitto <fabbione at fabbione.net>
> Date:
> Thu, 26 Aug 2004 10:34:31 +0200 (CEST)
> To:
> sounder at lists.no-name-yet.com
>
> To:
> sounder at lists.no-name-yet.com
>
>