From: Ken T. <ke...@we...> - 2000-09-08 12:26:59
|
Hello, I've uploaded ramdisks, diffs, READMEs and a source tree for the Apus installer to the redhat subdir of install. There are two of everything, one for 1999 and one for 2000 LinuxPPC Cds. I moved the existing contents to 'old' Ken. |
From: Alan B. <al...@ms...> - 2000-09-08 13:11:01
|
hi, > I've uploaded ramdisks, diffs, READMEs and a source tree for the Apus > installer to the redhat subdir of install. There are two of everything, > one for 1999 and one for 2000 LinuxPPC Cds. > > I moved the existing contents to 'old' just to verify: the latest kernel (000814/15) archives have kernels with HFS support. noone has reported this as broken, so this means the LinuxPPC 2000 installer should work fine. PS in the README, it would be good to add the CD mount demonstration for the kernel+ramdisk mount -t hfs /dev/hdb /mnt alan |
From: Ken T. <ke...@we...> - 2000-09-08 14:29:59
|
On Fri, 8 Sep 2000, Alan Buxey wrote: > just to verify: the latest kernel (000814/15) archives have kernels with > HFS support. noone has reported this as broken, so this means the LinuxPPC > 2000 installer should work fine. Can't see a precompiled kernel with that date... If there is one I'll give it a try and put the exact name in the README (hope its 2.2, still can't boot 2.3). Hope its a monolithic kernel too... > PS in the README, it would be good to add the CD mount demonstration > for the kernel+ramdisk Done. Ken. |
From: Alan B. <al...@ms...> - 2000-09-08 14:45:44
|
hi, > Can't see a precompiled kernel with that date... if you look at the actual linux-apus project page, rather than the FTP region, and choose the 'files' menu, it'll bring up a list in which theres vmapus-2.2.10-000814.lha and vmapus-2.2.10-000815.tar.gz, same contents, different upload date > Hope its a monolithic kernel too... the important parts are in there :-) alan |
From: Ken T. <ke...@we...> - 2000-09-08 14:54:02
|
On Fri, 8 Sep 2000, Alan Buxey wrote: > > Can't see a precompiled kernel with that date... > > if you look at the actual linux-apus project page, rather than the FTP > region, and choose the 'files' menu, it'll bring up a list in which theres > vmapus-2.2.10-000814.lha and vmapus-2.2.10-000815.tar.gz, same contents, > different upload date Give me an hour and I'll add that and a couple of other things to the README then can you copy all the ftp install to the module place please ? > > Hope its a monolithic kernel too... > > the important parts are in there :-) Fine. Ken. |
From: Alan B. <al...@ms...> - 2000-09-08 15:07:46
|
hi, > Give me an hour and I'll add that and a couple of other things to the > README then can you copy all the ftp install to the module place please ? can you please clarify. the modules contain the files, no readmes - they should be in the docs section - unless they are in archives (not something you want to do with ramdisk images I guess!) the README details can be added to the documentation tree as soon as, i guess. the docs are now up by the way, but boy! do they need some modification! (I think we should keep the FAQ...just upgrade it!...and have a seperate entry for Docs...as there is already designed on the linux-apus frontend web page....under which we have the documents relating to ramdisk installers etc) alan |
From: Ken T. <ke...@we...> - 2000-09-08 22:25:31
|
On Fri, 8 Sep 2000, Alan Buxey wrote: > can you please clarify. the modules contain the files, no readmes - they > should be in the docs section - unless they are in archives (not something > you want to do with ramdisk images I guess!) the README details can be > added to the documentation tree as soon as, i guess. OK, I didn't realise that's how it worked. I've put the files in the ftp area, please feel free to move/copy them at your pleasure. > the docs are now up by the way, but boy! do they need some modification! > > (I think we should keep the FAQ...just upgrade it!...and have a seperate > entry for Docs...as there is already designed on the linux-apus frontend > web page....under which we have the documents relating to ramdisk > installers etc) I'm quite happy to take on the FAQ but got no where with Jesper's Docbook magic. I think we should keep the sgml version and generate html, txt, whatever from it. I don't feel like generating a pure text version by hand from the sgml and updating it, and then doing it all again if I ever get Docbook to work. Ken. |
From: Alan B. <al...@ms...> - 2000-09-11 16:45:32
|
hi, Would it be possible to integrate the BadRAM system http://home.zonnet.nl/vanrein/badram/ with LinuxAPUS kernel? This would allow users of APUS to get cheap/free memory SIMMs to use with their system (faulty SIMMs invariably get thrown away...this nifty system gives SIMMs a new life! Anyone here know how well this could be integrated...x86 architecture being variably different with its memory allocation and MMU details alan |
From: Michel <dae...@st...> - 2000-09-08 13:25:44
|
Ken Tyler wrote: > I've uploaded ramdisks, diffs, READMEs and a source tree for the Apus > installer to the redhat subdir of install. There are two of everything, > one for 1999 and one for 2000 LinuxPPC Cds. Can you please also upload the stuff to the Ramdisks SourceForge module, and what about announcing it on the user list? > I moved the existing contents to 'old' That's fine, though maybe moving it to the top-level 'obsolete' would be better? Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
From: Ken T. <ke...@we...> - 2000-09-08 14:15:30
|
On Fri, 8 Sep 2000, Michel [iso-8859-1] Dänzer wrote: > Ken Tyler wrote: > > > I've uploaded ramdisks, diffs, READMEs and a source tree for the Apus > > installer to the redhat subdir of install. There are two of everything, > > one for 1999 and one for 2000 LinuxPPC Cds. > > Can you please also upload the stuff to the Ramdisks SourceForge module, and > what about announcing it on the user list? OK, I'll work on it. > > I moved the existing contents to 'old' > > That's fine, though maybe moving it to the top-level 'obsolete' would be > better? Also OK. Ken. |
From: Alan B. <al...@ms...> - 2000-09-08 14:26:44
|
hi, > Can you please also upload the stuff to the Ramdisks SourceForge module, and > what about announcing it on the user list? I'm doing that now.... so dont worry Ken! :-) I've also stuck a news release on site and released info to others - also moving the 'old' to the obsolete as asked alan |
From: Ken T. <ke...@we...> - 2000-09-08 14:42:18
|
On Fri, 8 Sep 2000, Alan Buxey wrote: > hi, > > > Can you please also upload the stuff to the Ramdisks SourceForge module, and > > what about announcing it on the user list? > I'm doing that now.... so dont worry Ken! :-) Good, no idea how to get it into a module ! > I've also stuck a news release on site and released info to others OK. > - also moving the 'old' to the obsolete as asked Too late ! :) Ken |
From: Alan B. <al...@ms...> - 2000-09-08 14:46:36
|
hi, > > I'm doing that now.... so dont worry Ken! :-) > > Good, no idea how to get it into a module ! that's okay, it is tricky/fiddly > > - also moving the 'old' to the obsolete as asked > > Too late ! :) i noticed! :-) alan |