Re: [gentoo-user] Re: DST didn't happen: quickinstall doc is wrong...

2007-03-12 Thread Albert Hopkins
On Mon, 2007-03-12 at 15:53 +, Grant Edwards wrote:
 Yup, that was evidently the problem. Perhaps step #2 should be
 documented in the Handbook and/or the Quickinstall 

Perhaps the constant nagging from the timezone-data package when it's
emerged as well as the system when it's booted isn't enough?

--
Albert W. Hopkins

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Re: DST didn't happen: quickinstall doc is wrong...

2007-03-12 Thread Allan Gottlieb
At Mon, 12 Mar 2007 15:53:40 + (UTC) Grant Edwards [EMAIL PROTECTED] 
wrote:

 On 2007-03-12, Albert Hopkins [EMAIL PROTECTED] wrote:
 On Mon, 2007-03-12 at 15:07 +, Grant Edwards wrote
 
 That was the old way of doing it.  For a number of reasons a new
 method is devised.  The new method is:

  1. copy file from /usr/share/zoneinfo to /etc/localtime
  2. set your timezone in /etc/conf.d/clock.

 Yup, that was evidently the problem. Perhaps step #2 should be
 documented in the Handbook and/or the Quickinstall?

I agree that it should be mentioned and filed
http://bugs.gentoo.org/show_bug.cgi?id=170591

(I was lucky and noticed the warning message during reboot that my
timezone was set to factory in /etc/conf.d/clock so was not bitten.)

allan

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Re: DST didn't happen: quickinstall doc is wrong...

2007-03-12 Thread Albert Hopkins
On Mon, 2007-03-12 at 16:28 +, Grant Edwards wrote:
  Perhaps the constant nagging from the timezone-data package
  when it's emerged
 
 When it's emerged as part of an update with 30 or 40 other
 packages, it's pretty easy to miss things like that.
 
This has long been a complaint among users of portage,including myself.
The portage devs have done work to alleviate most of these problems with
the ELOG system.  I really recommend taking advantage of it.  With it I
have portage info and warnings emailed to me and I have to say it has
really helped me become aware of what is changing on my system.

  as well as the system when it's booted
 
 My computers are generally only booted as a result of a power
 failure, and I'm not usually there to watch them boot.
 
  isn't enough?
 
 Apparently not, if so many people had problems with it. 

I agree with you that the Handbook needs to be updated, but in general
it's always best to pay attention to what the system is telling you.
The portage tree is always going to be updated faster than the Handbook
and four years of experience has shown me that the Handbooks is always
at least a little behind reality.  I think the authors work hard, but
they're always going to be chasing a moving target.

Also, people who do not frequently do installs are less likely to read
the Handbook so it's best to let real life supersede what's written in
the Handbook.

--
Albert W. Hopkins

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Re: DST didn't happen: quickinstall doc is wrong...

2007-03-12 Thread Albert Hopkins
On Mon, 2007-03-12 at 15:33 -0400, John covici wrote:
 I wish you could have an option for portage to stop until these things
 are acknowledged -- I had a 106 package update of which the timezone
 data were a part and I use script and check these little notices,
 however its easy to miss such things.

If that ever happened I hope it would be made optional.  I'm just the
opposite.  I would hate to come back to my system to learn that 105
packages didn't get built because someone decided to interrupt it
because of a change in an /etc/* file. Furthermore, I wouldn't trust
what individual package maintainers thought was worthy of interrupting
my build.  Builds should only be interrupted if they cannot continue.

--
Albert W. Hopkins

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Re: DST didn't happen: quickinstall doc is wrong...

2007-03-12 Thread Mark Knecht

On 3/12/07, Albert Hopkins [EMAIL PROTECTED] wrote:

On Mon, 2007-03-12 at 15:33 -0400, John covici wrote:
 I wish you could have an option for portage to stop until these things
 are acknowledged -- I had a 106 package update of which the timezone
 data were a part and I use script and check these little notices,
 however its easy to miss such things.

If that ever happened I hope it would be made optional.  I'm just the
opposite.  I would hate to come back to my system to learn that 105
packages didn't get built because someone decided to interrupt it
because of a change in an /etc/* file. Furthermore, I wouldn't trust
what individual package maintainers thought was worthy of interrupting
my build.  Builds should only be interrupted if they cannot continue.

--
Albert W. Hopkins


I agree. When doing the occasional emerge -e world the process needs
to move forward without interruption.

I am interested however in learning about how to get these messages
logged and sent by email or at least into some file that easy to look
at. I think they already go into the portage /var log file but I find
that pretty tedious and easy to miss messages.

Thanks,
Mark
--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Re: DST didn't happen: quickinstall doc is wrong...

2007-03-12 Thread Neil Bothwick
On Mon, 12 Mar 2007 15:33:54 -0400, John covici wrote:

 I wish you could have an option for portage to stop until these things
 are acknowledged -- I had a 106 package update of which the timezone
 data were a part and I use script and check these little notices,
 however its easy to miss such things.

Portage is supposed to be non-interactive whenever possible. I'd rather
take the trouble to read the emails sent out by ELOG than set a 106
package emerge running overnight, only to find the next morning that it
had stopped after the second package because of a minor warning that could
have been emailed or logged.


-- 
Neil Bothwick

Bother, said Pooh as he farted in front of a badly placed candle


signature.asc
Description: PGP signature


Re: [gentoo-user] Re: DST didn't happen: quickinstall doc is wrong...

2007-03-12 Thread Neil Bothwick
On Mon, 12 Mar 2007 14:19:03 -0700, Mark Knecht wrote:

 I am interested however in learning about how to get these messages
 logged and sent by email or at least into some file that easy to look
 at. I think they already go into the portage /var log file but I find
 that pretty tedious and easy to miss messages.

Read the section on the PORTAGE_ELOG settings ion /etc/make.conf.exmple 


-- 
Neil Bothwick

Idaho - It's not the end of the world, but you can see it from there.


signature.asc
Description: PGP signature