Text 6196, 86 rader
Skriven 2006-06-02 16:32:34 av Maurice Kinal (1:140/13.1)
   Kommentar till text 6193 av Paul Rogers (1:105/360.0)
Ärende: You gotta smile
=======================
Hey Paul!

Jun 02 09:10 06, Paul Rogers wrote to Maurice Kinal:

 PR> Grub has enough smarts it can find things by file name and
 PR> doesn't need to update the MBR for every little change.

That is definetly an attractive option.  Too bad it doesn't work here ... yet. 
So far this hasn't been a really big issue with me but the bootability has been
so lilo still wins in that regard.

 PR> Trust
 PR> me, lilo won't boot either if something hoses cyl 0.

What hosed it?  So far other the grub everything has worked out here and that
has yet to happen.  :::knock on wood:::

 PR> The good thing that came from all this is: apparently sfdisk can
 PR> copy one's partition table to a file and restore it from that.
 PR> I used to have programs for that on DOS.

Same here but seeing that DOS died over a decade ago that doesn't make a
difference anymore.  DOS is too crappy as an OS so no matter how good any
application was it relied on a flawed foundation and thus came tumbling down
hard and has never been able to recover from the shock.  Oh well.  I learned to
get along without all that and the rewards far outweighed what I lost.  DOS is
irrelevant.

 PR> So maybe it was a HW glitch.

Possibly.  Here it was and is grub that causes bootability problems so other
then testing it every now and then I stick to lilo.  For me the proof has been
in the pudding.  However I've never seen grub trash the partition table it just
won't boot my scheme(s) ... so far.

 PR> Now I won't trust this drive so
 PR> much and backup unfinished work.

Yeah.  In the case of kde I didn't bother.  What for?  Bloat is bloat and
obviously nothing more.  Not worth the bytes methinks.  Same with qt as I never
personally use it so again it is just occupying valuable space.  Also basic
system functionality doesn't require it so it just gets in the way of progress.
 Right?

 PR> I wasn't sure where I'd done my work on cloning POD, but
 PR> fortunately it was on the other system.  Last night I copied
 PR> that to the server and began creating the images.

Good plan.

 PR> 350+MB for
 PR> the backup files and scripts that would clone a running system,

The last one I did up was under 100M but with source it would have been around
200M.  I'll have to check later.  Also got distracted with crosscompiling and
still need to check whether that was a worthwhile pursuit.  Maybe later today. 
I already have a number of backups of that and I think I covered all the bases
as far as what is potentially possible boot-wise.  I think I am ready.

 PR> 320+MB for all the sources to make it a "development" system.

That sounds about right.  Depends on what you consider a "development" system. 
If I get really brutal I can pull a fully capable c system in under 100M but
really have to jump through some hoops to get there.  It is doable but I doubt
too many would agree that it is all that is *really* needed.  It is for me
though.

 PR> I'm going to make big tarballs of each so little things like
 PR> permissions don't get lost if a Windows box is used to copy the
 PR> CD images, so I may be able to squeeze them onto one full CD.
 PR> Still got a few wrinkles in the cloner script.

Understood.  One step at a time eh?

 PR> Started, yes.  But he's got 30-35 years to go.  I wish when I
 PR> started working I'd appreciated what I know now about
 PR> exponential growth (starting early) vs linear growth (saving
 PR> more).

Yeah.  Hindsight is always 20-20.

Life is good,
Maurice

--- Msged/LNX 6.2.0
 * Origin: The Pointy Stick Society XIX - Simplify man! (1:140/13.1)