|
From: Alan B. <al...@ms...> - 2001-05-15 14:15:35
|
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 |
|
From: Sven L. <lu...@dp...> - 2001-05-15 14:21:42
|
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 |
|
From: Christian T. S. <ct...@de...> - 2001-05-15 14:44:39
|
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/ |
|
From: Geert U. <ge...@li...> - 2001-05-15 14:55:30
|
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 -- 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 14:56:39
|
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 |
|
From: Geert U. <ge...@li...> - 2001-05-15 14:52:41
|
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 -- 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 14:58:59
|
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 |
|
From: Alan B. <al...@ms...> - 2001-05-15 15:15:48
|
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 |
|
From: Alan B. <al...@ms...> - 2001-05-15 15:10:03
|
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
|
|
From: Duncan G. <DG...@Du...> - 2001-05-15 17:38:23
|
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. |
|
From: Alan B. <al...@ms...> - 2001-05-15 21:27:24
Attachments:
bh_maker
|
hi, can people run this little utilty and give some feedback as to any errors it makes/gives? Its just the beginning of a small tool i knocked up this evening.... I've started looking through bootstrap source..are there any other places that i can see options in? the docs I do have are so out of date...can anyone supply any/all of the missing flags this utility currently does not ask for? alan PS thanks Duncan for responding! |
|
From: Duncan G. <DG...@Du...> - 2001-05-15 22:50:56
|
On 15-May-01, Alan Buxey wrote: AB> can people run this little utilty and give some feedback Runs OK for me (A4k/CSPPC/CV-PPC/OS3.5); output looks valid, but I haven't been able to test it properly as I don't have a functioning APUS system at the moment. Building one is on my (very) long list of things to do. AB> PS thanks Duncan for responding! ;-) What are the odds of bumping in to you at LinuxExpo in London this year? Duncan -- ... Dylan's brain was being unusually active for the time of the morning. |
|
From: Alan B. <al...@ms...> - 2001-05-16 09:54:06
|
hi, > Runs OK for me (A4k/CSPPC/CV-PPC/OS3.5); output looks valid, but I haven't > been able to test it properly as I don't have a functioning APUS system at > the moment. Building one is on my (very) long list of things to do. :-) okay, do you not use the 'noscsi' option on your CSPPC, or do you have any extra hardware that you enable etc? > What are the odds of bumping in to you at LinuxExpo in London this year? so long as I'm not still out in Japan upgrading Digital UNIX boxes (doubtful as I'm going out there in mid-june) the odds will be very high - perhaps we (and other UK/Euro people?) can arrange to meet at LinuxEpxo2001 @ Olympia London 4th-5th July (what day are you going?) not sorry for the blatant plug, its free and Linux ;-) alan |
|
From: Duncan G. <DG...@Du...> - 2001-05-16 17:45:21
|
On 16-May-01, Alan Buxey wrote: DG> I don't have a functioning APUS system at the moment. DG> Building one is on my (very) long list of things to do. AB> :-) okay, do you not use the 'noscsi' option on your CSPPC, AB> or do you have any extra hardware that you enable etc? The main problem is that my GVP SCSI card blew up (shows up in early startup, but as not working, and the machine won't boot with it in place). This means I've had to rewire all my SCSI devices to use the CSPPC onboard interface, where of course they are invisible under APUS. I do have an IDE hard drive I can install onto, and a LinuxPPC 2000Q4 set which LinuxPPC kindly sent me, but I no longer have an IDE CD-ROM. They one I did have kept locking up while duplicating discs with MakeCD, so I have replaced it with a SCSI one. I'll have to arse about installing from hard drive or over the network... I also have three x86 boxes to play with now, plus rather a lot of work in my day job ;-) And in three weeks my girlfriend is back in the country. She's planning to move in here, so I have to clear out a lot of the computer junk which makes the place so homely ;-) AB> - perhaps we (and other UK/Euro people?) can arrange to meet at AB> LinuxEpxo2001 @ Olympia London 4th-5th July (what day are you going?) I haven't decided yet, I don't think. I've told my boss that it's work-related, so I will be going, and I've registered (now that they've fixed their website). If you're going to organise (?) a piss up^W^Wmeeting, I can probably go whichever day suits the most other people. I can get to London in under an hour, so it makes no odds to me. Time for Star Trek... Duncan -- ... Visual Basic Chicken: USHighways!TheRoad.cross (aChicken) |
|
From: Ken T. <ke...@we...> - 2001-05-16 11:01:16
|
On Tue, 15 May 2001, Alan Buxey wrote: > can people run this little utilty and give some feedback as to any errors > it makes/gives? Its just the beginning of a small tool i knocked up this > evening.... Hello All, My results... Are you installing Debian from this floppy? (Y/N)y Okay, in this case /dev/ram is used as the root Do you have a gfx card? (Y/N)y Okay, what card do you have installed? (choose the number) 1) CVisionPPC/BVisionPPC 2) CVision3D 3) Picasso IV Choice>2 What resolution do you wish to run in? (choose number) 1) 640x480 2) 800x600 3) 1024x768 Choice>2 You have the option to turn native (AGA) gfx off...do you want to do this? (Y/N)y Okay, lets see what you think of this bootstrap: bootstrap --apus -k vmapus-2.4.4 root=/dev/ram video=cyberfb:mode:800x600-60 video=amifb:off video=cyberfb:... is for the CV64 card not the CV64/3D, which should be video=virge:... (not virgefb!) About the CV64/3d, I have a modified virge driver that supports initialization and mode changing for 2.2 and 2.4 kernels but didn't ever commit the changes as I always intended to 'make it better' but never got round to it, but they work. The 2.4 version is almost identical to 2.2, only a few name changes. I also almost have a 2.4 version with modedb support but it has a couple of problems that I haven't got round to fixing (yet). Ken. |
|
From: Alan B. <al...@ms...> - 2001-05-16 11:16:41
|
hi, > You have the option to turn native (AGA) gfx off...do you want to do this? (Y/N)y > Okay, lets see what you think of this bootstrap: > bootstrap --apus -k vmapus-2.4.4 root=/dev/ram video=cyberfb:mode:800x600-60 video=amifb:off > > video=cyberfb:... is for the CV64 card not the CV64/3D, > which should be video=virge:... (not virgefb!) thanks - its this quirky info that i need. was there any move to standardise the gfx-cards on APUS so they were all called in the same name format (eg virgefb, cyberfb, pm2fb etc)? what about the 'mode' part of virge, it too is 'alien', yes? What is you're bootstrap line that works with the virge? thanks, alan |
|
From: Ken T. <ke...@we...> - 2001-05-16 11:27:57
|
On Wed, 16 May 2001, Alan Buxey wrote: Hello, > thanks - its this quirky info that i need. was there any move to > standardise the gfx-cards on APUS so they were all called in the same name > format (eg virgefb, cyberfb, pm2fb etc)? I thought the standard was to drop the fb of the end. > what about the 'mode' part of virge, it too is 'alien', yes? What is > you're bootstrap line that works with the virge? video=virge:800x600-16 With the driver as I have it now it needs -n depth in bpp style for both 2.2 and 2.4, for 2.4 with modedb (if it ever works) it would accept the -n refresh style. Ken. |
|
From: Alan B. <al...@ms...> - 2001-05-16 11:32:50
|
hi, > > what about the 'mode' part of virge, it too is 'alien', yes? What is > > you're bootstrap line that works with the virge? > > video=virge:800x600-16 is there a source for all thes e- or is it a case of reading through all the driver .c files for their flags? from this, i guess such things as virge:1024x768-8, virge:640x480-24 will work? what controls the refresh for this card? > With the driver as I have it now it needs -n depth in bpp style for both > 2.2 and 2.4, for 2.4 with modedb (if it ever works) it would accept the -n > refresh style. okay, so I'll base it on the bpp mode for now. alan |
|
From: Ken T. <ke...@we...> - 2001-05-16 12:09:15
|
On Wed, 16 May 2001, Alan Buxey wrote: Hello, > is there a source for all thes e- or is it a case of reading through all > the driver .c files for their flags? > from this, i guess such things as virge:1024x768-8, virge:640x480-24 > will work? what controls the refresh for this card? I think all the relevant drivers in 2.2 and those in 2.4 which don't use modedb.c support, take modes like video=name:XRESxYRES-depth apart from amifb which takes options like ntsc, dblpal, vga and more. Some drivers also accept otions like video=cyberfb:cyber16 to give a 16 bit default mode. Yes, each driver needs its own collection of supported modes gathered by searching through the .c files, or a subset of common modes - if you are lucky. The refresh rate is determined by the constants in the mode data base built into each driver (apart from those using modedb). For instance 800x600-16 in (my) virgefb gives 50Hz refresh but 1024x768-8 gives 75Hz refresh, you get the refresh rate you're given!. Mode can be changed later by fbset, either to a mode in /etc/fb.modes, or by giving specific values for some or all of the parmeters. Only way to know the true refresh rate is to calculate it from pixelclock and the horizontal and vertical resolution, sync and margin values. > okay, so I'll base it on the bpp mode for now. With virge driver as it is in kernels (both 2.2 and 2.4) now, bootstrap needs the -v option, keep amiga video and be booted from a WB screen of the same xres, yres and depth. I should commit the virge changes. Ken. |
|
From: Giorgio T. <de...@ip...> - 2001-05-16 17:12:15
|
On 15-Mag-01, Alan Buxey wrote:
> hi,
>
> can people run this little utilty and give some feedback as to any errors
> it makes/gives? Its just the beginning of a small tool i knocked up this
> evening....
>
> I've started looking through bootstrap source..are there any other places
> that i can see options in? the docs I do have are so out of date...can
> anyone supply any/all of the missing flags this utility currently does not
> ask for?
>
>
> alan
>
> PS thanks Duncan for responding!
Nice!
Is a very good idea and works pretty.
Regards
--
Giorgio Terzi
|
|
From: Sven L. <lu...@dp...> - 2001-05-16 08:20:55
|
On Tue, May 15, 2001 at 06:36:58PM +0000, 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 |
|
From: Alan B. <al...@ms...> - 2001-05-15 16:39:49
|
hi,
okay, perhaps they just missed my email address when they/if they mailed
out information, but the directory structure has been heavily changed.
On May 1st directories for users and groups have been split into first,
then first+second letters of the user name or group:
OLD: /home/users/username, /home/users/foobar
NEW: /home/users/u/us/username, /home/users/f/fo/foobar
OLD: /home/groups/projectname, /home/groups/myproject
NEW: /home/groups/p/pr/projectname, /home/groups/m/my/myproject
this means its now /home/groups/l/li/linux-apus
this REALLY screwed up the Faq-O-Matic.... and yet noone informed us that
the FAQ was dead (for 2 weeks!) - typical of the users eh? ;-)
anyway, I've just been playing around with various files and have got it
back into a working order. Time spent WAS going to be used to add some
new items, but that'll now have to wait :-|
Alan
|
|
From: Geert U. <ge...@li...> - 2001-05-15 17:50:42
|
On Tue, 15 May 2001, Alan Buxey wrote:
> On May 1st directories for users and groups have been split into first,
> then first+second letters of the user name or group:
>
> OLD: /home/users/username, /home/users/foobar
> NEW: /home/users/u/us/username, /home/users/f/fo/foobar
So CVSROOT/loginfo has to be changed as well?
Gr{oetje,eeting}s,
Geert (peeking at loginfo to steal for fbdev :-)
--
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 18:04:37
|
Geert Uytterhoeven wrote: > On Tue, 15 May 2001, Alan Buxey wrote: > >>On May 1st directories for users and groups have been split into first, >>then first+second letters of the user name or group: >> >> OLD: /home/users/username, /home/users/foobar >> NEW: /home/users/u/us/username, /home/users/f/fo/foobar This info was in the motd for some time BTW. > So CVSROOT/loginfo has to be changed as well? You mean for the changelog? Don't think so, that's only on the CVS machine which doesn't offer access besides CVS. If anyone has a good idea how to get it outta there, speak up. -- Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \ XFree86 and DRI project member |
|
From: Geert U. <ge...@li...> - 2001-05-15 18:10:18
|
On Tue, 15 May 2001, Michel D=E4nzer wrote:
> Geert Uytterhoeven wrote:
> > On Tue, 15 May 2001, Alan Buxey wrote:
> >>On May 1st directories for users and groups have been split into firs=
t,
> >>then first+second letters of the user name or group:
> >>
> >> OLD: /home/users/username, /home/users/foobar
> >> NEW: /home/users/u/us/username, /home/users/f/fo/foobar
>=20
> This info was in the motd for some time BTW.
>=20
> > So CVSROOT/loginfo has to be changed as well?
>=20
> You mean for the changelog? Don't think so, that's only on the CVS mach=
ine=20
> which doesn't offer access besides CVS. If anyone has a good idea how t=
o get=20
> it outta there, speak up.
So the path to your homedir does not change on the CVS machine? Weird...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m6=
8k.org
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
|