Re: debian-installer status 2002-11-22
On Fri Nov 22, 2002 at 04:07:01PM +0100, Tollef Fog Heen wrote: and PowerPC. Bdale started on ia64 last night. I've played around with getting it up and running on BSD, but no luck so far, busybox seems to be fairly Linux-centric. It is not a high priority, but if somebody picks it up, it would be good. Busybox devel (which I really should get packaged up) has the infrastructure needed to support multiple OSs... I don't plan to do the porting myself, since my plate is pretty full at the moment, but I can can certainly help to guide those wishing to do the port... -Erik -- Erik B. Andersen http://codepoet-consulting.com/ --This message was written using 73% post-consumer electrons--
Accepted busybox 1:0.60.5-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 Oct 2002 06:23:51 -0600 Source: busybox Binary: busybox busybox-static busybox-udeb Architecture: source i386 Version: 1:0.60.5-1 Distribution: unstable Urgency: low Maintainer: Erik Andersen [EMAIL PROTECTED] Changed-By: Erik Andersen [EMAIL PROTECTED] Description: busybox- Tiny utilities for small and embedded systems. busybox-static - Standalone rescue shell with tons of builtin utilities. busybox-udeb - Tiny utilities for the debian-installer (udeb) Closes: 163890 164178 164968 Changes: busybox (1:0.60.5-1) unstable; urgency=low . * New version released. See Changelog for non-Debian specific details. * zcat no longer tries to delete source files (closes: #164968) * Eliminate /linuxrc from the .udeb (closes: #163890) * Fix description of the --install option (closes: #164178) Files: 68c5b499e081df8bd0769545ec188756 620 - optional busybox_0.60.5-1.dsc 19249a75c3bfccd01ed40c50865ff7a7 785216 - optional busybox_0.60.5.orig.tar.gz a9d3a5f873c6a9d85382b56206b89e11 20 - optional busybox_0.60.5-1.diff.gz 3b8efffa89a43aacd0de4faa1cc734fc 126596 utils optional busybox_0.60.5-1_i386.deb 4872969b31538a8c288c443c81314bd7 477454 shells optional busybox-static_0.60.5-1_i386.deb 062d17d73a2d4a34937a54540a9ea81a 72004 debian-installer standard busybox-udeb_0.60.5-1_i386.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9vORgX5tkPjDTkFcRAmskAJwLHV6CxBlfjNqruVGQV3DC+jQr8ACgj9un aUM/lzBreRrL17F5oKQ5XBU= =U0TS -END PGP SIGNATURE- Accepted: busybox-static_0.60.5-1_i386.deb to pool/main/b/busybox/busybox-static_0.60.5-1_i386.deb busybox-udeb_0.60.5-1_i386.udeb to pool/main/b/busybox/busybox-udeb_0.60.5-1_i386.udeb busybox_0.60.5-1.diff.gz to pool/main/b/busybox/busybox_0.60.5-1.diff.gz busybox_0.60.5-1.dsc to pool/main/b/busybox/busybox_0.60.5-1.dsc busybox_0.60.5-1_i386.deb to pool/main/b/busybox/busybox_0.60.5-1_i386.deb busybox_0.60.5.orig.tar.gz to pool/main/b/busybox/busybox_0.60.5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted busybox 1:0.60.4-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 18 Sep 2002 14:13:05 -0600 Source: busybox Binary: busybox busybox-static busybox-udeb Architecture: source i386 Version: 1:0.60.4-1 Distribution: unstable Urgency: low Maintainer: Erik Andersen [EMAIL PROTECTED] Changed-By: Erik Andersen [EMAIL PROTECTED] Description: busybox- Tiny utilities for small and embedded systems. busybox-static - Standalone rescue shell with tons of builtin utilities. busybox-udeb - Tiny utilities for the debian-installer (udeb) Closes: 124388 127522 129626 138060 148396 158706 Changes: busybox (1:0.60.4-1) unstable; urgency=low . * New version released. See Changelog for non-Debian specific details. * enable uname for the debian-installer (closes: #158706) * enable losetup for the boot floppies (closes: #138060) * init behaves itself better consoles go missing (closes: #129626) * In 'free', buffers change as buffered data increases (closes: #148396) * Functions for debootstrap added to the .udeb (closes: #124388) * This bug is not reproducable (closes: #127522) Files: b5ce1cc5634a0c89b3993ffc5ef2a68b 555 - optional busybox_0.60.4-1.dsc 3a91388fa4ec1ef7b2ba66f0b570cc8b 716158 - optional busybox_0.60.4-1.tar.gz a69bdbddaa3b8242f3d62a0c34a28fe2 196940 utils optional busybox_0.60.4-1_i386.deb bafbfee9c43a95caff9438b5b0d87d5b 545814 shells optional busybox-static_0.60.4-1_i386.deb 9696a6aa9d54d6a82f350a93dfa33a49 71978 debian-installer standard busybox-udeb_0.60.4-1_i386.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9iORmX5tkPjDTkFcRAl1GAJ9Zte4cRKkX/bW0tGnZtAqQcj3yUQCgxg3a ojIl28QnFSi5rNkTjErcoGY= =U01M -END PGP SIGNATURE- Accepted: busybox-static_0.60.4-1_i386.deb to pool/main/b/busybox/busybox-static_0.60.4-1_i386.deb busybox-udeb_0.60.4-1_i386.udeb to pool/main/b/busybox/busybox-udeb_0.60.4-1_i386.udeb busybox_0.60.4-1.dsc to pool/main/b/busybox/busybox_0.60.4-1.dsc busybox_0.60.4-1.tar.gz to pool/main/b/busybox/busybox_0.60.4-1.tar.gz busybox_0.60.4-1_i386.deb to pool/main/b/busybox/busybox_0.60.4-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please test this woody cd image
On Fri Apr 12, 2002 at 11:35:31AM +1000, Drew Parsons wrote: I just tested it on all the bootable x86 systems in my house: ... Toshiba 490CDT Satellite Pro Laptop: Works That's good news. What was your success booting the Potato CD on this laptop? In my experience, the Toshiba laptops (the 490CDT in particular) would not boot the Potato CD. As far as I'm aware, this was because the boot image on the CD was based on a 2.88MB floppy image, where the Toshiba laptops could only handle a 1.44MB image. I'm impressed to hear Toshiba laptops can boot normally again :) I didn't try Potato on this laptop. Its on loan to me while doing some software development. But at least with the new isolinux boot CD, I just dropped in the CD and it booted just fine into the installer with both the default idepci and with the bf24 kernels -Erik -- Erik B. Andersen http://codepoet-consulting.com/ --This message was written using 73% post-consumer electrons-- pgpZEMLYBmH5s.pgp Description: PGP signature
Re: Please test this woody cd image
On Thu Apr 11, 2002 at 08:31:55PM +1000, Anthony Towns wrote: Seriously: everyone reading this mail, burn a copy of Raphael's test image on a CD and try booting it in any computers you have handy. If it doesn't work on a machine where a potato CD does boot, please mail the lists! I just tested it on all the bootable x86 systems in my house: Dell Latitude C800 laptop: Works Dell Webpc thing:Works Toshiba 490CDT Satellite Pro Laptop: Works Compaq Armada 7730MT Laptop: Works Desktop box (VIA KT266A chipset/Athlon): Works I'm pleased to report 100% success at booting using isolinux. -Erik -- Erik B. Andersen http://codepoet-consulting.com/ --This message was written using 73% post-consumer electrons-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please test this woody cd image
On Wed Apr 10, 2002 at 06:02:28PM -0400, Matt Zimmerman wrote: On Wed, Apr 10, 2002 at 11:23:26PM +0200, Eduard Bloch wrote: #include hallo.h Matt Zimmerman wrote on Wed Apr 10, 2002 um 04:45:08PM: 10 days != long enough to test a completely different _primary_ way of booting the installation system. a) isolinux is not completely new. It is syslinux, extended with ability of reading iso9660. Show me one failure (caused not by general problems, i.e. with some laptops not beeing able to boot _any_ mkisofs-made cdrom) and I will shut up. The burden of proof is on you, who want to make a change with such broad effect so late in the release cycle. I have never even tried isolinux, while I have used syslinux many times. Other distros (such as slackware and mandrake) are already using isolinux in their installers. I don't hear too many people complaining that those distro fail to boot from CD... -Erik -- Erik B. Andersen http://codepoet-consulting.com/ --This message was written using 73% post-consumer electrons-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Anybody want to adopt cdrecord?
On Wed Apr 03, 2002 at 10:03:24AM -0800, David D.W. Downey wrote: Looks like it doesn't matter anymore. I've been removed as the new maitnainer by erik due to the 2 week delay. Once again, I apologize for the delay on the package but it couldn't be helped. Hopefully I can assist on some other package. Sorry about that. The package needed some immediate attention. If I'd had the time, I'd have done it myself... As is Wish it could have been otherwise, -Erik -- Erik B. Andersen http://codepoet-consulting.com/ --This message was written using 73% post-consumer electrons-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Anybody want to adopt cdrecord?
On Wed Apr 03, 2002 at 03:52:10PM +0200, Eduard Bloch wrote: #include hallo.h Adam Byrtek wrote on Wed Apr 03, 2002 um 09:12:02AM: #131325: cdrecord: crashes on 2.2.20 It *has* to be fixed before Woody! In fact I'm still using old (1.9-1) cdrecord because of this bug... Yes, it has. Erik: What about that patch for cdrecord, needed to not to depend on the running kernel? Why cannot we have to versions, cdrecord-2.4.x and cdrecord-2.4.x? I have not had the time to work in it, so on March 21st I put cdrtools up for adoption. David Downey agreed to take over, but it has been 2 weeks since then and he hasn't yet bothered to upload a new package yet. Since he hasn't done that yet, I guess I'm still the nominal maintainer. As such, if someone else that _is_ willing to do that job and wants to take over As for the 2.4.x vs 2.2.x stuff, it would be easy to make a patch to test the mmap behavior at runtime and then do the right thing. I havn't had the time to write such a patch, but that would take care of the problem once and for all. Setting compile bahavior based on the kernel running on the compiling box is just lame, but thats what cdrecord does -Erik -- Erik B. Andersen http://codepoet-consulting.com/ --This message was written using 73% post-consumer electrons-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [debian-installer] microdpkg
On Sun Aug 20, 2000 at 09:25:14PM -0700, Joey Hess wrote: I think that just like dpkg, it should be split into two programs: microdpkg-deb to handles the low-level unpacking of packages, and microdpkg, to do dependency checking, and so on. Maybe this will turn out not to make sense; some space might be saved if the two were combined. On the other hand, Erik Anderson might want to put microdpkg-deb in busybox -- Erik? I'm very open to the idea, after we agree on how to approach it. Maybe I'm missing something though (I almost certainly am), but do we really need a 'microdpkg-deb'? Wouldn't just 'microdpkg' be enough? When we go to install the base system, we really just want to unpack the .debs and drop them into place. For this to take place we can do something like the following: #!/bin/sh # Lame 5 minute micro-dpkg shell script... # Erik Andersen [EMAIL PROTECTED] if [ -z $1 ]; then echo usage: udpkg packagename.deb exit 1; fi; FOO=`basename $1` PACKAGE=`echo $FOO | sed -e s/_.*//g` ROOT=/ DPKG_INFO_DIR=/var/lib/dpkg/info/ #For debugging only DPKG_INFO_DIR=/tmp/fff/info ROOT=/tmp/fff mkdir -p $DPKG_INFO_DIR ar -p $1 data.tar.gz | zcat | (cd $ROOT ; \ tar -xvf - $DPKG_INFO_DIR/$PACKAGE.list) ar -p $1 control.tar.gz | zcat | (cd $DPKG_INFO_DIR ; \ tar -xf - ) if [ -f $DPKG_INFO_DIR/postinst ] ; then mv $DPKG_INFO_DIR/postinst $DPKG_INFO_DIR/$PACKAGE.postinst fi if [ -f $DPKG_INFO_DIR/postrm ] ; then mv $DPKG_INFO_DIR/postrm $DPKG_INFO_DIR/$PACKAGE.postrm fi if [ -f $DPKG_INFO_DIR/preinst ] ; then mv $DPKG_INFO_DIR/preinst $DPKG_INFO_DIR/$PACKAGE.preinst fi if [ -f $DPKG_INFO_DIR/prerm ] ; then mv $DPKG_INFO_DIR/prerm $DPKG_INFO_DIR/$PACKAGE.prerm fi if [ -f $DPKG_INFO_DIR/md5sums ] ; then mv $DPKG_INFO_DIR/md5sums $DPKG_INFO_DIR/$PACKAGE.md5sums fi if [ -f $DPKG_INFO_DIR/control ] ; then mv $DPKG_INFO_DIR/control $DPKG_INFO_DIR/$PACKAGE.control fi exit 0; If we really wanted to be cool, we could even use parse the control file, check the depends and the md5sums and such. I suspect doing that is overkill though. -Erik -- Erik B. Andersen email: [EMAIL PROTECTED] --This message was written using 73% post-consumer electrons--
Re: Embedded Debian (was: compaq iPaq)
Quoting Ben Armstrong [EMAIL PROTECTED]: sort of configuration at compile-time would be a useful. Is busybox used anywhere else in Debian? It's curious that busybox isn't packaged separately. debian developer and author/maintainer of busybox hat on For woody, we are creating a new section of the Debian archive for the debian-installer (new name for the boot floppies). BusyBox will be a stand-alone package in that section (actually, there are two busybox packages -- busybox and busybox-static, which is statically linked with everything turned on for rescuing your system when it is hosed). To build .debs of busybox, grab the source (either from CVS on opensource.lineo.com, or from released tarballs) just run 'dpkg-buildpackage' and it'll build. Next week as we start ramping up for woody, the new archive section will probably be showing up on mirrors and busybox .debs will be there. The source code in the boot floppies CVS tree is out of date, since we froze it quite a while ago, and has a number of bugs (none release critical, but some a bit annoying) that are fixed in the latest and greatest... -Erik -- Erik B. Andersen Web:http://www.xmission.com/~andersen/ email: [EMAIL PROTECTED] --This message was written using 73% post-consumer electrons--
Twin v3.1.5
Hi folks, Twin, the cross-platform windows emulator and development libs, has recently had version v3.1.5 released. I have been planning on packing it up, but now that this release is finally out, I find that I am absolutely swamped at my work! If anybody wants to pack it up for Debian, please feel free. See http://www.willows.com for details. -Erik -- Erik B. Andersen Web:http://www.inconnect.com/~andersen/ email: [EMAIL PROTECTED] --This message was written using 73% post-consumer electrons-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Policy based on the wrong technical assumptions
On Jun 29, Fernando wrote I fear the Documentation Policy is being based on the wrong technical assumptions. The fact is that what slows down HTML in an old system is not a web server or the cgi converters. It is the browser! [-stuff snipped-] Thanks, Fernando. Elvis (the vi clone) reads man pages and html, and formats them and displays them in color (unless you don't want that). In the latest beta version, which I havn't packaged up, it even will browse the web (the stable version only reads local files). -Erik -- Erik B. Andersen Web:http://www.inconnect.com/~andersen/ email: [EMAIL PROTECTED] --This message was written using 73% post-consumer electrons-- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dc and bc in Important?
On Jun 28, Carey Evans wrote [EMAIL PROTECTED] (Erik B. Andersen) writes: [snip] For most math, expr works just fine. Of course, expr is limited to integer math, but it works and is portable. Actually, for integer math, bash or ksh works quite well. bash$ a=41 bash$ let a+=1 bash$ echo $a 42 -- Carey Evans * [EMAIL PROTECTED] iThis is correct, but has the unfortunate side effect of not being portable, since not all /bin/sh happin to be bash. If you want to allow the program to run on non-Linux machines, or machines running ash, etc. then expr is the most portable way. If you don't care about using bash-isms, which is often the case for Debian, then what you describe above is much easier. -Erik -- Erik B. Andersen Web:http://www.inconnect.com/~andersen/ email: [EMAIL PROTECTED] --This message was written using 73% post-consumer electrons-- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
