Bug#315592: RFH aboot (Alpha bootloader): Looking for co-maintainers
Hallo Helge! On Don, 23 Jun 2005, Helge Kreutzmann wrote: Subject: RFH: aboot Package: wnpp Severity: normal I maintain aboot now for about 2 years, but unfortunately my private alpha run into serious problems late last year, and now I lost access to the university machines, so I currently cannot work on aboot. Ich bin kein DD, arbeite gerade aber daran TeXlive zu verpacken. Außerdem haben wir auf der Uni zwei alphas rumstehen die mit aboot laufen. Einziges Problem, ich lebe derzeit nicht in Wien, sondern in Siena (2 Jahre EU Projekt dort) und bin daher nur ab und zu auf der Uni in Wien um an den Maschinen rumzudoktern. Alles was nicht mit reboots zu tun hat, geht ja, aber rebooten remote ist ein bisschen zu gefährlich ;-) Wenn du meinst dass ich dir trotzdem helfen kann, sag mir! Prinzipiell können wir auch über einen account auf einer unserer alpha maschinen reden, wenn du sowas brauchsts. Derzeit rennt dort aber debian/woody! Herzliche Grüße Norbert --- Dr. Norbert Preining preining AT logic DOT at Università di Siena sip:[EMAIL PROTECTED] +43 (0) 59966-690018 gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- There was a point to this story, but it has temporarily escaped the chronicler's mind. --- This line perhaps best sums up the whole book. --- Douglas Adams, The Hitchhikers Guide to the Galaxy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315592: RFH aboot (Alpha bootloader): Looking for co-maintainers
Hi Helge, Great. Since I am not a DD, I will inform Steve Langasek, who did the uploads and helped me a great deal with all the packaging details. The first thing you can do is to check out our CVS from alioth (pkg-aboot). I'll ask Steve to add you to the group and get a little aqauinted with the source layout. Please ask if something is unclear, ... I cannot tell you the nitty gritty source details, but the overall layout and the purpose of the various tools/directories etc. I know. Out of the bugs, I'd consider #270801 the most anyoing. Unfortunately, netabootwrap is not in the upstream source, hence we are on our own. Ok. Do I get it right that aboot doesn't display any messages at all ? (not even 'aboot: Linux/Alpha SRM bootloader version ') ? For #153176 and #222904 I tried to collect as much info as possible, and also talked to upstream, but there is no solution yet. Please see the logs. Ok. I will look into this. If you know how to add other FS, then #153666 might be fun for you. Upstream is a little reluctant, though, to add more and more file systems. Since a patch is available, the next thing would be to test, if possible, and add it in the next upload which could deal with the new policy version as well (haven't looked yet, what this would require). I have done (am doing this) for other bootloaders. Should be doable for aboot as well. Suggestions for #271180 are welocme as well. I think it might be good to interpret booted_osflags the same way for netboot then for disk/cd boot. Ie as the aboot.conf entry to use for booting. This would require a small aboot.conf to be included in the netboot image. A very important thing is, though, to keep aboot buildable (by having machines to build and test on). Yep. Although SRM seems to be a reasonably well behaved firmware in my experience. And finally, I have the upstream e-mail adresses and can try to get them working on it again. And documentation fixes I can submit both for Debian as upstream (sourceforge) as well. Ok. Cheers, Peter (p2). signature.asc Description: Digital signature
Bug#315592: RFH aboot (Alpha bootloader): Looking for co-maintainers
Hello Peter, On Fri, Jun 24, 2005 at 01:58:27AM +0200, Peter De Schrijver wrote: I'm willing to help you out on this. I have 6 alpha machines (4 of which are debian supported now, the other 2 are turbo channel machines for which I did some work to get the linux kernel to work, but they aren't ready yet). I also maintain the quik package (oldworld powermac bootloader) and comaintain sibyl (Broadcom swarm bootloader). I'm familiar with alpha, mips, powerpc and arm architectures. I hope I can help you here. Great. Since I am not a DD, I will inform Steve Langasek, who did the uploads and helped me a great deal with all the packaging details. The first thing you can do is to check out our CVS from alioth (pkg-aboot). I'll ask Steve to add you to the group and get a little aqauinted with the source layout. Please ask if something is unclear, ... I cannot tell you the nitty gritty source details, but the overall layout and the purpose of the various tools/directories etc. I know. Out of the bugs, I'd consider #270801 the most anyoing. Unfortunately, netabootwrap is not in the upstream source, hence we are on our own. For #153176 and #222904 I tried to collect as much info as possible, and also talked to upstream, but there is no solution yet. Please see the logs. If you know how to add other FS, then #153666 might be fun for you. Upstream is a little reluctant, though, to add more and more file systems. Since a patch is available, the next thing would be to test, if possible, and add it in the next upload which could deal with the new policy version as well (haven't looked yet, what this would require). Suggestions for #271180 are welocme as well. A very important thing is, though, to keep aboot buildable (by having machines to build and test on). And finally, I have the upstream e-mail adresses and can try to get them working on it again. And documentation fixes I can submit both for Debian as upstream (sourceforge) as well. Long mail, short story: Thanks for joining, ask for details where you need them and have fun! Greetings Helge -- Dr. Helge Kreutzmann, Dipl.-Phys. [EMAIL PROTECTED] gpg signed mail preferred 64bit GNU powered http://www.itp.uni-hannover.de/~kreutzm Help keep free software libre: http://www.ffii.de/ pgptRLqr7WKor.pgp Description: PGP signature
Bug#315592: RFH aboot (Alpha bootloader): Looking for co-maintainers
On Fri, Jun 24, 2005 at 06:24:45PM +0200, Helge Kreutzmann wrote: Hello Peter, On Fri, Jun 24, 2005 at 01:58:27AM +0200, Peter De Schrijver wrote: I'm willing to help you out on this. I have 6 alpha machines (4 of which are debian supported now, the other 2 are turbo channel machines for which I did some work to get the linux kernel to work, but they aren't ready yet). I also maintain the quik package (oldworld powermac bootloader) and comaintain sibyl (Broadcom swarm bootloader). I'm familiar with alpha, mips, powerpc and arm architectures. I hope I can help you here. Great. Since I am not a DD, I will inform Steve Langasek, who did the uploads and helped me a great deal with all the packaging details. The first thing you can do is to check out our CVS from alioth (pkg-aboot). I'll ask Steve to add you to the group and get a little aqauinted with the source layout. Please ask if something is unclear, ... I cannot tell you the nitty gritty source details, but the overall layout and the purpose of the various tools/directories etc. I know. Yep, Peter is added to the alioth group (though of course, he didn't need that in order to become acquainted with the source layout :). Out of the bugs, I'd consider #270801 the most anyoing. Unfortunately, netabootwrap is not in the upstream source, hence we are on our own. That one's going to become more annoying with time, since initramfs generates consistently *smaller* images in 2.6 than initrd does... If you know how to add other FS, then #153666 might be fun for you. Upstream is a little reluctant, though, to add more and more file systems. Since a patch is available, the next thing would be to test, if possible, and add it in the next upload which could deal with the new policy version as well (haven't looked yet, what this would require). At the very least, it would be nice to have reliable ext3 support so that we aren't obliged to use a separate boot partition from d-i. I'm not as concerned about XFS support as I used to be, since ext3 in 2.6 has all the features I wanted previously. Cheers, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#315592: RFH aboot (Alpha bootloader): Looking for co-maintainers
Subject: RFH: aboot Package: wnpp Severity: normal I maintain aboot now for about 2 years, but unfortunately my private alpha run into serious problems late last year, and now I lost access to the university machines, so I currently cannot work on aboot. I am still interested in the alpha-architecture (and aboot), and will see if I can get my machine going again, but this will happen later this year as I just started a new job. I would like someone with an alpha and interest in keeping this architecture going in Debian to help me. There are not many bugs, and I tried to collect as much info as possible. I am still the (upstream) aboot-docu-maintainer, so if someone joins me I can try to coordinate future development (mainly bug fixing, and releasing version 1.0) with the upstream developers. And for someone with interest in file systems, there are wishlist bugs for more supported file systems to boot from :-)) -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.10-9-amd64-k8 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- Dr. Helge Kreutzmann, Dipl.-Phys. [EMAIL PROTECTED] gpg signed mail preferred 64bit GNU powered http://www.itp.uni-hannover.de/~kreutzm Help keep free software libre: http://www.ffii.de/ pgpLpLmYa0Ktg.pgp Description: PGP signature
Bug#315592: RFH aboot (Alpha bootloader): Looking for co-maintainers
Hi Helge, On Thu, Jun 23, 2005 at 09:47:57PM +0200, Helge Kreutzmann wrote: Subject: RFH: aboot Package: wnpp Severity: normal I maintain aboot now for about 2 years, but unfortunately my private alpha run into serious problems late last year, and now I lost access to the university machines, so I currently cannot work on aboot. I am still interested in the alpha-architecture (and aboot), and will see if I can get my machine going again, but this will happen later this year as I just started a new job. I would like someone with an alpha and interest in keeping this architecture going in Debian to help me. There are not many bugs, and I tried to collect as much info as possible. I am still the (upstream) aboot-docu-maintainer, so if someone joins me I can try to coordinate future development (mainly bug fixing, and releasing version 1.0) with the upstream developers. And for someone with interest in file systems, there are wishlist bugs for more supported file systems to boot from :-)) I'm willing to help you out on this. I have 6 alpha machines (4 of which are debian supported now, the other 2 are turbo channel machines for which I did some work to get the linux kernel to work, but they aren't ready yet). I also maintain the quik package (oldworld powermac bootloader) and comaintain sibyl (Broadcom swarm bootloader). I'm familiar with alpha, mips, powerpc and arm architectures. I hope I can help you here. Cheers, Peter (p2). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
