default route

2001-08-24 Thread Adam McKenna

Something else I noticed.  During install, if you configure the network and 
then, say, reformat your Linux partition, the installer remembers the network 
information (gets it from ifconfig, I presume), and fills in the values 
automatically for you when it asks you to configure the network again.  But 
it doesn't remember the default route.  It resets the default route back to 
its original default.

--Adam
-- 
Adam McKenna  [EMAIL PROTECTED]  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: PLIP install (was Re: Still no base tarball)

2001-08-24 Thread Santiago Garcia Mantinan

 I'm curious.  Does PLIP work in the woody boot-floppies?

Well, last time I tried it needed to make some steps by hand.

 Are there things we could do to make installation via PLIP network
 easier?

Yes, if it has not been corrected still, make a plip device configurable
under the normal installation proccess.

Setting up a plip interface differs a bit on a normal network interface
because it is a point to point interface, thus with a /32 netmask. Last time
I tried to set up one with the installation setup it couldn't handle it
well.

If I have time, remember, and nobody else does it before I do it, I'll try
to look at the status of this again with current release of the BF.

Regards...
-- 
Manty/BestiaTester - http://manty.net


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: Still no base tarball

2001-08-24 Thread David Damerell

On Thursday, 23 Aug 2001, Dale Scheetz wrote:
I downloaded the tarball from people several days ago and it took just at
4 1/2 hours. While I have a 56K modem, my country phone lines will only
support about 22k of traffic. I didn't make this up.

... plus, we don't all have 56K modems. I still was using a 28.8 until
the advent of cable modem, and my cable provider's monstrous
incompetence means that I do find myself using it now and then.

I'm not tied to the tarball. Floppies solve the problem just as well.
Basicly either could be used.[1] Which takes up the least space?

Floppy images, please! It's much more obvious what to do with them.

-- 
David Damerell [EMAIL PROTECTED] flcl?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




No Subject

2001-08-24 Thread Antonio Gonzalez


unsubscribe



cvs commit to boot-floppies by cts

2001-08-24 Thread cts

Repository: boot-floppies
who:cts
time:   Fri Aug 24 06:52:26 PDT 2001


Log Message:

m68k: amigainstall.tgz is built in bf-archive-install.sh (was undone again
in 1.111, by mistake I hope)


Files:

changed:release.sh


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




cvs commit to boot-floppies/debian by aph

2001-08-24 Thread aph

Repository: boot-floppies/debian
who:aph
time:   Fri Aug 24 07:13:41 PDT 2001


Log Message:

start 3.0.14


Files:

changed:changelog


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




cvs commit to boot-floppies/debian by aph

2001-08-24 Thread aph

Repository: boot-floppies/debian
who:aph
time:   Fri Aug 24 07:02:34 PDT 2001


Log Message:

build failed last night due to disk full; therefore, we accept the
release.sh change of last night from Christian in 3.0.13


Files:

changed:changelog


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




cvs commit to boot-floppies/debian by dwhedon

2001-08-24 Thread dwhedon

Repository: boot-floppies/debian
who:dwhedon
time:   Fri Aug 24 09:09:09 PDT 2001


Log Message:

- add clearer instructions for driver-# floppies from
  Bernie Boudet [EMAIL PROTECTED] closes: #106201


Files:

changed:changelog


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




cvs commit to boot-floppies/documentation/en by dwhedon

2001-08-24 Thread dwhedon

Repository: boot-floppies/documentation/en
who:dwhedon
time:   Fri Aug 24 09:09:09 PDT 2001


Log Message:

- add clearer instructions for driver-# floppies from
  Bernie Boudet [EMAIL PROTECTED] closes: #106201


Files:

changed:appendix.sgml


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Processed: admin

2001-08-24 Thread Debian Bug Tracking System

Processing commands for [EMAIL PROTECTED]:

 tags 106201 fixed
Bug#106201: Clearer instructions for driver-# floppies
Tags added: fixed


End of message, stopping processing here.

Please contact me if you need assistance.

Darren Benham
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Bug#109455: dhcp non-functional 3.0.11

2001-08-24 Thread Stephen Waters

On 23 Aug 2001 23:55:02 -0400, Daniel Bungert wrote:
 No, not yet.  Either dhclient or b-f reported success when I didn't have
 an IP yet - that's bad.
 
 I will take a look at it this weekend.

That is true. In fact, I suspect that a lot of folks using the
DHCP/network install option just might be cable and DSL installers...
perhaps a note like this would be useful:

---
DHCP failed to get an address from the server. If you are on a cable or
DSL connection, try power-cycling the cable or DSL modem to clear out
its cache.
---

Obviously, we cannot prepare for every contingency. I just think this
one would be a common enough, non-obvious solution to warrant a brief
message.

Cheers,
-s



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Bug#109455: dhcp non-functional 3.0.11

2001-08-24 Thread Stephen Waters

On 24 Aug 2001 11:01:01 -0400, Adam Di Carlo wrote:
  That is true. In fact, I suspect that a lot of folks using the
  DHCP/network install option just might be cable and DSL installers...
  perhaps a note like this would be useful:
 
 No, that's too hard to do, and it's more likely that our silly test
 will fail than anything else.
 
 I really think this is a dhcp-client bug ?  Or did any people really
 identify that it's something about the root disk which causes this?

I'm not familiar enough with either codebase to say whether dhclient
returns an error or not or that b-f incorrectly detects success when
dhclient actually reported failure.

I'm a Perl guy.

As far as difficulty of implementing the message, I just figured you'd
wrap the error with the help text instead of just returning Operation
failed which is definitely unhelpful. :-) I wouldn't worry about
testing for the condition.

Flow:
fork(dhclient)
dhclient returns failure (doesn't matter what the failure is)
printf(Suggestion helptext yadda. ERROR %s,ERRTEXT)
printf(Would you like to manually configure?)

$0.02,
-s



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Bug#109925: bf-3.0.12/i386 keymap fr-latin0 broken

2001-08-24 Thread Fabrice LORRAIN

Package: boot-floppies
Version: 3.0..12
Severity: normal
Arch : i386/idepci

Hi,

The support for the fr-latin0 keymap is broken in bf-3.0.12 (idepci).
From a discussion on d-devel-french, it seems to be broken as far as
potato-r0 !!!

The error I got  :
error loading the keymap i386/azerty/fr-latin0.kmap.

And the corresponding lines in /var/log/installer.log :
Aug 22 15:48:31 (none) syslog.info syslogd started: BusyBox v0.60.0
(2001.08.02-21:16+)
Aug 22 15:48:48 (none) user.info dbootstrap[38]: loadkmap: This is not a
valid binary keymap. 
Aug 22 15:48:48 (none) user.err dbootstrap[38]: Error loading the keymap
i386/azerty/fr-latin0.kmap from /etc/keymaps.tgz
Aug 22 15:51:34 (none) user.info dbootstrap[38]: loadkmap: This is not a
valid binary keymap. 
Aug 22 15:51:34 (none) user.err dbootstrap[38]: Error loading the keymap
i386/azerty/fr-latin0.kmap from /etc/keymaps.tgz
Aug 22 15:51:57 (none) user.info dbootstrap[38]: running cfdisk to
partition /dev/hda
...

There is certainly a pb of error code handling too. Instead of returning
to the keymap menu, I was ask
to chose my partition scheme after the error.

Fab


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: Bug#109826: base floppy images on the Debian CD

2001-08-24 Thread Ethan Benson

On Fri, Aug 24, 2001 at 09:34:37AM +0200, Raphael Hertzog wrote:

 Of course I can ... but do you really think someone is going to install
 the base system with 16 floppies ? I don't think so. I thought the
 whole point of the base system tarball was for people who wanted to setup
 rapidly a nfsroot. Splitting it is pointless for them.

for the bazillionth time now, basedebs.tgz is NOT NOT NOT a root
filesystem.  its a tarball of a bunch of .deb files.  

as for installing via floppies, some people still seem to want to do
it that way.

 BTW, the complete disks-i386/current directory is always automatically
 included on CD1 so I have no modifications to do to close this bug.

we will have to put basedebs.tgz somewhere else then to prevent it
from going on the CDs then.

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

 PGP signature


Re: Bug#109826: base floppy images on the Debian CD

2001-08-24 Thread Eduard Bloch

#include hallo.h
Ethan Benson wrote on Fri Aug 24, 2001 um 04:49:19AM:

 for the bazillionth time now, basedebs.tgz is NOT NOT NOT a root
 filesystem.  its a tarball of a bunch of .deb files.  

Exactly. What is the reason for having basedebs.tgz? We cannot have the
tarball INSTEAD of the deb files (or can we?) Who needs basedebs.tgz? We
could put DOS versions of tar and gzip on the CD plus a BATch file, so
people can make their own basedebs.tgz if they want. Puting the same
data in different forms is wastage of disc space.

Gruss/Regards,
Eduard.
-- 
...mit VIM kein Problem!
:wq

 PGP signature


Re: Bug#109826: base floppy images on the Debian CD

2001-08-24 Thread Raphael Hertzog

Le Thu, Aug 23, 2001 at 07:03:56PM -0400, Adam Di Carlo écrivait:
 I think split floppy images of base make the most sense.  It seems
 that we all agree on this point.
 
 Split floppy 1.44k images of base would cover the case where someone
 wants to install on a machine that has only floppy and no CD and no
 network access.
 
 Debian-CD folks, assume we can set aside a well-known location in the
 woody distribution archive for base images, built using debootstrap
 and splitting into 1.44k sized chunks, would you be willing to add
 this to CD#1 ?  I think we expect that to be around 24MB in total
 space consumed.

Of course I can ... but do you really think someone is going to install
the base system with 16 floppies ? I don't think so. I thought the
whole point of the base system tarball was for people who wanted to setup
rapidly a nfsroot. Splitting it is pointless for them.

BTW, the complete disks-i386/current directory is always automatically
included on CD1 so I have no modifications to do to close this bug.

Cheers,
-- 
Raphaël Hertzog -+- http://strasbourg.linuxfr.org/~raphael/
Le bouche à oreille du Net : http://www.beetell.com
Naviguer sans se fatiguer à chercher : http://www.deenoo.com
Formation Linux et logiciel libre : http://www.logidee.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: Bug#109826: base floppy images on the Debian CD

2001-08-24 Thread Philip Charles

Hoping that this will not add any more heat to this thread.

At present the Hurd CD installation requires the installation of a
tarball.  While Marcus Brinkmann is working on Hurd udeb's these are
probably some time away.

What I would be looking for is a way to install a tarball within the
Debian installer which would not require any significant hacking.

I also have good reason to suspect that consultants and the like produce
specialised tarballs for customised installations.  These people would
need tools to produce such tarballs.

Phil.

-
  Philip Charles; 39a Paterson St., Dunedin, New Zealand; +64 3 4882818
Mobile 025 267 9420.  I sell GNU/Linux CDs.   See http://www.copyleft.co.nz
 [EMAIL PROTECTED] - preferred.   [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




cvs commit to boot-floppies/scripts/rescue/messages/gl by jtarrio

2001-08-24 Thread jtarrio

Repository: boot-floppies/scripts/rescue/messages/gl
who:jtarrio
time:   Fri Aug 24 19:12:20 PDT 2001


Log Message:

Converted the Galician debian.txt file to the IBMPC charset


Files:

changed:debian.txt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: fail to boot on harddrive with a Performa 6400

2001-08-24 Thread Chris Tillman

 Hi everybody,
 
 Could someone help me for the following problem, please?

 I am a system administrator in a University and I tried to install Debian
 PPC (potato and woody) on some Performa 6400... the installation went
 relatively well with the potato boot floppies, but I have been unable to make
 it boot from the harddrive.
 I would like to use quik and not BootX since I don't want to let MacOS
 available on them.

 I have tried any possible configuration or trick from a lot of
 documentation sources:
 http://penguinppc.org/usr/quik
 http://penguinppc.org/usr/quik/quirks.shtml
 http://lppcfom.sourceforge.net/
 etc...

 (the Open Firmware on Performa 6400 is 2.0)

I have the same OF version on my PowerBase clone, FWIW

 Some people reported success making it boot (but maybe not with quik).

 I saw that I should change load-base to 10, keep input-device and
output-device
 to ttya, I removed the modem to see if it would change something, I upgraded
to
 woody to have a newer version of quik...

For Debian, I haven't seen any docs recommending a load-base change, in fact
I think I recall that was not recommended. As far as input-device and
output-device, the NetBSD page offers:

 http://www.netbsd.org/Ports/macppc/models.html

 Open Firmware output-device defaults to ttya, but ttya is the internal
modem (if installed). Thus, if you have an internal modem, use Boot
Variables to set console to ttyb.


I believe it would not make a difference whether the modem was actually
there or not. The above advice is in regards to being able to see the Open
Firmware command line. It also mentions:

 http://www.netbsd.org/Ports/macppc/models.html

 NetBSD may not boot if screen/kbd are used (use ttya or ttyb for your
console)


That would mean hooking up another computer to a serial port to be able to
see the OF command line.

But, quik would prevent you from having to do any of that if it was working
on your machine. Which version of quik and boot-floppies are you using? I
think Ethan did some work last month on it, though I can't locate it in CVS
to check.

 - mac-fdisk 
 /dev/hda
 #type namelength   base(
 size )  system
 /dev/hda1 Apple_partition_map Apple   63 @ 1   (
 31.5k)  Partition map
 /dev/hda2  Apple_Driver43 Macintosh   64 @ 64  (
 32.0k)  Driver 4.3
 /dev/hda3Apple_Driver_ATA Macintosh   64 @ 128 (
 32.0k)  Unknown
 /dev/hda4   Apple_Patches Patch Partition512 @ 192
 (256.0k)  Unknown
 /dev/hda5 Apple_UNIX_SVR2 swap26 @ 704
 (127.0M)  Linux swap
 /dev/hda6 Apple_UNIX_SVR2 /  3073760 @ 260704  (
 1.5G)  Linux native

Since you've evicted MacOS, you can also get rid of the driver and patch
partitions. But that wouldn't cause this problem I don't think.


 - of variables -
 nvsetenv load-base 0x10
 nvsetenv boot-device ata/ATA-Disk@0:0
 nvsetenv boot-file ata/ATA-Disk@0:6/boot/vmlinux-2.2.19 root=/dev/hda6
 


Maybe try nvsetenv (no parameters)? This will show all the nvram settings.
Then see what they are after quik runs? If you have another untouched
machine, maybe boot the installer there just to see what the virgin settings
are like?


**
|  .''`.  | Debian GNU/Linux: http://www.debian.org|
| : :'  : | debian-imac:http://debian-imac.sourceforge.net |
| `. `'`  |  . oo   Chris Tillman|
|   `-| (   -)  [EMAIL PROTECTED]|
*--*


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: fail to boot on harddrive with a Performa 6400

2001-08-24 Thread Ethan Benson

On Fri, Aug 24, 2001 at 04:27:24PM -0700, Chris Tillman wrote:
 
 But, quik would prevent you from having to do any of that if it was working
 on your machine. Which version of quik and boot-floppies are you using? I
 think Ethan did some work last month on it, though I can't locate it in CVS
 to check.

all boot-floppies are doing right now is setting boot-device and
installing the quik bootblock, nothing more.  that will not be enough
on most machines (and thus they will be rendered unbootable), but
should work some of the time on 7200, 7300 and 7600s.

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

 PGP signature


cvs commit to boot-floppies/scripts/rescue/messages/de by blade

2001-08-24 Thread blade

Repository: boot-floppies/scripts/rescue/messages/de
who:blade
time:   Fri Aug 24 13:12:42 PDT 2001


Log Message:

reformated first paragraph to fit on 80x25, replaced ctrl-alt-del with german names

Files:

changed:debian.txt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




cvs commit to boot-floppies/documentation/fi by tvainika

2001-08-24 Thread tvainika

Repository: boot-floppies/documentation/fi
who:tvainika
time:   Fri Aug 24 14:13:46 PDT 2001


Log Message:

translation updates by Panu Hällfors

Files:

changed:Tag: potato post-install.sgml


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




cvs commit to boot-floppies/utilities/dbootstrap/po by blade

2001-08-24 Thread blade

Repository: boot-floppies/utilities/dbootstrap/po
who:blade
time:   Fri Aug 24 13:56:23 PDT 2001


Log Message:

improved german translation

Files:

changed:de.po


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]