[NTLUG:Discuss] SOLVED! Re: Poison update in OpenSuSE 11.0??

[Stephen Davidson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Carl.

It would not surprise me if the refresh (3) of the boot loader was what
did it.  My other thought was that perhaps /boot had to be located on
the first partition.  I've had /boot on a separate partition on other
systems (including SuSE 9 & 10) w/o a problem, although its always been
the first partition.  This is the first time I've had an issue like this.

However, now that I've got it working, I don't want to go and
experiment, and possibly jinx something else up (the old "if it ain't
broke, don't fix it!).  I'm actually a Java Developer by trade, and the
Linux stuff is more so I don't have to be dealing with MS crashes and
related garbage.  Not really all the up on Linux, I just want it to work
so I can get on with my stuff.

Regards,
Steve


Carl Haddick wrote:
> On Wed, Jan 28, 2009 at 08:18:38PM -0600, Stephen Davidson wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> In case anyone else hits this mess;
>>
>> Solution:
>> 1) Swap partition should NOT be the default /dev/sda1
>> 2) Root partition with /boot SHOULD be /dev/sda1, NOT the default /dev/sda2
>> 3) After update, but BEFORE required reboot, start Yast, edit
>> bootloader, and select option "Write BootLoader to Disk".
>>
> 
> I respect reality, and I trust that cured the problems, but it's also a
> bit surprising.  I'm no expert, but I've never heard of restrictions
> regarding what device or partitions are appropriate for swap.  I've
> never had trouble adding swap in regular files, for instance - it seems
> that swap is forgiving.
> 
> I've also often put /boot on a separate mount from /, so that's
> interesting that /boot has to be on root.  Putting /boot on a separate
> partition, as I recall, made putting / on a software RAID device easier
> (lazier for me, I admit).
> 
> Interesting.
> 
> Carl
> 
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFJgha0SphIUSiVzgYRAvLpAKCw8gYe72R8f6m+eMMjRS1D5wgnNwCeI1/I
CSJLJCrEQnJ0HGFlYZeK+Ac=
=DEtn
-----END PGP SIGNATURE-----