Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] 0.9.6.3-rc3 (grimoire 0.7) ISO is up

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: George Sherwood <pilot AT beernabeer.com>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] 0.9.6.3-rc3 (grimoire 0.7) ISO is up
  • Date: Wed, 21 Mar 2007 11:06:48 +0400

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

On Wed, 21 Mar 2007 01:16:45 -0500
Jeremy Blosser <jblosser-smgl AT firinn.org> wrote:

> On Mar 21, George Sherwood [pilot AT beernabeer.com] wrote:
> > Completed update to stable-0.8 with no major problems.
> >
> > 1. Not part of the iso, but to a new user might seem that way.
> > After updating to stable-0.8 on the next reboot the system fails to
> > boot with grub due to the menu.1st having entries that won't work
> > on defaults. The original system is installed with:
> >
> > kernel (hd0,0)/boot/vmlinuz-2.6.19.5 root=/dev/hda1 ro
> >
> > After a sorcery rebuild the new menu.1st looks like:
> >
> > kernel /vmlinuz-2.6.20.3 root=/dev/hda1 ro vga=791
> >
> > Of course the file is not found and the boot fails. On my test
> > system the vga=791 causes a problem also. Of course both these can
> > be fixed during spell configuration, but I am not sure a new user
> > will know what to change all the time. I haven't tried lilo so not
> > sure how that works.
>
> These aren't new AFAIK.

I don't think are new either and I wouldn't say they are gating to
release a new iso either. There are bigger problems with such an old
stable grimoire on the old iso.


>
> > 2. After my initial reboot I installed openssh so I could scp
> > my /var/spool/sorcery directory over from another machine. Too slow
> > here to download it all again. That worked fine, but after the
> > rebuild, I got an error about portmap not configured and that
> > networking was not started and sshd wouldn't start again either.
> > Casting portmap solved that problem.
>
> Sounds like the same old BS about remote_fs provider getting mangled
> somewhere.
>

Guess I don't know what is the old BS about this.

George
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFGANmIkVJnfkgKg60RAtv1AJ9/cT1SB3i+tiNW+On6xKXK7AkfjQCggZ9D
57laZLRK4CFIY6dxKOOpNpo=
=GQE3
-----END PGP SIGNATURE-----



Archive powered by MHonArc 2.6.24.

Top of Page