[openbeos] Re: Second patch release bug & Michael Phipps status
- From: Colin Rogers <crogers@xxxxxxxxxxxx>
- To: "'openbeos@xxxxxxxxxxxxx'" <openbeos@xxxxxxxxxxxxx>
- Date: Fri, 15 Mar 2002 17:21:30 -0000
Andrew,
What we need is a testing "director". Someone who knows the config of all
the testers machines, and can make sure that releases and patches have been
tested on enough different systems for him to give an okay to a release.
I've made this point before and it managed to inspire ZERO replies.
Considering that the incredibly important(!) window resizing issue managed
to inspire hundreds of replies - I can easily say there is something wrong
here!
Col.
-----Original Message-----
From: Andrew Gildehaus [mailto:agildehaus@xxxxxxxxxxxxx]
Sent: 15 March 2002 17:17
To: openbeos@xxxxxxxxxxxxx
Subject: [openbeos] Re: Second patch release bug & Michael Phipps status
Wait, wait ... he can access the net through his wife's computer but
can't logon to SourceForge and remove the patch? Or does his wife's
machine just do email?
This is a serious problem, folks. We currently have no procedure for
making releases and this crap is what results. There's a lesson in
this somewhere.
Andrew
> Ok folks, here's the lowdown...
>
> The second patch release has been posted on the Sourceforge Files
> page.
> It is called 'OpenBeOS-20020315' and you don't want to run it.
>
> Let me repeat: DO NOT RUN THIS INSTALL!!!
>
> The installer has a serious bug: all the system files are moved from
> the standard location (/boot/beos/system) on the boot drive. It makes
> the partition unbootable. The files are all still there -- at /boot/
> home/Desktop/OpenBeOS/Saved Files/system. Unfortunately, /boot/beos/
> system is left empty.
>
> It appears to be a case of moving files instead of copying them.
> Whatever the foulup, you cannot boot the partition after running the
> install and re-starting the machine. Michael Phipps was bitten by
> this
> himself and is thus now without a working BeOS system. He tested the
> installation on his one and only BeOS partition (tisk, tisk) which is
> now unbootable. He was able to send me an email from his wife's
> machine, but he has asked me to let everyone know that he will be
> unavailable thru email for a few days until he has this fixed.
> Unfortunately, as project admin, he's the only guy with the power to
> remove the patch file from the Sourceforge page, so we'll have to
> stare
> at it for a few days.
>
> If you have a second BeOS partition, then it's no big deal to fix the
> problem. Just mount the troublesome drive while in the other
> partition
> and copy all the system files back. For example, the following
> command
> line should do it:
>
> cp -rf "/BOOT/home/Desktop/OpenBeOS/Saved Files/system" /BOOT/beos
>
> only replace 'BOOT' with the real mount name for the volume that the
> install was run on.
>
> If someone downloaded this patch, installed it on their one and only
> BeOS partition (as Michael did), then they've got a definite problem.
> If they have a valid R5 CD that can be booted from, great -- just
> boot
> from this and do the copy command as above. Michael evidently can't
> go
> the CD route because his dual processor machine won't let him (not
> sure
> why). People in this circumstance will have to find a way to boot a
> BeOS partition so they can copy the system files back. One route, if
> need be, would be to download the BeOS Personal Edition for Windows
> (or
> Linux) and use that to boot from. There are probably other, more
> drastic recovery techniques that are too ugly to mention. I'm not
> going
> to worry about this too much yet, tho: I'm not sure that anyone
> (besides Michael) has been bitten by this. Nobody may have even
> noticed
> the new patch download file was there yet anyway.
>
> Anyway, that's the scoop.
This transmission is confidential and intended solely for the person or
organisation to whom it is addressed. It may contain privileged and
confidential information. If you are not the intended recipient, you should
not copy, distribute or take any action in reliance on it. If you have
received this transmission in error, please notify the sender immediately.
Any opinions or advice contained in this e-mail are those of the individual
sender except where they are stated to be the views of RDF Group or EMS plc.
All messages passing through this gateway are virus scanned.
Other related posts:
