[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: some news



On Thu, Jul 12, 2001 at 11:36:49AM +0200, Stefan Gybas wrote:
> Date: Thu, 12 Jul 2001 11:36:49 +0200
> From: Stefan Gybas <gybas@trustsec.de>
> To: debian-s390@lists.debian.org
> Subject: Re: some news
> 
> On Thu, Jul 12, 2001 at 10:22:00AM +0200, Martin Michlmayr wrote:
> 
> > What about boot-floppies support?  Richard?
> 
> We don't need boot-floppies like on i386. What we need is an installer
> that configures the system, much like base-config, but with many additions
> like network configuration (iucv, ctc, lcs or qeth). The first installation
> steps have to be done outside of Linux, e.g. on VM or in an LPAR - we "just"
> need documentation for this. I think the new debian-installer is much better
> suited for S/390 than the old boot-floppies so maybe we should try to make
> it work on S/390 instead of spending a lot of time on boot-floppies.
> 
> We have disussed some details at LinuxTag 2001 but we are not sure if we can
> do all this until woody is released. I'll talk to the release manager if
> we should try to release woody or not.

The pages I used for the talk at LinuxTag 2001 can be found at
http://pax.gt.owl.de/~higson/LinuxTag2001/Deb390-talk.html

I'm planning on putting up a 400CYL hercules-bootable DASD and it's
tarfile some time next week. (A snapshot of the system I demonstrated 
at LinuxTag) This will include enough documentation to enable a 
debian-developer to IPL Debian/390 and `apt-get update` on LPAR, VM 
or hercules. 

I really want to build and verify a 2.4.5 kernel based on the patches which 
(finally) found their way to the developer-works site beforehand though.
At the moment I'm at 2.2.19, because of problems I had been having
with the CTC on the 2.4.x series. 

I will describe how to get and install the OCO modules, (2.2.19 and 2.4.5)
but not provide them, because I haven't scripted the "install-ritual" yet.

You can either just IPL the DASD on hercules, or ...
 use an existing L390, 
 add a disk, dasdfmt, mke2fs, mount as /mnt, 
 cd /mnt && tar xvf tarfile.tar
 cd /mnt/boot && make it bootable (I need to learn zilo)

 To do it the Marist-1 way, I'd need to brutally strip down the size of the
 initrd (it's too big at the moment). I'm inclined to say that this particular
 "install-path" isn't available right now...

 Ideally, we should be able to offer several installation methods, including
 boot from `debian.ins` on a CDROM at the HMC, but we're not there yet.

Richard
-- 
Unix:        Your gun, Your bullet, Your foot, Your choice.
M$-CE/ME/NT: Same as Unix, BUT: No choice, and We Aim Higher.
Have a nice day ;-) Richard Higson mailto:richard.higson@gt.owl.de



Reply to: