Re: successful installation with 2.3.5 boot-floppies
Before everyone gets too bent out of shape, let me re-assure you all that
the debian-testing group is here to help, and now that we have releases to
work on, I am confident that the team will begin testing.
I've been pretty busy trying to find a job (finding work is always harder
than doing work...) but I should have some time to put toward the testing
of this latest release in the next day or two.
First, I want to thank Adam Di Carlo for his dedication to this job.
Without his efforts it is not clear where we would be with the boot
floppies, and I think we owe him a greatful Thank You.
To the debian-testing list/team I can only say, Go to:
http://people.debian.org/~aph/debian/dists/woody/main/
and download and test as much of the boot floppies as possible.
I'll be testing the CD boot process, as that is not as complex as building
a complete CD. For those who can also toast a CD, here is the process:
1. Create an ARCHIVES subdirectory where the components to toast will be
placed.
2. CD to ARCHIVES and create the subdirectory boot/
3. Copy the rescue image file into the ARCHIVES/boot/ directory.
4. Copy a rescue image file, the Drivers tarball, and the Base tarball
into the ARCHIVES root directory for ease of installation.
5. Make the ISO image file using the command:
mkisofs -r -T -v -o boot/<rescue imagefile name> \
-c boot/boot.catalog \
-o TARGET/binary.iso \
ARCHIVES
6. Toast TARGET/binary.iso onto CD media
7. Test.
I posted a sample report form on the debian-testing list a while back
which got no comment. I can only assume that it was satisfactory ;-)
Please use that form when reporting test results. Feel free to CC your
report to the boot floppies mailing list if there is information of
interest for these folks. I will try to make periodic composite reports to
that group, but the quicker they get the info the sooner it can be acted
upon.
If anyone in the testing group has any further questions, or needs another
copy of the sample testing report, feel free to contact me.
Waiting is,
On 12 Jun 2001, Adam Di Carlo wrote:
> Anthony Towns <aj@azure.humbug.org.au> writes:
>
> > On Fri, Jun 08, 2001 at 12:04:49PM -0600, Matt Kraai wrote:
> > I was under the impression the boot-floppy disks were being based on
> > packages in sid (busybox, debootstrap, etc) and used to install packages
> > from woody (dpkg.deb, bash.deb, libc6.deb, etc). This still seems the
> > sensible thing to do, to me, but stuff I read seems to indicate the
> > opposite is happening?
>
> No, if you're reading that, who-ever wrote it is wrong.
>
> What we do is build using sid packages, as you say, until base
> freezes, and we let the testers choose which distro (stable, testing,
> unstable) they want to install.
>
> With regards to telling the testers what to do, I feel that's the
> responsibility of the testing coordinator (is Dale Scheetz the
> coordinator?).
>
> If there is no testing coordinator, then that is going to be a problem
> that someone shoudl do something about.
>
>
> > The main goal for boot-floppies at the moment, btw, is much simpler
> > than what you appear to be thinking: what we need right now are some
> > boot-floppies in the archive accompanied by a list of do's, don't's and
> > workarounds that can be used by competent testers to do woody
> > installs.
>
> AFAIK, unless I hear otherwise from testers, we are at that point the
> second that 2.3.5 is moved from incoming into woody (or sid I guess).
>
> > These only need to be available for i386,
>
> They are there for i386 and powerpc at least. BenC said he'd build
> sparc shortly. m68k might have to wait for 2.3.6, they seem to have a
> build problem.
>
> > they're allowed to only work for
> > one method ("You can't use these floppies for CD installs, nor for
> > DHCP"),
>
> Not many such limitations but I don't have any woody CDs yet to test
> with.
>
> > they're allowed to have special instructions that you have to carry out
> > very precisely ("Switch to VC 2, type this confusing sed command... Before
> > rebooting, switch to VC 2, and chmod these directories like so..."),
> > all they have to do is be usable to install a functional woody system.
>
> Yah -- the bad bug still outstanding is the busybox tar problem, which
> is causing a *VERY* insecure system to be produced.
>
> > It'd be nice to start having "released" beta boot-floppies, asap. Even
> > without multiple architecture support, and whatever else.
>
> We've had "released" versions since Sun, 8 Apr 2001 03:59:31 -0400.
> They just weren't working very well.
>
> Anthony, I sense some impatience and/or hostility here. What is it
> we can do to make you more happy?
>
> I'm trying to release the code more quickly -- 6 uploads since early
> april. We are averaging about 10 days between releases.... Do you
> have some expectations beyond taht which are not being met?
>
> I could always use more qualified hackers of course....
>
> Personally I would put a little concern in about the coordination of
> the testing effort. Is that in place? I have no idea, maybe...
>
> --
> .....Adam Di Carlo....adam@onshore.com.....<URL:http://www.onshored.com/>
>
>
> --
> To UNSUBSCRIBE, email to debian-testing-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
>
Dwarf
--
_-_-_-_-_- Author of "Dwarf's Guide to Debian GNU/Linux" _-_-_-_-_-_-
_- _-
_- aka Dale Scheetz Phone: 1 (850) 656-9769 _-
_- Flexible Software 11000 McCrackin Road _-
_- e-mail: dwarf@polaris.net Tallahassee, FL 32308 _-
_- _-
_-_-_-_-_- Released under the GNU Free Documentation License _-_-_-_-
available at: http://www.polaris.net/~dwarf/
Reply to: