Re: (forw) #240677 shadow: FTBFS: cannot compile sub.c
On Sun, Mar 28, 2004 at 10:28:49PM +0200, Christian Perrier wrote:
This happend while I was trying to build a NMU for getting all shadow
translations out of BTS
Can someone with more coding skills than me have a look at it?
- Forwarded message from Christian Perrier [EMAIL PROTECTED] -
...
if /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../lib
-O2 -Wall -MT sub.lo -MD -MP -MF .deps/sub.Tpo \
-c -o sub.lo `test -f 'sub.c' || echo './'`sub.c; \
then mv -f .deps/sub.Tpo .deps/sub.Plo; \
else rm -f .deps/sub.Tpo; exit 1; \
fi
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../lib -O2 -Wall -MT sub.lo -MD -MP -MF
.deps/sub.Tpo -c sub.c -o sub.o
sub.c: In function `subsystem':
sub.c:81: error: increment of read-only member `pw_shell'
make[3]: *** [sub.lo] Erreur 1
make[3]: quittant le r?pertoire ?
/home/bubulle/src/debian/shadow/shadow-4.0.3/libmisc ?
make[2]: *** [all-recursive] Erreur 1
make[2]: quittant le r?pertoire ? /home/bubulle/src/debian/shadow/shadow-4.0.3 ?
make[1]: *** [all] Erreur 2
make[1]: quittant le r?pertoire ? /home/bubulle/src/debian/shadow/shadow-4.0.3 ?
make: *** [build] Erreur 2
GCC has become much more sensitive about writes to read-only
variables recently. The attached patch should fix the problem.
--
Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/
diff -ru shadow-4.0.3-old/lib/prototypes.h shadow-4.0.3/lib/prototypes.h
--- shadow-4.0.3-old/lib/prototypes.h 2004-03-29 00:27:22.0 -0800
+++ shadow-4.0.3/lib/prototypes.h 2004-03-29 00:29:58.0 -0800
@@ -203,7 +203,7 @@
extern void sulog(const char *, int, const char *, const char *);
/* sub.c */
-extern void subsystem(const struct passwd *);
+extern void subsystem(struct passwd *);
/* ttytype.c */
extern void ttytype(const char *);
diff -ru shadow-4.0.3-old/libmisc/sub.c shadow-4.0.3/libmisc/sub.c
--- shadow-4.0.3-old/libmisc/sub.c 2004-03-29 00:27:22.0 -0800
+++ shadow-4.0.3/libmisc/sub.c 2004-03-29 00:29:39.0 -0800
@@ -51,7 +51,7 @@
*/
void
-subsystem(const struct passwd *pw)
+subsystem(struct passwd *pw)
{
/*
* The new root directory must begin with a / character.
linux-kernel-di-386_0.57_i386.changes ACCEPTED
Accepted: brltty-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/brltty-modules-2.4.24-speakup-di_0.57_i386.udeb brltty-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/brltty-modules-2.4.25-1-386-di_0.57_i386.udeb cdrom-core-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/cdrom-core-modules-2.4.24-speakup-di_0.57_i386.udeb cdrom-core-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/cdrom-core-modules-2.4.25-1-386-di_0.57_i386.udeb cdrom-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/cdrom-modules-2.4.24-speakup-di_0.57_i386.udeb cdrom-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/cdrom-modules-2.4.25-1-386-di_0.57_i386.udeb ext3-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/ext3-modules-2.4.24-speakup-di_0.57_i386.udeb ext3-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/ext3-modules-2.4.25-1-386-di_0.57_i386.udeb fat-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/fat-modules-2.4.24-speakup-di_0.57_i386.udeb fat-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/fat-modules-2.4.25-1-386-di_0.57_i386.udeb fb-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/fb-modules-2.4.24-speakup-di_0.57_i386.udeb fb-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/fb-modules-2.4.25-1-386-di_0.57_i386.udeb firewire-core-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/firewire-core-modules-2.4.24-speakup-di_0.57_i386.udeb firewire-core-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/firewire-core-modules-2.4.25-1-386-di_0.57_i386.udeb floppy-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/floppy-modules-2.4.24-speakup-di_0.57_i386.udeb floppy-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/floppy-modules-2.4.25-1-386-di_0.57_i386.udeb ide-core-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/ide-core-modules-2.4.24-speakup-di_0.57_i386.udeb ide-core-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/ide-core-modules-2.4.25-1-386-di_0.57_i386.udeb ide-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/ide-modules-2.4.24-speakup-di_0.57_i386.udeb ide-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/ide-modules-2.4.25-1-386-di_0.57_i386.udeb input-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/input-modules-2.4.24-speakup-di_0.57_i386.udeb input-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/input-modules-2.4.25-1-386-di_0.57_i386.udeb ipv6-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/ipv6-modules-2.4.24-speakup-di_0.57_i386.udeb ipv6-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/ipv6-modules-2.4.25-1-386-di_0.57_i386.udeb irda-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/irda-modules-2.4.24-speakup-di_0.57_i386.udeb irda-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/irda-modules-2.4.25-1-386-di_0.57_i386.udeb isa-pnp-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/isa-pnp-modules-2.4.24-speakup-di_0.57_i386.udeb isa-pnp-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/isa-pnp-modules-2.4.25-1-386-di_0.57_i386.udeb jfs-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/jfs-modules-2.4.24-speakup-di_0.57_i386.udeb jfs-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/jfs-modules-2.4.25-1-386-di_0.57_i386.udeb kernel-image-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/kernel-image-2.4.24-speakup-di_0.57_i386.udeb kernel-image-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/kernel-image-2.4.25-1-386-di_0.57_i386.udeb linux-kernel-di-386_0.57.dsc to pool/main/l/linux-kernel-di-386/linux-kernel-di-386_0.57.dsc linux-kernel-di-386_0.57.tar.gz to pool/main/l/linux-kernel-di-386/linux-kernel-di-386_0.57.tar.gz loop-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/loop-modules-2.4.24-speakup-di_0.57_i386.udeb loop-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/loop-modules-2.4.25-1-386-di_0.57_i386.udeb md-modules-2.4.24-speakup-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/md-modules-2.4.24-speakup-di_0.57_i386.udeb md-modules-2.4.25-1-386-di_0.57_i386.udeb to pool/main/l/linux-kernel-di-386/md-modules-2.4.25-1-386-di_0.57_i386.udeb nic-extra-modules-2.4.24-speakup-di_0.57_i386.udeb to
powerpc beta3 update installation report
Package: installation-reports INSTALL REPORT Debian-installer-version: 20040329, sarge_d-i businesscard uname -a: Linux cairhien 2.6.1-rc1-ben1 #1 Fri Jan 2 16:57:27 GMT 2004 ppc GNU/Linux (normal system, not newly installed system, sorry) Date: 2004-03-29 10:10 Method: CD-RW, ftp.uk.debian.org, local HTTP proxy Machine: Aluminium PowerBook G4 15 Processor: PPC 1GHz Memory: 512MB Root Device: IDE, /dev/hda10 Root Size/partition table: /dev/hda #type name length base ( size ) system /dev/hda1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hda2 Apple_Driver43 Macintosh 56 @ 64( 28.0k) Driver 4.3 /dev/hda3 Apple_Driver43 Macintosh 56 @ 120 ( 28.0k) Driver 4.3 /dev/hda4Apple_Driver_ATA Macintosh 56 @ 176 ( 28.0k) Unknown /dev/hda5Apple_Driver_ATA Macintosh 56 @ 232 ( 28.0k) Unknown /dev/hda6 Apple_FWDriver Macintosh512 @ 288 (256.0k) Unknown /dev/hda7 Apple_Driver_IOKit Macintosh512 @ 800 (256.0k) Unknown /dev/hda8 Apple_Patches Patch Partition 512 @ 1312 (256.0k) Unknown /dev/hda9 Apple_Bootstrap bootstrap 1600 @ 1824 (800.0k) NewWorld bootblock /dev/hda10Apple_UNIX_SVR2 swap 1048576 @ 3424 (512.0M) Linux swap /dev/hda11Apple_UNIX_SVR2 root62914560 @ 1052000 ( 30.0G) Linux native /dev/hda12Apple_UNIX_SVR2 spare 27879120 @ 63966560 ( 13.3G) Linux native /dev/hda13 Apple_HFS Mac OS X25364552 @ 91845680 ( 12.1G) HFS /dev/hda14 Apple_Free8 @ 117210232 ( 4.0k) Free space # installed to swap Output of lspci: 00:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 AGP 00:10.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4e50 01:0b.0 Host bridge: Apple Computer Inc.: Unknown device 0035 01:12.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev 03) 01:13.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller 01:17.0 Class ff00: Apple Computer Inc.: Unknown device 003e 01:18.0 USB Controller: Apple Computer Inc.: Unknown device 003f 01:19.0 USB Controller: Apple Computer Inc.: Unknown device 003f 01:1a.0 USB Controller: Apple Computer Inc.: Unknown device 003f 01:1b.0 USB Controller: NEC Corporation USB (rev 43) 01:1b.1 USB Controller: NEC Corporation USB (rev 43) 01:1b.2 USB Controller: NEC Corporation USB 2.0 (rev 04) 06:0b.0 Host bridge: Apple Computer Inc.: Unknown device 0036 06:0d.0 Class ff00: Apple Computer Inc.: Unknown device 003b 06:0e.0 FireWire (IEEE 1394): Apple Computer Inc. UniNorth 2 FireWire (rev 81) 06:0f.0 Ethernet controller: Apple Computer Inc. UniNorth 2 GMAC (Sun GEM) (rev 80) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: I actually did two installs here, one with the 20040328 businesscard with an ofboot.b hacked by me so that it would boot, and one with the fixed businesscard manty produced this morning. I didn't have time for a full install this morning since I had to go to work. However, I ran last night's install to completion, and this morning's image booted successfully and got up to base-installer. Since I was installing from testing, I think that's sufficient. kbd-chooser didn't do anything, and hasn't done on powerpc for a while; this was probably #240171, fixed in kbd-chooser 0.47, but I haven't tested that version yet. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
iso-codes's change cause a countrychooser error
Hello, Since iso-codes changed Taiwan to Taiwan, Province of China, the whole pharse are showed as two seperated choices. Please look at the screenshot: http://linuxfire.dhis.org/~carlos/screenshots/countrychooser_err.png Thanks. -- Best Regards, Carlos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian installer for Apple XServe
Sven Luther wrote: Researching the 'missing driver' a bit further, it actually looks like the config option that is needed is: CONFIG_BLK_DEV_PDC202XX_NEW=y This driver supports the Promise Ultra 100 TX2 [PDC20268], which seems to be the IDE device to which the harddisks are attached. So, what is the status on that one? Not builtin, but i am going to modify that now. When will this be included in the nightly then? I would love to try if this works, but rather not waste any time on downloading and burning an image that does not have this setting included. Regards, Pepijn. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240797: powerpc beta3 update installation report
Package: installation-reports INSTALL REPORT Debian-installer-version: 20040329, sarge_d-i businesscard uname -a: Linux cairhien 2.6.1-rc1-ben1 #1 Fri Jan 2 16:57:27 GMT 2004 ppc GNU/Linux (normal system, not newly installed system, sorry) Date: 2004-03-29 10:10 Method: CD-RW, ftp.uk.debian.org, local HTTP proxy Machine: Aluminium PowerBook G4 15 Processor: PPC 1GHz Memory: 512MB Root Device: IDE, /dev/hda10 Root Size/partition table: /dev/hda #type name length base ( size ) system /dev/hda1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hda2 Apple_Driver43 Macintosh 56 @ 64( 28.0k) Driver 4.3 /dev/hda3 Apple_Driver43 Macintosh 56 @ 120 ( 28.0k) Driver 4.3 /dev/hda4Apple_Driver_ATA Macintosh 56 @ 176 ( 28.0k) Unknown /dev/hda5Apple_Driver_ATA Macintosh 56 @ 232 ( 28.0k) Unknown /dev/hda6 Apple_FWDriver Macintosh512 @ 288 (256.0k) Unknown /dev/hda7 Apple_Driver_IOKit Macintosh512 @ 800 (256.0k) Unknown /dev/hda8 Apple_Patches Patch Partition 512 @ 1312 (256.0k) Unknown /dev/hda9 Apple_Bootstrap bootstrap 1600 @ 1824 (800.0k) NewWorld bootblock /dev/hda10Apple_UNIX_SVR2 swap 1048576 @ 3424 (512.0M) Linux swap /dev/hda11Apple_UNIX_SVR2 root62914560 @ 1052000 ( 30.0G) Linux native /dev/hda12Apple_UNIX_SVR2 spare 27879120 @ 63966560 ( 13.3G) Linux native /dev/hda13 Apple_HFS Mac OS X25364552 @ 91845680 ( 12.1G) HFS /dev/hda14 Apple_Free8 @ 117210232 ( 4.0k) Free space # installed to swap Output of lspci: 00:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 AGP 00:10.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4e50 01:0b.0 Host bridge: Apple Computer Inc.: Unknown device 0035 01:12.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev 03) 01:13.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller 01:17.0 Class ff00: Apple Computer Inc.: Unknown device 003e 01:18.0 USB Controller: Apple Computer Inc.: Unknown device 003f 01:19.0 USB Controller: Apple Computer Inc.: Unknown device 003f 01:1a.0 USB Controller: Apple Computer Inc.: Unknown device 003f 01:1b.0 USB Controller: NEC Corporation USB (rev 43) 01:1b.1 USB Controller: NEC Corporation USB (rev 43) 01:1b.2 USB Controller: NEC Corporation USB 2.0 (rev 04) 06:0b.0 Host bridge: Apple Computer Inc.: Unknown device 0036 06:0d.0 Class ff00: Apple Computer Inc.: Unknown device 003b 06:0e.0 FireWire (IEEE 1394): Apple Computer Inc. UniNorth 2 FireWire (rev 81) 06:0f.0 Ethernet controller: Apple Computer Inc. UniNorth 2 GMAC (Sun GEM) (rev 80) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: I actually did two installs here, one with the 20040328 businesscard with an ofboot.b hacked by me so that it would boot, and one with the fixed businesscard manty produced this morning. I didn't have time for a full install this morning since I had to go to work. However, I ran last night's install to completion, and this morning's image booted successfully and got up to base-installer. Since I was installing from testing, I think that's sufficient. kbd-chooser didn't do anything, and hasn't done on powerpc for a while; this was probably #240171, fixed in kbd-chooser 0.47, but I haven't tested that version yet. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iso-codes's change cause a countrychooser error
Quoting Carlos Z.F. Liu ([EMAIL PROTECTED]):
Hello,
Since iso-codes changed Taiwan to Taiwan, Province of China, the
whole pharse are showed as two seperated choices.
Please look at the screenshot:
http://linuxfire.dhis.org/~carlos/screenshots/countrychooser_err.png
Hmmm. I took care of this in the full list build by replacing , by
- . However, this was forgotten in postinst where the short list is
built dynamically.
The attached patch should solve this (untested).
--- postinst.old2004-03-23 19:26:38.0 +0100
+++ postinst2004-03-29 13:25:40.0 +0200
@@ -49,7 +49,7 @@
}
country2code() {
- COUNTRYNAME=$(echo $1 | sed s/^$INDENT//)
+ COUNTRYNAME=$(echo $1 | sed s/^$INDENT// | sed s/ - /, /g)
line=`grep $COUNTRYNAME$ $countries`
if [ -n $line ]; then
@@ -123,7 +123,7 @@
set $line
IFS=$OLD_IFS
if [ $2 ]; then
- countryname=${INDENT}$2;
+ countryname=$(echo
${INDENT}$2 | sed s/, / - /g)
fi
if [ ! -z ${SHORTLIST} ]; then
SHORTLIST=${SHORTLIST},
debian-boot@lists.debian.org
http://www.8power.net/index.asp?user=linlin email ! []http://sesoft.k900.com [][][]http://oysoft.k456.com
Re: iso-codes's change cause a countrychooser error
Quoting Christian Perrier ([EMAIL PROTECTED]): The attached patch should solve this (untested). Now tested and seems to work. I commit the change -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: powerpc beta3 update installation report
On Mon, Mar 29, 2004 at 11:23:42AM +0100, Colin Watson wrote: Package: installation-reports INSTALL REPORT Sorry for this duplicate; I meant to send it to the BTS, but hadn't had enough caffeine yet. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian installer for Apple XServe
On Mon, Mar 29, 2004 at 12:34:57PM +0200, Pip Oomen wrote: Sven Luther wrote: Researching the 'missing driver' a bit further, it actually looks like the config option that is needed is: CONFIG_BLK_DEV_PDC202XX_NEW=y This driver supports the Promise Ultra 100 TX2 [PDC20268], which seems to be the IDE device to which the harddisks are attached. So, what is the status on that one? Not builtin, but i am going to modify that now. When will this be included in the nightly then? I would love to try if this works, but rather not waste any time on downloading and burning an image that does not have this setting included. Mmm, i will have to do a new build. We are currently busy with other stuff, but i will see what i can do. Mmm, the -4 is in testing now, so it should be ok. There is some time needed until it appears in the nightly build though. I need to build and upload (takes me around 6 hours or so, will probably miss this evenings dinstall run), then once it is in the archive, a .udeb needs to be build (one more day), and then debian-installer needs to be built, and finally the image needs to be generated. Probably it will be ok by next weekend, but mail me first for confirmation. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Create bootable CD with custom kernel
I am currently trying to get Debian running on an Apple Xserve G4/133DP, but, as discussed with Sven Luther, it turns out the current pmac kernel does not include the correct IDE driver. While the change in the kernel makes its way into the nightlies, I was wondering if it is possible to build my own CD image. One thing that is complicating this however, is the fact that the building process is not capable of cross-building, and I am currently lacking any PPC machine to do the build on, although I did succeed in cross-compiling the kernel. Now, is anyone aware of a way to take today's nightly and somehow replace the kernel image with one I built myself? Kind regards, Pepijn. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Delivery Bot (debian-boot@lists.debian.org)
Delivery Agent - Translation failed - failed message - J%H|kK9agLEQjBJ-k'Twz9x!8gQO2$tRUuqyroZ_ OqG0xVn8v+C09e%40wr8z!irF0%~#'Gfu#$pk|osl %hn2T$m0gE_7M-t76xpGZcNw'c,;'*Z,6B|4 J0sH?mvnf:|(+van;ZSRA.r'*KIVN% The message has been sent as a binary attachment. -- Virus Warning Message (on the network) message24052.pif is removed from here because it contains a virus. --- Virus Warning Message (on the network) (B (BFound virus WORM_NETSKY.Q in file message24052.pif (BThe file is deleted. (B (BTherefore we removed the attachment-file (Bby Mail Server and sent the message to you. (B (B(Japanese) $BK\%a!<%k$KE:IU$5$l$F$$$?%U%!%$%k$K%&%#%k%9$,[EMAIL PROTECTED](B $B$=$N$?$a!"%a!<%k%5!<%P$K$h$C$FE:IU%U%!%$%k$r
Re: Create bootable CD with custom kernel
On Mon, Mar 29, 2004 at 01:39:02PM +0200, Pip Oomen wrote: I am currently trying to get Debian running on an Apple Xserve G4/133DP, but, as discussed with Sven Luther, it turns out the current pmac kernel does not include the correct IDE driver. While the change in the kernel makes its way into the nightlies, I was wondering if it is possible to build my own CD image. One thing that is complicating this however, is the fact that the building process is not capable of cross-building, and I am currently lacking any PPC machine to do the build on, although I did succeed in cross-compiling the kernel. Now, is anyone aware of a way to take today's nightly and somehow replace the kernel image with one I built myself? Not an easy thing. Probably, if you built it in, you can just use the new vmlinux, you need to use the exact same config though, and there is chance that the symbols will not change, and thus the initrd should be ok. No guarantee though, as the module and versioned symbols stuff is still mostly black magic for me. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240669: Source of this problem
The problem here is the new code in 6.2.5-5 to only run in daemon mode if the global config doesn't. Unfortunately, the default /etc/fetchmailrc file contains a commented out daemon 300 line, which the grep -qs check is picking up, AFAICT. Anyway, uncommenting the line in /etc/fetchmailrc makes it daemonise again In fact, upon examination, it doesn't appear to be using /etc/default/fetchmailrc anymore... dpkg says it doesn't own it anymore, so the comment in /usr/share/doc/fetchmail/examples/fetchmailrc.example needs to be fixed, and possibly some kind of notice in NEWS.Debian so people know to delete /etc/default/fetchmail and fix /etc/fetchmailrc -- Paul TBBle Hampson, [EMAIL PROTECTED] 6th year CompSci/Asian Studies student, ANU Shorter .sig for a more eco-friendly paperless office. signature.asc Description: Digital signature
Re: r12047 - trunk/packages/cdrom-detect/debian/po
On Sun, Mar 28, 2004 at 07:22:25PM -0700, Tetralet wrote: Author: tetralet-guest Date: Sun Mar 28 19:22:25 2004 New Revision: 12047 Modified: trunk/packages/cdrom-detect/debian/po/zh_TW.po Log: Updated Traditional Chinese (zh_TW) translation Please use one revision per update, not 20. Bastian -- Women professionals do tend to over-compensate. -- Dr. Elizabeth Dehaver, Where No Man Has Gone Before, stardate 1312.9. signature.asc Description: Digital signature
compra de cartuchos compativeis
Lista de preços
unsubscribe
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i and 2.6
[let's move this to -boot] * Jeff Bailey [EMAIL PROTECTED] [2004-03-29 09:13]: On Mon, 2004-03-29 at 09:06, Martin Michlmayr wrote: Do you know the status of Linux 2.6 and debian-installer? Someone would be interested in adding Altix support to d-i but this needs a 2.6 Itanium kernel. If you boot in expert mode on i386, it prompts you with a list of kernels to choose from. I've never tried it on ia64, but at least the mechanism exists. Note that this is just limited 2.6 support: It's not setting up udev or hotplug, but does install discover2 anyway, which should handle most of what you need. Has anyone tested a 2.6 installation yet? Someone would be interested in adding support for the SGI Altix, but this needs a 2.6 kernel. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240760: Bootloader
Something I forgot to mention. Currently, no boot loader is installed. What I'd ideally like to see is a program which detects whether the Netwinder or CATS firmware is present, and then sets various values in the firmware after asking the user if that's okay. (At least, we should display one page telling the user how to set the firmware and boot the system; but ideally, we would set it for them.) -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
get sp0rts at nocost
Title: New Details Completely Fr'ee Di'gital Ca'ble Fr'ee PP'V, Sp'orts, Mo'vies and mo're! To find out more, cl'ick image or Visit us Here. earthshaking geodetic pluggable diffractometer burlesque buck pickett aversion cupric marino aqueous topgallant catnip woodcarver shoehorn cdc bellingham bagel rigging arraign hepatitis bidden bellum puffed analogous bloodbath southbound toil carryover loeb samba staple despite decontrol thunderflower groggy ugly revoke carve nutritive parade afoot firecracker accommodate pocus butyrate canterelle bulky pizzeria betty duane bean mantel budweiser tiffany apply macintosh hull gape robbery dugout amplify purslane resolve carnival betsey gleason fiddle bruno emily adiabatic dragnet butterball decipher jacobs vortices property columbia quench crossword appease drape sleek northrup infiltrate cling constrictor trickster introversion dissension dysprosium arid bamberger napkin corrugate mafia inventory pixel draw neutral affiliate infertile wide chloroform choke java mclean titian talisman magician amaranth chantilly brandeis frugal nazarene earth hastings serology reverberate wraith glamorous sweaty gibbet whipple odd trig brain vow severalfold mobcap elastic antigorite bridgetown emasculate beebread camelback davenport inholding allege annotate awesome compound health blackbody java tommie squeegee august share cannon dadaist retrogressive anthropology intent jules
Bug#240697: acknowledged by developer (closing)
C. Gatzemeier wrote: To provide for both ends I'd suggest: -- Have prerelease installs default to point to the fixed name (sarge) -- At release time change installation default to point to stable as usual, and issue a security patch to change explicit sarge systems to point to stable. No, we can't afford to need to release an entire new version of the installer at release time. We must be able to freeze it and do serious testing of the actual version we release. -- see shy jo signature.asc Description: Digital signature
Bug#240842: Sarge i386 netinst can't configure PCMCIA network card
Package: installation-reports Debian-installer-version: http://gluck.debian.org/cdimage/testing/sarge_d-i/i386/beta3/sarge-i386-netinst.iso uname -a: Linux rumba 2.4.25-1-686 #1 Tue Feb 24 10:55:59 EST 2004 i686 GNU/Linux Date: 2004-03-29, 10:00 UTC Method: Boot from above mentioned ISO image Machine: IBM Thinkpad 600E with xirc2ps_cs network card Processor: Mobile Pentium II, 400 MHz Memory: 24 kB Root Device: TOSHIBA CD-ROM XM-1902B on /dev/hdc Root Size/partition table: FilesystemSize Used Avail Use% Mounted on /dev/hda1 4.2G 2.0G 2.1G 49% / tmpfs 142M 0 142M 0% /dev/shm /dev/hda3 4.7G 2.4G 2.1G 54% /home Output of lspci: pcilib: Cannot open /sys/bus/pci/devices :00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) :00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) :00:02.0 CardBus bridge: Texas Instruments PCI1251A :00:02.1 CardBus bridge: Texas Instruments PCI1251A :00:06.0 Multimedia audio controller: Cirrus Logic CS 4610/11 [CrystalClear SoundFusion Audio Accelerator] (rev 01) :00:07.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) :00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) :00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) :00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02) :01:00.0 VGA compatible controller: Neomagic Corporation NM2200 [MagicGraph 256AV] (rev 20) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [E] Config network: [E] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [E] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: The problem was that it couldn't configure the network. Going into a shell showed that cardmgr would say no sockets found!, like this: Mar 26 17:22:18 rumba cardmgr[836]: starting, version is 3.1.33 Mar 26 17:22:19 rumba cardmgr[836]: no sockets found! Mar 26 17:22:19 rumba cardmgr[836]: exiting Originally, I thought it was the wrong kernel module. I tried many things, most of which I've forgotten now. But then, I managed to upgrade the whole system to unstable, and that did it. I /think/ it was the upgrade of pcmcia-cs to 3.2.5-2.5, but of course I'm not sure whether it was this package or perhaps another package. I'm reluctant to wipe the installation to try again, with just the newer pcmcia-cs. (This is my main machine that I need to work on every day.) But if you make a new image with the more recent pcmcia-cs included, then I can try to boot it to see if that fixes the problem. I hope I managed to describe this well enough. In the best luser manner, I managed not to keep track of what I did. Maybe I can convince myself to try another install, now that I know how to fix it... Kai -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iso-codes's change cause a countrychooser error
On Mon, Mar 29, 2004 at 01:37:41PM +0200, Christian Perrier wrote: Quoting Christian Perrier ([EMAIL PROTECTED]): The attached patch should solve this (untested). Now tested and seems to work. I commit the change Thanks. -- Best Regards, Carlos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240760: Bootloader
On Mon, Mar 29, 2004 at 03:03:12PM +0100, Martin Michlmayr wrote: Something I forgot to mention. Currently, no boot loader is installed. What I'd ideally like to see is a program which detects whether the Netwinder or CATS firmware is present, and then sets various values in the firmware after asking the user if that's okay. (At least, we should display one page telling the user how to set the firmware and boot the system; but ideally, we would set it for them.) Notice that the nobootloader package does this partially, that is it informs the user what the root partition is. Ideally, we would have a per arch/subarch switch there, and give more precise information if possible. Like for powerpc/chrp/pegasos, we have to type in the OF : boot ide:0 vmlinuz-2.4.25-powerpc root=/dev/hda3 If /boot is mounted as first partition of the first IDE drive, and root is on partition 3 of the same. This would be usefull and easy enough to go, so feel free to add the needed info for arm hardware in there, until you can set it directly. Maybe we can then spawn another binary package from nobootloader, which would then set those firmware values or something. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tasks overrides update
Konstantinos Margaritis wrote: please, what do I have to do to have the task overrides list updated? I have setup a 'greek' task in tasksel that doesn't work because tasksel doesn't find any available packages (#235433, #238765). This is since Jan 28, 2 months ago. Whom do I have to beg for this? (I have an idea, but I'll double check, wishful thinking :-) It was in unstable but not testing, this should be fixed on the next dinstall run. -- see shy jo signature.asc Description: Digital signature
Bug#239133: using 3-28-04 iso image sarge-m68k-businesscard.iso 3-29-04 mac hd-media images
Seems like you're making progress. ext3 filesystem option shows up when formatting. Installation of packages from the mounted iso image is successful until it says it can't find a a valid kernel image during the base installation. At which point the install reverts back to the screen with about 20 options: partition a disk, install the base system, etc. At that point I had about 90 MB installed on the /target/ partition. I rebooted the system at that point. I tried using my own kernel and modules by copying them from another working system on a different scsi dri ve. I managed to boot into a prompt after changing the /etc/fstab file to mount the root and swap partitions: the fstab file only had two comment lines in with no entries to mount any file systems. But I could proceed no further: I was asked for a password which the system had not set up. I tried entering a blank password for root, but that didn't work. Apparently, the business card iso is lacking kernel images for the mac kernel? Hank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: default group issue
Package: adduser Severity: wishlist Joey Hess wrote: So he just wants some infrastructure around this. That seems reasonable. How about something like this: - Add to adduser.conf a CONSOLEGROUPS variable, defaulting to CONSOLEGROUPS=audio cdrom dialout floppy video - Add a --console-user flag to adduser, which creates the user in that set of groups. - Make passwd's config script pass --console-user when calling adduser. Of course we'll need Roland Bauerschmidt to decide about the adduser changes. A preliminary adduser patch is attached. (Now, in the meantime, I'd not mind putting a quick fix in base-config, but only if we have plans to do the real fix and later back that out.) It seems to me that this feature is still too specific to that particular application. I'd prefer having a more generic template mechanism with a few common templates predefined (such as 'system' or 'console'). Anyway, as some concepts in adduser would have to be rethought for that to implement, I believe it's too big a change for sarge (assuming we'll release this year...). The other problem I see with your suggested option is that it won't be widely known for some time. I guess most users that come some so far to figure out there's a --console-user option would've added the user to the groups manually before. With a more generic template mechanism, I think it would be sensible to prompt for the kind of user that is to be added when adduser is called in interactive mode. Despite those considerations, I see that you probably need something to work with for sarge. If you really want that feature for sarge, I'd be willing to add the suggested option and make it an alias to '--template console' once that's implemented. Thoughts? Roland (I'll be on vacation for about a week, leaving Wednesday; so I'm not gonna be able to answer during that time) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240372: SPARCstation 5 installation report
Joshua Kwan wrote: On Fri, 26 Mar 2004 17:03:00 -0700, Peter Karbaliotis wrote: WARNING: Your /etc/fstab does not contain the fsck passno field. I will kludge around things for you, but you should fix your /etc/fstab file as soon as you can. And then the boot hangs because the root filesystem is read-only Could you attach the fstab file from the machine if that's possible? Sorry about the delay, but I didn't have a chance to get at the system until today. The fstab contains just the following: # UNCONFIGURED FSTAB FOR BASE SYSTEM -- [EMAIL PROTECTED] 780-492-7660 Computing and Network Services University of Alberta -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: default group issue
Roland Bauerschmidt wrote: Despite those considerations, I see that you probably need something to work with for sarge. If you really want that feature for sarge, I'd be willing to add the suggested option and make it an alias to '--template console' once that's implemented. Yes, we would like to have something for sarge. -- see shy jo signature.asc Description: Digital signature
Re: Release update
(copy to Alastair McKinstry as slang packages maintainer, Shlomi Loubaton as current worker on BIDI support for d-i and -boot as this concern comes from Debian Installer needs) * As of now, no new packages will be added to the base system. This means that packages in the base system *must not* change their package relationships. * Large changes to the base system must be cleared with the release team and the d-i team before being uploaded to unstable. The recent work on BIDI (bi-directional language support), aimed at getting right-to-left languages support in Debian Installer, is likely to induce changes to slang packages. One of these will probably make some slang1 packages depend on libfribidi0. I'm not sure of this because I'm not the one who tried to implement BIDI support in slang (Shlomi Loubaton is), but I highly suspect this. As a side effect this would make libfribidi0 a candidate for being in the base system. Thus, I prefer mention all this as soon as possible, of course... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA network configuration
On Sun, Mar 28, 2004 at 20:27 -0500, Joey Hess wrote:
Per Olofsson wrote:
(Please CC me on replies.)
1. Change /etc/pcmcia/network{,.opts} to somehow tell netcfg that a
particular interface is a PCMCIA network card and then modify
netcfg so that it doesn't add the auto option on these interfaces.
This seems to be the straightforward way to do it.
Yes. And as you said, the other ones are more post-sarge
approaches. So let's go with this one.
Now, how to implement this? What first comes to mind is to add a
special field to /etc/network/devnames and use that file, since netcfg
already reads it. One could also add cardctl to pcmcia-cs-udeb and use
it to get the card name. The problem is that card names might contain
a colon so I'd have to add the field between the interface name and
the description. Or should it just write a list of PCMCIA interface
names in another file, perhaps?
--
Pelle
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release update
On Mon, Mar 29, 2004 at 06:21:02PM +0200, Christian Perrier wrote: (copy to Alastair McKinstry as slang packages maintainer, Shlomi Loubaton as current worker on BIDI support for d-i and -boot as this concern comes from Debian Installer needs) * As of now, no new packages will be added to the base system. This means that packages in the base system *must not* change their package relationships. * Large changes to the base system must be cleared with the release team and the d-i team before being uploaded to unstable. The recent work on BIDI (bi-directional language support), aimed at getting right-to-left languages support in Debian Installer, is likely to induce changes to slang packages. One of these will probably make some slang1 packages depend on libfribidi0. I'm not sure of this because I'm not the one who tried to implement BIDI support in slang (Shlomi Loubaton is), but I highly suspect this. As a side effect this would make libfribidi0 a candidate for being in the base system. Thus, I prefer mention all this as soon as possible, of course... Including libfribidi0 in the base system would have to be done as soon as possible to avoid repeatedly breaking old d-i images, which is a perpetual problem. You'll have to check with aj. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA network configuration
Per Olofsson wrote: Now, how to implement this? What first comes to mind is to add a special field to /etc/network/devnames and use that file, since netcfg already reads it. One could also add cardctl to pcmcia-cs-udeb and use it to get the card name. The problem is that card names might contain a colon so I'd have to add the field between the interface name and the description. Or should it just write a list of PCMCIA interface names in another file, perhaps? I don't think getting really accurate card names is all that important, very few people will have two pcmcia network cards. So calling it PCMCIA network card N is probably fine, or whatever it does now. Anyway, this is separate from teaching netcfg about hotpluggable cards. Whether their interface is turned on by pcmcia or by some other method (usb hotplug?), the key thing is that these card should not get auto entries. A /etc/network/devhotplug or something could list them. Is modifying pcmcia-cs to deal with this going to be problimatic, and is there another way to do it besides including cardctl? Something in /proc? I know that so far we have managed to use pcmcia-cs without changing its init scripts. -- see shy jo signature.asc Description: Digital signature
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
I'm sorry. I don't have the skills in assembler language to help with this phase. However, I'll happily test things on my farm of old Macs of various flavors. For what it's worth, since MacOS7.6 and (I think) 8.6 boot on M68k Macs, the boot sector is very likely to be in M68k machine language, not PowerPC. Hope that helps! Rick On Monday, March 29, 2004, at 02:32 AM, Sven Luther wrote: On Sun, Mar 28, 2004 at 07:00:06PM -0500, Rick Thomas wrote I'll do whatever I can to help with testing. No problem. If you feel like disassembling the miboot stage 1 boot-sector, and providing me info on what it does, i would appreciate. It seems i am legally barred from doing it myself if i want to write the reimplementation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#238038: acknowledged by developer (Bug#238038: fixed in discover1 1.5-7)
reopen 238038 thanks On Wed, Mar 24, 2004 at 10:03:06PM -0800, Debian Bug Tracking System wrote: Version: 1.5-7 - Actually include that README.Debian; Closes: #238038 Hmmm, the README is missing again, now with: Package: discover Version: 2.0.3-4 regards, Mario -- I heard, if you play a NT-CD backwards, you get satanic messages... That's nothing. If you play it forwards, it installs NT. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Some issues with UTF-8 locale
Konstantinos Margaritis wrote:
On Sunday 28 March 2004 23:58, Joey Hess wrote:
Unfortunatly tasksel uses slang, not newt, so this patch is not
going to fix it..
I made patch for tasksel utf8 support in tasksel (attached).
Tested it with uk_UA.{UTF-8|KOI8-U} and el_GR.UTF-8 locales.
Can anyone test it too (but do not forget clean build directory)?
--
Eugeniy Meshcheryakov
Kyiv National Taras Shevchenko University
Information and Computing Centre
http://icc.univ.kiev.ua
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Some issues with UTF-8 locale
Oops, patch attached :-)
--
Eugeniy Meshcheryakov
Kyiv National Taras Shevchenko University
Information and Computing Centre
http://icc.univ.kiev.ua
Index: slangui.c
===
--- slangui.c (revision 409)
+++ slangui.c (working copy)
@@ -239,7 +239,7 @@
_(Debian Task Installer v%s - (c) 1999-2004 SPI and others),
VERSION);
SLsmg_gotorc(0, 0);
- SLsmg_write_nstring(buf, strlen(buf));
+ SLsmg_write_string(buf);
_resizing = 0;
switch (_chooserinfo.whichwindow) {
@@ -350,7 +350,7 @@
void ui_shadow(int y, int x, unsigned int dy, unsigned int dx)
{
int c;
- unsigned short ch;
+ SLsmg_Char_Type ch;
if (SLtt_Use_Ansi_Colors) {
for (c=0;cdy-1;c++) {
@@ -360,13 +360,13 @@
* character plus alternate character set attribute. -- JED
*/
ch = SLsmg_char_at();
- ch = (ch 0x80FF) | (0x02 8);
+ ch = SLSMG_BUILD_CHAR(SLSMG_EXTRACT_CHAR(ch), 0x2);
SLsmg_write_raw(ch, 1);
}
for (c=0;cdx;c++) {
SLsmg_gotorc(y+dy, x+1+c);
ch = SLsmg_char_at();
- ch = (ch 0x80FF) | (0x02 8);
+ ch = SLSMG_BUILD_CHAR(SLSMG_EXTRACT_CHAR(ch), 0x2);
SLsmg_write_raw(ch, 1);
}
}
@@ -398,12 +398,12 @@
* of the other buttons into account.
*/
ui_button(_chooserinfo.rowoffset + _chooserinfo.height + 1,
-_chooserinfo.coloffset + (_chooserinfo.width - strlen(_(Task ^Info)) + 1) / 2,
+_chooserinfo.coloffset + (_chooserinfo.width - ts_mbstrwidth(_(Task ^Info)) + 1) / 2,
_(Task ^Info), issel);
break;
case BUTTON_HELP: // Right justified
ui_button(_chooserinfo.rowoffset + _chooserinfo.height + 1,
-_chooserinfo.coloffset + _chooserinfo.width - 5 - strlen(_(^Help)) + 1,
+_chooserinfo.coloffset + _chooserinfo.width - 5 - ts_mbstrwidth(_(^Help)) + 1,
_(^Help), issel);
break;
}
@@ -512,18 +512,24 @@
SLsmg_gotorc(row, col);
SLsmg_write_char('');
/* Anything following a ^ in txt is highlighted, and the ^ removed. */
- p = strchr(txt, '^');
+ p = ts_mbstrchr(txt, L'^');
if (p) {
+wchar_t w;
+int ret;
+
if (p txt) {
- SLsmg_write_nstring(txt, p - txt);
+ SLsmg_write_nchars(txt, p - txt);
}
p++;
if (selected)
SLsmg_set_color(SELHIGHLIGHT);
else
SLsmg_set_color(HIGHLIGHT);
-SLsmg_write_char(p[0]);
-p++;
+ret = mbtowc(w, p, MB_CUR_MAX);
+if (ret =0)
+ return;
+SLsmg_write_char(w);
+p += ret;
if (selected)
SLsmg_set_color(SELBUTTONOBJ);
else
@@ -537,7 +543,7 @@
void ui_title(int row, int col, int width, char *title)
{
- int pos = col + (width - strlen(title))/2;
+ int pos = col + (width - ts_mbstrwidth(title))/2;
SLsmg_gotorc(row, pos - 1);
SLsmg_set_char_set(1);
SLsmg_write_char(SLSMG_RTEE_CHAR);
@@ -564,7 +570,7 @@
SLsmg_fill_region(row+1, col+1, height-2, width-2, ' ');
for (ri = topline; ri numlines ri - topline height - hoffset; ri++) {
SLsmg_gotorc(row + 1 + ri-topline, col + 1);
-if (strlen(buf[ri]) leftcol)
+if (ts_mbstrwidth(buf[ri]) leftcol)
SLsmg_write_nstring(buf[ri]+leftcol, width - woffset);
}
if (scroll SCROLLBAR_VERT numlines height-hoffset)
@@ -671,7 +677,7 @@
SLsmg_gotorc(row, _chooserinfo.coloffset + 1 + 2);
snprintf(buf, 1024, %s , getsectiondesc(TASK_SECTION(_tasksary[index])));
SLsmg_write_nstring(buf, _chooserinfo.width - 1 - 2);
- spot = 1 + 2 + strlen(buf);
+ spot = 1 + 2 + ts_mbstrwidth(buf);
if (spot _chooserinfo.width / 2 - 3) spot = _chooserinfo.width / 2 - 3;
SLsmg_gotorc(row, _chooserinfo.coloffset + spot);
SLsmg_draw_hline( _chooserinfo.width / 2 - spot );
Index: strutl.h
===
--- strutl.h (revision 409)
+++ strutl.h (working copy)
@@ -1,7 +1,10 @@
/* $Id: strutl.h,v 1.1 1999/11/21 22:01:04 tausq Rel $ */
#ifndef _STRUTL_H
#define _STRUTL_H
+#include wchar.h
char *reflowtext(int width, char *txt);
+char *ts_mbstrchr(char *, wchar_t);
+int ts_mbstrwidth(const char *);
#endif
Index: Makefile
===
--- Makefile (revision 409)
+++ Makefile (working copy)
@@ -8,10 +8,10 @@
CFLAGS=-g -Wall #-Os
DEBUG=1
ifeq (0,$(DEBUG))
-DEFS=-DVERSION=\$(VERSION)\ -DPACKAGE=\$(PROGRAM)\ -DLOCALEDIR=\/usr/share/locale\ \
+DEFS=-DUTF8 -DVERSION=\$(VERSION)\ -DPACKAGE=\$(PROGRAM)\ -DLOCALEDIR=\/usr/share/locale\ \
-DTASKDIR=\$(TASKDIR)\
else
-DEFS=-DVERSION=\$(VERSION)\ -DPACKAGE=\$(PROGRAM)\ -DLOCALEDIR=\/usr/share/locale\ \
+DEFS=-DUTF8 -DVERSION=\$(VERSION)\ -DPACKAGE=\$(PROGRAM)\ -DLOCALEDIR=\/usr/share/locale\ \
-DTASKDIR=\.\ -DDEBUG
endif
VERSION=$(shell expr `dpkg-parsechangelog 2/dev/null |grep Version:` : '.*Version: \(.*\)' | cut -d - -f 1)
Index: strutl.c
Processed: Re: Bug#238038 acknowledged by developer (Bug#238038: fixed in discover1 1.5-7)
Processing commands for [EMAIL PROTECTED]: reopen 238038 Bug#238038: discover: changelog names README.Debian, but none there Bug reopened, originator not changed. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240760: Successful report on Rebel Netwinder (ARM)
* Joey Hess [EMAIL PROTECTED] [2004-03-28 22:40]: Hmm, sounds like a failure to call partconf-mkfstab, though the current version of partconf should do so. The logs say partconf-mkfstab version 0.27 was called. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Some issues with UTF-8 locale
Eugeniy Meshcheryakov wrote:
I made patch for tasksel utf8 support in tasksel (attached).
Tested it with uk_UA.{UTF-8|KOI8-U} and el_GR.UTF-8 locales.
Can anyone test it too (but do not forget clean build directory)?
I can confirm that things still display fine with this patch in latin
languages. I cannot test unicode.
--
see shy jo
signature.asc
Description: Digital signature
Bug#240760: Successful report on Rebel Netwinder (ARM)
* Joey Hess [EMAIL PROTECTED] [2004-03-29 13:16]: The logs say partconf-mkfstab version 0.27 was called. Called how? It has changed from doing this when it is configured to providing a partconf-mkfstab program that partconf runs. Sorry, called wasn't the right word. The logs show it was installed. I have no idea if it was really called. Let me do another install - what would I look out for? When and how should partconf run partconf-mkfstab? -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240760: Successful report on Rebel Netwinder (ARM)
Martin Michlmayr wrote: * Joey Hess [EMAIL PROTECTED] [2004-03-28 22:40]: Hmm, sounds like a failure to call partconf-mkfstab, though the current version of partconf should do so. The logs say partconf-mkfstab version 0.27 was called. Called how? It has changed from doing this when it is configured to providing a partconf-mkfstab program that partconf runs. -- see shy jo signature.asc Description: Digital signature
Bug#240760: Successful report on Rebel Netwinder (ARM)
* Joey Hess [EMAIL PROTECTED] [2004-03-29 13:38]: It should run it after formatting and mounting the partitions. You could check to make sure that there is a /usr/lib/partconf/mkfstab after that point, and if no /target/etc/ftab was created, try to run it by hand and see if it's failing. /usr/lib/partconf/mkfstab exists, /target/etc/fstab is not created, and running mkfstab by hand creates a correct /etc/fstab file. So I assume that the state machine is broken and mkfstab never called. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
exim cannot find gnutls
hi! I'm trying to use the daily build of 2004-03-28 to install Sarge on a compaq deskpro 5000. (Pentium 200, 2G harddisk.) I have two 3com 905 ethernet cards in it. I'm using the netinst daily because beta 3 hangs in the partition manager. The first part of the installer works fine, but while installing the base system, all programs that depend on the mail-transport-agent fail because exim4 cannot find gnutls libraries. Then debian-installer considers the install a failure and does not want to continue. I'm sorry I cannot attach logfiles, but those got eaten by a faulty floppy. Tomorrow I'll try again. Is it possible to have the installer just ignore the exim failures (I'm going to replace it by postfix anyway) and continue with the installation? Would it help to download the large .iso because that one does contain gnutls? Thanks, Joeri PS. Is there a reference somewhere that explains the meaning of all those cute little icons in the partition program? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fake
Your message has been received. Someone will be responding soon. God bless you! The IOM Team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240760: Successful report on Rebel Netwinder (ARM)
Martin Michlmayr wrote: * Joey Hess [EMAIL PROTECTED] [2004-03-29 13:38]: It should run it after formatting and mounting the partitions. You could check to make sure that there is a /usr/lib/partconf/mkfstab after that point, and if no /target/etc/ftab was created, try to run it by hand and see if it's failing. /usr/lib/partconf/mkfstab exists, /target/etc/fstab is not created, and running mkfstab by hand creates a correct /etc/fstab file. So I assume that the state machine is broken and mkfstab never called. Hmm. Well, I did test it when I added it.. but not very much. -- see shy jo signature.asc Description: Digital signature
Bug#239133: using 3-28-04 iso image sarge-m68k-businesscard.iso 3-29-04 mac hd-media images
I'm sorry that I missed your original install report. I thought I allowed for multiple cdroms, but the code says otherwise. Would you mind running the following commands on your dual cdrom box and letting me know what you get? dmesg | grep -i cdrom | grep -i ide | cut -d: -f 1 dmesg | grep -i detected | grep -i scsi | grep -i cd-rom | cut -d' ' -f 4 As for partitioning, the the newer, slower, and slicker partitioner, called partman, is available from the expert menu as Partition a disk. I'd be interested in your critique of partman too. The libgcrypt7 failure was a transient base package change and should be fixed. On Mon, Mar 29, 2004 at 11:11:49AM -0500, Hank wrote: Seems like you're making progress. ext3 filesystem option shows up when formatting. Installation of packages from the mounted iso image is successful until it says it can't find a a valid kernel image during the base installation. At which point the install reverts back to the screen with about 20 options: partition a disk, install the base system, etc. At that point I had about 90 MB installed on the /target/ partition. That's interesting. I haven't tried hd-media with the businesscard, since the businesscard cd doesn't have a single deb on it -- just d-i udebs. Did you download base from a mirror? I rebooted the system at that point. I tried using my own kernel and modules by copying them from another working system on a different scsi dri ve. I managed to boot into a prompt after changing the /etc/fstab file to mount the root and swap partitions: the fstab file only had two comment lines in with no entries to mount any file systems. base-installer didn't get to finish, so it shouldn't be a surprise that things weren't all setup right. :-\ But I could proceed no further: I was asked for a password which the system had not set up. I tried entering a blank password for root, but that didn't work. That's base-config weirdness. Usually base-config starts and among other things, lets you set the root password. I suppose another thing that didn't get setup correctly. Apparently, the business card iso is lacking kernel images for the mac kernel? Yes, by design. I wonder if you hit a transient mirror problem? Thanks, Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! [EMAIL PROTECTED]
Re: Release update
On Mon, Mar 29, 2004 at 06:21:02PM +0200, Christian Perrier wrote: (copy to Alastair McKinstry as slang packages maintainer, Shlomi Loubaton as current worker on BIDI support for d-i and -boot as this concern comes from Debian Installer needs) * As of now, no new packages will be added to the base system. This means that packages in the base system *must not* change their package relationships. * Large changes to the base system must be cleared with the release team and the d-i team before being uploaded to unstable. The recent work on BIDI (bi-directional language support), aimed at getting right-to-left languages support in Debian Installer, is likely to induce changes to slang packages. One of these will probably make some slang1 packages depend on libfribidi0. I'm not sure of this because I'm not the one who tried to implement BIDI support in slang (Shlomi Loubaton is), but I highly suspect this. As a side effect this would make libfribidi0 a candidate for being in the base system. Thus, I prefer mention all this as soon as possible, of course... As mentioned on IRC, I believe it would be inappropriate to add libfribidi0 to the base system at this stage, since this would be a significant change to a very important library (libslang). Fortunately, we can have d-i translated into Hebrew and Arabic *without* making any changes to the base system, which is one reason why I feel this way. For d-i, we only need a fribidi-enabled slang udeb, we don't need fribidi support in the base system. This does mean that post-reboot, BIDI support will not be available in debconf, but I think this is a reasonable goal for the first release of Debian which contains any BIDI installation support at all, and it's also compatible with commonly recognized translation priorities (install manual + d-i stage 1, then stage 2 packages, then the rest). -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: PCMCIA network configuration
On Mon, Mar 29, 2004 at 12:42 -0500, Joey Hess wrote: I don't think getting really accurate card names is all that important, very few people will have two pcmcia network cards. So calling it PCMCIA network card N is probably fine, or whatever it does now. Yeah, that was merely a side thing. Right now it uses generic names, i.e. Ethernet or Fast Ethernet and Wireless ethernet (802.11x), but no mention of PCMCIA what I've seen. Whether their interface is turned on by pcmcia or by some other method (usb hotplug?), the key thing is that these card should not get auto entries. Actually, this is only about PCMCIA/Cardbus cards. USB interfaces and such should get auto entries, as they are not brought up by hotplug by default anymore. A /etc/network/devhotplug or something could list them. Perhaps devnoauto would be more accurate. Is modifying pcmcia-cs to deal with this going to be problimatic, Ideally the network script should only do this if it is invoked from withing debian-installer. Perhaps put a special network script in the udeb, or add the code with some kind of check so that it is not activated on a real Debian system. Shouldn't be too problematic really. and is there another way to do it besides including cardctl? cardctl is only needed to determine the names, sorry about mixing things up :) Something in /proc? I know that so far we have managed to use pcmcia-cs without changing its init scripts. I've looked, but I haven't found anything. I would have suggested that first if I had. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[console-common] wrong+unexported TEXTDOMAIN in install-keymap
Hi, [Well, perhaps this report should have been sent to console-common, directly, but I want to get a confirmation from other d-i translators.] After I've translated the console-common/po/tr.po and attempted to test it, I've noticed that Turkish messages could not be displayed. I found that the problem was in fact caused by using a wrong and unexported TEXTDOMAIN. Could someone confirm this bug and apply my fix? Here is how I test it for Turkish: LC_ALL=tr_TR install-keymap # display Usage in Turkish --- install-keymap.old 2004-03-29 22:04:38.0 +0300 +++ install-keymap 2004-03-29 22:05:23.0 +0300 @@ -8,7 +8,7 @@ KMAPEXT=kmap # Set uo i18n if possible -TEXTDOMAIN=console-common +export TEXTDOMAIN=install-keymap if [ -x /usr/bin/gettext ] then GETTEXT=/usr/bin/gettext -s -- roktas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release update
Quoting Steve Langasek ([EMAIL PROTECTED]): As mentioned on IRC, I believe it would be inappropriate to add libfribidi0 to the base system at this stage, since this would be a significant change to a very important library (libslang). Fortunately, we can have d-i translated into Hebrew and Arabic *without* making any changes to the base system, which is one reason why I feel this way. For d-i, we only need a fribidi-enabled slang udeb, we don't need fribidi support in the base system. This does mean that post-reboot, BIDI support will not be available in debconf, but I think this is a reasonable goal for the first release of Debian which contains any BIDI installation support at all, and it's also compatible with commonly recognized translation priorities (install manual + d-i stage 1, then stage 2 packages, then the rest). I think this is a good compromise. Until now, Shlomi Loubaton's modified slang depends on libfribidi for all generated packages, but this is not really needed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Update to Debian Installer translators documentation
On Monday 29 March 2004 08:37, Christian Perrier wrote: Quoting Konstantinos Margaritis ([EMAIL PROTECTED]): Hi, I'd like to suggest a few changes to doc/translations.txt, wrt to the suggested packages for translation: Fine. I'll change it. You could even have done this youself, probably. After all, if you have commit access, this is because d-i people are confident in your mental health..:-) I prefer to check first, commit after. :-) These priority lists were added long ago and this is not well maintained, for sure. Thanks for taking care to review them. I wanted to coordinate some translation jobs to some people and needed to straighten out these packages anyway. The culprit template has been removed very recently after a bug report I made, as this was so-called debconf abuse. It also seems that gdm is not available for translation as well, probably a similar case? Konstantinos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
On Sun, Mar 28, 2004 at 07:27:33PM +0200, Sven Luther wrote: On Sun, Mar 28, 2004 at 11:55:03AM -0500, Joey Hess wrote: Jeremie Koenig wrote: The plan was to request a sarge-ignore tag on the d-i build-depends on miboot, which is in contrib, and try to find a better solution for next releases. This is the first I've heard of this. Has the sarge-ignore status of the GFDL docs really created such a slippery slope? I doubt it. Well, we had it in woody boot-floppies, it seems. Ignorance is not precedent. When we learn that non-free stuff is in main, our Social Contract obliges us to act on it, not immediately grandfather what we have found into our definition of Free Software. -- G. Branden Robinson|Computer security is like an onion: Debian GNU/Linux |the more you dig in, the more you [EMAIL PROTECTED] |want to cry. http://people.debian.org/~branden/ |-- Cory Altheide signature.asc Description: Digital signature
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
On Sun, Mar 28, 2004 at 09:16:14AM +0200, Sven Luther wrote: 2) a small file, the boot1 macos ressource, a 1K boot-sector to be copied to the floppy boot sector, is taken from the mac os system file. This is non-free, binary only, altough, well, the file in question only contains some ROM calls to initialize HFS, and load the boot2, open the mac os system file, and load boot2, which is provided by the GPL-free part of miboot mentioned above. Worse case scenario, this could be clean-room reimplemented. To do it, you need two MacOS hackers. Hacker #1 looks at the existing boot sector, writes a complete plain English description of it, and posts it to debian-boot and/or debian-powerpc. Hacker #2 affirms that he has never looked at the existing boot sector, and will not do so in the future. He or she understands MacOS well enough to know how to hand-code 1kB worth of assembly (or possibly compilable C code) to create a functionally-identical boot sector from the plain English description. -- G. Branden Robinson| Religion is excellent stuff for Debian GNU/Linux | keeping common people quiet. [EMAIL PROTECTED] | -- Napoleon Bonaparte http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
On Mon, Mar 29, 2004 at 04:05:48PM -0500, Branden Robinson wrote: Hacker #2 affirms that he has never looked at the existing boot sector, and will not do so in the future. He or she understands MacOS well enough to know how to hand-code 1kB worth of assembly (or possibly compilable C code) to create a functionally-identical boot sector from the plain English description. If I understand right from my GNU hacking, it's preferable to take a slightly different approach if possible. Doing some of it in C instead of ASM (if at all possible, obviously) might result in that anyway. Tks, Jeff Bailey -- Ignorance was bliss. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA network configuration
On Mon, Mar 29, 2004 at 21:19 +0200, pelle wrote: Ideally the network script should only do this if it is invoked from withing debian-installer. Perhaps put a special network script in the udeb, or add the code with some kind of check so that it is not activated on a real Debian system. Shouldn't be too problematic really. What is problematic, though, is Cardbus cards. I borrowed one today and it didn't work with d-i. cardmgr doesn't configure these cards, it lets hotplug handle them instead, and d-i doesn't use hotplug. This is not a big problem however since discover can detect these cards if you just start cardmgr first, so it's easily fixable. The real problem is the installed system. cardmgr doesn't bring up Cardbus network interfaces, and neither does /etc/init.d/networking. hotplug used to bring up these interfaces but does not do that anymore by default. As is described in /usr/share/doc/hotplug/README.Debian, you need to add something like this to /etc/network/interfaces: mapping hotplug script grep map eth1 So d-i would have to generate this for these cards, I guess. I'm not sure how you determine whether a specific network interface belongs to a Cardbus card or a 16-bit card, though. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [console-common] wrong+unexported TEXTDOMAIN in install-keymap
Hi,
Unfortunately there are other problems with install-keymap regarding the
i18n issues, which render the translation efforts of 'console-data' (as
suggested for second-stage installation [1]) somewhat problematic.
Messages with shell variables doesn't work, e.g.
$GETTEXT 2 confffile ${CONFFILE} is a symlink : not overwriting
The messaging interface could have been rewritten with the
gettext shell helper (I mean the 'gettext.sh' from gettext-base
package.) But this package has a lower priority ('standart') than
console-common ('important') which introduces a dependency problem.
Maybe there should be another workaround. Or just for the i18n
requirements, shouldn't the gettext-base package have a more higher
priority. Any comment?
[1] http://people.debian.org/~seppy/d-i/2nd-stage/packages-list
--
roktas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240911:
Package: installation-reports Debian-installer-version: beta-3 100MB install image [i386] uname -a: not applicable Date: 2004-03-29:20:00:00 Method: Boot from CD-ROM Machine: No-Name Processor: Pentium III 1.3 GHz Memory: 512 MB Root Device: IDE: second disk Root Size/partition table: part1:512 MB swap, part2:30 GB ReiserFs Output of lspci: not applicable Base System Installation Checklist: Initial boot worked:[x] Configure network HW: [x] (not main problem, see notes) Config network: [x] (not main problem, see notes) Detect CD: [x] Load installer modules: [x] Detect hard drives: [x] Partition hard drives: [x] (not main problem, see notes) Create file systems:[x] Mount partitions: [x] Install base system:[x] Install boot loader:[E] Reboot: [E] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: First some comments that are unrelated to the errors that I got later: Network: - I use ADSL to connect to the internet. DHCP fails. I find it strange that I can't go on without putting in a fantasy ip address. - When asked for default gateway the text says I can leave it blank. This, however results in an error and I have to put something in. Partitioning: - I consider myself quite experienced in installing Debian. I don't know what LVM is, though and got lost in some (to me meaningless) submenus before realising that I have to select format. Now on to the real problem: I currently have SID running off /dev/hdb2 (hdb1 is swap) with lilo in hdb2 that I chainload from the Windows NT bootloader on /dev/hda (I use dd to write the hdb2 boosector to a file and move that to my hda partition). I removed the hdb drive and replaced it with a blank one. I wanted the new system to work exactly the same way. This is what I did (I tried several times. Numbers in parenthesis correspond to the different tries): - Booted from d-i beta3 CD-ROM (1) Created hdb1 (512 MB swap) and hdb2 (30 GB Reiserfs /) (1) Entered hd(1,1) for GRUB installation. GRUB fails. Console 3 says that it failed in stage 2 (I didn't copy the full message to paper) (1) Now LILO installation comes up (I guess because GRUB failed). After being totally dumbfounded by the ...target/disc/lun/ stuff I decide to poke around /dev/ on console 2 and find out what to put there by analysing the contents of /dev/ide/ (1) I mount a vfat partition and dd if=the same target/lun/part combination as above of=mounted vfat partiton bs=512 count=1 (1) I select reboot and see GRUB installing (WTF?) (1) As was expected, after copying the bootsector file to my windows partition and rebooting a GRUB bootblock is chainloaded and hangs displaying just GRUB once. (1) Trying to boot from CD with linux root=/dev/hdb2 stops with kernel-panic - Booted from d-i beta3 CD-ROM (2) Created hdb1 (512 MB swap), hdb2 (20 MB ext3 /boot) and hdb3 (30 GB Reiserfs /) (2) GRUB hd(1,1) doesn't fail this time. (2) The rest is the same as in (1), again system hangs at GRUB (2) Trying to boot from CD with linux root=/dev/hdb2 stops with kernel-panic - Booted from d-i beta3 CD-ROM (3) Created hdb1 (512 MB swap), hdb2 (20 MB ext3 /boot) and hdb3 (30 GB XFS /) (3) GRUB hd(1,1) doesn't fail this time either. (3) The rest is the same as in (1), again system hangs at GRUB (3) Trying to boot from CD with linux root=/dev/hdb2 stops with kernel-panic - Booted from d-i beta3 CD-ROM (4) Created hdb1 (512 MB swap) and hdb2 (30 GB XFS /) (4) Skipped bootloader installation as the installer told me that XFS doesn't allow a bootblock on a partition (4) Trying to boot from CD with linux root=/dev/hdb2 stops with kernel-panic Conclusion: After 3 hours I gave up and put my old drive back in. Maybe I would have gotten it to work if there was a rescue image in the installer CD, which would have allowed me to get into my installation and tweak lilo.conf manually (this is the way I had set up my current system using woody). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PCMCIA network configuration
Per Olofsson wrote: The real problem is the installed system. cardmgr doesn't bring up Cardbus network interfaces, and neither does /etc/init.d/networking. hotplug used to bring up these interfaces but does not do that anymore by default. That seems serously brain-dead. Why should this not just work whenever any cardbus card is inserted? How am I as a user supposed to know the difference between a cardbus card and some other PCMCIA card? Is hotplug really this bad? As is described in /usr/share/doc/hotplug/README.Debian, you need to add something like this to /etc/network/interfaces: mapping hotplug script grep map eth1 So d-i would have to generate this for these cards, I guess. I'm not sure how you determine whether a specific network interface belongs to a Cardbus card or a 16-bit card, though. Or it suggests mapping hotplug\n\tscript echo to bring them all up. So we could add that to /etc/network/interfaces by default, which would be an ugly way to work around this. I went back and looked at the thread starting at http://lists.debian.org/debian-devel/2003/debian-devel-200302/thrd4.html, and it seems that this behavior was added to give more control to work around various bad interactions involving hotplug, but that no consideration was made of people who want things to Just Work. So if we put in any kind of mappings for hotplug, we will default the system to having the issues described in that thread (or some of them, #141399 seems to have been fixed by not starting hotplug until after S39ifupdown)), and if we don't, users will be unable to complete the install with their cardbus cards at all. Surely there must be a better solution in hotplug. -- see shy jo signature.asc Description: Digital signature
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
Scripsit Sven Luther [EMAIL PROTECTED] On Mon, Mar 29, 2004 at 12:52:12AM +0100, Henning Makholm wrote: Huh? Is the bootsector use written in a kind of machine language that the regular as(1) for the architecture does not support? I thought that i386 was the only platform with *that* problem. I suppose that the boot sector may contain a bit more than the standard elf or coff format. Not sure though. In the absence of other evidence I'd assume that it's a short fixed header followed by raw machine code, designed to be loaded at some magic address and executed immediately. It *may* take a custom ld(1) script to produce quite the right setup, but after that, getting it into a usable format should be a simple matter - use objdump and a short piece of perl if everything else fails. Google macintosh boot block turns up official Apple information that seems like it might be what you're looking for. (And which it would be OK to look at for a cleanroom implementor). -- Henning Makholm Cigarer er fulde af røg. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [console-common] wrong+unexported TEXTDOMAIN in install-keymap
On Tue, Mar 30, 2004 at 12:57:02AM +0300, Recai Oktas wrote:
Hi,
Unfortunately there are other problems with install-keymap regarding the
i18n issues, which render the translation efforts of 'console-data' (as
suggested for second-stage installation [1]) somewhat problematic.
Messages with shell variables doesn't work, e.g.
$GETTEXT 2 confffile ${CONFFILE} is a symlink : not overwriting
Right, this can be rewritten as
printf `$GETTEXT confffile %s is a symlink : not overwriting` $CONFFILE 2
echo 2
Your previous post is also right, TEXTDOMAIN is wrongly set.
Denis
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240914: Package: installation-reports
Package: installation-reports Debian-installer-version: beta 3, from http://www.debian.org/devel/debian-installer/ uname -a: Linux (none) 2.4.25-1-386 #1 Tue Feb 24 08:11:13 EST 2004 i686 unknown Date: March 29 Method: Boot floppies, didn't complete installation Machine: Sony VAIO Picturebook PCG-C1VN Processor: Transmeta 600 mhz Memory: 128 mb Root Device: IDE - haven't gotten to configure it yet Output of lspci: lspci: not found Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [E] Config network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: Hey, I'm trying out the new Debian installer on a Sony Picturebook laptop - I figure this is a bit trickier than your standard install so it should be a good stress test of sorts. Since I don't have a cd-rom drive with it, I'm working off a usb floppy drive. I got the boot, root, and net drivers floppies and started up in expert mode, expecting to need to manually tweak some things. I was pleasantly surprised to find that the boot disk automatically loaded the usb drivers so that it could properly load the root disk. Anyway, the installer started up fine, my only issue being that the very bottom of the display got clipped off, and subsequent attempts to boot with vga=ask and trying out different modes didn't seem to help this. Either way, not a big deal, so I went ahead with the installation. Now my next snag is with the network - unfortunately, this computer also doesn't have a built in network card, and all I've got at the moment is a Microsoft wireless pcmcia card (MN-520). Luckily, I do have wireless access here, and searching the net shows that the card should work with the orinoco_cs module. I load the network drivers from the floppy, and then choose detect network hardware. Unfortunately, it doesn't seem to be able to detect the card automatically, and I wind up with a list of modules. I choose the orinoco_cs one, don't set any options to pass in, and it comes back to the list of modules without any explanation about if it loaded properly or had an error. It would have been nice to see a loaded successfully or error message. From here, things went downhill. I try choosing orinoco_cs again and this time nothing seems to happen. The only way I can find to get out of this menu is to select none of the above. What's worse, when I go back to detect network hardware, the list of modules no longer shows up - it just tries to detect and then comes back to the main menu. Strangely, configure the network does exactly the same thing. Finally, as a last resort, I try to execute a shell, and now the clipping at the bottom of the screen gets a bit more annoying. lsmod shows the orinoco_cs is listed (along with orinoco and hermes and ds and pcmcia_core, which all are used by orinoco_cs), so that seems promising, but I'm not really sure what I'm supposed to do at this point, having never set up a wireless connection in Linux before. I try ifconfig which doesn't do anything, and iwconfig shows: lo no wireless extensions. Anyway, that's about where I got stuck. I will probably try to just find a wired ethernet card to borrow from someone else for the base install, but hopefully the above report will be useful. I'm pretty impressed by the fact that it even booted off the usb floppy drive, but a bit disappointed (though not particularly surprised) to get stuck. Thanks. -Ari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240697: acknowledged by developer (closing)
Am Montag, 29. März 2004 17:08 schrieb Joey Hess: -- Have prerelease installs default to point to the fixed name (sarge) -- At release time change installation default to point to stable as usual, and issue a security patch to change explicit sarge systems to point to stable. No, we can't afford to need to release an entire new version of the installer at release time. We must be able to freeze it and do serious testing of the actual version we release. An entire new version of d-i is needed to change the default entries generated by the mirror chooser in the sources.list? That would also be the case changing from sarge to stable when releasing. If it is that intrusive this point might IMHO rather support having the default to be sarge already from earlier on. I have the feeling the negative reasoning might have been a little too quick. Thought merely exchanging a file that contains the default from sarge to stable, with a tiny securtiy update some time after the release for those that have installed sarge before the release, could be sufficient. Kind Regards, Christian
Processed: Translation is for discover1
Processing commands for [EMAIL PROTECTED]: reassign 240308 discover1 Bug#240308: Discover: Spanish debconf translation Bug reassigned from package `discover' to `discover1'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240918: __NR__llseek undeclared when compiling on amd64.
Package: busybox-cvs Version: 20040101 When trying to build the package I get the following error: gcc -I./include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Wall -Wstrict-prototypes -Wshadow -Os -fomit-frame-pointer -DNDEBUG -c -o util-linux/fdisk.o util-linux/fdisk.c util-linux/fdisk.c: In function `my_llseek': util-linux/fdisk.c:873: error: `__NR__llseek' undeclared (first use in this function) util-linux/fdisk.c:873: error: (Each undeclared identifier is reported only onceutil-linux/fdisk.c:873: error: for each function it appears in.) make[1]: *** [util-linux/fdisk.o] Error 1 make[1]: Leaving directory `/usr/src/busybox-cvs-20040101' make: *** [build-arch-static-stamp] Error 2 Patch: --- fdisk.c.old 2004-03-29 16:19:12.491937714 -0600 +++ fdisk.c 2004-03-29 16:20:14.076090497 -0600 @@ -856,7 +856,7 @@ */ -#if defined(__alpha__) || defined(__ia64__) || defined(__s390x__) +#if defined(__alpha__) || defined(__ia64__) || defined(__s390x__) || defined (__x86_64__) #define my_llseek lseek Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240760: Successful report on Rebel Netwinder (ARM)
* Joey Hess [EMAIL PROTECTED] [2004-03-29 13:55]: /usr/lib/partconf/mkfstab exists, /target/etc/fstab is not created, and running mkfstab by hand creates a correct /etc/fstab file. So I assume that the state machine is broken and mkfstab never called. Hmm. Well, I did test it when I added it.. but not very much. #240372 contains a report of an emtpy fstab as well. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240697: acknowledged by developer (closing)
C. Gatzemeier wrote: An entire new version of d-i is needed to change the default entries generated by the mirror chooser in the sources.list? In its most common form the installer consists of a CD image, yes. That would also be the case changing from sarge to stable when releasing. If it is that intrusive this point might IMHO rather support having the default to be sarge already from earlier on. The current images will already do the right thing if sarge happens to have been released. No last minute change is needed. I have the feeling the negative reasoning might have been a little too quick. You're welcome to your opinion. -- see shy jo signature.asc Description: Digital signature
About that Alpha kernel bug mentioned in beta3 errata
Hello,
if that bug (alpha cannot install from SCSI cdrom) is the one mentioned in
http://lists.debian.org/debian-boot/2004/debian-boot-200401/msg00374.html,
then I've run into it as well with a daily build shortly before d-i beta3.
Is this fixed now? If not here is some additional info:
On my system (an AS 2100A Lynx btw, cool these are supported now):
# cd /dev/cdroms
# ls -l
lr-xr-xr-x 1 root root 34 Jan 1 1970 cdrom0 -
yyyscsi/host0/bus0/target6/lun0/cd
[actually, the 'y's are y with dieresis, 0xff in ISO-8859-1]
And it is possible to work around it: create a _correct_ link under
another name, e.g.
# ln -s ../scsi/host0/bus0/target6/lun0/cd cdrom1
then try detecting the cdrom again, voila.
The symlink gets created in drivers/cdrom/cdrom.c:register_cdrom():
if (pos = 0) {
char vname[16];
sprintf (vname, cdrom%d, cdi-number);
strncpy (rname + pos, ../, 3);
devfs_mk_symlink (devfs_handle, vname,
DEVFS_FL_DEFAULT,
rname + pos, slave, NULL);
devfs_auto_unregister (cdi-de, slave);
}
That piece of code is shared by all kinds of cdroms, and all
architectures... so how can it be broken on alpha and not on x86,
and with SCSI but not IDE? I think the strncpy (rname + pos, ../, 3);
call fails, and strncpy is arch specific. This would mean that, in the
end, alpha stxncpy.S is broken again. I don't know enough alpha assembly
to understand what's going on, but it seems there are a lot of hairy
corner cases, depending on data length and alignment. Maybe one could
replace the strncpy with array member assignments and see what happens.
I can't try this myself because I only have access to this one alpha machine
and it still waits for its dose of Linux.
The other possibility would be a gcc optimizer bug.
One final remark: it would tremendously help troubleshooting hardware /
kernel related problems if a rmmod command were available from the
d-i shell prompt.
Regards,
Bjoern Brill
P.S.: please cc me on replies, I'm not on the list.
--
Bjorn Brill [EMAIL PROTECTED]
Frankfurt am Main, Germany
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Translations and changelogs, SVN
On Thu, Mar 25, 2004 at 08:21:28PM -0500, Joey Hess wrote: [...] Check out one of these uris: svn://svn.debian.org/d-i/people/joeyh/trans/po_anon (anonymous checkouts only) svn+ssh://svn.debian.org/svn/d-i/people/joeyh/trans/po (non-anonymous only) Really nice. I'm not sure where to put this permanatly or what to call it. I agree that it does not belong in trunk. Maybe a toplevel pofiles directory? No better idea at the moment. Note that it will require periodic maintenance as new po directories are added to the tree and as things are moved around. Yes. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
Scripsit Branden Robinson [EMAIL PROTECTED] Worse case scenario, this could be clean-room reimplemented. Before doing that, somebody ought to approach Apple and ask explicit permission to reverse-engineer the boot-block code and distribute the reverse-engineered source under a free license. The worst that can happen is that the request ends up with some clueless corporate lawyer whose instinctive reaction is, No way; that's *our* IP - but if he has the slightest bit of clue he will realise that Apple does not really have any commercial interest in clinging to this particular piece of IP. -- Henning MakholmDe kan rejse hid og did i verden nok så flot Og er helt fortrolig med alverdens militær -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
USB Mass Storage installation
I'm building a new USB mass storage device from the 0329 netinstall.iso: Using the installation manual section 4.4.1: zcat boot.img.gz /dev/sda (was gzip -cd and not zcat) mount -t vfat /dev/sda /mnt cp sarge-i386-netinst.iso /mnt sync (I added this) umount /mnt Not much left of my USB device. Can't mount it or do anything with it after this, but it will start a boot session. I am trying to mount it using 'mount -t vfat /dev/sda1 /mnt' on a SuSE machine ( no debian yet ... ). mounting /dev/sda doesn't work either: loki:/home/tallison # mount -t vfat /dev/sda /mnt/ mount: wrong fs type, bad option, bad superblock on /dev/sda, or too many mounted file systems However, I was hoping to use this as a starting point for pulling in daily builds and doing install tests. But recovering from this is pretty tough to do. I have a 256MB stick. I have not yet tried the method in section 4.4.2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240926: Missing drivers
Title: Missing drivers Package: installation-reports Debian-installer-version: http://gluck.debian.org/cdimage/testing/daily/alpha/current/HYPERLINK http://gluck.debian.org/cdimage/testing/daily/alpha/current/sarge-alpha-netinst.isosarge-alpha-netinst.iso uname -a: unable to do so Date: March 29, 2004 Method: CD-ROM install image Machine: AlphaServer 3305 (Noritake) Processor: Alpha 21164 Memory: 384Mb Root Device: SCSI Qlogic ISP1020 Root Size/partition table: Didn't get there. Will be two SCA 4Gb Seagate Barracudas Output of lspci: command is unavailable Base System Installation Checklist: Initial boot worked: [O] Configure network HW: [E] Config network: [ ] Detect CD: [E] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Create file systems: [ ] Mount partitions: [ ] Install base system: [ ] Install boot loader: [ ] Reboot: [ ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: The Qlogic ISP1020 (qlogicisp) is a very popular SCSI chipset on the motherboards of older Alpha systems, as well as the DEC TULIP chipset on the network cards that came with these systems. Neither of these drivers are included on the install CD, which means I can't use a net install nor a CD install, since I have no drivers for my SCSI system or my network card. They should definitely be included on any CD image supplied. Regards, Ron Sokoloski Regional IT Manager, Southern Ontario Osprey Media Group Ltd. 17 Queen Street, St. Catharines, ON, L2R 5G5 Phone: (905) 688-7251 Ext. 350 Cell: (905) 380-0795
Title: Untitled Document I 6 : : . , . 1/3, - . : , , ,, . : 1. 1.1. 1.2. 1.3. - ; - ; - ; - . 2. 2.1. 2.2. - ; -; - . 2.3. 3. 3.1 - ; - ; -. 3.2. 3.3. - - ; - . 4. 4.1. 4.2. 4.3. 4.4. 5. : - - , , - - , . : : 500 . : , , , - , , , . : 2 5%. 3 7%. . . : . / (044) 2 28 9 , 4.5.4 9.8 7.9 DotMail. 303267184.
Bug#240934: Installation report
Package: installation-reports INSTALL REPORT Debian-installer-version: beta 3 uname -a: Linux lhotse 2.4.25-1-386 #1 Tue Feb 24 08:11:13 EST 2004 i686 GNU/Linux Date: Er, sometime in mid March Method: Burn beta 3 ISO to CD-R. Put CD in CD-ROM. Reboot and follow instructions. Machine: mongrel built with scavenged bits (Chaintech 7KJD mobo) Processor: AMD XP1600+ Memory: 256MB Root Device: IDE Root Size/partition table: Er, will the output from df do ? : Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda1 14421344 1404172 12284612 11% / /dev/hda3 14160404 42948 13398148 1% /home tmpfs 128516 0128516 0% /dev/shm /dev/hda2 is swap. The machine has a single ~30GB disk as /dev/hda. (this is after I've apt-get-ed a fair amount of stuff). Output of lspci: 00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] System Contr oller (rev 13) 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] AGP Bridge 00:09.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74) 00:0a.0 SCSI storage controller: Adaptec AHA-2940/2940W / AIC-7871 (rev 03) 00:0e.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA Bridge] (rev 10) 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/ C/VT8235 PIPC Bus Master IDE (rev 06) 00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 1e) 00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 1e) 00:11.4 Non-VGA unclassified device: VIA Technologies, Inc. VT8235 ACPI (rev 10) 01:05.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64 /Model 64 Pro] (rev 15) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: A good experience up to the point where I got asked whether I wanted to use apt or dselect (dpkg?) to install packages. I freaked out at the near infinite possibilities and didn't pick anything. I'd really like to see some broad category type install options at this point. (e.g personal system, development workstation, headless server much like RedHat used to do) and have them install huge swathes of packages. Maybe analysis of the popularity contest data can provide some useful classifications here. Maybe there could simply be some pseudo-packages (e.g debian-development-workstation, say) with a huge number of dependencies to suck lots of stuff in. Post install I haven't had much luck getting xfree, gdm or even a vnc server up and running on the machine, which is a shame as I seem to remember it being very easy with the previously installed Woody. (I can ssh in and tunnel X to run gnome apps no problem. In fact I'm running evolution on the machine over X/ssh to send this email, so my issues seem to be more to do with the X server setup; I haven't had much time to investigate further though). Other things: I am a little surprised that lsmod shows pcmcia_core loaded (none of my other non-laptop machines loads this). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240937: installation-reports: beta3 i386 When no hard drive present, partitioning menus make no sense
Package: installation-reports Version: Debian Installer Beta 3 Severity: minor Dell Dimension X400 - installed with no IDE hard drive in the box, booted from floppies boot.img and root.img - came up fine. When reached the partitioning menu, I realized I had not put a HD in the machine at all - the only media devices were cdrom and floppy. The Partition menu was weird and circular in this case, rather than pointing out there was not any device acceptable to recevie the installation. Keep up the good work - this installer looks GREAT! Once I put an actual hard drive in the system, it came up perfectly - you guys rock! Matt Weatherford seattle, wa note: this bug NOT reported on the actual system that was installed. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.3-1-686-smp Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#239627: mails stupid debconf note to user when lilo is installed in d-i
Joey Hess [EMAIL PROTECTED] writes: Package: lilo, lilo-installer Severity: normal Tags: d-i When lilo-installer installs lilo in the debian installer, lilo tries to display a debconf note warning the user that they need to run /sbin/lilo. Since it is running in noninteractive mode, debconf mails If you look into the lilo.config file on debian directory of the lilo source, you will notice that this warning is being displayed because there is a file called /boot/boot.b being either a symbolic link or a normal file. Those files were used by lilo prior to 22.3.3 versions and you _really_ need to rerun lilo if you are upgrading from such lower versions. This is the case when upgrading from woody to sarge. That's why this debconf note is there. The question is, why are those files there when installing a new system? Newer versions of lilo don't create that file. If lilo-installer is creating it, I'd really want to know why. this note to root (exim redirects it to user mail). Then lilo-installer goes on and runs lilo to make the system bootable; exactly what the note was warning needs to be done. This is especially annoying if the DNS of the machine is messed up, then there is a blue screen in d-i while lilo is installed, waiting for a DNS timeout. This needs to be integrated better. If lilo truely needs to display this note (why? grub does not display a similar note), then there needs to be some mechanism for lilo to be told that it is being installed by lilo-installer, and that lilo-installer will take care of this and the note need not be displayed in this case. -- see shy jo -- Andrés Roldán [EMAIL PROTECTED] GPG Key-ID: 0xB29396EB http://people.fluidsignal.com/~aroldan pgp0.pgp Description: PGP signature
Re: kernel 2.2 packages cleanup
Heyho, Adrian Bunk [EMAIL PROTECTED] writes: - lids-2.2 Can definitely be removed since I am thinking about orphaning the lids packages at all. But you'll hear from me about that. david -- |David Spreen | Debian GNU Developer | |Email: [EMAIL PROTECTED]| http://www.debian.org/| |--| |1024D/FCB1DD23: C6AE BDCC 834C 8118 71A3 6341 7611 2FBC FCB1 DD23| -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: m68k bootloader package(s)?
Stephen R Marenka [EMAIL PROTECTED] writes: Right now the amiga and mac m68k bootloaders don't exist in the debian archive. This probably makes sense, because they aren't linux programs. However, it makes locating them and making them available for cdroms and such more trouble. The total size is about 2MB. What do ya'll think, should I put them in a package for convenience or just leave them on a website? Thanks, Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! [EMAIL PROTECTED] Please do. An udeb is probably enough unless you want to add scripts to install it to AFFS (for amiboot). MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
modprobe usb-storage
This is primarily a request for better documentation. I desparately need to get memory sticks working on my Sony Vaio (PCG-Z505FA) The stuff I've found on the web falls into 3 categories: no idea; it just works on theirs; and modprobe several packages. I've installed from the official stable Debian release 3.0 but can find no way to get useful information out of modprobe usb-storage It is possible that the module is already in (lsmod doesn't see it if it is and mounting the memorystick doesn't work.) If it is not there, where do I find it in the CDs, has it been replaced, what is the alternative? Peter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#239627: mails stupid debconf note to user when lilo is installed in d-i
Andrés Roldán wrote: If you look into the lilo.config file on debian directory of the lilo source, you will notice that this warning is being displayed because there is a file called /boot/boot.b being either a symbolic link or a normal file. Those files were used by lilo prior to 22.3.3 versions and you _really_ need to rerun lilo if you are upgrading from such lower versions. This is the case when upgrading from woody to sarge. That's why this debconf note is there. The question is, why are those files there when installing a new system? Newer versions of lilo don't create that file. If lilo-installer is creating it, I'd really want to know why. Could it have anything to do with the lilo.conf file having install=/boot/boot.b in it? -- see shy jo signature.asc Description: Digital signature
Bug#240952: installation-reports
Package: installation-reports INSTALL REPORT Debian-installer-version: 18-03-2004 03:30 http://gluck.debian.org/cdimage/testing/sarge_d-i/i386/beta3/sarge-i386-netinstall.iso uname -a: Linux trinitynew 2.6.3-1-686-smp #2 SMP Tue Feb 24 20:29:08 EST 2004 i686 GNU/Linux Date: 25-03-2004 03:00.00 Method: Base install from cd-rom after reboot network install from ftp.nl.debian.org (not proxied) Machine: Clone Processor: Dual P3 800 Mhz Memory: 1024 Mb Root Device: IDE Seagate 30 Gb Root Size/partition table: Device Boot Start End Blocks Id System /dev/hda1 11275102414067 HPFS/NTFS /dev/hda212761287 96390 83 Linux /dev/hda312881409 979965 83 Linux /dev/hda41410372218579172+ f W95 Ext'd (LBA) /dev/hda514102017 4883728+ 83 Linux /dev/hda620182503 3903763+ 83 Linux /dev/hda725043597 8787523+ 83 Linux /dev/hda835983722 1004031 82 Linux swap Output of lspci: 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4) 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 16) 00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 16) 00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) 00:0a.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang] 00:0b.0 Multimedia audio controller: Creative Labs: Unknown device 0007 00:0b.1 Input device controller: Creative Labs: Unknown device 7005 00:0e.0 Unknown mass storage controller: Triones Technologies, Inc. HPT366/368/370/370A/372 (rev 03) 01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5964 (rev 01) 01:00.1 Display controller: ATI Technologies Inc: Unknown device 5d44 (rev 01) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Switched into the expert mode to get the 2.6 kernel. No problems found. Regards, Michel van der Klei signature.asc Description: This is a digitally signed message part
Bug#238038: marked as done (discover: changelog names README.Debian, but none there)
Your message dated Mon, 29 Mar 2004 21:24:29 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#238038: acknowledged by developer (Bug#238038: fixed in discover1 1.5-7) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 14 Mar 2004 22:37:25 + From [EMAIL PROTECTED] Sun Mar 14 14:37:25 2004 Return-path: [EMAIL PROTECTED] Received: from piggy.rz.tu-ilmenau.de [141.24.4.8] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1B2eEX-0001AE-00; Sun, 14 Mar 2004 14:37:25 -0800 Received: from gate.22.kls.lan (vpn31.rz.tu-ilmenau.de [141.24.172.31]) by piggy.rz.tu-ilmenau.de (8.12.10/8.12.10) with ESMTP id i2EMbLm9023167 for finalrecipients; Sun, 14 Mar 2004 23:37:23 +0100 (MET) Received: from darkside.22.kls.lan ([EMAIL PROTECTED] [192.168.22.1]) by gate.22.kls.lan (8.12.11.Beta0/8.12.11.Beta0) with ESMTP id i2EMbLCU020810 for [EMAIL PROTECTED]; Sun, 14 Mar 2004 23:37:21 +0100 Received: from darkside.22.kls.lan ([EMAIL PROTECTED] [127.0.0.1]) by darkside.22.kls.lan (8.12.11/8.12.11) with ESMTP id i2EMbLHK005073 for [EMAIL PROTECTED]; Sun, 14 Mar 2004 23:37:21 +0100 Received: (from [EMAIL PROTECTED]) by darkside.22.kls.lan (8.12.11/8.12.11) id i2EMbKsI005071 for [EMAIL PROTECTED]; Sun, 14 Mar 2004 23:37:20 +0100 Date: Sun, 14 Mar 2004 23:37:20 +0100 From: Mario 'BitKoenig' Holbe [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: discover: changelog names README.Debian, but none there Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.5.1+cvs20040105i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_12 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_12 X-Spam-Level: Package: discover Version: 1.5-3 Severity: minor Hello, the discover changelog states: discover (1.5-3) unstable; urgency=low ... * Add README.Debian documenting how to deal with 2.6 issues But there is no README.Debian or anything like this. regards, Mario -- reich sein heisst nicht, einen Ferrari zu kaufen, sondern einen zu verbrennen Dietmar Wischmeier --- Received: (at 238038-done) by bugs.debian.org; 30 Mar 2004 02:24:31 + From [EMAIL PROTECTED] Mon Mar 29 18:24:31 2004 Return-path: [EMAIL PROTECTED] Received: from out004pub.verizon.net (out004.verizon.net) [206.46.170.142] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1B88vW-0002xh-00; Mon, 29 Mar 2004 18:24:30 -0800 Received: from squee ([68.160.34.247]) by out004.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id [EMAIL PROTECTED]; Mon, 29 Mar 2004 20:24:30 -0600 Received: by squee (Postfix, from userid 1000) id 456EE4755B; Mon, 29 Mar 2004 21:24:29 -0500 (EST) Date: Mon, 29 Mar 2004 21:24:29 -0500 From: David Nusinow [EMAIL PROTECTED] To: Mario 'BitKoenig' Holbe [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#238038: acknowledged by developer (Bug#238038: fixed in discover1 1.5-7) Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] User-Agent: Mutt/1.5.5.1+cvs20040105i X-Authentication-Info: Submitted using SMTP AUTH at out004.verizon.net from [68.160.34.247] at Mon, 29 Mar 2004 20:24:30 -0600 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: On Mon, Mar 29, 2004 at 07:57:10PM +0200, Mario 'BitKoenig' Holbe wrote: reopen 238038 thanks On Wed, Mar 24, 2004 at 10:03:06PM -0800, Debian Bug Tracking System wrote: Version: 1.5-7 - Actually include that README.Debian; Closes: #238038 Hmmm, the README is missing again, now with: Package: discover Version: 2.0.3-4 This README is for discover version 1.x. It is in the discover1 package now, as we're in a
Re: exim cannot find gnutls
On Mon, Mar 29, 2004 at 08:40:39PM +0200, Joeri van Ruth wrote: I'm trying to use the daily build of 2004-03-28 to install Sarge on a compaq deskpro 5000. (Pentium 200, 2G harddisk.) I have two 3com 905 ethernet cards in it. I'm using the netinst daily because beta 3 hangs in the partition manager. The first part of the installer works fine, but while installing the base system, all programs that depend on the mail-transport-agent fail because exim4 cannot find gnutls libraries. Exactly what images are you using? The 20040328 sarge-i386-netinst.iso I'm looking at contains a version of debootstrap that fixes this. Alternatively, might you be using an HTTP proxy that is giving you old data? -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240959: installation-reports
Package: installation-reports Debian-installer-version: http://gluck.debian.org/cdimage/testing/sarge_d-i/i386/beta3/sarge-i386-netinst.iso, 29th March 04 uname -a: Linux zombie 2.4.25-1-386 #1 Tue Feb 24 08:11:13 EST 2004 i386 unknown Date: 30th March 04 Method: Boot from CD Machine: Dell Optiplex GX1 Processor: PIII 450 Memory: 256MB Root Device: IDE (WD400BB) Root Size/partition table: works fine Output of lspci: not found Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [E] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: CD image would boot after POST screen and initialise the installer, but would not be able to mount the net-install CDROM to install the base system. Gave error message saying possibly use net install method instead. Downloaded net install floppy images (blech) and currently downloading base packages after successfully partitioning HDD. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#239627: mails stupid debconf note to user when lilo is installed in d-i
Joey Hess wrote: Andrs Roldn wrote: If you look into the lilo.config file on debian directory of the lilo source, you will notice that this warning is being displayed because there is a file called /boot/boot.b being either a symbolic link or a normal file. Those files were used by lilo prior to 22.3.3 versions and you _really_ need to rerun lilo if you are upgrading from such lower versions. This is the case when upgrading from woody to sarge. That's why this debconf note is there. The question is, why are those files there when installing a new system? Newer versions of lilo don't create that file. If lilo-installer is creating it, I'd really want to know why. Could it have anything to do with the lilo.conf file having install=/boot/boot.b in it? Probably. It shouldn't; it shouldn't really have any install= line at all by default, for a current version -- or install=menu, which is much like the default -- or install=bmp, which is correct if there's a bitmap= option in the file. -- Make sure your vote will count. http://www.verifiedvoting.org/
unsubscribe
Regards Thomas E. Kamire Systems Engineer Kenya Airways Ltd, P.O. BOX 41010 Nairobi, Kenya Tel: +254+2+32822311 Cell: +254 722 483 253 [EMAIL PROTECTED] Lets Make Things Better - Together -Original Message- From: Nathanael Nerode [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 7:17 AM To: Subject: Re: Bug#239627: mails stupid debconf note to user when lilo is installed in d-i Joey Hess wrote: Andrés Roldán wrote: If you look into the lilo.config file on debian directory of the lilo source, you will notice that this warning is being displayed because there is a file called /boot/boot.b being either a symbolic link or a normal file. Those files were used by lilo prior to 22.3.3 versions and you _really_ need to rerun lilo if you are upgrading from such lower versions. This is the case when upgrading from woody to sarge. That's why this debconf note is there. The question is, why are those files there when installing a new system? Newer versions of lilo don't create that file. If lilo-installer is creating it, I'd really want to know why. Could it have anything to do with the lilo.conf file having install=/boot/boot.b in it? Probably. It shouldn't; it shouldn't really have any install= line at all by default, for a current version -- or install=menu, which is much like the default -- or install=bmp, which is correct if there's a bitmap= option in the file. -- Make sure your vote will count. http://www.verifiedvoting.org/
Re: Create bootable CD with custom kernel
On Mon, 2004-03-29 at 18:52, Sven Luther wrote: No guarantee though, as the module and versioned symbols stuff is still mostly black magic for me. Indeed, that is exactly why I am hanging around this 200 mails per day debian-boot list :). It my interest to learn this black magic, especially black magic modules like NVIDIA and PCMCIA... tschuess, -- Rahmat M. Samik-Ibrahim -- vLSM.org -- http://rms46.vLSM.org/ -- Fetch my GNUPG public key at http://rms46.vlsm.org/pgp/pub.txt --- signature.asc Description: This is a digitally signed message part
Bug#240963: Sarge Beta 3 Report
Package: installation-reports Debian-installer-version: http://gluck.debian.org/cdimage/testing/sarge_d-i/i386/beta3/sarge-i386-netinst.iso uname -a: Linux atussa3 2.4.25-1-386 #1 Tue Feb 24 08:11:13 EST 2004 i686 GNU/Linux Date: March 29, 2004 Method: I chose FTP for package source instead of CDROM because it couldn't see my /dev/cdrom Machine: Compaq Presario Processor: 1ghz Athlon Memory: 256MB Root Device: IDE hard drive Root Size/partition table: 60GB Output of lspci: 00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] System Controller (rev 25) 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] AGP Bridge (rev 01) 00:04.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07) 00:04.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 07) 00:06.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX (rev 10) 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 14) 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE () 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 06) 00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 06) 00:07.4 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 10) 00:0c.0 FireWire (IEEE 1394): Texas Instruments TSB12LV23 IEEE-1394 Controller 00:0f.0 Modem: PCTel Inc HSP MicroModem 56 (rev 02) 01:05.0 VGA compatible controller: nVidia Corporation NV15 [GeForce2 GTS/Pro] (rev a3) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [E] The CD drive wasn't detected, and therefore I had to use a network install from FTP. Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: I am new to Debian, but hope to switch permenantly from Redhat/Fedora once Sarge goes stable. I took basically every default, and stopped at the package selection screen that listed taskel, etc... I went to McDonalds and came back about 30 minutes later. There was a strange error written over the taskel option. I think it might have had something to do with power management kicking in or something. Anyway, it only caused cosmetic problems with the menu, everything else seemed to work fine. Except once I selected taskel and then selected a Desktop installation... packages were downloaded, but then it said that all of the selected packages couldn't be installed. I selected taskel again, and then desktop install again. Then everything seemed to go through without error. Once GDM started up, I logged into KDE. Then I got the following error: --- Sound server informational message: Error while initializing the sound driver: device /dev/dsp can't be opened (Permission denied) The sound server will continue, using the null output device. --- I think it goes without saying that sound doesn't work. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240959: additional information
I did attempt to mount the CDROM using an extra console (mount /dev/cdroms/cd0 /cdrom; or similar.. i forget the exact paths) but it wouldn't mount the disc. the symlink was pointing to what looked like a SCSI emulation of my IDE CDROM device. post-install the symlink is pointing to /dev/hdc as it should. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: USB Mass Storage installation
Il mar, 2004-03-30 alle 01:17, Tom Allison ha scritto: I'm building a new USB mass storage device from the 0329 netinstall.iso: Using the installation manual section 4.4.1: zcat boot.img.gz /dev/sda (was gzip -cd and not zcat) mount -t vfat /dev/sda /mnt cp sarge-i386-netinst.iso /mnt sync (I added this) umount /mnt [...] No sure about this, but I think it should be: 0. insterst USB and check in /var/log/syslog that it is recongnized as /dev/sda 1. zcat boot.img.gz /dev/sda 2. mount -t vfat /dev/sda1 /mnt 3. cp sarge-i386-netinst.iso /mnt 4. umount /mnt (this will also sync) 5. reboot The mount command require a partition name (/dev/sda1) and not a disk name (/dev/sda). If this work then I think the installation manual should be corrected too. Bye, Giuseppe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
net install disk loses nic drivers
Hello! I've been using the net install disk -- the 30mb iso image to boot up and download all files needed for the debian install. During the install, everything is great. After the first reboot during the installation, the nic drivers/modules do not load. This is happening with sarge and sid, various 2.4 and 2.6 kernels. Any ideas how to correct this other than keeping a copy of the driver on disk for the install? Thanks! Christopher Davis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
gdm templates, common templates (was: Re: Update to Debian Installer translators documentation)
Quoting Konstantinos Margaritis ([EMAIL PROTECTED]): The culprit template has been removed very recently after a bug report I made, as this was so-called debconf abuse. It also seems that gdm is not available for translation as well, probably a similar case? I don't exactly understand your point thereyou mean gdm templates? I guess they're available just like other po-debconf templates from: http://people.debian.org/~barbier/intl/l10n/po-debconf/ By the way, these *dm templates are common templates, IIRC. Such common templates are currently not handled very efficiently as they are in all packages which uses them instead of being separate so that they're translated only once. Among the dozens ideas I have without time for making them real, a debconf-common-templates package exists: -nothing in it except debconf templates -includes all common templates used by several packages such as Database serveur host, Database name, Database userused by gazillions of *sql-based packages Packages which want to use these templates would then only need to register them with debconf This would save a lot of translation time, for sureand this would also help in getting consistency among packages. I deeply hope I will have something ready before debconf so that I may include somehting about this in my talk there. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: m68k bootloader package(s)?
On Wed, Mar 17, 2004 at 01:41:16PM -0600, Stephen R Marenka wrote: Right now the amiga and mac m68k bootloaders don't exist in the debian archive. This probably makes sense, because they aren't linux programs. However, it makes locating them and making them available for cdroms and such more trouble. The total size is about 2MB. What do ya'll think, should I put them in a package for convenience or just leave them on a website? I would recomend uploading them to contrib. After all, if i remember well, both amiboot and apusboot are GPLed software, which just need a foreign toolchain to build. The same will go for miboot, once we have reimplemented the first boot stage of it. See the thread about boot loaders i started, and the legal problems that have to do with it. This means that debian-installer in main will not be able to build depend on them, which is a shame, but we may create a debian-installer-contrib or whatever, which will build the needed stuff for them, as joeyh suggested. I have no idea how this can be regrouped into debian-cd or whatever later on. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
On Mon, Mar 29, 2004 at 10:56:21PM +0100, Henning Makholm wrote: Scripsit Sven Luther [EMAIL PROTECTED] On Mon, Mar 29, 2004 at 12:52:12AM +0100, Henning Makholm wrote: Huh? Is the bootsector use written in a kind of machine language that the regular as(1) for the architecture does not support? I thought that i386 was the only platform with *that* problem. I suppose that the boot sector may contain a bit more than the standard elf or coff format. Not sure though. In the absence of other evidence I'd assume that it's a short fixed header followed by raw machine code, designed to be loaded at some magic address and executed immediately. It *may* take a custom ld(1) script to produce quite the right setup, but after that, getting it into a usable format should be a simple matter - use objdump and a short piece of perl if everything else fails. Notice that benh, the miboot author, told me that he was not really in the clear how the hardware passes control to boot1, and thus didn't try to make a clean reimplementation. So, altough i didn't look at it, it may contain a bit more than just plain assembly output, checksums, and other markers maybe. Google macintosh boot block turns up official Apple information that seems like it might be what you're looking for. (And which it would be OK to look at for a cleanroom implementor). Ok, will have a look. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
On Mon, Mar 29, 2004 at 10:56:21PM +0100, Henning Makholm wrote: Scripsit Sven Luther [EMAIL PROTECTED] On Mon, Mar 29, 2004 at 12:52:12AM +0100, Henning Makholm wrote: Huh? Is the bootsector use written in a kind of machine language that the regular as(1) for the architecture does not support? I thought that i386 was the only platform with *that* problem. I suppose that the boot sector may contain a bit more than the standard elf or coff format. Not sure though. In the absence of other evidence I'd assume that it's a short fixed header followed by raw machine code, designed to be loaded at some magic address and executed immediately. It *may* take a custom ld(1) script to produce quite the right setup, but after that, getting it into a usable format should be a simple matter - use objdump and a short piece of perl if everything else fails. Google macintosh boot block turns up official Apple information that seems like it might be what you're looking for. (And which it would be OK to look at for a cleanroom implementor). Mmm, i found it : http://developer.apple.com/documentation/mac/Files/Files-101.html I have a fear suspision that this may be more related to newworld, than the oldworld stuff needed for miboot, which may probably be varying between the different models we may need to support. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: gdm templates, common templates (was: Re: Update to Debian Installer translators documentation)
On Tue, Mar 30, 2004 at 07:42:26AM +0200, Christian Perrier wrote: Quoting Konstantinos Margaritis ([EMAIL PROTECTED]): [...] It also seems that gdm is not available for translation as well, probably a similar case? I don't exactly understand your point thereyou mean gdm templates? I guess they're available just like other po-debconf templates from: http://people.debian.org/~barbier/intl/l10n/po-debconf/ No, gdm does not use po-debconf, you filed a bugreport with a patch 8 months ago (#200121). Unfortunately Josselin Mouette did not hijack gdm, so this bugreport won't be fixed soon. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
On Mon, Mar 29, 2004 at 01:10:36PM -0800, Jeff Bailey wrote: On Mon, Mar 29, 2004 at 04:05:48PM -0500, Branden Robinson wrote: Hacker #2 affirms that he has never looked at the existing boot sector, and will not do so in the future. He or she understands MacOS well enough to know how to hand-code 1kB worth of assembly (or possibly compilable C code) to create a functionally-identical boot sector from the plain English description. If I understand right from my GNU hacking, it's preferable to take a slightly different approach if possible. Doing some of it in C instead of ASM (if at all possible, obviously) might result in that anyway. Notice that there is 200bytes or so of m68k asm, most of them A-trap calls to the Mac OS rom, concerned. I doubt you have much chance of getting anything but a 100% identical code, whatever the way you go at generating it. Anything you may do, these calls are needed, you could add some noop calls in between, or some random stuff, but i doubt that this will be more than smoke and mirrors. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
On Mon, Mar 29, 2004 at 11:53:49PM +0100, Henning Makholm wrote: Scripsit Branden Robinson [EMAIL PROTECTED] Worse case scenario, this could be clean-room reimplemented. Before doing that, somebody ought to approach Apple and ask explicit permission to reverse-engineer the boot-block code and distribute the reverse-engineered source under a free license. The worst that can happen is that the request ends up with some clueless corporate lawyer whose instinctive reaction is, No way; that's *our* IP - but if he has the slightest bit of clue he will realise that Apple does not really have any commercial interest in clinging to this particular piece of IP. some 50 or so m68k assembly instruction to call rom functions on obsolet and not supported anymore hardware, i seriously doubt even the cluelesslest corporate lawyer will have a problem with that. But stay tuned, something interesting may come out of this discussion, and thanks to Henning Makholm for providing the link to the boot sector docs at apple, altough it needs to be taken with a grain of salt, as it seems to contradict itself in many places. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
On Sun, Mar 28, 2004 at 10:30:23PM +0100, Matthew Garrett wrote: Sven Luther wrote: 1) A description in text form of what the individual bits of this 1K boot sector does, and what is needed for miboot booting. 2) a small C program or shell script which generate said 1K boot sector from some kind of more formal version of the above description. If you can document the functionality of the code (and this instruction followed by this instruction followed by this instruction isn't good enough - describe what's happening) and if someone else then writes an implementation based on that and releases it under a free license, we can ship it. And what about a : call mac os rom function 'blah', followed by call to mac os rom function 'foo' and so on ? And it happens that there is only one recomended way of making those macos rom functions (A-traps i hear) ? This doesn't solve the other problem, and namely the fact that miboot and other boot loaders are not buildable from main without a considerable cross compiler development effort, which may not be worth it. Yes, that's somewhat more of an issue. I'd expect amiboot to be buildable without excessive effort, although the Amiga includes aren't Free. We can't really ship amiboot as part of d-i anyway - it's a loadlin equivilent, not a syslinux one. Amiga-lilo used to exist and The main difference being that all the stuff needed are part of the amiga rom, while this is not the case for msdos, if i remember well. I think that the easiest way would be to have a amiga bootable partition, with amiboot and the auto-executing amiga shell script needed to launch it. This may all be installable from linux, provided either i finish the affs create implementation in libparted, or we package Roman Zippel's mkaffs. This would be a rather clean way of doing this, and you can even rely on the early amiga-rom based boot selector, and play with boot priorities to have it auto loaded or go to amiga os. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
