Re: APUS Debian Boot-Floppies Images and bugs
On 17-May-01, Alan Buxey wrote: AB> How much fits onto one 880K formatted disk, i cant recall, AB> its been so longis it 856k? I think it depends which filesystem you use, and whether you have many small files verses few big ones. For a disk mostly filled with one large file (like a kernel image), FFS should be more efficient, since it doesn't put headers on every block, IIRC, using all 512 bytes for actual data. FFS has been in ROM since v37, so it should be safe to assume everyone can boot from an FFS disk. Except maybe a (very) few A3000 users. If you get really desperate, there exist crunchers which can store Amiga (68K) executables in a cruched format and decompress them as they load. Don't know if anyone's used these under an at all recent version of AmigaOS, though. Duncan -- ... You sound reasonable...Time to up my medication. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Alan Buxey wrote: > > I already considered all this and am now at 848 K. How much space exactly > > do we have? > > well, if we need the following > > s:startup-sequence - a few bytes... > libs:ppc.library (for powerup - not needed for A1200, but for a3k/a4k > a1200 has this in ROM) > *or* we go with WarpUPwhich ever has the smallest libraries > envarc: a few bytes of required env: variables for WarpUP (if used) > the boot tool (eg one i'm working on.) tens of K > could be compressed (eg with stonecracker) if > needed) > bootstrap + the bootstrap_pup or bootstrap_wup - 100's of k's > > How much fits onto one 880K formatted disk, i cant recall, its been so > longis it 856k? > > I can see the kernel needing to be ~500k nastycould 2.2.10 get > this small? I doubt it. Brainstorming: We could throw out _all_ disk drivers except that for the floppy; everything else would have to be loaded as modules. This brings it down to 660K. OTOH the modules will take lots of space; is there some kind of limit, e.g. from the ramdisk size? We could make one floppy with just the kernel on it and another one which boots, copies everything to RAM: and... you get the idea. -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > We could make one floppy with just the kernel on it and another one which > boots, copies everything to RAM: and... you get the idea. yes, that may have to be the way disk1:bootstrap -k disk2:vmlinux.gztype-stuff alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Thu, 17 May 2001, Alan Buxey wrote:
> > I don't think this is feasible as some people won't have anything connected
> > to their AGA output. Right now all the Amiga framebuffer devices are in.
>
> agreed - a lot of people either dont have a monitor that can 'do' the AGA
> modes (even the 29.xHz VGA thing) , others dont have scan-doublers or TV's
> handy (if they've got a modulator).
Note that `vga' and `vga70' in Linux/amifb are real 31 kHz modes, not the
`approximating' stuff from AmigaOS.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > BTW if we could use bzip2, we'd be all set already: this is a weakness of 'bootstrap', yes? alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > You mean our test ramdisk.image.gz ? I asked eons ago if we should convert it > to ext2, if it's still Minix we should do that now. We could use it as a > rescue or other fancy stuff with a current glibc etc. yep, dropping minix will cleave a small lump off the kernel. > I already considered all this and am now at 848 K. How much space exactly do > we have? well, if we need the following s:startup-sequence - a few bytes... libs:ppc.library (for powerup - not needed for A1200, but for a3k/a4k a1200 has this in ROM) *or* we go with WarpUPwhich ever has the smallest libraries envarc: a few bytes of required env: variables for WarpUP (if used) the boot tool (eg one i'm working on.) tens of K could be compressed (eg with stonecracker) if needed) bootstrap + the bootstrap_pup or bootstrap_wup - 100's of k's How much fits onto one 880K formatted disk, i cant recall, its been so longis it 856k? I can see the kernel needing to be ~500k nastycould 2.2.10 get this small? alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > I don't think this is feasible as some people won't have anything connected > to their AGA output. Right now all the Amiga framebuffer devices are in. agreed - a lot of people either dont have a monitor that can 'do' the AGA modes (even the 29.xHz VGA thing) , others dont have scan-doublers or TV's handy (if they've got a modulator). recovering/installing etc is bad enough..without having to unplug/digaround etc for a display device... of course, if it were my choice I'd say ditch all gfx and we'll go for serial-output - after all, everyone should have a vt100 terminal 8-) alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Thu, 17 May 2001, Michel Dänzer wrote:
> Geert Uytterhoeven wrote:
> > On Thu, 17 May 2001, Michel Dänzer wrote:
> > > I already considered all this and am now at 848 K. How much space exactly
> > > do we have?
> >
> > IIRC you have 837 kB free on an OFS-formatted floppy. Since we all use FFS
> > these days it (at least the kernel) should fit. And don't use DC-FFS since
> > it will waste^H^H^H^H^Hconsume even more diskspace.
>
> :) AFAIR FFS gives the full 880K minus a few?
>
> BTW if we could use bzip2, we'd be all set already:
>
> michdaen@pismo> du -sk vmapus.bz2 ~/src/apus-cvs/2.4
> 776 vmapus.bz2
Has no one added bzip2 support to zlib yet?
However, the increased size of zlib may offset the decreased size of the
kernel.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Geert Uytterhoeven wrote: > > On Thu, 17 May 2001, Michel Dänzer wrote: > > I already considered all this and am now at 848 K. How much space exactly > > do we have? > > IIRC you have 837 kB free on an OFS-formatted floppy. Since we all use FFS > these days it (at least the kernel) should fit. And don't use DC-FFS since > it will waste^H^H^H^H^Hconsume even more diskspace. :) AFAIR FFS gives the full 880K minus a few? BTW if we could use bzip2, we'd be all set already: michdaen@pismo> du -sk vmapus.bz2 ~/src/apus-cvs/2.4 776 vmapus.bz2 -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Thu, 17 May 2001, Michel Dänzer wrote:
> I already considered all this and am now at 848 K. How much space exactly do
> we have?
IIRC you have 837 kB free on an OFS-formatted floppy. Since we all use FFS
these days it (at least the kernel) should fit. And don't use DC-FFS since it
will waste^H^H^H^H^Hconsume even more diskspace.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Sven LUTHER wrote: > But, we definitively need 2 batches of kernels, since i suppose some guys > would want the networking stuff also. They can use the non floppy version > though. Can't they use the modules? I'd really like to have a single .config, otherwise maintenance is a nightmare. >>Is this small enough? I guess I could squeeze out a few more K... >> >>Do we need support for foreign partition maps? > > not really, they could be modules. No they can't. I've removed anything but Amiga, I think those who really need something else should build their own kernels. > Also do you have pm2fb and co in there ? maybe this 880 ko kernels would be only for aga, this way we have only 1 possible video= mode in the amiboot script. Other modes can be choosen later on. I don't think this is feasible as some people won't have anything connected to their AGA output. Right now all the Amiga framebuffer devices are in. -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Alan Buxey wrote: >>>Do we need Minix fs support yet? >>> >>Not for installation. > > the ramdisk image no longer uses MiniFS? if so minifs could be dropped > ages ago. You mean our test ramdisk.image.gz ? I asked eons ago if we should convert it to ext2, if it's still Minix we should do that now. We could use it as a rescue or other fancy stuff with a current glibc etc. > I guess we also dont need OCS gfx support...as PowerPC cards only work on > ECS and AGA systems. > > On this line of thought...sound isnt essential, neither is parallel port?, > joystick.. I already considered all this and am now at 848 K. How much space exactly do we have? -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Thu, 17 May 2001, Sven LUTHER wrote:
> On Wed, May 16, 2001 at 12:09:02PM +0200, Geert Uytterhoeven wrote:
> > The only problem is that people might not have enough memory for both RAM: and
> > kernel/ramdisk.
>
> huh, how much is this ? i guess most apus users have at least 8MB by now, is
> that not enough ? Let's start a query on sourceforge to have an idea ?
>
> Or maybe we could clone the linux/m68k registry pages to say only apus and
> have them on sourceforge ? what do you think geert ?
Robert Ramiega took over maintenance of the Linux/m68k registry about 2 years
ago. However, the registry wasn't updated since Feb 2000.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Wed, May 16, 2001 at 07:01:33PM +0200, Giorgio Terzi wrote: > Hello Sven > > ... > > what program are you using on the floppy disk ? I suppose that if it is the > > same as the one you use normally, it would be dependent on warp-up. But i > > guess warp-up is not in rom, so did you put it on the floppy also ? > > I am trying to use our classic kernel loader " `bootstrap` ". > > > Did you try it with the standard powerup stuff ? Since you are booting from a > > floppy, this should be the standard setting, is it not ? > > I shall test it... > > > Could you provide us with some logs (bootstrap & dmesg) of the crashed launch > > ? Post it to the linux-apus list please. Also the script you use for > > launching could be usefull. > > >> I am trying to understand why... > > OK, i finish my tests and if i can't find solutions i will. > > >> For an 880k floppy the space problem makes impossible to do it. > >> But i wish to be contraddicted... :)) > > > > Well, we could split the kernel in 2 and join it in ram: before launching it. > > Or we could try for a less than 880Ko modular kernel, but i have not big > > hopes on this one. Michel Daenzer is the apus kernel package maintainer for > > debian. > > As rightly written by Geert Uytterhoeven is possible to join in ram the kernel > but > as he also writes there maybe problems with Amigas with a small RAM amount. > > > BTW, > > > > Upto now, you were able to bootstarp from the floppy disk set, > > No... because as written on top this letter i am testing " `bootstrap` " > on floppy. > > and able to > > install and configure the kernel & modules, isn't it. All this with the > > 2.2.10 kernel. > > Yes, also using floppy-disks. > >(btw did you solve the 2.2.19 requirement of install.sh ? did > > you try the little patch i sent to you yesterday or the day before ? > > Right! , another thing i must put in the test's list. > > > floppies useable. You could try the networked (trough ppp) install after > > that, but i guess this should be ok. > > With ppp ? Nice... > But i was not able to find a ppp configuration mask in the > network section of dbootstrap program... > is it a new feature? Just select the configure the network menu item, and it should ask you if youare going to use ppp or eth, if you choose ppp, i think it will ask you for all relevant info, and configure pppd for you (even fire up the connection before downloading base.attar.gz). Not sure this is still so though, but i guess it is. Nothing apus specific here thoguh.? > I haven't found the woody's base tarball, maybe is still early, > or maybe i have not found its right path, > but its path is so in ftp as in CD-ROM i think: > > dists/woody/disks-powerpc/current/ yes, i think, not sure though. Maybe there is not yet such a thing, is there a i386 one already ? BTW, normally you should be able to build it from the archive during the boot floppies build. It was so for potato. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Wed, May 16, 2001 at 12:09:02PM +0200, Geert Uytterhoeven wrote: > On Wed, 16 May 2001, Alan Buxey wrote: > > > Well, we could split the kernel in 2 and join it in ram: before launching it. > > > Or we could try for a less than 880Ko modular kernel, but i have not big hopes > > > on this one. Michel Daenzer is the apus kernel package maintainer for debian. > > > > a small, but brief note: > > > > IS there not a very very big problem with having the kernel in ram: when > > launching? > > > > joining two files up into ram: is no problem (6 lines of code max.) but > > doesnt ram: just get completely trashed when the bootstrap loads up the > > kernel (and thus corrupting the kernel image?) > > No, the bootstrap first allocates memory for the kernel (and the ramdisk), then > loads the image, and only then trashes the rest. > > > i thought this was the case and people have to have the installer and > > kernel on media, rather than in volatile ram: > > The only problem is that people might not have enough memory for both RAM: and > kernel/ramdisk. huh, how much is this ? i guess most apus users have at least 8MB by now, is that not enough ? Let's start a query on sourceforge to have an idea ? Or maybe we could clone the linux/m68k registry pages to say only apus and have them on sourceforge ? what do you think geert ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Wed, May 16, 2001 at 11:04:51AM +0100, Alan Buxey wrote: > hi, > > > Well, we could split the kernel in 2 and join it in ram: before launching it. > > Or we could try for a less than 880Ko modular kernel, but i have not big hopes > > on this one. Michel Daenzer is the apus kernel package maintainer for debian. > > a small, but brief note: > > > IS there not a very very big problem with having the kernel in ram: when > launching? Non, i used to do it before, when there was the interrupt issue with the internal hardrive or the scsi one, don't remember. At that time you had to copy the stuff to ram:, wait for a bit that no more disk interrupts were pending, and then launch the stuff. Unless it changed since then, that is. > joining two files up into ram: is no problem (6 lines of code max.) but > doesnt ram: just get completely trashed when the bootstrap loads up the > kernel (and thus corrupting the kernel image?) Yes, but at that time, bootstrap will already have copied the kernel code to it's rigthfull place, so no problem. > i thought this was the case and people have to have the installer and > kernel on media, rather than in volatile ram: ram: in this case is just another media. > > 3) coordinate with alan for the floppy disk booting thingy. > > working on disk-layout, tools and required libraries now. :))) Friendly, sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > Yep, you can remove OCS/ECS support, but it'll save only a few bytes, I guess. dont A3k PowerUP owners have to have ECS - if they dont have GFX card? (are there any such people?) alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Wed, May 16, 2001 at 09:28:01PM +0200, Geert Uytterhoeven wrote: > On Wed, 16 May 2001, Michel Dänzer wrote: > > Sven LUTHER wrote: > > > > I am trying to understand why... > > > > For an 880k floppy the space problem makes impossible to do it. > > > > But i wish to be contraddicted... :)) > > > > > > Well, we could split the kernel in 2 and join it in ram: before launching > > > it. Or we could try for a less than 880Ko modular kernel, but i have not big > > > hopes on this one. > > > > I am experimenting, and it looks promising. I basically moved everything > > except video and disk drivers to modules and here's what it gives so far: > > > > michdaen@pismo> gzip -cv9 vmlinux > vmapus.gz ~/src/apus-cvs/2.4 > > vmlinux: 60.1% > > michdaen@pismo> ll vmapus.gz~/src/apus-cvs/2.4 > > -rw-r--r--1 michdaen src888321 May 16 19:49 vmapus.gz > > michdaen@pismo> du -k vmapus.gz ~/src/apus-cvs/2.4 > > 868 vmapus.gz > > > > Is this small enough? I guess I could squeeze out a few more K... > > Probably not yet. > > > Do we need support for foreign partition maps? > > Not for installation. > > > Do the fbcon packed pixels modules work? > > Yes, but only for modular drivers. > > I'd say include fbcon-afb (amifb), fbcon-cfb8 (gfx cards) and fbcon-cfb16 > (gfx cards with amiboot -v). > > You don't need fbcon-ilbm since amifb doesn't need it unless you use > video=amifb:ilbm. > > You don't need fbcon-mfb since amifb will fallback to fbcon-afb/fbcon-ilbm for > depth 1 when fbcon-mfb is not available. > > You don't need fbcon-cfb24 and fbcon-cf32 since no one wants to run an install > console in those depths anyway. I don't think you need it for half-supported > gfx cards with amiboot -v, only depth 16. Also do you have pm2fb and co in there ? maybe this 880 ko kernels would be only for aga, this way we have only 1 possible video= mode in the amiboot script. Other modes can be choosen later on. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Wed, May 16, 2001 at 07:58:06PM +0200, Michel Dänzer wrote: > Sven LUTHER wrote: > > > > I am trying to understand why... > > > For an 880k floppy the space problem makes impossible to do it. > > > But i wish to be contraddicted... :)) > > > > Well, we could split the kernel in 2 and join it in ram: before launching > > it. Or we could try for a less than 880Ko modular kernel, but i have not big > > hopes on this one. > > I am experimenting, and it looks promising. I basically moved everything > except video and disk drivers to modules and here's what it gives so far: > > michdaen@pismo> gzip -cv9 vmlinux > vmapus.gz ~/src/apus-cvs/2.4 > vmlinux: 60.1% > michdaen@pismo> ll vmapus.gz~/src/apus-cvs/2.4 > -rw-r--r--1 michdaen src888321 May 16 19:49 vmapus.gz > michdaen@pismo> du -k vmapus.gz ~/src/apus-cvs/2.4 > 868 vmapus.gz mmm, a bit just maybe, will it fit with amiboot and the script ? But, we definitively need 2 batches of kernels, since i suppose some guys would want the networking stuff also. They can use the non floppy version though. > Is this small enough? I guess I could squeeze out a few more K... > > Do we need support for foreign partition maps? not really, they could be modules. > Do the fbcon packed pixels modules work? > > Do we need Minix fs support yet? Not anymore, since now root images are ext2 fs, not minix, but i am not sure, please someone confirm this. > The other side of the story will probably be the space needed for the > modules... That's no problem, the infrastructure is there already for splitten modules.tgz file, they come in 3 floppies for i386. i guess the module reading and joining is size independent, we just would need to add the stuff to cut it in 880 or 720 Ko chunks (but i386 already support 1.44, 1.2 and 2.88 ones, so the stuff is in there already). Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Thu, 17 May 2001, Alan Buxey wrote:
> > > Do we need Minix fs support yet?
> >
> > Not for installation.
>
> the ramdisk image no longer uses MiniFS? if so minifs could be dropped
> ages ago.
Hmm... I don't know. Someone should check this.
> I guess we also dont need OCS gfx support...as PowerPC cards only work on
> ECS and AGA systems.
Yep, you can remove OCS/ECS support, but it'll save only a few bytes, I guess.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > > Do we need Minix fs support yet? > > Not for installation. the ramdisk image no longer uses MiniFS? if so minifs could be dropped ages ago. I guess we also dont need OCS gfx support...as PowerPC cards only work on ECS and AGA systems. On this line of thought...sound isnt essential, neither is parallel port?, joystick.. alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Thu, 17 May 2001, Michel Dänzer wrote:
> Geert Uytterhoeven wrote:
> > You don't need fbcon-cfb24 and fbcon-cf32 since no one wants to run an
> > install console in those depths anyway. I don't think you need it for
> > half-supported gfx cards with amiboot -v, only depth 16.
>
> Will this prevent X from running in those depths?
No, fbcon-* files are used for the console only.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Geert Uytterhoeven wrote: > You don't need fbcon-cfb24 and fbcon-cf32 since no one wants to run an > install console in those depths anyway. I don't think you need it for > half-supported gfx cards with amiboot -v, only depth 16. Will this prevent X from running in those depths? Thanks for your feedback! michdaen@pismo> du -sk src/apus-cvs/2.4/vmapus.gz~ 856 src/apus-cvs/2.4/vmapus.gz More suggestions welcome... -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Wed, 16 May 2001, Michel Dänzer wrote:
> Sven LUTHER wrote:
> > > I am trying to understand why...
> > > For an 880k floppy the space problem makes impossible to do it.
> > > But i wish to be contraddicted... :))
> >
> > Well, we could split the kernel in 2 and join it in ram: before launching
> > it. Or we could try for a less than 880Ko modular kernel, but i have not big
> > hopes on this one.
>
> I am experimenting, and it looks promising. I basically moved everything
> except video and disk drivers to modules and here's what it gives so far:
>
> michdaen@pismo> gzip -cv9 vmlinux > vmapus.gz ~/src/apus-cvs/2.4
> vmlinux: 60.1%
> michdaen@pismo> ll vmapus.gz~/src/apus-cvs/2.4
> -rw-r--r--1 michdaen src888321 May 16 19:49 vmapus.gz
> michdaen@pismo> du -k vmapus.gz ~/src/apus-cvs/2.4
> 868 vmapus.gz
>
> Is this small enough? I guess I could squeeze out a few more K...
Probably not yet.
> Do we need support for foreign partition maps?
Not for installation.
> Do the fbcon packed pixels modules work?
Yes, but only for modular drivers.
I'd say include fbcon-afb (amifb), fbcon-cfb8 (gfx cards) and fbcon-cfb16
(gfx cards with amiboot -v).
You don't need fbcon-ilbm since amifb doesn't need it unless you use
video=amifb:ilbm.
You don't need fbcon-mfb since amifb will fallback to fbcon-afb/fbcon-ilbm for
depth 1 when fbcon-mfb is not available.
You don't need fbcon-cfb24 and fbcon-cf32 since no one wants to run an install
console in those depths anyway. I don't think you need it for half-supported
gfx cards with amiboot -v, only depth 16.
> Do we need Minix fs support yet?
Not for installation.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Sven LUTHER wrote: > > I am trying to understand why... > > For an 880k floppy the space problem makes impossible to do it. > > But i wish to be contraddicted... :)) > > Well, we could split the kernel in 2 and join it in ram: before launching > it. Or we could try for a less than 880Ko modular kernel, but i have not big > hopes on this one. I am experimenting, and it looks promising. I basically moved everything except video and disk drivers to modules and here's what it gives so far: michdaen@pismo> gzip -cv9 vmlinux > vmapus.gz ~/src/apus-cvs/2.4 vmlinux: 60.1% michdaen@pismo> ll vmapus.gz~/src/apus-cvs/2.4 -rw-r--r--1 michdaen src888321 May 16 19:49 vmapus.gz michdaen@pismo> du -k vmapus.gz ~/src/apus-cvs/2.4 868 vmapus.gz Is this small enough? I guess I could squeeze out a few more K... Do we need support for foreign partition maps? Do the fbcon packed pixels modules work? Do we need Minix fs support yet? The other side of the story will probably be the space needed for the modules... -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On 16-May-01, Giorgio Terzi wrote: >> Well, we could split the kernel in 2 and join it in ram: before >> launching it. Or we could try for a less than 880Ko modular kernel, but >> i have not big hopes on this one. Michel Daenzer is the apus kernel >> package maintainer for debian. GT> As rightly written by Geert Uytterhoeven is possible to join in GT> ram the kernel but as he also writes there maybe problems with GT> Amigas with a small RAM amount. Is this a relevant problem for APUS? How many users have PowerPC boards and less than the critical amount of RAM (8MB?)? Duncan -- ... "That's interesting," said Dougal, turning around in circles. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Hello Sven ... > what program are you using on the floppy disk ? I suppose that if it is the > same as the one you use normally, it would be dependent on warp-up. But i > guess warp-up is not in rom, so did you put it on the floppy also ? I am trying to use our classic kernel loader " `bootstrap` ". > Did you try it with the standard powerup stuff ? Since you are booting from a > floppy, this should be the standard setting, is it not ? I shall test it... > Could you provide us with some logs (bootstrap & dmesg) of the crashed launch > ? Post it to the linux-apus list please. Also the script you use for > launching could be usefull. >> I am trying to understand why... OK, i finish my tests and if i can't find solutions i will. >> For an 880k floppy the space problem makes impossible to do it. >> But i wish to be contraddicted... :)) > > Well, we could split the kernel in 2 and join it in ram: before launching it. > Or we could try for a less than 880Ko modular kernel, but i have not big > hopes on this one. Michel Daenzer is the apus kernel package maintainer for > debian. As rightly written by Geert Uytterhoeven is possible to join in ram the kernel but as he also writes there maybe problems with Amigas with a small RAM amount. > BTW, > > Upto now, you were able to bootstarp from the floppy disk set, No... because as written on top this letter i am testing " `bootstrap` " on floppy. and able to > install and configure the kernel & modules, isn't it. All this with the > 2.2.10 kernel. Yes, also using floppy-disks. (btw did you solve the 2.2.19 requirement of install.sh ? did > you try the little patch i sent to you yesterday or the day before ? Right! , another thing i must put in the test's list. > floppies useable. You could try the networked (trough ppp) install after > that, but i guess this should be ok. With ppp ? Nice... But i was not able to find a ppp configuration mask in the network section of dbootstrap program... is it a new feature? I haven't found the woody's base tarball, maybe is still early, or maybe i have not found its right path, but its path is so in ftp as in CD-ROM i think: dists/woody/disks-powerpc/current/ is it right ? Thank you again, Regards -- Giorgio Terzi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Wed, 16 May 2001, Alan Buxey wrote:
> > Well, we could split the kernel in 2 and join it in ram: before launching it.
> > Or we could try for a less than 880Ko modular kernel, but i have not big hopes
> > on this one. Michel Daenzer is the apus kernel package maintainer for debian.
>
> a small, but brief note:
>
> IS there not a very very big problem with having the kernel in ram: when
> launching?
>
> joining two files up into ram: is no problem (6 lines of code max.) but
> doesnt ram: just get completely trashed when the bootstrap loads up the
> kernel (and thus corrupting the kernel image?)
No, the bootstrap first allocates memory for the kernel (and the ramdisk), then
loads the image, and only then trashes the rest.
> i thought this was the case and people have to have the installer and
> kernel on media, rather than in volatile ram:
The only problem is that people might not have enough memory for both RAM: and
kernel/ramdisk.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > Well, we could split the kernel in 2 and join it in ram: before launching it. > Or we could try for a less than 880Ko modular kernel, but i have not big hopes > on this one. Michel Daenzer is the apus kernel package maintainer for debian. a small, but brief note: IS there not a very very big problem with having the kernel in ram: when launching? joining two files up into ram: is no problem (6 lines of code max.) but doesnt ram: just get completely trashed when the bootstrap loads up the kernel (and thus corrupting the kernel image?) i thought this was the case and people have to have the installer and kernel on media, rather than in volatile ram: > 3) coordinate with alan for the floppy disk booting thingy. working on disk-layout, tools and required libraries now. alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 06:36:58PM +, Duncan Gibb wrote: > On 15-May-01, Alan Buxey wrote: > > AB> certainly boot-programs (such as the APUS/AF-booter (by Mr Duncan ) > AB> need MUI libraries, but the plain boothack/bootstrap for APUS just > AB> needs powerpc.library, which is in ROM > > Evening, Dr Buxley. That MUI-GUI is aeons out of date now, and really wants > re-implementing much less quick-and-dirtily. Any GUI launcher or frontend > small enough to be of use on a boot floppy would have to be rewritten to use > only ROM-resident stuff. Yes, that would be very nice. BTW, it could be directly integrated with ami/apusboot also. That said, this would be the second step for this, the first step would be a text only thing. Friendl,y Sven Lutherr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 07:18:52PM +0200, Giorgio Terzi wrote: > Hello Christian, hello all, > > ... > > Floppys on m68k are completely useless AFAIK. Since Amigalilo is not > > supported by Debian, who needs floppies anyways when everything comes on CD? > > I have "loaded" from floppies the images i have put on them only > for the sake of test! > > I have not bootstrapped with rescue floppy-disk! > > I also know that is impossible for Amiga to bootstrap with a MS-DOS floppy > disk. > But i have tested that, if someone is mad like me, :)) he can load and > configure > the kernel and the drivers by means of floppy disks , is it so bad ? > Debian dbootstrap program gives also this chance! > > I have tried to bootstrap APUS with a 1,76K Amiga floppy-disk and with > this format the problem is not the space, but in bootstrap program > (i use Warp-Up) that after the loading of the (of course compressed) > kernel crashes. what program are you using on the floppy disk ? I suppose that if it is the same as the one you use normally, it would be dependent on warp-up. But i guess warp-up is not in rom, so did you put it on the floppy also ? Did you try it with the standard powerup stuff ? Since you are booting from a floppy, this should be the standard setting, is it not ? Could you provide us with some logs (bootstrap & dmesg) of the crashed launch ? Post it to the linux-apus list please. Also the script you use for launching could be usefull. > I am trying to understand why... > For an 880k floppy the space problem makes impossible to do it. > But i wish to be contraddicted... :)) Well, we could split the kernel in 2 and join it in ram: before launching it. Or we could try for a less than 880Ko modular kernel, but i have not big hopes on this one. Michel Daenzer is the apus kernel package maintainer for debian. Both solution may be used, if there is time to try it out and such. > For Sven Luther: > I was very busy in the last days, and i think i have lost some steps.:)) Ok, i understand you. BTW, Upto now, you were able to bootstarp from the floppy disk set, and able to install and configure the kernel & modules, isn't it. All this with the 2.2.10 kernel. (btw did you solve the 2.2.19 requirement of install.sh ? did you try the little patch i sent to you yesterday or the day before ? > Please may you list me what do you need for the next tests ? > Thank you. Ok, now the next step would be : 1) download the base tarball of woody (if there is such a thing) and try the installation of it. If this works, then i would call the basic apus boot floppies useable. You could try the networked (trough ppp) install after that, but i guess this should be ok. 2) you could try it with an 2.4.x kernel, to see if it works also, and to see if much changes where needed for it, what do you think ? 3) coordinate with alan for the floppy disk booting thingy. That's all i see for now. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On 15-May-01, Alan Buxey wrote: AB> certainly boot-programs (such as the APUS/AF-booter (by Mr Duncan ) AB> need MUI libraries, but the plain boothack/bootstrap for APUS just AB> needs powerpc.library, which is in ROM Evening, Dr Buxley. That MUI-GUI is aeons out of date now, and really wants re-implementing much less quick-and-dirtily. Any GUI launcher or frontend small enough to be of use on a boot floppy would have to be rewritten to use only ROM-resident stuff. Duncan -- ... I have plenty of talent and vision. I just don't give a damn. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Hello Christian, hello all, ... > Floppys on m68k are completely useless AFAIK. Since Amigalilo is not > supported by Debian, who needs floppies anyways when everything comes on CD? I have "loaded" from floppies the images i have put on them only for the sake of test! I have not bootstrapped with rescue floppy-disk! I also know that is impossible for Amiga to bootstrap with a MS-DOS floppy disk. But i have tested that, if someone is mad like me, :)) he can load and configure the kernel and the drivers by means of floppy disks , is it so bad ? Debian dbootstrap program gives also this chance! I have tried to bootstrap APUS with a 1,76K Amiga floppy-disk and with this format the problem is not the space, but in bootstrap program (i use Warp-Up) that after the loading of the (of course compressed) kernel crashes. I am trying to understand why... For an 880k floppy the space problem makes impossible to do it. But i wish to be contraddicted... :)) For Sven Luther: I was very busy in the last days, and i think i have lost some steps.:)) Please may you list me what do you need for the next tests ? Thank you. Regards -- Giorgio Terzi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 04:19:14PM +0100, Alan Buxey wrote: > hi, > > > mmm, they are not really difficult to do, i remember writting my own split > > programs, because non where availabel back then. > > /me thinks there are several free clones of join/split on aminet It's trivial to write, just some read/writes and an appropriate for loop. > > (altough not test them). The only real problem is the choice program, but if > > you only want the launch the debian install stuff, then even that is not > > needed. > > a small C program could output the bootstrap line required to ram: and > then the script would execute that command What is the problem with executing it directly from the C program, trough some instance of the exec family of function (see the exec (3) man page ?) It would be easier than what you propose. ideally this program would : 1) ask for the user choice (install debian with or without kernel options, use an existing partition (with or without kernel options), boot into amigaos (well CLI)). 2) test if we are using a 1.76Mo floppy disk (maybe reading the size of the linux kernel would do it, if it >880Ko, then we are in a 1.76 Mo floppy disk). 3) if the above test fails, ask if we want to use a 2 floppy kernel setup, if yes, load the 2 halves of the kernel, join them and copy them to ram:. modify the -k option accordingly. 4) invoke ami/apus boot with the options provided by above. That's it, we have working 880Ko and 1.76Mo amiga (m68k and apus) rescue disks. Someone could even contribute some nice graphical stuff if they feel like it, either a GUI stuff, or some hardware banging menu with a big debian scrolling in the background. mmm, now that i think of it, i do have some such asm code lying around somewhere. Too sad i don't have a working amiga right now, nor time for it. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > mmm, they are not really difficult to do, i remember writting my own split > programs, because non where availabel back then. /me thinks there are several free clones of join/split on aminet > (altough not test them). The only real problem is the choice program, but if > you only want the launch the debian install stuff, then even that is not > needed. a small C program could output the bootstrap line required to ram: and then the script would execute that command alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > But the bootblock is code. Of course we can reverse engineer and clean room > reimplement one (IIRC it justs opens dos.library and returns 1 or 0). over 10,000 coders have made their own bootblocks for Amiga floppies...either commercial games or demo disks. some even got sine-scrolling messages with a chip-tune to fit into that one sector 8-) > Yep. But it's quite useless without real commands on the disk :-) theres...50?..commands in AmigaROM and the libraries built-in (all major AmigaOS ones - after all, workbench can boot up with just the 'loadwb' command on a bootable floppy!) > Because it's easier to mess up things with tar/lha than with ADF or DMS? > Alternatively, let them use gunzip and dd :-) :-) oh dear, I can imagine where that'd lead alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi,
> > no, and yes. Under AmigaOS you run 'install df0:' but this doesnt
> > put any files onto the disk as such, it just writes a bootblock
> > (a few hundred bytes) to the floppy. Theres no reason why we couldnt have
> > an AmigaOS bootblock and write it to disk with 'dd'
>
> but you do get access to the CLI if i remember well, isn't it ?
yes - but you only run stuff that is in AmigaROM.
> Not on cyberstorm boards. how big is it anyway ? I don't think we can ship
> that, but then maybe we could, if we ask nicely. Ralph would be the author, no
> that there is no phase5 anymore. Also this don't apply to the m68k case.
I guess we have to ask Ralph for permission for the CS_PPC cards.
> why not a plain gzipped tarball or lha archive ?
because the floppy still must be 'install'ed , whereas an ADF image *is*
the whole floppy and will write-out nicely. of course, if you are going
to do everything under AmigaOS (courtesy of an emergencyboot.{lha/tar.gz}
on the Debian CD) then you can just stick a small AmigaOS script into the
same directory which will format a floppy, install it then depack stuff
onto it
alan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 04:50:29PM +0200, Geert Uytterhoeven wrote: > On Tue, 15 May 2001, Sven LUTHER wrote: > > On Tue, May 15, 2001 at 03:17:52PM +0100, Alan Buxey wrote: > > > > And did you have the same amount of stuff in it ? > > > > > > these are the standard downloadables from APUS@sourceforge > > > > > > they have pretty much the same functionality. I guess > > > there are many features that can be cut out of 2.4.4 > > > (but most stuff, such as khttpd are as modules already) > > > > Ok, do you still volunteer to give it a try ? > > > > mmm, would it be possible to make 880Ko ones ? i don't think so, but then you > > may be able to do it, splitting the kernel in 2 and reconstructiong it again > > in the ramdisk. You would need copy and join though. Are those in the AimgaOS > > rom ? maybe ... > > Copy and join are in C:. :((( thought so. mmm, they are not really difficult to do, i remember writting my own split programs, because non where availabel back then. You could write them in C, a kind of very small amiboot utility ? Or even maybe implement the functionality in ami/apus boot to have separate files on separate floppies. But this isn't really worth it. The 1.76 Mo floppy stuff would be though, as it is not really difficult to do. I am nsure someone with a 1.76Mo floppy could make them in less than 10 minutes. Even i could give make them right now (altough not test them). The only real problem is the choice program, but if you only want the launch the debian install stuff, then even that is not needed. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 04:49:26PM +0200, Geert Uytterhoeven wrote: > On Tue, 15 May 2001, Sven LUTHER wrote: > > On Tue, May 15, 2001 at 03:15:14PM +0100, Alan Buxey wrote: > > > > Don't you need some part of AmigaOS to make a floppy bootable? > > > > > > no, and yes. Under AmigaOS you run 'install df0:' but this doesnt > > > put any files onto the disk as such, it just writes a bootblock > > > (a few hundred bytes) to the floppy. Theres no reason why we couldnt have > > > an AmigaOS bootblock and write it to disk with 'dd' > > But the bootblock is code. Of course we can reverse engineer and clean room > reimplement one (IIRC it justs opens dos.library and returns 1 or 0). > > > but you do get access to the CLI if i remember well, isn't it ? > > Yep. But it's quite useless without real commands on the disk :-) Well, but it could call the ami/apus boot launching script. We could even have a (self written) little ask and choose program, or could that be done with just a script ? > > > theres no issue of copyright with bootable floppies. PD software has been > > > on such things for years. I guess as a last resort we can create a > > > bootable emegency floppy, compact it into ADF format and then it can go > > > onto the CD - and users can make it themselves from under AmigaOS with > > > transADF and the like? > > > > why not a plain gzipped tarball or lha archive ? > > Because it's easier to mess up things with tar/lha than with ADF or DMS? > Alternatively, let them use gunzip and dd :-) anything you feel best. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 09:44:26AM -0500, Christian T. Steigies wrote: > On Tue, May 15, 2001 at 04:23:38PM +0200, Sven LUTHER wrote: > > > > > > not that i can think of. certainly boot-programs (such as the > > > APUS/AF-booter (by Mr Duncan ) need MUI libraries, but the plain > > > boothack/bootstrap for APUS just needs powerpc.library, which is in ROM > I don't use APUS, plain old A2k. AFAIK amiboot needs some AOS libraries, > Geert? Which are in the rom, most of them anyway, isn't it. They will be installed on any amiga hardware we care to use, unless you are speaking about the rare draco boxes. > > If nothing did change since potato, boot floppies are non free anyway. > Um, the lha code was removed long ago. m68k is not the reason for bf to be > non-free. Is it still? BTW, it was in contrib... There were some other thinks there, i think. > > > theres no issue of copyright with bootable floppies. PD software has been > > > on such things for years. I guess as a last resort we can create a > > > bootable emegency floppy, compact it into ADF format and then it can go > > > onto the CD - and users can make it themselves from under AmigaOS with > > > transADF and the like? > You did not get my point... if you need linux to write the linux > boot-floppy, you alread have linux installed, so what? If you need AOS to > write the floppy, you already have AOS installed, so just double click on the > StartInstall Icon. SO WHAT? It does not work from a PC, unless you have a Suppose you want to reformat your harddisk, so that it be full linux (not adviceable but still), suppose you have to buy a new harddisk, because you older one died, and you can only have one connected at a time (for whatever reason). Suppose you want ot have a rescue floppy, in case something goes (very) wrong while you were just testing the boot floppies for example. All the above objections are the same if you were using linux on i386. > special controller, and it will give you no improvement when you do it on an > amiga. Don't tell me you could need a rescue floppy, you can always use Or you may just prepare the floppies on amiga 1 and do the installation on amiga 2, or on the one of a friend (which has strange powerup libraries installed which will make apusboot fail) > StartInstall to get a rescue system up (unless you trash your AOS disk, but > you mount them read-only, so its not going to happen). I do not see any Why not, a badly done fdisk job will do just that ? > benefit from bootable floppies for amigas. I can already hear the users > screaming "your floppy does not work on my system"... but if somebody else > is going to put that into bf, document it and take all the hits from the > users, youre welcome. Sure, but the real question, is if it is easy to do (most of use do someting similar on our harddisk by hand anyway), then why not do it. mmm, what do you feel could be a reason for them not to work for people ? The only reason i see is if they try 1.76Mo floppies in 880Ko drives. > > why not a plain gzipped tarball or lha archive ? > How do you write the bootblock with tar? Or lha? Only ADF, DMS and similar > would work. you just to it with install under amigaos, and then copy the stuff over to your floppy disk. why make things complicated when you can make it easy. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, 15 May 2001, Christian T. Steigies wrote:
> On Tue, May 15, 2001 at 04:23:38PM +0200, Sven LUTHER wrote:
> > > not that i can think of. certainly boot-programs (such as the
> > > APUS/AF-booter (by Mr Duncan ) need MUI libraries, but the plain
> > > boothack/bootstrap for APUS just needs powerpc.library, which is in ROM
> I don't use APUS, plain old A2k. AFAIK amiboot needs some AOS libraries,
Me neither.
> Geert?
Since we switched for ixemul.library to libnix, no non-ROM libraries are needed
anymore, except perhaps SetPatch and 68040.library for '040 boxes (aiii).
> > > almost all supported stuff...the only main exception that rings alarm
> > > bells in my head is the CyverVision3D - doesnt this have to be initialised
> > > to the resolution you want under workbench before laucnhing into APU - or
> > > is this now fixed?
> CV3D works, at least from the m68k kernel images. Ken did not officially
> release the source yet (are you listeing?), but the lastet driver works on
> ZorroII (and probably on Zorro3, since he did it).
Yep, where are the patches???
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, 15 May 2001, Sven LUTHER wrote:
> On Tue, May 15, 2001 at 03:17:52PM +0100, Alan Buxey wrote:
> > > And did you have the same amount of stuff in it ?
> >
> > these are the standard downloadables from APUS@sourceforge
> >
> > they have pretty much the same functionality. I guess
> > there are many features that can be cut out of 2.4.4
> > (but most stuff, such as khttpd are as modules already)
>
> Ok, do you still volunteer to give it a try ?
>
> mmm, would it be possible to make 880Ko ones ? i don't think so, but then you
> may be able to do it, splitting the kernel in 2 and reconstructiong it again
> in the ramdisk. You would need copy and join though. Are those in the AimgaOS
> rom ? maybe ...
Copy and join are in C:.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, 15 May 2001, Sven LUTHER wrote:
> On Tue, May 15, 2001 at 03:15:14PM +0100, Alan Buxey wrote:
> > > Don't you need some part of AmigaOS to make a floppy bootable?
> >
> > no, and yes. Under AmigaOS you run 'install df0:' but this doesnt
> > put any files onto the disk as such, it just writes a bootblock
> > (a few hundred bytes) to the floppy. Theres no reason why we couldnt have
> > an AmigaOS bootblock and write it to disk with 'dd'
But the bootblock is code. Of course we can reverse engineer and clean room
reimplement one (IIRC it justs opens dos.library and returns 1 or 0).
> but you do get access to the CLI if i remember well, isn't it ?
Yep. But it's quite useless without real commands on the disk :-)
> > theres no issue of copyright with bootable floppies. PD software has been
> > on such things for years. I guess as a last resort we can create a
> > bootable emegency floppy, compact it into ADF format and then it can go
> > onto the CD - and users can make it themselves from under AmigaOS with
> > transADF and the like?
>
> why not a plain gzipped tarball or lha archive ?
Because it's easier to mess up things with tar/lha than with ADF or DMS?
Alternatively, let them use gunzip and dd :-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 04:23:38PM +0200, Sven LUTHER wrote: > > > > not that i can think of. certainly boot-programs (such as the > > APUS/AF-booter (by Mr Duncan ) need MUI libraries, but the plain > > boothack/bootstrap for APUS just needs powerpc.library, which is in ROM I don't use APUS, plain old A2k. AFAIK amiboot needs some AOS libraries, Geert? > If nothing did change since potato, boot floppies are non free anyway. Um, the lha code was removed long ago. m68k is not the reason for bf to be non-free. Is it still? BTW, it was in contrib... > > > Can all hardware already be set up by the kernel? > > > > almost all supported stuff...the only main exception that rings alarm > > bells in my head is the CyverVision3D - doesnt this have to be initialised > > to the resolution you want under workbench before laucnhing into APU - or > > is this now fixed? CV3D works, at least from the m68k kernel images. Ken did not officially release the source yet (are you listeing?), but the lastet driver works on ZorroII (and probably on Zorro3, since he did it). > > theres no issue of copyright with bootable floppies. PD software has been > > on such things for years. I guess as a last resort we can create a > > bootable emegency floppy, compact it into ADF format and then it can go > > onto the CD - and users can make it themselves from under AmigaOS with > > transADF and the like? You did not get my point... if you need linux to write the linux boot-floppy, you alread have linux installed, so what? If you need AOS to write the floppy, you already have AOS installed, so just double click on the StartInstall Icon. SO WHAT? It does not work from a PC, unless you have a special controller, and it will give you no improvement when you do it on an amiga. Don't tell me you could need a rescue floppy, you can always use StartInstall to get a rescue system up (unless you trash your AOS disk, but you mount them read-only, so its not going to happen). I do not see any benefit from bootable floppies for amigas. I can already hear the users screaming "your floppy does not work on my system"... but if somebody else is going to put that into bf, document it and take all the hits from the users, youre welcome. > why not a plain gzipped tarball or lha archive ? How do you write the bootblock with tar? Or lha? Only ADF, DMS and similar would work. Christian -- http://people.debian.org/~cts/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 03:17:52PM +0100, Alan Buxey wrote: > hi, > > > And did you have the same amount of stuff in it ? > > these are the standard downloadables from APUS@sourceforge > > they have pretty much the same functionality. I guess > there are many features that can be cut out of 2.4.4 > (but most stuff, such as khttpd are as modules already) Ok, do you still volunteer to give it a try ? mmm, would it be possible to make 880Ko ones ? i don't think so, but then you may be able to do it, splitting the kernel in 2 and reconstructiong it again in the ramdisk. You would need copy and join though. Are those in the AimgaOS rom ? maybe ... But then, i don't think the 880Ko ones are really worth it. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 03:15:14PM +0100, Alan Buxey wrote: > hi, > > > Don't you need some part of AmigaOS to make a floppy bootable? > > no, and yes. Under AmigaOS you run 'install df0:' but this doesnt > put any files onto the disk as such, it just writes a bootblock > (a few hundred bytes) to the floppy. Theres no reason why we couldnt have > an AmigaOS bootblock and write it to disk with 'dd' but you do get access to the CLI if i remember well, isn't it ? > > Doesn't at least amiboot need some libraries to be present on the system you > > are booting from? > > not that i can think of. certainly boot-programs (such as the > APUS/AF-booter (by Mr Duncan ) need MUI libraries, but the plain > boothack/bootstrap for APUS just needs powerpc.library, which is in ROM Not on cyberstorm boards. how big is it anyway ? I don't think we can ship that, but then maybe we could, if we ask nicely. Ralph would be the author, no that there is no phase5 anymore. Also this don't apply to the m68k case. If nothing did change since potato, boot floppies are non free anyway. > > Can all hardware already be set up by the kernel? > > almost all supported stuff...the only main exception that rings alarm > bells in my head is the CyverVision3D - doesnt this have to be initialised > to the resolution you want under workbench before laucnhing into APU - or > is this now fixed? > > > How do you get the image on the floppy, from linux? From AmigaOS? It > > probably has to be done on an amiga to use the 1.76MB drives (or on a PC > > with a catweasel controller, even less probable). > > Linux can write 1.76Mb floppy images: > > brw-rw 1 almb floppy 2, 96 May 25 2000 fd0H1760 > > it can also write 1.92Mb diskettes, but that is flakey on most floppy > hardware. The reasons why PC disk-drives cannot read Amiga floppy disks > is not because they cannot cope with the capacity, its all down to the > format of the layout and timings. If you're running APUS you'll be running > with Amiga hardware anyway. > > > So I guess you need an Amgia, running AmigaOS, to create these floppies, to > > then be able to boot from those floppies. Probably we will not be allowed to > > ship those floppies or even images of them, due to copyright reasons, so > > every user has to create them himself. > > theres no issue of copyright with bootable floppies. PD software has been > on such things for years. I guess as a last resort we can create a > bootable emegency floppy, compact it into ADF format and then it can go > onto the CD - and users can make it themselves from under AmigaOS with > transADF and the like? why not a plain gzipped tarball or lha archive ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 03:05:01PM +0100, Alan Buxey wrote: > hi, > > > What is the size of the 2.4.x kernel compared to the 2.2.10 one ? > > bigger, I recall 2.4.4 being over 3Mb (compared to 2.2.10 being just over > 2.1Mb) What about gzipped kernels ? And did you have the same amount of stuff in it ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > And did you have the same amount of stuff in it ? these are the standard downloadables from APUS@sourceforge they have pretty much the same functionality. I guess there are many features that can be cut out of 2.4.4 (but most stuff, such as khttpd are as modules already) alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > Don't you need some part of AmigaOS to make a floppy bootable? no, and yes. Under AmigaOS you run 'install df0:' but this doesnt put any files onto the disk as such, it just writes a bootblock (a few hundred bytes) to the floppy. Theres no reason why we couldnt have an AmigaOS bootblock and write it to disk with 'dd' > Doesn't at least amiboot need some libraries to be present on the system you > are booting from? not that i can think of. certainly boot-programs (such as the APUS/AF-booter (by Mr Duncan ) need MUI libraries, but the plain boothack/bootstrap for APUS just needs powerpc.library, which is in ROM > Can all hardware already be set up by the kernel? almost all supported stuff...the only main exception that rings alarm bells in my head is the CyverVision3D - doesnt this have to be initialised to the resolution you want under workbench before laucnhing into APU - or is this now fixed? > How do you get the image on the floppy, from linux? From AmigaOS? It > probably has to be done on an amiga to use the 1.76MB drives (or on a PC > with a catweasel controller, even less probable). Linux can write 1.76Mb floppy images: brw-rw 1 almb floppy 2, 96 May 25 2000 fd0H1760 it can also write 1.92Mb diskettes, but that is flakey on most floppy hardware. The reasons why PC disk-drives cannot read Amiga floppy disks is not because they cannot cope with the capacity, its all down to the format of the layout and timings. If you're running APUS you'll be running with Amiga hardware anyway. > So I guess you need an Amgia, running AmigaOS, to create these floppies, to > then be able to boot from those floppies. Probably we will not be allowed to > ship those floppies or even images of them, due to copyright reasons, so > every user has to create them himself. theres no issue of copyright with bootable floppies. PD software has been on such things for years. I guess as a last resort we can create a bootable emegency floppy, compact it into ADF format and then it can go onto the CD - and users can make it themselves from under AmigaOS with transADF and the like? alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > What is the size of the 2.4.x kernel compared to the 2.2.10 one ? bigger, I recall 2.4.4 being over 3Mb (compared to 2.2.10 being just over 2.1Mb) alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 08:20:48AM -0500, Christian T. Steigies wrote: > On Tue, May 15, 2001 at 02:45:28PM +0200, Sven LUTHER wrote: > > On Tue, May 15, 2001 at 11:57:11AM +0100, Alan Buxey wrote: > > > hi, > > > > > > > Can you boot from an external 1.76MB floppy ? > > > > > > yes. its treated just as the old classic external floppies that I'm sure > > > most people had with their A500's > > > > > > > but 1.76MB floppies would be easily supported, almost nothing needs to be > > > > changed, apart from the rescue disk creation. Does someone with a 1.76MB > > > > floppy volunteer for that ? > > > > > > if you give me the instructions and details I can test this. > > > > Well, just format a floppy disk, but the bootstrap program on it, a linux > > kernel (in compressed form) and a little script that will boot it, from a > > ramdisk. > Don't you need some part of AmigaOS to make a floppy bootable? no, you just have to make it bootable with install, i think. > Doesn't at least amiboot need some libraries to be present on the system you > are booting from? mmm, yes, i think at least the powerup libraries, which reside on the powerup boards, at least in their blizzard edition. There may be some others, but i am sure you can fit them in the 1.76-1.44 = 320Ko you have left after you put the kernel there. (and geert spoke of less than 500ko m68k modular kernels). And remember those days when you didn't had harddisks on your amiga. > Can all hardware already be set up by the kernel? Sure, i guess at least most of it could. Maybe for some of the graphic cards this is not the case, but people in this case just could boot from the harddisk anyway. > How do you get the image on the floppy, from linux? From AmigaOS? It > probably has to be done on an amiga to use the 1.76MB drives (or on a PC > with a catweasel controller, even less probable). Well, you just make a 1.76MB tarball, that can be unzipped/copied on the floppy disk by the user. Also i guess with an amiga hardware, the floppy is accesible under linux, so you could dd it to it. At least this is the case with my 880Ko floppy. > So I guess you need an Amgia, running AmigaOS, to create these floppies, to > then be able to boot from those floppies. Probably we will not be allowed to No, you just need an amiga running amigaos or linux. > ship those floppies or even images of them, due to copyright reasons, so > every user has to create them himself. No, don't think so, not sure though. Amiboot/apusboot is GPled (i think, but anyway, we already ship it in the boot-floppies package) as is the kernel. The little script would be just anything you want it to be, i guess you could GPL it also. Sure you would not have GUI or workbench or ... but it would work. > Due you really think this is worth it, considering how unreliable floppies > are? Please tell me when I am too pessimistic ;-) It is easy to do (i think, will have to test though). I don't think a lot of people will use it, but it could come in handy in some cases, i guess. What do you do actually, you just copy all needed stuff to your harddisk and work from there. In the case of not having a amiga partition, you just boot into a workbench boot floppy, copy the kernel and amiboot to ramdisk, and launch it from there. > No, I don't have a HD floppy drive, only with the catweasel controller, and > no driver for it exists yet. Yes, i have it also not. It is worth a try though, don't you think, especially if people with it volunteer to do it. > And no, I will not put a new harddisk into my old Amiga, even if I had to set > up a system from scratch, I could very well use a bootable MOD, but maybe > more users have HD drives than MOs... ;))) Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 02:45:28PM +0200, Sven LUTHER wrote: > On Tue, May 15, 2001 at 11:57:11AM +0100, Alan Buxey wrote: > > hi, > > > > > Can you boot from an external 1.76MB floppy ? > > > > yes. its treated just as the old classic external floppies that I'm sure > > most people had with their A500's > > > > > but 1.76MB floppies would be easily supported, almost nothing needs to be > > > changed, apart from the rescue disk creation. Does someone with a 1.76MB > > > floppy volunteer for that ? > > > > if you give me the instructions and details I can test this. > > Well, just format a floppy disk, but the bootstrap program on it, a linux > kernel (in compressed form) and a little script that will boot it, from a > ramdisk. Don't you need some part of AmigaOS to make a floppy bootable? Doesn't at least amiboot need some libraries to be present on the system you are booting from? Can all hardware already be set up by the kernel? How do you get the image on the floppy, from linux? From AmigaOS? It probably has to be done on an amiga to use the 1.76MB drives (or on a PC with a catweasel controller, even less probable). So I guess you need an Amgia, running AmigaOS, to create these floppies, to then be able to boot from those floppies. Probably we will not be allowed to ship those floppies or even images of them, due to copyright reasons, so every user has to create them himself. Due you really think this is worth it, considering how unreliable floppies are? Please tell me when I am too pessimistic ;-) No, I don't have a HD floppy drive, only with the catweasel controller, and no driver for it exists yet. And no, I will not put a new harddisk into my old Amiga, even if I had to set up a system from scratch, I could very well use a bootable MOD, but maybe more users have HD drives than MOs... Christian -- http://people.debian.org/~cts/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 01:26:52PM +0200, Michel Dänzer wrote: > > > Geert Uytterhoeven wrote: > > > On Tue, 15 May 2001, Sven LUTHER wrote: > > > >>On Tue, May 15, 2001 at 11:11:38AM +0200, Geert Uytterhoeven wrote: > >> > >>>On Tue, 15 May 2001, Sven LUTHER wrote: > >>>You cannot boot from 1.4 MB floppies, only from 880 kB or 1760 kB floppies. > >>> > >>Well, ok no problem, just make a tarball that can be copied to 1760Kb > >>floppies, it is even better, since we have more place for stuff. > >> > >>I don't think we can ever fit a kernel and amiboot in 880kb, could we ? > >> > > > > My 2.4.4 zImage is only 458036 bytes long. I have lots of modules, but it could > > work. I remember I once did. > > > Can we use modules for the install on APUS? Our strategy has been to include > all possible hardware into the kernel. Why not, the only problem is that you need the things from which you boot included in the kernel. That would mean most ide/scsi driver stuff, as well as ppp and eth networking and filesystems. Apart from that, most stuff is probably not needed. Also, there is no reason the kernel of the boot floppies will be the final installed one. I heard speach about 2.4.x being big (probably on i386) that is too big to fit into a floppy, so they planed to have 2.2.latest on the boot floppies, and provide the user a choice of other kernels during the real install. Now, i don't know if this would be 'hand' installed kernels, or done automaticcaly. What is the size of the 2.4.x kernel compared to the 2.2.10 one ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 12:59:21PM +0200, Geert Uytterhoeven wrote: > On Tue, 15 May 2001, Sven LUTHER wrote: > > On Tue, May 15, 2001 at 11:11:38AM +0200, Geert Uytterhoeven wrote: > > > On Tue, 15 May 2001, Sven LUTHER wrote: > > > You cannot boot from 1.4 MB floppies, only from 880 kB or 1760 kB floppies. > > > > Well, ok no problem, just make a tarball that can be copied to 1760Kb > > floppies, it is even better, since we have more place for stuff. > > > > I don't think we can ever fit a kernel and amiboot in 880kb, could we ? > > My 2.4.4 zImage is only 458036 bytes long. I have lots of modules, but it could > work. I remember I once did. mmm, yes, this could be a nice option, Michel, would you provide 2 different kerel packages, or maybe a multiple binary version ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 01:36:19PM +0200, Geert Uytterhoeven wrote: > On Tue, 15 May 2001, Alan Buxey wrote: > > > Also, is there a way (under linux) to detect if the floppy is of the 1.76 or > > > the 880 variety ? > > > > dont know - I always believe that floppies are too dumb..you only know > > what you can do when things you try fail ;-) > > grep FD_HD_3 linux/drivers/block/amiflop.c. > > But I don't think you can easily find out from userspace. Maybe we could provide this kind of info trough the proc filesystem ? (As usual, i think your answer would be : sure you can, any volunteer ?, isn't it ?) Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 11:57:11AM +0100, Alan Buxey wrote: > hi, > > > Can you boot from an external 1.76MB floppy ? > > yes. its treated just as the old classic external floppies that I'm sure > most people had with their A500's > > > but 1.76MB floppies would be easily supported, almost nothing needs to be > > changed, apart from the rescue disk creation. Does someone with a 1.76MB > > floppy volunteer for that ? > > if you give me the instructions and details I can test this. Well, just format a floppy disk, but the bootstrap program on it, a linux kernel (in compressed form) and a little script that will boot it, from a ramdisk. Maybe the script could ask a few question before booting or something such, don't know, what would be best to ask ? You could the follwoing settings : 1first question : From where to boot ? a) from the floppy provided kernel and root image (root=/dev/mem or whatever) b) from a user provided partition c) into amigados, so the user can play himself. Don't know if the floppy would be able to contain the needed thing to provide a working amiga shell or workbench though. 2nd question : provide additional parameters. a) video option : aga, pm2fb, other, ... b) other needed options (don't know about them, ...) c) anything else ... or maybe only one question, which response would provide all of the above, like having a a') and b') above, but where the user can provide a more complete and general kernel options line. What do you think about it ? > > Also, is there a way (under linux) to detect if the floppy is of the 1.76 or > > the 880 variety ? > > dont know - I always believe that floppies are too dumb..you only know > what you can do when things you try fail ;-) What about trying to read past the 880 Kb with dd or something such ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, 15 May 2001, Alan Buxey wrote:
> > My 2.4.4 zImage is only 458036 bytes long. I have lots of modules, but it could
> > work. I remember I once did.
>
> custom images targetted for each APUS environment might be squeezed in.
Oh yes, this was an m68k image. APUS images are probably quite larger due to
PPC asm being less compact.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, 15 May 2001, Alan Buxey wrote:
> > Also, is there a way (under linux) to detect if the floppy is of the 1.76 or
> > the 880 variety ?
>
> dont know - I always believe that floppies are too dumb..you only know
> what you can do when things you try fail ;-)
grep FD_HD_3 linux/drivers/block/amiflop.c.
But I don't think you can easily find out from userspace.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > My 2.4.4 zImage is only 458036 bytes long. I have lots of modules, but it could > work. I remember I once did. custom images targetted for each APUS environment might be squeezed in. alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Geert Uytterhoeven wrote: > On Tue, 15 May 2001, Sven LUTHER wrote: > >>On Tue, May 15, 2001 at 11:11:38AM +0200, Geert Uytterhoeven wrote: >> >>>On Tue, 15 May 2001, Sven LUTHER wrote: >>>You cannot boot from 1.4 MB floppies, only from 880 kB or 1760 kB floppies. >>> >>Well, ok no problem, just make a tarball that can be copied to 1760Kb >>floppies, it is even better, since we have more place for stuff. >> >>I don't think we can ever fit a kernel and amiboot in 880kb, could we ? >> > > My 2.4.4 zImage is only 458036 bytes long. I have lots of modules, but it could > work. I remember I once did. Can we use modules for the install on APUS? Our strategy has been to include all possible hardware into the kernel. -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, 15 May 2001, Sven LUTHER wrote:
> On Tue, May 15, 2001 at 11:11:38AM +0200, Geert Uytterhoeven wrote:
> > On Tue, 15 May 2001, Sven LUTHER wrote:
> > You cannot boot from 1.4 MB floppies, only from 880 kB or 1760 kB floppies.
>
> Well, ok no problem, just make a tarball that can be copied to 1760Kb
> floppies, it is even better, since we have more place for stuff.
>
> I don't think we can ever fit a kernel and amiboot in 880kb, could we ?
My 2.4.4 zImage is only 458036 bytes long. I have lots of modules, but it could
work. I remember I once did.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > Can you boot from an external 1.76MB floppy ? yes. its treated just as the old classic external floppies that I'm sure most people had with their A500's > but 1.76MB floppies would be easily supported, almost nothing needs to be > changed, apart from the rescue disk creation. Does someone with a 1.76MB > floppy volunteer for that ? if you give me the instructions and details I can test this. > Also, is there a way (under linux) to detect if the floppy is of the 1.76 or > the 880 variety ? dont know - I always believe that floppies are too dumb..you only know what you can do when things you try fail ;-) alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 11:11:38AM +0200, Geert Uytterhoeven wrote: > On Tue, 15 May 2001, Sven LUTHER wrote: > > On Mon, May 14, 2001 at 08:26:44AM -0500, Christian T. Steigies wrote: > > > On Mon, May 14, 2001 at 01:05:03PM +0200, Sven LUTHER wrote: > > > > > > > > I don't know if it is possible to enable such a per subarch warning (altough > > > > it may be common the the m68K/amiga folk). > > > Floppys on m68k are completely useless AFAIK. Since Amigalilo is not > > > supported by Debian, who needs floppies anyways when everything comes on CD? > > > > Well, you may want to use floppies nonetheless, suppose you have a frechly > > bought harddisk to install from. Imagine the following scenario (if you have > > 1.4MB floppies, that is). > > > > - you have one rescue floppy, bootable and formated in amiga style (is that > >possible for 1.4MB ones ?). On this floppy you put your gzipped kernel, the > > You cannot boot from 1.4 MB floppies, only from 880 kB or 1760 kB floppies. Well, ok no problem, just make a tarball that can be copied to 1760Kb floppies, it is even better, since we have more place for stuff. I don't think we can ever fit a kernel and amiboot in 880kb, could we ? Maybe a 2 floppies solution ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, May 15, 2001 at 10:19:33AM +0100, Alan Buxey wrote:
> hi,
>
> > >#if cpu(sparc) || #cpu(powerpc)
> > >const char *fs_type_tab[] = { "ext2", NULL };
> > >#else
> > >const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> > >#endif
> > > as you can understand is impossible for a powerpc machine
> > > to load a msdos partition, so i have modified it so:
> > >#if cpu(sparc) || #cpu(powerpc)
> > >const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> > >#else
> > >const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> > >#endif
> >
> > I changed this to :
> >
> > #if cpu(sparc)
> > const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> > #else
> > const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> > #endif
>
> surely,
>
> #if cpu(sparc)
> const char *fs_type_tab[] = { "ext2", NULL };
> #else
> const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> #endif
>
> this would give the powerpc the msdos and ext2, but keep the sparc - which
> orginally didnt have the msdos option - as it was.
Yes, that is what i meant, ...
> > Ok, but like said most amiga have only the 720/880Ko floppy variety.
>
> most A4k's have a 1.76Mb internal, a lot of A1200 people have an external
> HD floppy, but internal was 880k - not possible to have some choose option
> (df0, df1 or skip?)
Can you boot from an external 1.76MB floppy ?
also i am not sure if it would worth it to try to support 880kb floppies, as
that would mean splitting the disks over various files,
but 1.76MB floppies would be easily supported, almost nothing needs to be
changed, apart from the rescue disk creation. Does someone with a 1.76MB
floppy volunteer for that ?
Also, is there a way (under linux) to detect if the floppy is of the 1.76 or
the 880 variety ?
Friendly,
Sven Luther
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi,
> >#if cpu(sparc) || #cpu(powerpc)
> >const char *fs_type_tab[] = { "ext2", NULL };
> >#else
> >const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> >#endif
> > as you can understand is impossible for a powerpc machine
> > to load a msdos partition, so i have modified it so:
> >#if cpu(sparc) || #cpu(powerpc)
> >const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> >#else
> >const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> >#endif
>
> I changed this to :
>
> #if cpu(sparc)
> const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> #else
> const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> #endif
surely,
#if cpu(sparc)
const char *fs_type_tab[] = { "ext2", NULL };
#else
const char *fs_type_tab[] = { "msdos", "ext2", NULL };
#endif
this would give the powerpc the msdos and ext2, but keep the sparc - which
orginally didnt have the msdos option - as it was.
> Ok, but like said most amiga have only the 720/880Ko floppy variety.
most A4k's have a 1.76Mb internal, a lot of A1200 people have an external
HD floppy, but internal was 880k - not possible to have some choose option
(df0, df1 or skip?)
alan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Tue, 15 May 2001, Sven LUTHER wrote:
> On Mon, May 14, 2001 at 08:26:44AM -0500, Christian T. Steigies wrote:
> > On Mon, May 14, 2001 at 01:05:03PM +0200, Sven LUTHER wrote:
> > >
> > > I don't know if it is possible to enable such a per subarch warning (altough
> > > it may be common the the m68K/amiga folk).
> > Floppys on m68k are completely useless AFAIK. Since Amigalilo is not
> > supported by Debian, who needs floppies anyways when everything comes on CD?
>
> Well, you may want to use floppies nonetheless, suppose you have a frechly
> bought harddisk to install from. Imagine the following scenario (if you have
> 1.4MB floppies, that is).
>
> - you have one rescue floppy, bootable and formated in amiga style (is that
>possible for 1.4MB ones ?). On this floppy you put your gzipped kernel, the
You cannot boot from 1.4 MB floppies, only from 880 kB or 1760 kB floppies.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Mon, May 14, 2001 at 08:26:44AM -0500, Christian T. Steigies wrote: > On Mon, May 14, 2001 at 01:05:03PM +0200, Sven LUTHER wrote: > > > > I don't know if it is possible to enable such a per subarch warning (altough > > it may be common the the m68K/amiga folk). > Floppys on m68k are completely useless AFAIK. Since Amigalilo is not > supported by Debian, who needs floppies anyways when everything comes on CD? Well, you may want to use floppies nonetheless, suppose you have a frechly bought harddisk to install from. Imagine the following scenario (if you have 1.4MB floppies, that is). - you have one rescue floppy, bootable and formated in amiga style (is that possible for 1.4MB ones ?). On this floppy you put your gzipped kernel, the amiboot program, and a small script launching it. You could even use the amiboot/apusboot configuration GUI that exists, but it uses MUI, i think, and as thus may not be useable, either because of the non freeness of it, or because the MUI library don't fit on your floppy disk. - you have the standard set of root image and drivers floppy. With this, you may be able to boot from the rescue floppy and do the install as usual. But even without the rescue floppy, you may still be able to use the standard root and driver floppies, needing only to install on a disk the kernel, the amiboot/apusboot program and the launching script. Giorgio seems to have tested the install method from floppies, so if it works, why not let the possibility to people to use it, even if it may well never be used. That is unless there is something not working that i don't know of. Now, this would only work if you have a floppy that can read 1.44MB floppies, soit would be nice to enable a warning , in the case of subarch being either apus or amiga, that warns users that you need a 1.44MB floppy, or even test for it (is this possible ?) But then maybe i am only speaking nonsense, please enlighten me if this is the case. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Mon, May 14, 2001 at 02:21:46PM +0200, Sven LUTHER wrote:
> On Fri, May 11, 2001 at 10:38:07PM +0200, Giorgio Terzi wrote:
> > Bug 1: dbootstrap
> >
> > The APUS rescue image is MSDOS formatted but in file
> > choose_medium.c from line 34 the code is so:
> >#if cpu(sparc) || #cpu(powerpc)
> >const char *fs_type_tab[] = { "ext2", NULL };
> >#else
> >const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> >#endif
> > as you can understand is impossible for a powerpc machine
> > to load a msdos partition, so i have modified it so:
> >#if cpu(sparc) || #cpu(powerpc)
> >const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> >#else
> >const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> >#endif
>
> I changed this to :
>
> #if cpu(sparc)
> const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> #else
> const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> #endif
>
> Should work, i think. Does one of the powerpc boot floppies people have
> anything to say about it before i commit ?
Shouldn't this be the following:
#if #cpu(sparc)
const char *fs_type_tab[] = { "ext2", NULL };
#else
const char *fs_type_tab[] = { "msdos", "ext2", NULL };
#endif
The way you wrote it changes the behavior for sparc as well, and
makes the #if totally superfluous.
Matt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Mon, May 14, 2001 at 01:05:03PM +0200, Sven LUTHER wrote: > > I don't know if it is possible to enable such a per subarch warning (altough > it may be common the the m68K/amiga folk). Floppys on m68k are completely useless AFAIK. Since Amigalilo is not supported by Debian, who needs floppies anyways when everything comes on CD? Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Fri, May 11, 2001 at 10:38:07PM +0200, Giorgio Terzi wrote:
> Hello Sven,
>
> In first i wish to thank you for your help and for your last
> e-mail. :)))
>
> But let's speak about job.
>
> The second goal is reached!
>
> Now is possible to load & install Rescue & Driver images from
> floppies, CD-ROMS,HD-Partitions.
> But to do this we must correct some bugs :
>
> Bug 1: dbootstrap
>
> The APUS rescue image is MSDOS formatted but in file
> choose_medium.c from line 34 the code is so:
>#if cpu(sparc) || #cpu(powerpc)
>const char *fs_type_tab[] = { "ext2", NULL };
>#else
>const char *fs_type_tab[] = { "msdos", "ext2", NULL };
>#endif
> as you can understand is impossible for a powerpc machine
> to load a msdos partition, so i have modified it so:
>#if cpu(sparc) || #cpu(powerpc)
>const char *fs_type_tab[] = { "msdos", "ext2", NULL };
>#else
>const char *fs_type_tab[] = { "msdos", "ext2", NULL };
>#endif
I changed this to :
#if cpu(sparc)
const char *fs_type_tab[] = { "msdos", "ext2", NULL };
#else
const char *fs_type_tab[] = { "msdos", "ext2", NULL };
#endif
Should work, i think. Does one of the powerpc boot floppies people have
anything to say about it before i commit ?
> After this, rescue.bin was loaded and kernel extracted & configured.
> I think this #if is obsolete because, as you will see some lines
> after in the source file , mount loops between the various filesystems
> (msdos & ext2 now, but may will be more ?) attempting
> to load the image files.
>
> For CD-ROM & for HD partition loading system the drivers was also
> successfully loaded & configured.
> For CD-ROM i used my Potato CD-ROM N.1.For hard disk i have
> built a debian tree in an Amiga partition.
>
> Bug 2: floppy images build & configuration
>
> After the kernel configuration, it was renamed as vmlinuz-2.2.19,
> and this comes from the install.sh script.
> For APUS this name is wrong as it is really a 2.2.10 kernel.
> Maybe it is possible to use the $subarch variable to distinguish the
> various powerpc kernel architecture's versions during the install.sh
> configuration ?
mmm, you can use the apuskver variable defined at line 30 of the config file :
ifeq "$(architecture)" "powerpc"
kver:= 2.2.19
pcmcia_kver := 2.2.19-pmac
apuskver:= 2.2.10
endif
So i guess what is used is kver, not apuskver.
Notice that the install.sh script is generated at line 12 of the rescue.sh
script, from the install.sh.txt file, but passing only the kver and arch
variables, not the subarch and apuskver one. There may be need for more
extensive modification here, i don't know m4 enough to really help out here.
Also it seems to me the write_powerpc routine only knows about quick, don't
think this will be working on apus, we may be more near what the
write_m68kinfo does, ity would need testing though.
lines 396-401 of rescue.sh should be generating the right thing for apus,
altough i don't really see a reason why we shall not go the ext2 way.
It would be also be interresting to see if we need lines 450+ of rescue.sh,
about broken loop device, this sound like the loop bug of the original boot
floppies.
Line 552 of rescue.sh also has some $kver related things we shall look into.
mmm, line 573 of rescue.sh calls write_m86kinfo, so we don't have to worry
about quick as feared above, we still would need to make sure that subarch and
apuskver is passed to m4 when generating install.sh.
That's all i see in rescue.sh.
mmm, maybe this would be enough (try the attached patch) ?
write_installsh () {
if [ "x$noinstall" = x ]; then
if [ "$subarch" != apus ]; then
m4 -D__ERROR_MESS__=$scripts/messages/$language/install.sh.txt \
-D__version__=$kver -D__arch__=$arch \
<$scripts/install.sh >$mnt/install.sh
chmod 755 $mnt/install.sh
else
m4 -D__ERROR_MESS__=$scripts/messages/$language/install.sh.txt \
-D__version__=$apuskver -D__arch__=$arch \
<$scripts/install.sh >$mnt/install.sh
chmod 755 $mnt/install.sh
fi
fi
Could you try it out ?
> I have tested also the floppy disk use:
>
> Bug 3: fd0 device problems
>
> For APUS /dev/fd0 is unable to load the rescue floppy disk.
> I think it defaults to the Amiga floppy formats.
> I must erase it and recreate it with 'mknod fd0 b 2 28'
> that is the same of /dev/fd0u1440 in a "standard" installation.
>
> After this change the rescue floppy was successfully loaded.
Ok, but like said most amiga have only the 720/880Ko floppy variety.
> Bug 4: dboostrap problem.
>
> dbootsrap was not able to recognize the driver's floppy disk
> because the drivers' default names was treated as complete
> names but they are really "root names" for example:
> drv14 is a "root name"
> drv14apus.bin is a driver's complete name.
> In file floppy_merge.c i have modified the line 197 :
>
>if (!s
Re: APUS Debian Boot-Floppies Images and bugs
On Mon, May 14, 2001 at 11:50:40AM +0100, Alan Buxey wrote: > hi, > > > Bug 3: fd0 device problems > > > > For APUS /dev/fd0 is unable to load the rescue floppy disk. > > I think it defaults to the Amiga floppy formats. > > I must erase it and recreate it with 'mknod fd0 b 2 28' > > that is the same of /dev/fd0u1440 in a "standard" installation. > > > > After this change the rescue floppy was successfully loaded. > > problem: the internal floppy of the A1200 is only a sub-Mb model, > so it cannot read HD1440 images. But i guess there were some HD1440 models sold, isn't it. I think it makes sense to support them if possible. Ideally would be to have a warning when you choose this option that you need 1.4MB floppies support, or else we will get a lot of complaints about why the floppy method don't work. I don't know if it is possible to enable such a per subarch warning (altough it may be common the the m68K/amiga folk). Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
hi, > Bug 3: fd0 device problems > > For APUS /dev/fd0 is unable to load the rescue floppy disk. > I think it defaults to the Amiga floppy formats. > I must erase it and recreate it with 'mknod fd0 b 2 28' > that is the same of /dev/fd0u1440 in a "standard" installation. > > After this change the rescue floppy was successfully loaded. problem: the internal floppy of the A1200 is only a sub-Mb model, so it cannot read HD1440 images. well done on the other work though! alan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Fri, May 11, 2001 at 10:38:07PM +0200, Giorgio Terzi wrote:
> Hello Sven,
>
> In first i wish to thank you for your help and for your last
> e-mail. :)))
>
> But let's speak about job.
>
> The second goal is reached!
>
> Now is possible to load & install Rescue & Driver images from
> floppies, CD-ROMS,HD-Partitions.
> But to do this we must correct some bugs :
>
> Bug 1: dbootstrap
>
> The APUS rescue image is MSDOS formatted but in file
> choose_medium.c from line 34 the code is so:
>#if cpu(sparc) || #cpu(powerpc)
>const char *fs_type_tab[] = { "ext2", NULL };
>#else
>const char *fs_type_tab[] = { "msdos", "ext2", NULL };
>#endif
> as you can understand is impossible for a powerpc machine
> to load a msdos partition, so i have modified it so:
>#if cpu(sparc) || #cpu(powerpc)
>const char *fs_type_tab[] = { "msdos", "ext2", NULL };
>#else
>const char *fs_type_tab[] = { "msdos", "ext2", NULL };
>#endif
> After this, rescue.bin was loaded and kernel extracted & configured.
> I think this #if is obsolete because, as you will see some lines
> after in the source file , mount loops between the various filesystems
> (msdos & ext2 now, but may will be more ?) attempting
> to load the image files.
Ok, will check it in on monday. BTW, could you send me all your changes in
patch form ? You know how to do so, isn't it ? you use diff -ur original.tree
changed.tree, or if you did change only a file, you do diff -u file.orig
file.new. This is the most usefull manner of sharing changes to code.
As what happened here, i guess it worked ok before (as potato used msdos disks
also) but was changed later on. BTW, it don't really makes sense to use msdos
root images, so we could as well go with the ext2 stuff for apus, but we have
to find were it is that this is specified.
> For CD-ROM & for HD partition loading system the drivers was also
> successfully loaded & configured.
> For CD-ROM i used my Potato CD-ROM N.1.For hard disk i have
> built a debian tree in an Amiga partition.
mmm, ok, i guess this will not work well because of the link issue, but then
it is only for testing.
> Bug 2: floppy images build & configuration
>
> After the kernel configuration, it was renamed as vmlinuz-2.2.19,
> and this comes from the install.sh script.
> For APUS this name is wrong as it is really a 2.2.10 kernel.
> Maybe it is possible to use the $subarch variable to distinguish the
> various powerpc kernel architecture's versions during the install.sh
> configuration ?
Yes, i remember there was a apus subarch, and already in potato i had to use
2.2.10, while other ppc subarches used 2.2.12 or later kernels.
Maybe we should also go the 2.4.x route, but i am not sure if it is ready
already. Let's ask on the apus lists about it.
> I have tested also the floppy disk use:
>
> Bug 3: fd0 device problems
>
> For APUS /dev/fd0 is unable to load the rescue floppy disk.
> I think it defaults to the Amiga floppy formats.
> I must erase it and recreate it with 'mknod fd0 b 2 28'
> that is the same of /dev/fd0u1440 in a "standard" installation.
>
> After this change the rescue floppy was successfully loaded.
Err, do you have a 1.44MB floppy ? Most people would have only 880KB ones, so
this is not really needed. Maybe it would be good if you changedebootstrap, so
as to look for fd0u1440 directly, instead of for /dev/fd0, in case we are on
the apus subarch. Also some comment somewhere about it would be welcome. Don't
know if there is a place for adding description of the entries though.
Also i think i recall that we had /dev/fd0 for 720Ko floppies, and /dev/df0
for 880KB amiga floppies, or maybe it was /dev/pc0 or somethign such ...
> Bug 4: dboostrap problem.
>
> dbootsrap was not able to recognize the driver's floppy disk
> because the drivers' default names was treated as complete
> names but they are really "root names" for example:
> drv14 is a "root name"
> drv14apus.bin is a driver's complete name.
> In file floppy_merge.c i have modified the line 197 :
>
>if (!strcmp (basenames[i], block.header.name))
> as follows:
>if (!strncmp (basenames[i], block.header.name,strlen(basenames[i])))
>
> after this i have also loaded the drivers!
huh, this is very nice work already, very good.
Just when making such changes, it is needed to check that it don't break other
arches/subarches. Is there a way to test for the apus subarch when doing the
changes ? somethign like :
if (arch="ppc" && subarch="apus")
if (!strcmp (basenames[i], block.header.name));
else if (!strncmp (basenames[i], block.header.name,strlen(basenames[i])));
I remember being able to do things like that before.
Maybe they are even macros to do per arch things ?
> I can't test network installations because at this moment i haven't it.
maybe we could put the files somewhere and ask for someone with a network
connection to test this ?
> Next steps:
> 1) I shall take a look fo
Re: APUS Debian Boot-Floppies Images and bugs
At 10:38 PM +0200 5/11/01, Giorgio Terzi wrote: >Bug 4: dboostrap problem. > >dbootsrap was not able to recognize the driver's floppy disk >because the drivers' default names was treated as complete >names but they are really "root names" for example: >drv14 is a "root name" >drv14apus.bin is a driver's complete name. >In file floppy_merge.c i have modified the line 197 : > >if (!strcmp (basenames[i], block.header.name)) >as follows: >if (!strncmp (basenames[i], block.header.name,strlen(basenames[i]))) I just fixed this in bf cvs, none of the powerpc driver disks were listed as known driver disks, so I added drv14pmac, drv14apus, drv14chrp, and drv14prep. Stephen -- Stephen R. MarenkaIf life's not fun, you're not doing it right! <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
APUS Debian Boot-Floppies Images and bugs
Hello Sven,
In first i wish to thank you for your help and for your last
e-mail. :)))
But let's speak about job.
The second goal is reached!
Now is possible to load & install Rescue & Driver images from
floppies, CD-ROMS,HD-Partitions.
But to do this we must correct some bugs :
Bug 1: dbootstrap
The APUS rescue image is MSDOS formatted but in file
choose_medium.c from line 34 the code is so:
#if cpu(sparc) || #cpu(powerpc)
const char *fs_type_tab[] = { "ext2", NULL };
#else
const char *fs_type_tab[] = { "msdos", "ext2", NULL };
#endif
as you can understand is impossible for a powerpc machine
to load a msdos partition, so i have modified it so:
#if cpu(sparc) || #cpu(powerpc)
const char *fs_type_tab[] = { "msdos", "ext2", NULL };
#else
const char *fs_type_tab[] = { "msdos", "ext2", NULL };
#endif
After this, rescue.bin was loaded and kernel extracted & configured.
I think this #if is obsolete because, as you will see some lines
after in the source file , mount loops between the various filesystems
(msdos & ext2 now, but may will be more ?) attempting
to load the image files.
For CD-ROM & for HD partition loading system the drivers was also
successfully loaded & configured.
For CD-ROM i used my Potato CD-ROM N.1.For hard disk i have
built a debian tree in an Amiga partition.
Bug 2: floppy images build & configuration
After the kernel configuration, it was renamed as vmlinuz-2.2.19,
and this comes from the install.sh script.
For APUS this name is wrong as it is really a 2.2.10 kernel.
Maybe it is possible to use the $subarch variable to distinguish the
various powerpc kernel architecture's versions during the install.sh
configuration ?
I have tested also the floppy disk use:
Bug 3: fd0 device problems
For APUS /dev/fd0 is unable to load the rescue floppy disk.
I think it defaults to the Amiga floppy formats.
I must erase it and recreate it with 'mknod fd0 b 2 28'
that is the same of /dev/fd0u1440 in a "standard" installation.
After this change the rescue floppy was successfully loaded.
Bug 4: dboostrap problem.
dbootsrap was not able to recognize the driver's floppy disk
because the drivers' default names was treated as complete
names but they are really "root names" for example:
drv14 is a "root name"
drv14apus.bin is a driver's complete name.
In file floppy_merge.c i have modified the line 197 :
if (!strcmp (basenames[i], block.header.name))
as follows:
if (!strncmp (basenames[i], block.header.name,strlen(basenames[i])))
after this i have also loaded the drivers!
I can't test network installations because at this moment i haven't it.
Next steps:
1) I shall take a look for ZIP installation.
2) I shall try to download the woody base_system and install it
Friendly,
--
Giorgio Terzi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
