Menu
▾
▴
linux-apus-devel
|
From: Giorgio T. <de...@ip...> - 2001-05-11 20:43:14
|
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
|
|
From: Stephen R M. <st...@ma...> - 2001-05-12 15:07:29
|
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. Marenka If life's not fun, you're not doing it right! <sma...@be...> |
|
From: Sven L. <lu...@dp...> - 2001-05-12 15:20:43
|
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 for ZIP installation.
mmm, should be the same as harddisk installation, should it not ?
> 2) I shall try to download the woody base_system and install it
Ok, that will permit us to test the rest of it, but i think the most difficult
part is already done.
Friendly,
Sven Luther
|
|
From: Alan B. <al...@ms...> - 2001-05-14 10:51:07
|
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 |
|
From: Sven L. <lu...@dp...> - 2001-05-14 11:03:17
|
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 |
|
From: Christian T. S. <ct...@de...> - 2001-05-14 13:26:49
|
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 |
|
From: Alan B. <al...@ms...> - 2001-05-14 13:37:07
|
hi, > Floppys on m68k are completely useless AFAIK. Since Amigalilo is not > supported by Debian, who needs floppies anyways when everything comes on CD? we use floppy images, but not the floppy disk medium ;-) alan |
|
From: Sven L. <lu...@dp...> - 2001-05-15 08:54:47
|
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 |
|
From: Geert U. <ge...@li...> - 2001-05-15 09:14:59
|
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 -- ge...@li...
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
|
|
From: Sven L. <lu...@dp...> - 2001-05-15 09:44:08
|
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 |
|
From: Geert U. <ge...@li...> - 2001-05-15 11:02:45
|
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 -- ge...@li...
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
|
|
From: Michel <mic...@ii...> - 2001-05-15 11:28:46
|
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 |
|
From: Sven L. <lu...@dp...> - 2001-05-15 13:03:43
|
On Tue, May 15, 2001 at 01:26:52PM +0200, Michel D=E4nzer wrote: >=20 >=20 > Geert Uytterhoeven wrote: >=20 > > On Tue, 15 May 2001, Sven LUTHER wrote: > >=20 > >>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 fl= oppies. > >>> > >>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= ? > >> > >=20 > > My 2.4.4 zImage is only 458036 bytes long. I have lots of modules, bu= t it could > > work. I remember I once did. >=20 >=20 > Can we use modules for the install on APUS? Our strategy has been to in= clude=20 > 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 we= ll 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 fina= l installed one. I heard speach about 2.4.x being big (probably on i386) th= at is too big to fit into a floppy, so they planed to have 2.2.latest on the bo= ot 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 |
|
From: Alan B. <al...@ms...> - 2001-05-15 14:05:31
|
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 |
|
From: Sven L. <lu...@dp...> - 2001-05-15 14:19:20
|
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 |
|
From: Alan B. <al...@ms...> - 2001-05-15 14:18:16
|
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 |
|
From: Sven L. <lu...@dp...> - 2001-05-15 14:36:46
|
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 |
|
From: Geert U. <ge...@li...> - 2001-05-15 14:53:43
|
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 -- ge...@li...
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
|
|
From: Sven L. <lu...@dp...> - 2001-05-15 15:02:52
|
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 |
|
From: Alan B. <al...@ms...> - 2001-05-15 15:19:36
|
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 |
|
From: Sven L. <lu...@dp...> - 2001-05-15 15:32:41
|
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 |
|
From: Alan B. <al...@ms...> - 2001-05-15 11:30:23
|
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 |
|
From: Geert U. <ge...@li...> - 2001-05-15 11:40:56
|
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 -- ge...@li...
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
|
|
From: Sven L. <lu...@dp...> - 2001-05-15 12:58:36
|
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 |
|
From: Giorgio T. <de...@ip...> - 2001-05-15 17:21:33
|
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
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X