Re: Slink release - what's left?
On Feb 16, Michael Schmitz wrote: > Adam Di Carlo wrote: > > Even after we release, officially, I think it's important to keep > > working on the boot floppies, on the documentation, and on the CD. > > Adam, just a general comment from my side (I realize that you are > not responsible for this, but you asked): Personally, I'm screaming > mad that I find new updates to base packages almost every day on > master even though we're in a pretty prolonged freeze now. Meaning I > can't just rebuild part of the boot-floppies but have to go through > the full cycle again which takes around 4-5 hours each time on the > machine I use. It still requires manually adding the Mac magic, and > general babysitting the build process, can only be done after office > hours etc. I think Adam was speaking in general terms (i.e. so we're ready for making potato stuff without suddenly running around like headless chickens a month before release). As far as boot-floppies for m68k (and other platforms, for that matter) goes, I don't see any need to keep them in daily sync with the installed packages on master. IMHO as long as the base system is functioning, the user's first dselect run should take care of anything that has been superseded. People installing from frozen can deal with it until it becomes Really Frozen (tm) at the end of the week; then we can build new disk images from the archives and make sure they work with a week to spare until we're Really Really Frozen And We *Really* Mean It This Time (tm). Chris -- = |Chris Lawrence| The Linux/m68k FAQ | | <[EMAIL PROTECTED]> | http://www.linux-m68k.org/faq/faq.html | | || | Amiga A4000/060 with | Visit the Lurker's Guide to Babylon 5: | | Linux/m68k 2.1.127 | <*> http://www.midwinter.com/lurk/ <*> | =
Re: Slink release - what's left?
Adam Di Carlo wrote: > > The latest boot-floppies 2.1.6 for m68k just arrived in Incoming; > > the only thing I'd like to change (undiscovered blatant bugs aside) > > is upgrading the VME and Mac kernels to 2.0.36 (Nick is doing the > > VME kernel packages, and I'll try to do the Mac part). After that, > > I'd consider switching to boot-floppies 2.1.7 (if there's enough > > time until release). > > Even after we release, officially, I think it's important to keep > working on the boot floppies, on the documentation, and on the CD. Adam, just a general comment from my side (I realize that you are not responsible for this, but you asked): Personally, I'm screaming mad that I find new updates to base packages almost every day on master even though we're in a pretty prolonged freeze now. Meaning I can't just rebuild part of the boot-floppies but have to go through the full cycle again which takes around 4-5 hours each time on the machine I use. It still requires manually adding the Mac magic, and general babysitting the build process, can only be done after office hours etc. I realize that it's important to keep working on all these things, but working on the m68k boot floppies for over a month now has taken a far bigger chunk out of my day than I can afford to spend in future. Frankly, it won't be me to continue working on this. Michael
Re: Slink release - what's left?
On Fri, 12 Feb 1999 22:14:24 -0800, Michael Schmitz <[EMAIL PROTECTED]> said: > The latest boot-floppies 2.1.6 for m68k just arrived in Incoming; > the only thing I'd like to change (undiscovered blatant bugs aside) > is upgrading the VME and Mac kernels to 2.0.36 (Nick is doing the > VME kernel packages, and I'll try to do the Mac part). After that, > I'd consider switching to boot-floppies 2.1.7 (if there's enough > time until release). Even after we release, officially, I think it's important to keep working on the boot floppies, on the documentation, and on the CD. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/>
Re: Slink release - what's left?
Steve Dunham wrote: > > Where are we up to on non-i386 boot/installation? If we're going to > > release together, which I assume is still the plan, then we need to get > > this sorted _soon_. I know someone (Eric? Stephane?) is working on the > > sparc disks and I have some support for them now. I've seen work ongoing > > on the m68k disks, too. I've not seen much for Alpha yet, but that may be > > my fault. > > Eric is working on the disks. I think he is going to patch slink_cd > for the dual boot stuff. (It's pretty simple, I can come up with the > patch after I know how he is naming the disk images. > > I'm not sure if he will have time to finish it until this weekend. He > is adding support to boot-floppies to handle 2.2.x kernels and install > the right kernel depending on the architecture of the Sparc kernel. The latest boot-floppies 2.1.6 for m68k just arrived in Incoming; the only thing I'd like to change (undiscovered blatant bugs aside) is upgrading the VME and Mac kernels to 2.0.36 (Nick is doing the VME kernel packages, and I'll try to do the Mac part). After that, I'd consider switching to boot-floppies 2.1.7 (if there's enough time until release). Michael
Re: Slink release - what's left?
Steve Dunham wrote: > Steve McIntyre <[EMAIL PROTECTED]> writes: > > > Where are we up to on non-i386 boot/installation? If we're going to > > release together, which I assume is still the plan, then we need to get > > this sorted _soon_. I know someone (Eric? Stephane?) is working on the > > sparc disks and I have some support for them now. I've seen work ongoing > > on the m68k disks, too. I've not seen much for Alpha yet, but that may be > > my fault. > > Eric is working on the disks. I think he is going to patch slink_cd > for the dual boot stuff. (It's pretty simple, I can come up with the > patch after I know how he is naming the disk images. > > I'm not sure if he will have time to finish it until this weekend. He > is adding support to boot-floppies to handle 2.2.x kernels and install > the right kernel depending on the architecture of the Sparc kernel. > > The changes to slink_cd to implement the dual booting are trivial. I > believe that Eric is going to take care of this. (I can do it if he > doesn't.) resc1440.bin, drv1440.bin for 2.0.35 sparclinux resc1440-2.2.1.bin, drv1440-2.2.1.bin for alternate 2.2.1 sparclinux resc1440-2.2.1-sun4u.bin, drv1440-2.2.1-sun4u.bin for 2.2.1 ultralinux Could you fix slink_cd yourself then send back the patch to me? I don't have much time to spend on debian this weekend and my priority is to fix bugs related to 2.2 kernel support in bootdisks. BTW, I did a fresh install on a SparcClassic using a tftpboot image built with TILO & your 2.2.1 kernels. No major problems... if using a framebuffer. I just was unable to configure the device drivers (modconf exited immediately; I need to investigate...). The big problem I have is in serial console support. Since linux is using /dev/console now, I cannot detect in a trivial manner whether it is connected to a serial console or not. I need to find a way to discriminate between linux console & serial console... Thanks for your help. -- Eric Delaunay | "La guerre justifie l'existence des militaires. [EMAIL PROTECTED] | En les supprimant." Henri Jeanson (1900-1970)
Re: Slink release - what's left?
Steve McIntyre <[EMAIL PROTECTED]> writes: > Where are we up to on non-i386 boot/installation? If we're going to > release together, which I assume is still the plan, then we need to get > this sorted _soon_. I know someone (Eric? Stephane?) is working on the > sparc disks and I have some support for them now. I've seen work ongoing > on the m68k disks, too. I've not seen much for Alpha yet, but that may be > my fault. Eric is working on the disks. I think he is going to patch slink_cd for the dual boot stuff. (It's pretty simple, I can come up with the patch after I know how he is naming the disk images. I'm not sure if he will have time to finish it until this weekend. He is adding support to boot-floppies to handle 2.2.x kernels and install the right kernel depending on the architecture of the Sparc kernel. The changes to slink_cd to implement the dual booting are trivial. I believe that Eric is going to take care of this. (I can do it if he doesn't.) Once anders X patches are in Branden's hands, the remaining issues will be the install documentation and the gdb package. Steve [EMAIL PROTECTED]
Slink release - what's left?
[ Apologies for the major cross-post - I need input from lots of you... ] Consensus on -testing appears to be that we're about ready to ship the i386 release. I'm adding the final touches to the slink-cd script (v 1.06) right now. Changes from slink-cd v 1.05 up to now are: slink-cd (1.06) unstable; urgency=low * slink_cd changes: * handle non-US links better * Copy Release Notes onto all CDs * Create README.1ST - lists slink_cd version, creation date, disk label (from .disk/info) and gives simple instructions on what to do to run the installation system. * Copy the full set of files for the installation manual to /install. * Add sym-links for the installation manual into /doc. * others: * Created README.1ST.i386 - template for README.1ST above. * Removed test genlinks option from arch. * Added hfs.map for Apple people - not sure what to do with it yet. * Added mkisofsrc to packaging. -- Steve McIntyre <[EMAIL PROTECTED]> Thu, 11 Feb 1999 11:47:53 - Where are we up to on non-i386 boot/installation? If we're going to release together, which I assume is still the plan, then we need to get this sorted _soon_. I know someone (Eric? Stephane?) is working on the sparc disks and I have some support for them now. I've seen work ongoing on the m68k disks, too. I've not seen much for Alpha yet, but that may be my fault. Also, this is the contents of the README.1ST.i386 file I've written, which will hopefully be the first thing people will look at if they need help on getting the installation system up. Comments/changes are welcome. And similar information for other arches would also help a lot. README for Debian 2.1 CD installation. == To boot the installation system from CD, you will need to insert either CD#1 or CD#2 in your CD-ROM drive and reboot. CD#1 contains a normal kernel that should work for most people and contains many drivers. CD#2 is a smaller system based on the "tecra" kernel - this is smaller because it has fewer drivers compiled in to avoid a known problem with large kernels on laptops, especially the Toshiba Tecra series. If your system will not boot from CD, there are other options: Boot a DOS system with CD drivers, then run /install/boot.bat from the first CD. Make boot floppies from the images on the first CD, in the directory /dists/stable/main/disks-i386/current. The program rawrite2.exe in that directory will write the floppy images under DOS. See /install/install.txt for more information. Steve McIntyre <[EMAIL PROTECTED]> 10 Feb 1999 Prepended to this file automatically will be This Debian installation CD was created by slink_cd version $VER on $DATE It is labelled $LABEL Anything else? -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer
