[prev in list] [next in list] [prev in thread] [next in thread]
List: taroon-beta-list
Subject: RE: you're in a maze of twisty passages, all alike
From: "Kern, Thomas" <Thomas.Kern () hq ! doe ! gov>
Date: 2003-09-25 17:50:41
Message-ID: 136DF57821740-01 () Department_of_Energy_E-Mail_Security_Server
[Download RAW message or body]
What I have done to get around the problems of up2date updating up2date in
the middle of doing other updates is to update up2date by itself on one
command and then use up2date to do everything else on a second command. I
don't do it every night, just once a week.
I have been doing this manually, but hope to make it into a cronjob soon. My
problem with automating it is reading the 'script' log of activity. All of
these hash mark activity indicators look fine in real time but make it
difficult to read after the fact. Is there some way to get rid of the
hashmark output without getting rid of all of the activity reporting?
/Thomas Kern
/301-903-2211
-----Original Message-----
From: Denis Hennessy [mailto:dhennessy@network365.com]
Sent: Thursday, September 25, 2003 11:46
To: taroon-beta-list@redhat.com
Subject: you're in a maze of twisty passages, all alike
I'm so frustrated with trying to get my test machine up to date that I'm
about to give up and wait for the next CD build. I'm wondering if I'm
missing an easier route. Here's what's happening:
1. Install from beta2 CDs a few weeks ago. Install every package.
2. Run up2date-nox -u every night.
However, this only worked for a while. Then a variety of up2date problems
stop it working, with the result that I'm now many hundreds of megabytes out
of date. The cycle is now:
Run up2date-nox -u. This will fail either at some dependency check or later
during the download (it seems to loop getting the same package).
'Fix' the problem. Right now I simply rpm -e the problem package.
Try again. This pretty much always fails with the 'abuse of service'
message. The one that says it can't appear with normal use... Retrying has
no effect since every use is blocked with an abuse failure.
All I'm trying to do is keep a machine up to date with the current full list
of packages. Is there a simpler way?
/dh
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2655.35">
<TITLE>RE: you're in a maze of twisty passages, all alike</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>What I have done to get around the problems of up2date updating \
up2date in the middle of doing other updates is to update up2date by itself on one \
command and then use up2date to do everything else on a second command. I don't do it \
every night, just once a week. </FONT></P>
<P><FONT SIZE=2> </FONT>
<BR><FONT SIZE=2>I have been doing this manually, but hope to make it into a cronjob \
soon. My problem with automating it is reading the 'script' log of activity. All of \
these hash mark activity indicators look fine in real time but make it difficult to \
read after the fact. Is there some way to get rid of the hashmark output without \
getting rid of all of the activity reporting?</FONT></P>
<P><FONT SIZE=2>/Thomas Kern</FONT>
<BR><FONT SIZE=2>/301-903-2211 </FONT>
<BR><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Denis Hennessy [<A \
HREF="mailto:dhennessy@network365.com">mailto:dhennessy@network365.com</A>] </FONT> \
<BR><FONT SIZE=2>Sent: Thursday, September 25, 2003 11:46</FONT> <BR><FONT SIZE=2>To: \
taroon-beta-list@redhat.com</FONT> <BR><FONT SIZE=2>Subject: you're in a maze of \
twisty passages, all alike</FONT> </P>
<BR>
<P><FONT SIZE=2>I'm so frustrated with trying to get my test machine up to date that \
I'm about to give up and wait for the next CD build. I'm wondering if I'm missing an \
easier route. Here's what's happening:</FONT></P>
<P><FONT SIZE=2>1. Install from beta2 CDs a few weeks ago. Install every \
package.</FONT> <BR><FONT SIZE=2>2. Run up2date-nox -u every night.</FONT>
</P>
<P><FONT SIZE=2>However, this only worked for a while. Then a variety of up2date \
problems stop it working, with the result that I'm now many hundreds of megabytes out \
of date. The cycle is now:</FONT></P> <BR>
<P><FONT SIZE=2>Run up2date-nox -u. This will fail either at some dependency check or \
later during the download (it seems to loop getting the same package). </FONT></P>
<P><FONT SIZE=2>'Fix' the problem. Right now I simply rpm -e the problem package. \
</FONT> <BR><FONT SIZE=2>Try again. This pretty much always fails with the 'abuse of \
service' message. The one that says it can't appear with normal use... Retrying has \
no effect since every use is blocked with an abuse failure.</FONT></P>
<P><FONT SIZE=2>All I'm trying to do is keep a machine up to date with the current \
full list of packages. Is there a simpler way?</FONT> </P>
<P><FONT SIZE=2>/dh</FONT>
</P>
</BODY>
</HTML>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic