cvs commit to boot-floppies/utilities/dbootstrap/po by aph
Repository: boot-floppies/utilities/dbootstrap/po who:aph time: Mon Jul 9 00:51:19 PDT 2001 Log Message: update-po Files: changed:cs.po da.po de.po eo.po es.po fi.po fr.po gl.po hr.po hu.po it.po ja.po ko.po pl.po pt.po ru.po sk.po sv.po tr.po zh_CN.po -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/utilities/dbootstrap/po by aph
Repository: boot-floppies/utilities/dbootstrap/po who:aph time: Mon Jul 9 00:52:26 PDT 2001 Log Message: remove zh_TW here as well Files: changed:Makefile -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp-client uselessness on powerpc
On Sun, Jul 08, 2001 at 06:01:06PM -0800, Ethan Benson wrote: > another problem with dhcp-client is it prevents manual network > configuration since the maintainer apparently won't remove or alter > the initscript that runs it on every boot. /etc/network/interfaces is > how we do things since potato its time to move on. (bug filed over a > year ago). That is probably unfair, ref bug #98680. I am about to test the 3.0 version on hppa... Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp-client uselessness on powerpc
On Sun, Jul 08, 2001 at 06:01:06PM -0800, Ethan Benson wrote: > On Sun, Jul 08, 2001 at 08:44:40PM -0500, Stephen R Marenka wrote: > > > > I've never had trouble with dhcp-client on my powerpc -- what gives? > > maybe its because i have a bootp server instead of a dhcp server, but > accoring to the fucking manual that should not matter. Maybe that's the difference, mine's a dhcp server. I don't suppose you're in a position to test that? Are you using the bootp package? Maybe I can scrounge a test system together. > personally im thinking we should go back to pump but then i don't give > a damn either way. Actually, the reason I put dhcp-client in is that pump wouldn't work on my powerpc. I guess we've gone full circle. :-\ Certainly it's easy enough to control since dbootstrap loads whichever one it finds, so mess with the extract files to switch back and forth. > another problem with dhcp-client is it prevents manual network > configuration since the maintainer apparently won't remove or alter > the initscript that runs it on every boot. /etc/network/interfaces is > how we do things since potato its time to move on. (bug filed over a > year ago). The top of the init script on my machine looks like the following. if [ -f /etc/network/interfaces ]; then grep -q '^iface.*dhcp' /etc/network/interfaces && exit 0 fi Doesn't this mean that it exits if it encounters a dhcp entry in interfaces? Thanks, Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! <[EMAIL PROTECTED]> PGP signature
Re: dhcp-client uselessness on powerpc
On Mon, Jul 09, 2001 at 06:55:01AM -0500, Stephen R Marenka wrote: > > Maybe that's the difference, mine's a dhcp server. I don't suppose > you're in a position to test that? Are you using the bootp package? > Maybe I can scrounge a test system together. eb@plato eb$ dlocate -s bootp | grep ^Ver Version: 2.4.3-3 you can see my bootptab if you want, pump, OpenFirmware and MacOS all work fine with it so i am not inclined to believe its misconfigured. i have no interest in setting up a dhcp server. > Actually, the reason I put dhcp-client in is that pump wouldn't work on > my powerpc. I guess we've gone full circle. :-\ pump has never failed for me, but all i ever used it for was testing that bootp network config in boot-floppies worked, and it does for potato which uses pump. > Certainly it's easy enough to control since dbootstrap loads whichever > one it finds, so mess with the extract files to switch back and forth. to what end? pump works, dhcp-client does not. > The top of the init script on my machine looks like the following. > > if [ -f /etc/network/interfaces ]; then > grep -q '^iface.*dhcp' /etc/network/interfaces && exit 0 > fi > > Doesn't this mean that it exits if it encounters a dhcp entry in > interfaces? yup, and it means it runs if it doesn't find one, which means if your network is configured statically in /e/n/interfaces dhcp runs off and fucks it up, lets demonstrate shall we? root@socrates /root# cat /sbin/dhclient #!/bin/sh echo "i have now fucked your networking, have a nice day" exit 0 root@socrates /root# cat /etc/network/interfaces # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface iface lo inet loopback iface eth0 inet static address 192.168.0.1 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 gateway 192.168.0.10 root@socrates /root# /mnt/etc/init.d/dhcp-client start i have now fucked your networking, have a nice day root@socrates /root# that initscript should have exited without doing anything because my network is statically configured. this is the dhcp-client installed by debootstrap less then a week ago, current woody. -- Ethan Benson http://www.alaska.net/~erbenson/ PGP signature
Re: dhcp-client uselessness on powerpc
On Mon, Jul 09, 2001 at 04:24:17AM -0800, Ethan Benson wrote: > On Mon, Jul 09, 2001 at 06:55:01AM -0500, Stephen R Marenka wrote: > > > > Maybe that's the difference, mine's a dhcp server. I don't suppose > > you're in a position to test that? Are you using the bootp package? > > Maybe I can scrounge a test system together. > > eb@plato eb$ dlocate -s bootp | grep ^Ver > Version: 2.4.3-3 > > you can see my bootptab if you want, pump, OpenFirmware and MacOS all > work fine with it so i am not inclined to believe its misconfigured. > > i have no interest in setting up a dhcp server. I didn't mean to imply it was your bootp problem, but rather the problem with dhcp-client may be specific to your setup. I was considering what it would take to try to reproduce this. > > Actually, the reason I put dhcp-client in is that pump wouldn't work on > > my powerpc. I guess we've gone full circle. :-\ > > pump has never failed for me, but all i ever used it for was testing > that bootp network config in boot-floppies worked, and it does for > potato which uses pump. Pump has repeatedly failed for me on a production dhcp network and on multiple, different powerpc machines. However, I haven't tried the latest version with the latest bf. > > Certainly it's easy enough to control since dbootstrap loads whichever > > one it finds, so mess with the extract files to switch back and forth. > > to what end? pump works, dhcp-client does not. pump works for you. But the point of the statement was it's easy enough to switch back to pump, just change the extract files. > > The top of the init script on my machine looks like the following. > > > > if [ -f /etc/network/interfaces ]; then > > grep -q '^iface.*dhcp' /etc/network/interfaces && exit 0 > > fi > > > > Doesn't this mean that it exits if it encounters a dhcp entry in > > interfaces? > > yup, and it means it runs if it doesn't find one, which means if your > network is configured statically in /e/n/interfaces dhcp runs off and > fucks it up, lets demonstrate shall we? > > root@socrates /root# cat /sbin/dhclient > #!/bin/sh > echo "i have now fucked your networking, have a nice day" > exit 0 > root@socrates /root# cat /etc/network/interfaces > # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) > > # The loopback interface > iface lo inet loopback > > iface eth0 inet static > address 192.168.0.1 > netmask 255.255.255.0 > network 192.168.0.0 > broadcast 192.168.0.255 > gateway 192.168.0.10 > root@socrates /root# /mnt/etc/init.d/dhcp-client start > i have now fucked your networking, have a nice day > root@socrates /root# > > that initscript should have exited without doing anything because my > network is statically configured. Which only proves that the script ran and the daemon is running needlessly. I agreed it's screwed up, but not that it fucked up your network. My home network is static and my work is dhcp, I switch back and forth regularly with dhcp-client managing not to cause problems. I would expect that without a dhclient.conf (or whatever) that it doesn't configure any interfaces. So, is your complaint substantive? Has dhcp-client actually screwed up your static network (when it runs, that is ;-)? Just curious. > this is the dhcp-client installed by debootstrap less then a week ago, > current woody. It'd be nice if we had a small bootp/dhcp client that didn't have so many bugs (especially old ones) filed against it. I want a gripping hand choice. -- Stephen R. Marenka If life's not fun, you're not doing it right! <[EMAIL PROTECTED]> PGP signature
Re: dhcp-client uselessness on powerpc
On Mon, Jul 09, 2001 at 07:51:33AM -0500, Stephen R Marenka wrote: > > Which only proves that the script ran and the daemon is running > needlessly. I agreed it's screwed up, but not that it fucked up your > network. My home network is static and my work is dhcp, I switch back > and forth regularly with dhcp-client managing not to cause problems. I > would expect that without a dhclient.conf (or whatever) that it doesn't > configure any interfaces. So, is your complaint substantive? Has > dhcp-client actually screwed up your static network (when it runs, that > is ;-)? Just curious. yes it has and does, see the bug report. if the network is statically configured dhcp should /not/ run. why is this so difficult? its much faster to just fix the fscking bug rather then argue stupid excuses not to fix it. -- Ethan Benson beginning to think i should stop wasting my time on this project http://www.alaska.net/~erbenson/ PGP signature
Bug#77766: marked as done ([i386] pcmcia modules w/o symbols not found)
Your message dated Mon, 09 Jul 2001 11:45:26 -0400 with message-id <[EMAIL PROTECTED]> and subject line Closing old report 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.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 23 Nov 2000 00:15:15 + >From [EMAIL PROTECTED] Wed Nov 22 18:15:15 2000 Return-path: <[EMAIL PROTECTED]> Received: from (burrito.onshore.com) [64.22.101.122] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13yk2k-0002XT-00; Wed, 22 Nov 2000 18:15:14 -0600 Received: from arroz.fake (localhost [127.0.0.1]) by burrito.onshore.com (Postfix) with ESMTP id E260F93802; Wed, 22 Nov 2000 19:15:41 -0500 (EST) Sender: [EMAIL PROTECTED] To: Andreas Schuldei <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: [i386] pcmcia modules w/o symbols not found References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> From: Adam Di Carlo <[EMAIL PROTECTED]> Date: 22 Nov 2000 19:15:41 -0500 In-Reply-To: Andreas Schuldei's message of "Tue, 21 Nov 2000 19:37:11 +0100" Message-ID: <[EMAIL PROTECTED]> Lines: 29 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Delivered-To: [EMAIL PROTECTED] Package: pcmcia-modules-2.2.18pre21, boot-floppies Severity: important Version: 3.1.22-0.1potato Andreas Schuldei <[EMAIL PROTECTED]> writes: > * Adam Di Carlo ([EMAIL PROTECTED]) [001121 19:34]: > > Andreas Schuldei <[EMAIL PROTECTED]> writes: > > > > > * Adam Di Carlo ([EMAIL PROTECTED]) [001119 21:58]: > > > > > > I got a problem with the bootfloppys 2000-11-19: > > > when I try to configure pcmcia on my HP Omnibook insmod fails for pcmcia_core > > > and i82365 due to unresolved symbols. As well you get a pile of unresolved > > > sysmbols on depmod -a. > > > > Which flavor of kernel? > the default one straight form the normal directory. I can confirm this problem. This email is a critical bug report. The package which has the problem is pcmcia-modules-2.2.18pre21_3.1.22-0.1potato_i386.deb I guess I'll try to get that fixed ASAP for boot-floppies 2.2.19 i386. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> --- Received: (at 77766-done) by bugs.debian.org; 9 Jul 2001 15:50:09 + >From [EMAIL PROTECTED] Mon Jul 09 10:50:08 2001 Return-path: <[EMAIL PROTECTED]> Received: from tisch.mail.mindspring.net [:::207.69.200.157] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 15JdIW-00012U-00; Mon, 09 Jul 2001 10:50:08 -0500 Received: from ariel.local.net (sdn-ar-002vacharP230.dialsprint.net [168.191.213.246]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id LAA08717 for <[EMAIL PROTECTED]>; Mon, 9 Jul 2001 11:49:58 -0400 (EDT) Received: from ariel (localhost [127.0.0.1]) by ariel.local.net (Postfix) with ESMTP id 8B314DFDD for <[EMAIL PROTECTED]>; Mon, 9 Jul 2001 11:45:26 -0400 (EDT) To: [EMAIL PROTECTED] Subject: Closing old report From: [EMAIL PROTECTED] Date: Mon, 09 Jul 2001 11:45:26 -0400 Sender: [EMAIL PROTECTED] Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] This was fixed long ago. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: BusyBox 0.52 uploaded to unstable
On Sat, Jul 07, 2001 at 03:29:25AM -0600, Erik Andersen wrote: > I just released busybox 0.52 and new busybox packages are now sitting > in incoming. Things look quite solid, but some actual testing with the > boot floppies is probably needed before this gets moved into woody and > becomes part of the boot floppies. Works fine in boot-floppies for hppa. Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp-client uselessness on powerpc
On Mon, Jul 09, 2001 at 12:08:37PM +0100, Richard Hirst wrote: > On Sun, Jul 08, 2001 at 06:01:06PM -0800, Ethan Benson wrote: > > another problem with dhcp-client is it prevents manual network > > configuration since the maintainer apparently won't remove or alter > > the initscript that runs it on every boot. /etc/network/interfaces is > > how we do things since potato its time to move on. (bug filed over a > > year ago). > > That is probably unfair, ref bug #98680. I am about to test > the 3.0 version on hppa... Tested dhcp-client 3.0beta2RC10-1 with both dhcp and static eth0 configurations. Worked fine, doesn't install any /etc/init.d script. Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: BusyBox 0.52 uploaded to unstable
On Mon Jul 09, 2001 at 06:04:37PM +0100, Richard Hirst wrote: > On Sat, Jul 07, 2001 at 03:29:25AM -0600, Erik Andersen wrote: > > I just released busybox 0.52 and new busybox packages are now sitting > > in incoming. Things look quite solid, but some actual testing with the > > boot floppies is probably needed before this gets moved into woody and > > becomes part of the boot floppies. > > Works fine in boot-floppies for hppa. Excellent! Thanks for the report Richard. I vote we move busybox 0.52 into the woody boot floppies then. I already had about 1/2 of the changes for 0.52's in the patch for the 0.51 package, and the patch was getting cumbersomely large. This will make things much easier for me to maintain. -Erik -- Erik B. Andersen email: [EMAIL PROTECTED], [EMAIL PROTECTED] --This message was written using 73% post-consumer electrons-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dhcp-client uselessness on powerpc
On Mon, Jul 09, 2001 at 06:14:34PM +0100, Richard Hirst wrote: > On Mon, Jul 09, 2001 at 12:08:37PM +0100, Richard Hirst wrote: > > On Sun, Jul 08, 2001 at 06:01:06PM -0800, Ethan Benson wrote: > > > another problem with dhcp-client is it prevents manual network > > > configuration since the maintainer apparently won't remove or alter > > > the initscript that runs it on every boot. /etc/network/interfaces is > > > how we do things since potato its time to move on. (bug filed over a > > > year ago). > > > > That is probably unfair, ref bug #98680. I am about to test > > the 3.0 version on hppa... > > Tested dhcp-client 3.0beta2RC10-1 with both dhcp and static eth0 > configurations. Worked fine, doesn't install any /etc/init.d script. Forgot to say I had to make a couple of changes to b-f to make it work: 1. change SMALL_BASE_LIST_all to reference dhclient rather than dhclient-2.2.x 2. change netconfig.c to #define NC_DHCLIENT_FILE "/sbin/dhclient". Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
proposal: option to keep kernel keymap during install
Hi,
Some older hppa boxes have keyboards for which we have a keymap
that works in the kernel, but don't have one in the console-data
pkg. For these systems I'd like to avoid selecting a keymap
during install. I can do that at the moment, but the installer
keeps prompting for keyboard config at each step. A nice simple
solution is to just offer the keyboard config once, and then if
the user hits cancel, don't offer again. In the second stage
install you will then be offerred keyboard config again, and you
can select to keep the kernel keytable. Diff below. What do
people think? I can commit it no-one objects, or I can make it
#if #cpu(hppa). Longer term, we can get a keymap in to console-data,
get the b-f build to pull it in, etc.
Richard
Index: utilities/dbootstrap/main_menu.c
===
RCS file: /cvs/debian-boot/boot-floppies/utilities/dbootstrap/main_menu.c,v
retrieving revision 1.63
diff -u -r1.63 main_menu.c
--- utilities/dbootstrap/main_menu.c2001/07/09 01:25:39 1.63
+++ utilities/dbootstrap/main_menu.c2001/07/09 18:40:45
@@ -106,6 +106,7 @@
#ifndef _TESTING_
char *found_root = NULL;
#endif
+ int offerred_keyboard = 0;
struct stat statbuf;
int (*next_action) (void);
int (*alternate_action) (void);
@@ -278,11 +279,13 @@
if ((! NAME_ISREG (KEYBD_SETTINGS_FILE, &statbuf))
&& NAME_ISEXE ("/sbin/loadkmap", &statbuf)
&& (serialConsole < 0)
+ && (!offerred_keyboard)
#if #cpu (m68k)
&& (strcmp(Arch2, "VME") != 0)
#endif
) {
+ offerred_keyboard = 1;
#ifdef USE_LANGUAGE_CHOOSER
/* assert (lang != NULL); */
if (lang->keymap != NULL && lang->keymap[0] != '\0')
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies by rhirst
Repository: boot-floppies who:rhirst time: Mon Jul 9 13:39:02 PDT 2001 Log Message: ia64 support. Now builds working boot-floppies. ia64 has a new boot partition type, EFI (0xef), which is formatted as FAT, so I added it as another FSTYPE_MSDOS. Files: changed:Makefile config kernel.sh release.sh rescue.sh rootdisk.sh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/utilities/dbootstrap by rhirst
Repository: boot-floppies/utilities/dbootstrap who:rhirst time: Mon Jul 9 13:39:05 PDT 2001 Log Message: ia64 support. Now builds working boot-floppies. ia64 has a new boot partition type, EFI (0xef), which is formatted as FAT, so I added it as another FSTYPE_MSDOS. Files: changed:bootconfig.c dbootstrap.h partition_config.c -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/utilities/libfdisk by rhirst
Repository: boot-floppies/utilities/libfdisk who:rhirst time: Mon Jul 9 13:39:06 PDT 2001 Log Message: ia64 support. Now builds working boot-floppies. ia64 has a new boot partition type, EFI (0xef), which is formatted as FAT, so I added it as another FSTYPE_MSDOS. Files: changed:fdisk.c fdisk.h -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/debian by rhirst
Repository: boot-floppies/debian who:rhirst time: Mon Jul 9 13:39:03 PDT 2001 Log Message: ia64 support. Now builds working boot-floppies. ia64 has a new boot partition type, EFI (0xef), which is formatted as FAT, so I added it as another FSTYPE_MSDOS. Files: changed:changelog -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/make by rhirst
Repository: boot-floppies/make who:rhirst time: Mon Jul 9 13:39:04 PDT 2001 Log Message: ia64 support. Now builds working boot-floppies. ia64 has a new boot partition type, EFI (0xef), which is formatted as FAT, so I added it as another FSTYPE_MSDOS. Files: changed:ia64.rules -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/scripts/rootdisk by rhirst
Repository: boot-floppies/scripts/rootdisk who:rhirst time: Mon Jul 9 13:39:04 PDT 2001 Log Message: ia64 support. Now builds working boot-floppies. ia64 has a new boot partition type, EFI (0xef), which is formatted as FAT, so I added it as another FSTYPE_MSDOS. Files: changed:SMALL_BASE_LIST_ia64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#104117: 3.0.7-2001-07-04: Report Problem : fails when NFS not writeable, segv on second try
Package: boot-floppies Version: N/A; reported 2001-07-09 Severity: important Tags: woody I tried to test the "report problem" item, and selected NFS. It mounted the /tmp of my workstation just fine, but failed to be allowed to write a file there. It printed a messy error message across the interface... (stderr to tty still not working, I take it.) I unmounted it via the menu, then fixed my exports to say "no_root_squash", and tried again. This time it failed with slightly different error (?) at least I think it was different... it segv then restarted at that point. -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux karlheg 2.4.5 #2 Wed Jun 20 12:25:29 PDT 2001 i686 Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/make by aph
Repository: boot-floppies/make who:aph time: Tue Jul 10 00:23:42 PDT 2001 Log Message: fix a dependancy for root.bin (might be non-LANG_CHOOSER only) Files: changed:root -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/documentation by aph
Repository: boot-floppies/documentation who:aph time: Tue Jul 10 00:24:04 PDT 2001 Log Message: cope with a recent message change Files: changed:po2sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
