I don't think 10 is enough. Wash has a buildworld problem on current
and, on his listing, you would only make it about half way
through the
error 1 messages and may miss the one that means something.
I log for a different reason. If you had one die and I
didn't, I want to
be able to
Well, it worked! After a fashion...
This morning I swapped my small primary HDD and larger secondary HDD,
then created the new slices/mount points, and re-installed:
Primary Master 8.something G:
/ 500M
Swap256M
/var500M
/tmp500M
/usrremainder over 6G
Secondary Slave 2.1G:
bw w -j5
893.563u 311.353s 30:31.44 65.7%1302+1591k 53927+138930io
2331pf+0w
The wall clock time is really how efficient your process is. The fact
that your user time or sys time is faster doesn't mean much
if the wall
clock time is 1/3 longer.
Wall clock? Would that be
On Sunday 31 August 2003 04:05 pm, Charles Howse wrote:
bw w -j5
893.563u 311.353s 30:31.44 65.7%1302+1591k 53927+138930io
2331pf+0w
The wall clock time is really how efficient your process is. The
fact that your user time or sys time is faster doesn't mean much if
the wall
Well, here are my current versions of the update scripts.
I hope they are complicated enough for everyone. grin
Contrary to Kent's suggestion, I'm only logging the last 10 lines of the
important commands. I defer to his experience and knowledge, but I
can't see the value in logging 7500 lines of
On Monday 01 September 2003 11:13 am, Charles Howse wrote:
Well, here are my current versions of the update scripts.
I hope they are complicated enough for everyone. grin
Contrary to Kent's suggestion, I'm only logging the last 10 lines of
the important commands. I defer to his experience
Most of the time, you only need to see the last 4 or 5. I
think that I
only look at one of my builds to see the chmod 444 freebsd.cf and
fire up the next script.
OK, I understand. I think I will go ahead and change tail to tail -n
50. That should provide plenty of feedback, eh?
BTW,
On Monday 01 September 2003 01:11 pm, Charles Howse wrote:
BTW, If you add both of your kernels to /etc/make.conf, you
would only
need one buildkernel. The first one is the one that is installed. I
have it commented now but I used to use
#KERNCONF=RUBY GENERIC
to build both and
I'll be glad to post the scripts for review if anyone's interested.
I'll take a look and test them for you also.
OK, any input or corrections welcome.
I definitly would be interested in more error checking and
reporting, and I'm thinking about using \time to append the
time it takes the
On Sunday 31 August 2003 01:25 pm, Charles Howse wrote:
I'll be glad to post the scripts for review if anyone's
interested.
I'll take a look and test them for you also.
OK, any input or corrections welcome.
I definitly would be interested in more error checking and
reporting, and I'm
I'll be glad to post the scripts for review if anyone's
interested.
I'll take a look and test them for you also.
OK, any input or corrections welcome.
I definitly would be interested in more error checking and
reporting, and I'm thinking about using \time to append the
time
On Sunday 31 August 2003 02:19 pm, Charles Howse wrote:
I'll be glad to post the scripts for review if anyone's
interested.
I'll take a look and test them for you also.
OK, any input or corrections welcome.
I definitly would be interested in more error checking and
When I started timing my buildworlds, I figured out that you need
everything but the right hand stuff in the following
AMD Athlon 2000+ XP
877.636u 233.835s 23:02.33 80.4%1350+1662k 46008+7469io
2359pf+0w
bw w -j2
891.151u 303.327s 35:02.77 56.8%1305+1600k 52256+138679io
13 matches
Mail list logo
