Re: boot-floppies 2.3.5 ready for testing (i386 and powerpc so far)

[Bas Zoetekouw]

Hi Adam!

You wrote:

> I would like to open the door wide for testing.  I apologize for the
> state of the boot-floppies bug tracking area -- it's a mess.  We will
> try to clean that up.  However, even so, please don't hesitate to file
> bugs.
> Alternatively, just take rough notes during installation and send
> those to <[EMAIL PROTECTED]>.

I just tested new boot flops. Unfortunately, the installation was not
successfull (see below).

Some remarks:

 - There are too much drivers on the driver flops. Why do we need joystick, 
   sound and video drivers on the boot disks? Just including 
   block, net, fs, cdrom, scsi and usb would save about 7MB
   (uncompressed). 
 - There is a warning about creating an empty ld.so.conf after
   downloading the base system.
 - While downloading the essential packages, the package named are
   displayed. This is nice, so the user can see what is being done.
   However, when installing those packages, just the message "Installing
   essential packages" is displayed. It would be nice if here also the
   package currently being processed would be displayed. The same point
   applies to the installation of the base packages.
 - There is a warning about creating an empty lilo.conf. Same for
   exim.conf.
 - I get a warning "Failure trying to run dpkf --force-auto-select
   --force-overwrite --force". The installation doesn't proceed after
   this (this warning continues to appear).

-- 
Kind regards,
+---+
| Bas Zoetekouw  | Si l'on sait exactement ce   |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?|
|[EMAIL PROTECTED] |   Pablo Picasso  |
+---+ 


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

Re: E2fsprogs 1.20 released

[Adam Di Carlo]

Yann Dirson <[EMAIL PROTECTED]> writes:

> On Thu, Jun 14, 2001 at 03:49:30AM -0400, Theodore Tso wrote:
> > The e2fsprogs 1.21-WIP-0614 release which I just uploaded has some new
> > configure options; if you compile it:
> 
> > configure  --enable-elf-shlibs --disable-swapfs --disable-imager --disable-resizer 
>--disable-debugfs '--with-ccopts=-O2 -fomit-frame-pointer'
> 
> Gasp, I had not realized that, the 1st 1.21-WIP-0614 package doesn't
> make use of this.
> 
> > Would this be workable for you?
> 
> I can have the pics libs and an e2fsck.bf binary built reduced, and
> shipped in the e2fslibs-pic package with not much work.

Yann, thanks for doing this.  You too, Theodore.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onshored.com/>



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

Re: boot-floppies 2.3.5 ready for testing (i386 and powerpc so far)

[Stephen R Marenka]

On Fri, Jun 15, 2001 at 03:57:39PM +0200, Bas Zoetekouw wrote:
>  - I get a warning "Failure trying to run dpkf --force-auto-select
>--force-overwrite --force". The installation doesn't proceed after
>this (this warning continues to appear).

At least one of the packages is failing to configure, can you look at
the logs to figure out which one?

Thanks,

Stephen

-- 
Stephen R. Marenka If life's not fun, you're not doing it right!
<[EMAIL PROTECTED]>

 PGP signature

Re: boot-floppies 2.3.5 ready for testing (i386 and powerpc so far)

[Ethan Benson]

On Fri, Jun 15, 2001 at 03:57:39PM +0200, Bas Zoetekouw wrote:

> Some remarks:
> 
>  - There are too much drivers on the driver flops. Why do we need joystick, 
>sound and video drivers on the boot disks? Just including 
>block, net, fs, cdrom, scsi and usb would save about 7MB
>(uncompressed). 

we get whatever the kernel-image gives us.  

>  - There is a warning about creating an empty ld.so.conf after
>downloading the base system.

harmless, ignore.  or tell aj to kill this silly warning.  its not
really a warning either, just informative (though why anyone would
care i don't know).  

>  - While downloading the essential packages, the package named are
>displayed. This is nice, so the user can see what is being done.
>However, when installing those packages, just the message "Installing
>essential packages" is displayed. It would be nice if here also the
>package currently being processed would be displayed. The same point
>applies to the installation of the base packages.

hmm, that would be nice, but tricky given the way debootstrap works.  

in fact everything you see in regards to base install comes from
debootstrap and not boot-floppies, we just read its stdout and stuff
it in dialogs.  

>  - There is a warning about creating an empty lilo.conf. Same for
>exim.conf.

see above.

>  - I get a warning "Failure trying to run dpkf --force-auto-select
>--force-overwrite --force". The installation doesn't proceed after
>this (this warning continues to appear).

hmm what archetecture?  we were seeing this on powerpc due to
powerpc-utils screwing with config files.  but it must be something
else..  unfortunatly its not very easy to see what package is causing
this error.  

note that if you keep hitting `ok' over and over it will eventually
stop.  debootstrap loops over 20 times on errors as it brute forces
the base system into order.  

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

 PGP signature

Re: boot-floppies 2.3.5 ready for testing (i386 and powerpc so far)

[Ethan Benson]

On Fri, Jun 15, 2001 at 09:08:20AM -0500, Stephen R Marenka wrote:
> On Fri, Jun 15, 2001 at 03:57:39PM +0200, Bas Zoetekouw wrote:
> >  - I get a warning "Failure trying to run dpkf --force-auto-select
> >--force-overwrite --force". The installation doesn't proceed after
> >this (this warning continues to appear).
> 
> At least one of the packages is failing to configure, can you look at
> the logs to figure out which one?

unfortunatly the logs are useless, they don't say anything more then
what the dialog says.  

the closest i have come is booting, or chrooting to the /target system
and running dpkg --audit or apt-get check, one of those will display
all brokenly installed/unconfigured packages.

also was this installing testing or sid?  it could be that
groff-base/man-db dependency thing again (which seems to be fixed up
now). 

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

 PGP signature

cvs commit to boot-floppies/utilities/dbootstrap by stephen.r.marenka

[stephen . r . marenka]

Repository: boot-floppies/utilities/dbootstrap
who:stephen.r.marenka
time:   Fri Jun 15 07:26:08 PDT 2001


Log Message:

Minor cosmetic quik cruft removal.

Files:

changed:bootconfig.c


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

Bug#101010: magicfilter does not depend on djtools. magicfilter tries to execute /usr/bin/djscript

[pj]

Package: base
Version: N/A; reported 2001-06-15
Severity: important



-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux Aquarius 2.4.5-ac13 #1 Thu Jun 14 21:44:08 CEST 2001 i586
Locale: LANG=C, LC_CTYPE=C



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

Processed: reassign

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 101010 magicfilter
Bug#101010: magicfilter does not depend on djtools. magicfilter tries to execute 
/usr/bin/djscript
Bug reassigned from package `base' to `magicfilter'.

>
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]

cvs commit to boot-floppies by aph

[aph]

Repository: boot-floppies
who:aph
time:   Fri Jun 15 09:49:08 PDT 2001


Log Message:

ignorables


Files:

changed:.cvsignore


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

cvs commit to boot-floppies/debian by aph

[aph]

Repository: boot-floppies/debian
who:aph
time:   Fri Jun 15 09:49:19 PDT 2001


Log Message:

ignorables


Files:

changed:.cvsignore


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

base*.tgz is gone, and why it's gone

[Adam Di Carlo]

Dale Scheetz <[EMAIL PROTECTED]> writes:

> I've been downloading these files for a test session, and I can't find the
> base tarball. Where can I find this file? It is normally in the images
> directories, but I can't find it.

There is no base tarball anymore.  The functionality has been
superceeded by debootstrap (the package).

FYI, what debootstrap does is simply download (or get from CD) the
packages in base at runtime.  Essentially, it replaces the
bootdisks.sh script in boot-floppies -- we used to build the base
system at boot-floppies build time.

Why is this better?  For one, it's going to be able to work with
debian-installer, for sid release, since boot-floppies is going away
in sid.  For two, its better because we don't have to create another
boot-floppies release to capture updates in base.  We're able to turn
around base fixes as easily as updating the packages in the archive.

For three, it's better because it means less for the overworked
debian-boot team to be directly responsible for. :)

Some have asked for some way to install base via floppies -- you'll
have to take it up with AJ.  CVS for the debootstrap package is
available in the same cvsroot as boot-floppies.  I'm happy to try to
accomodate this on the boot-floppies side if the support is added to
debootstrap and some split images provided.  However, AJ might not be
willing to do this at all, since it will invalidate (for floppy
install anyhow) many of the benefits above.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onshored.com/>


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

install disk woes

[Duane Powers]

Hi List,

sorry for the long post, I've posted to debian-user, no help, went to 
the irc channel, no help, and tried debian-isp. still no help. Didn't 
know debian had a list for the boot disks. :o\ anyway.

I've built a custom kernel for my hardware, (compaq proliant 2500R with 
compaq smart2 array controller, and have put it on the rescue disk 
properly, I followed the guides on www.debian.org, and built ramdisk 
support in, see below for the .config for the kernel. I ran rdev.sh 
after copying the kernel to the floppy.  I boot and before it prompts 
for the root disk, it says "This kernel does not have RAMdisk support" 
any clues? If I then insert a root disk, it kernel panics, with can't 
load filesystem on 02:00. I'm using kernel 2.4.5 and a standard rescue 
image from www.debian.org. (1.44)

Thanks in Advance,

Duane Powers

-
config
-

#
# Automatically generated by make menuconfig: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
CONFIG_M686=y
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_TOSHIBA is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
# CONFIG_MTRR is not set
# CONFIG_SMP is not set
# CONFIG_X86_UP_IOAPIC is not set

#
# General setup
#
CONFIG_NET=y
# CONFIG_VISWS is not set
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_PM=y
# CONFIG_ACPI is not set
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_PC_SUPERIO=y
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
# CONFIG_PARPORT_1284 is not set

#
# Plug and Play configuration
#
CONFIG_PNP=y
CONFIG_ISAPNP=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
CONFIG_BLK_CPQ_DA=y
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_BLK_DEV_LVM is not set

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK is not set
# CONFIG_NETFILTER is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set
# CONFIG_P

cvs commit to boot-floppies/debian by aph

[aph]

Repository: boot-floppies/debian
who:aph
time:   Fri Jun 15 12:10:13 PDT 2001


Log Message:

install-docs actually puts the docs in the right place now


Files:

changed:rules


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

Re: install disk woes

[Richard Hirst]

On Fri, Jun 15, 2001 at 11:57:13AM -0700, Duane Powers wrote:
> Hi List,
> 
> sorry for the long post, I've posted to debian-user, no help, went to 
> the irc channel, no help, and tried debian-isp. still no help. Didn't 
> know debian had a list for the boot disks. :o\ anyway.
> 
> I've built a custom kernel for my hardware, (compaq proliant 2500R with 
> compaq smart2 array controller, and have put it on the rescue disk 
> properly, I followed the guides on www.debian.org, and built ramdisk 
> support in, see below for the .config for the kernel. I ran rdev.sh 
> after copying the kernel to the floppy.  I boot and before it prompts 
> for the root disk, it says "This kernel does not have RAMdisk support" 
> any clues? If I then insert a root disk, it kernel panics, with can't 
> load filesystem on 02:00. I'm using kernel 2.4.5 and a standard rescue 
> image from www.debian.org. (1.44)

You didn't build ramdisk support in.  I think you need at least
these set:

> # CONFIG_BLK_DEV_LOOP is not set
> # CONFIG_BLK_DEV_RAM is not set
> # CONFIG_BLK_DEV_INITRD is not set

Richard


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

cdrom entry in /etc/fstab

[Santiago Vila]

Slightly off-topic question:

It is ok at all for apt to use /cdrom as a mount point?

(I think it violates the spirit of FHS when it says mount points in /
are just a convenience for the user and they are not to be used
directly by any software).


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

Re: E2fsprogs 1.20 released

[tytso]

On Fri, Jun 15, 2001 at 10:08:00AM -0400, Adam Di Carlo wrote:
> > > The e2fsprogs 1.21-WIP-0614 release which I just uploaded has some new
> > > configure options; if you compile it:
> > 
> > > configure  --enable-elf-shlibs --disable-swapfs --disable-imager 
>--disable-resizer --disable-debugfs '--with-ccopts=-O2 -fomit-frame-pointer'
> > 
> > Gasp, I had not realized that, the 1st 1.21-WIP-0614 package doesn't
> > make use of this.

Yeah, it's a new feature I had just added in response to my finding
out about the debian bootkit needs.

> > > Would this be workable for you?
> > 
> > I can have the pics libs and an e2fsck.bf binary built reduced, and
> > shipped in the e2fslibs-pic package with not much work.

One of the reasons why I added this support was to avoid needing to
build a pics library.  As I understand it, the library was just built
so you could put together a minimal .so library that had only the
modules necessary for mke2fs and e2fsck.  The configuration options
above should allow you to generate such a library directly, without
having to go through the intermediate pics library step.  It also
allowed me to be a bit more selective about which bits to include and
not include. 

Finally, I believe the .so library is minimal; that is, every single
.o file included in libext2fs.so.2.4 is needed for one of mke2fs or
e2fsck, if it is compiled with the above configuration options.  If
you find some excess files still, please let me know; I'll consider
that a bug and fix it.

- Ted


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

boot disks 2.3.5

[Matthew Sackman]

Hi there,

May I firstly say how happy I am with the new boot disks - although I don't
have to floppy disks to be able to do a full install, what I have tested seems
to work very well indeed, and adds a number of very useful features over the
potato install disks.

However, one thing comes to mind: if one is installing to, say, a hardware RAID
array, which appears to linux as a single SCSI drive, but requires a module
loading, then how do you do it? The 'Preload module' option seemed promising,
but didn't seem to do what I was after.

What would be the steps required: use the install floppies to create a new root
floppy which contains the module required marked to be loaded, and then go into
the install sequence? If so, then how does one achieve this?

Many thanks for your time - as I said, things are looking very good indeed.

Matthew

-- 

Matthew Sackman
Nottingham,
ENGLAND

Using Debian/GNU Linux
Enjoying computing

It said 'Required Windows XP or better.'
So I installed Linux.

 PGP signature

cvs commit to boot-floppies/utilities/dbootstrap by peterk

[peterk]

Repository: boot-floppies/utilities/dbootstrap
who:peterk
time:   fre jun 15 23:47:12 MEST 2001


Log Message:

Fixed several spellling mist stakes

Files:

changed:problem_report.c


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

Re: boot disks 2.3.5

[Stephen R Marenka]

On Fri, Jun 15, 2001 at 10:00:28PM +0100, Matthew Sackman wrote:

> However, one thing comes to mind: if one is installing to, say, a hardware RAID
> array, which appears to linux as a single SCSI drive, but requires a module
> loading, then how do you do it? The 'Preload module' option seemed promising,
> but didn't seem to do what I was after.
> 
> What would be the steps required: use the install floppies to create a new root
> floppy which contains the module required marked to be loaded, and then go into
> the install sequence? If so, then how does one achieve this?

The full-up method can be found here:

http://www.debian.org/releases/stable/i386/ch-boot-floppy-techinfo.en.html#s-rescue-replace-kernel

-- 
Stephen R. Marenka If life's not fun, you're not doing it right!
<[EMAIL PROTECTED]>

 PGP signature

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

[peterk]

Repository: boot-floppies/utilities/dbootstrap/po
who:peterk
time:   lör jun 16 00:09:38 MEST 2001


Log Message:

Massive update

Files:

changed:sv.po


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

cvs commit to boot-floppies/scripts/rescue/messages/sv by peterk

[peterk]

Repository: boot-floppies/scripts/rescue/messages/sv
who:peterk
time:   lör jun 16 00:14:07 MEST 2001


Log Message:

Translation updates.


Files:

changed:.translation_of debian.txt debian.txt.sparc debian.txt.vme f5.txt


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

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

[peterk]

Repository: boot-floppies/utilities/dbootstrap/po
who:peterk
time:   lör jun 16 00:19:31 MEST 2001


Log Message:

Minor change

Files:

changed:sv.po


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

Re: boot disks 2.3.5

[Matthew Sackman]

Many thanks for this - it rather solves the problem. In which case, what is the
'Preload modules' option for? - the menu description page in the install
program didn't seem to make it very clear.

With thanks,

Matthew

On Fri, Jun 15, 2001 at 04:52:22PM -0500, Stephen R Marenka wrote:
> On Fri, Jun 15, 2001 at 10:00:28PM +0100, Matthew Sackman wrote:
> 
> > However, one thing comes to mind: if one is installing to, say, a hardware RAID
> > array, which appears to linux as a single SCSI drive, but requires a module
> > loading, then how do you do it? The 'Preload module' option seemed promising,
> > but didn't seem to do what I was after.
> > 
> > What would be the steps required: use the install floppies to create a new root
> > floppy which contains the module required marked to be loaded, and then go into
> > the install sequence? If so, then how does one achieve this?
> 
> The full-up method can be found here:
> 
> 
>http://www.debian.org/releases/stable/i386/ch-boot-floppy-techinfo.en.html#s-rescue-replace-kernel
> 
> -- 
> Stephen R. Marenka If life's not fun, you're not doing it right!
> <[EMAIL PROTECTED]>



-- 

Matthew Sackman
Nottingham,
ENGLAND

Using Debian/GNU Linux
Enjoying computing

It said 'Required Windows XP or better.'
So I installed Linux.

 PGP signature

Re: boot disks 2.3.5

[Duane Powers]

Stephen R Marenka wrote:

> On Fri, Jun 15, 2001 at 10:00:28PM +0100, Matthew Sackman wrote:
> 
> 
>>However, one thing comes to mind: if one is installing to, say, a hardware RAID
>>array, which appears to linux as a single SCSI drive, but requires a module
>>loading, then how do you do it? The 'Preload module' option seemed promising,
>>but didn't seem to do what I was after.
>>
>>What would be the steps required: use the install floppies to create a new root
>>floppy which contains the module required marked to be loaded, and then go into
>>the install sequence? If so, then how does one achieve this?
>>
> 
> The full-up method can be found here:
> 
> 
>http://www.debian.org/releases/stable/i386/ch-boot-floppy-techinfo.en.html#s-rescue-replace-kernel
> 
> 

List,

Please pardon my post. I'm a newbie. and a bad one at that. :o\

This applies to me precisely. Most of you probably saw my post earlier 
this morning, and after beating  of the stupid out of myself,
I compiled a kernel properly, and managed to get into the install 
process. However, when I try to load the operating system, I'm running 
into trouble that isn't covered at all in the above url. Questions I 
have would include, do I need to modify the root.bin disk? if so, how? 
why? how about the driver disks? Do I need to do anything other than 
modules.tgz? Do I have to install via driver disks? I can't get that 
far, I am getting an error when I try to remount the rescue disk,at the 
"install operating system kernel and modules" step, telling me Unable to 
mount the Rescue Floppy. You may have inserted the wrong floppy.  Please 
try again" which I can't find any information on, at least, not yet. I 
tried donwloading, from the net, but I get a wrong rescue disk error 
there as well, so now I'm lost.

Again, I'm probably way out of my league here, but redhat just doesn't 
do it for me. 

Thanks in advance,

duane



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

Re: Install manual organization

[siward]

Chris Tillman wrote:

> Here's my thinking about re-organization the manual along the lines
> you proposed. We'll need much less space to talk about installation
> source options without a base tarball or floppies.
>
> Installing Debian GNU/Linux 2.2 For PowerPC
>
> Contents
>
> 1 Welcome to Debian
>
> 1.1 What is Debian?
> 1.2 What is GNU/Linux?
> 1.3 What is Debian GNU/Linux?
> 1.4 What is Debian GNU/Hurd?
> 1.5 Getting Debian
> 1.6 Getting the Newest Version of This Document
> 1.7 Organization of This Document
> 1.8 WARNING: This Document Has Known Problems
> 1.9 About Copyrights and Software Licenses
>

Hello Chris,
  nice that youre working on docs,
  i send you a few thoughts, hope you like them.

I think the document should start with chapter 0 : "Welcome to this
document".
  contents, warning about document problems, foreword, getting newest
version,
  indication of copyright of document and purpose of document could be
(part of) this.
  maybe some words about or from the authors ?

Apart from this,
  for a document containing section "getting debian",
  chapter title "Welcome to Debian" seems slightly premature.

GNU/Linux : i think it should be Linux/GNU/X
  

> 2 System Requirements

/snip

> delete ->  4.6 Partitioning Prior to Installation (we recommend using Debian 
>partitioning tools)

  i really dont know, but, would defragmenting be advantageous ?

> 7.6 ``Partition a Hard Disk''

/snip

8.1 If You Are New to Unix

  shouldnt that be "Linux" ?

/snip

  have fun, 
  Siward



(c) Linus is a registered name of "Linux" Torvalds


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

Re: Revisions for Chapter 2, System Requirements

[David Whedon]

Thu, Jun 14, 2001 at 11:36:16PM -0700 wrote:
> 
> Proposed revisions for Chapter 2, System Requirements attached.

Hi Chris,

I took a look at the changes and they look good, my only question is :

Why take the following out?  I think it should stay.

 
-There are, however, some limitations in our boot floppy set with
-respect to supported hardware.  Some Linux-supported platforms might
-not be directly supported by our boot floppies.  If this is the case,
-you may have to create a custom rescue disk (see ), or investigate network installations.
-
 Rather than attempting to describe all the different hardware
 configurations which are supported for &arch-title;, this section
 contains general information and pointers to where additional

> 
> **
> |  .''`.  | Debian GNU/Linux: |
> | : :'  : | debian-imac: |
> | `. `'`  |  . oo   Chris Tillman|
> |   `-| (   -)  [EMAIL PROTECTED]|
> *"--"*



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

Re: boot disks 2.3.5

[Stephen R Marenka]

On Fri, Jun 15, 2001 at 11:21:05PM +0100, Matthew Sackman wrote:
> Many thanks for this - it rather solves the problem. In which case, what is the
> 'Preload modules' option for? - the menu description page in the install
> program didn't seem to make it very clear.

Got me, I thought that's what it was for. I believe someone is clearing
up the documentation regarding that bit for woody. That's probably
something I should figure out when I get some time.

Happy Trails!

Stephen

-- 
Stephen R. Marenka If life's not fun, you're not doing it right!
<[EMAIL PROTECTED]>

 PGP signature

Re: boot disks 2.3.5

[Stephen R Marenka]

On Fri, Jun 15, 2001 at 03:27:31PM -0700, Duane Powers wrote:
> Stephen R Marenka wrote:
 
> This applies to me precisely. Most of you probably saw my post earlier 
> this morning, and after beating  of the stupid out of myself,
> I compiled a kernel properly, and managed to get into the install 
> process. However, when I try to load the operating system, I'm running 
> into trouble that isn't covered at all in the above url. Questions I 
> have would include, do I need to modify the root.bin disk? if so, how? 
> why? how about the driver disks? Do I need to do anything other than 
> modules.tgz? Do I have to install via driver disks? I can't get that 
> far, I am getting an error when I try to remount the rescue disk,at the 
> "install operating system kernel and modules" step, telling me Unable to 
> mount the Rescue Floppy. You may have inserted the wrong floppy.  Please 
> try again" which I can't find any information on, at least, not yet. I 
> tried donwloading, from the net, but I get a wrong rescue disk error 
> there as well, so now I'm lost.

I agree that the documentation isn't really suitable for newbies. On the
occassion I had to do this, I didn't need to modify the root.bin. I also
just grabbed the rescue and modules disks off the net to get through the
installation. I believe I ended up manually mounting my custom rescue 
disk and copying the appropriate stuff into /boot. I also set the
/vmlinuz link manually and renamed the /lib/modules/xxx directory. The
renaming is because I was using the compact disk set which had 
"flavored" kernels and my kernel was plain.

That's not very easy. What I probably need to do is go through the whole
process again, document it, and fix the documentation. Or better yet,
maybe someone else will come along and clean it up for us. :-)
 
> Again, I'm probably way out of my league here, but redhat just doesn't 
> do it for me. 

Got that right!

-- 
Stephen R. Marenka If life's not fun, you're not doing it right!
<[EMAIL PROTECTED]>

 PGP signature

new debootstrap in incoming

[Anthony Towns]

Hi guys,

There's a new debootstrap in incoming which includes groff-base and some
other changes. Probably worth a rebuild of b-f's, as with current/old
debootstrap's, groff (in base) dies because it depends on groff-base.

Cheers,
aj

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

``_Any_ increase in interface difficulty, in exchange for a benefit you
  do not understand, cannot perceive, or don't care about, is too much.''
  -- John S. Novak, III (The Humblest Man on the Net)


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

Re: Revisions for Chapter 2, System Requirements

[Chris Tillman]

> Thu, Jun 14, 2001 at 11:36:16PM -0700 wrote:
>> 
>> Proposed revisions for Chapter 2, System Requirements attached.
>
> Hi Chris,
>
> I took a look at the changes and they look good, my only question is :
>
> Why take the following out?  I think it should stay.
>
>  
> -There are, however, some limitations in our boot floppy set with
> -respect to supported hardware.  Some Linux-supported platforms might
> -not be directly supported by our boot floppies.  If this is the case,
> -you may have to create a custom rescue disk (see  -id="rescue-replace-kernel">), or investigate network installations.
> -
>  Rather than attempting to describe all the different hardware
>  configurations which are supported for &arch-title;, this section
>  contains general information and pointers to where additional
>

thanks for the feedback.

Sorry, I should have explained; I moved it to the Troubleshooting the Boot
Process section (at the end of rescue-boot right now). It sounded like
something people would be looking for when the regular installation didn't
work.

**
|  .''`.  | Debian GNU/Linux: |
| : :'  : | debian-imac: |
| `. `'`  |  . oo   Chris Tillman|
|   `-| (   -)  [EMAIL PROTECTED]|
*"--"*


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

Make Debian Floppy

[Chris Tillman]

For posterity, I've attached the Make Debian Floppy script. It really is 
convenient to use, just drag the *.bin images to the script icon and supply
floppies. You need Disk Copy (the utility) and Applescript (the system
extension).

If you gunzip it within Linux, the resource fork for the script will be
lost. But you can still use it, just load the remaining text into Script
Editor and save it as a Classic Applet again (that will make it droppable).

The source for the script is accessible when you open it with Script Editor.

-- This Applescript uses the Disk Copy utility to
-- create a floppy for use in installing and/or booting Linux
-- on a powerpc, for example the Debian distribution floppy
-- images like root.bin.

-- This script copyright Chris Tillman, [EMAIL PROTECTED],
-- and is available to all under the terms of the
-- GNU GENERAL PUBLIC LICENSE (GPL).


**
|  .''`.  | Debian GNU/Linux: |
| : :'  : | debian-imac: |
| `. `'`  |  . oo   Chris Tillman|
|   `-| (   -)  [EMAIL PROTECTED]|
*"--"*

 MakeDebianFloppy.gz

Re: Make Debian Floppy

[Ethan Benson]

On Fri, Jun 15, 2001 at 11:33:15PM -0700, Chris Tillman wrote:
> 
> For posterity, I've attached the Make Debian Floppy script. It really is 
> convenient to use, just drag the *.bin images to the script icon and supply
> floppies. You need Disk Copy (the utility) and Applescript (the system
> extension).
> 
> If you gunzip it within Linux, the resource fork for the script will be
> lost. But you can still use it, just load the remaining text into Script
> Editor and save it as a Classic Applet again (that will make it droppable).
> 
> The source for the script is accessible when you open it with Script Editor.

i think you need to only distribute this as text.  we certainly cannot
distribute the applet on the CDs because it contains non-free code.
in fact i suspect that the GPL is an innappropriate licence due to
that conflict.  


> -- This Applescript uses the Disk Copy utility to
> -- create a floppy for use in installing and/or booting Linux
> -- on a powerpc, for example the Debian distribution floppy
> -- images like root.bin.
> 
> -- This script copyright Chris Tillman, [EMAIL PROTECTED],
> -- and is available to all under the terms of the
> -- GNU GENERAL PUBLIC LICENSE (GPL).
> 
> 
> **
> |  .''`.  | Debian GNU/Linux: |
> | : :'  : | debian-imac: |
> | `. `'`  |  . oo   Chris Tillman|
> |   `-| (   -)  [EMAIL PROTECTED]|
> *"--"*



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

 PGP signature

Re: base*.tgz is gone, and why it's gone

[Anthony Towns]

On Fri, Jun 15, 2001 at 02:41:01PM -0800, Ethan Benson wrote:
> i think as far as an implementation detail goes creating a tarball
> containing /var/cache/apt/archives of the base/required packages then
> teaching debootstrap to extract it there and use the packages would be
> fairly easy.

Actually it's not *that* easy. Not that hard either, but there are
complications. One is that the base tarball needs to be updated whenever
either of:
(a) debootstrap changes
(b) any deb that debootstrap considers to be in base changes
which means there's no single .deb that it can be uploaded with. (Anything
else will likely result in bugs or GPL violations)

Further, base tarballs aren't debs, so need byhand processing by ftpmaster
(at the moment anyway), which causes irritating delays and extra effort and
such.

Further (and this is the showstopper atm), there's no way of automatically
determining which .debs debootstrap considers to be in base. I'm in the
process of fixing this though.

> dbootstrap could take care of putting a broken up
> tarball back together again in /tmp.  

I dunno about /tmp: that's likely to have barely any
space. /target/debian-mirror, or /target/var-debian-mirror, or just
plain /target/var/*/apt/ would be more sensible.

Cheers,
aj

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

``_Any_ increase in interface difficulty, in exchange for a benefit you
  do not understand, cannot perceive, or don't care about, is too much.''
  -- John S. Novak, III (The Humblest Man on the Net)

 PGP signature

Re: base*.tgz is gone, and why it's gone

[Ben Collins]

On Fri, Jun 15, 2001 at 02:41:01PM -0800, Ethan Benson wrote:
> but if aj wants base.tgz in all incarnations dead we shall have to
> forgo hard disk and floppy installation methods.  

Why? The floppy and harddrive installation requires you to download
images from a new connection. That being that case, it's safe to say you
will have some sort of net connection to complete the installation via
dboostrap.

If you don't have a net connection, use a CD install, since presumably
just having base wont be enough in this case anyway.

-- 
 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'


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

Re: base*.tgz is gone, and why it's gone

[Philip Charles]

On Fri, 15 Jun 2001, Ethan Benson wrote:

> i tend to agree, though there are some contrived cases where
> installing via a base tarball without net access is useful.  
> 
> for example i have a very slow internet connection and several
> machines, i would like to download the base tarball once and then
> reuse on each machine.  also after i install one and use apt-move to
> make a mini mirror of the archive which other machines can use in
> addition to the net access.  since all machines have mostly the same
> packages installed at a minimum (priority standard) those will only
> have to be downloaded once.  
> 
> debootstrap doesn't like apt-move mirrors since they don't have
> proper Release files. 
> 
> i know there are other ways to work around this just none as
> straightforward as downloading base.tgz and using it multiple times.  
> 
> > If you don't have a net connection, use a CD install, since presumably
> > just having base wont be enough in this case anyway.
> 
> thats the ideal method of course.  asside from getting a real internet
> connection. 

The great advantage of the potato b-f is its flexibility.  There are a
number of people out there who use b-f in peculiar ways as consultants or
for in-house pojects.  Most of these people have little or no connection
with the Debian project as such.

In my case I am OK.  I have learnt enough about b-f over the last months
to know what to hack to produce the Hurd CDs using a tarball, other people
may not be so fortunate.

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]

Re: base*.tgz is gone, and why it's gone

[Ethan Benson]

On Fri, Jun 15, 2001 at 07:07:00PM -0400, Ben Collins wrote:
> On Fri, Jun 15, 2001 at 02:41:01PM -0800, Ethan Benson wrote:
> > but if aj wants base.tgz in all incarnations dead we shall have to
> > forgo hard disk and floppy installation methods.  
> 
> Why? The floppy and harddrive installation requires you to download
> images from a new connection. That being that case, it's safe to say you
> will have some sort of net connection to complete the installation via
> dboostrap.

i tend to agree, though there are some contrived cases where
installing via a base tarball without net access is useful.  

for example i have a very slow internet connection and several
machines, i would like to download the base tarball once and then
reuse on each machine.  also after i install one and use apt-move to
make a mini mirror of the archive which other machines can use in
addition to the net access.  since all machines have mostly the same
packages installed at a minimum (priority standard) those will only
have to be downloaded once.  

debootstrap doesn't like apt-move mirrors since they don't have
proper Release files. 

i know there are other ways to work around this just none as
straightforward as downloading base.tgz and using it multiple times.  

> If you don't have a net connection, use a CD install, since presumably
> just having base wont be enough in this case anyway.

thats the ideal method of course.  asside from getting a real internet
connection. 

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

 PGP signature

Re: base*.tgz is gone, and why it's gone

[Ethan Benson]

On Fri, Jun 15, 2001 at 02:31:14PM -0400, Adam Di Carlo wrote:
> 
> Why is this better?  For one, it's going to be able to work with
> debian-installer, for sid release, since boot-floppies is going away
> in sid.  For two, its better because we don't have to create another
> boot-floppies release to capture updates in base.  We're able to turn
> around base fixes as easily as updating the packages in the archive.

sid will never be released, its forevermore unstable.  once woody
becomes stable we pick a new name for the next testing branch.

> Some have asked for some way to install base via floppies -- you'll
> have to take it up with AJ.  CVS for the debootstrap package is
> available in the same cvsroot as boot-floppies.  I'm happy to try to
> accomodate this on the boot-floppies side if the support is added to
> debootstrap and some split images provided.  However, AJ might not be
> willing to do this at all, since it will invalidate (for floppy
> install anyhow) many of the benefits above.

i think as far as an implementation detail goes creating a tarball
containing /var/cache/apt/archives of the base/required packages then
teaching debootstrap to extract it there and use the packages would be
fairly easy.  dbootstrap could take care of putting a broken up
tarball back together again in /tmp.  

but if aj wants base.tgz in all incarnations dead we shall have to
forgo hard disk and floppy installation methods.  

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

 PGP signature

Re: base*.tgz is gone, and why it's gone

[Ben Collins]

On Fri, Jun 15, 2001 at 05:09:33PM -0600, Jason Gunthorpe wrote:
> 
> On 15 Jun 2001, Adam Di Carlo wrote:
> 
> > There is no base tarball anymore.  The functionality has been
> > superceeded by debootstrap (the package).
> 
> Hrm. This is midely annoying to say the least :<
> 
> The base tarball is *very* useful for NFS root booting other
> architectures which I do alot, particularly when the NFS serving box is
> not a debian box. It is very nice to be able to say 'fetch this tar,
> unpack it, setup NFS and boot this kernel'.
> 
> I'm not sure how you can automate that process without haxoring the .debs
> since they can't really have their post insts run. It would be nice if
> there is possible solution, particularly if said solution could run on
> non-Debian unix's..

Maybe debootstrap could be hacked to support this? I'm not sure how you
would create a fully installed system in a chroot on a different arch
though.

-- 
 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'


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

Re: base*.tgz is gone, and why it's gone

[Anthony Towns]

On Fri, Jun 15, 2001 at 05:09:33PM -0600, Jason Gunthorpe wrote:
> I'm not sure how you can automate that process without haxoring the .debs
> since they can't really have their post insts run. It would be nice if
> there is possible solution, particularly if said solution could run on
> non-Debian unix's..

Hrm? debootstrap works on non-Debian Linux's, at least (I've had one
report of a successful run under Red Hat, eg). It probably works on
non-Debian Unix's that have a Linux-binary-compatibility module of some
sort, modulo some bugs.

It can be used to create a base.tgz, at any rate.

Cheers,
aj

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

``_Any_ increase in interface difficulty, in exchange for a benefit you
  do not understand, cannot perceive, or don't care about, is too much.''
  -- John S. Novak, III (The Humblest Man on the Net)

 PGP signature

Bug#100996: boot-floppies regress. seriously

[Gaby Schilders]

Package: Installation
Version: 2.3.5
Severity: grave

Complete version: 2.3.5-2001-06-14 compact

Error-message: debootstrap exited with error 1.
dpkg --force-depends --force-overwrite --force failed.

(approximation) I tracked this down to be in /usr/lib/
debootstrap/scripts/woody

I cannot explain why this fails but if I try to do
dpkg
from /usr/bin it isn't there (anymore?) and if I try
to
do it from /target/usr/bin it fails whining over
libraries.

Install-sequence: boot from compact rescue, load
compact root. Do everything from scratch.
US keyboard, swap, clean root partition.
Install kernel and modules from floppy, configure
network then install the base system over the net from
http://ftp.nl.debian.org/debian

The first part works out fine, then it says it's
installing some empty files, then wants to continue
but
gives the error message stated above repeatedly.
After ok-ing all the errors you return to the menu.

Hope this helps,

Gaby


Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie


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

Bug#101001: bootfloppies: cfdisk messes up

[Gaby Schilders]

Package: Installation
Version: 2.3.4
Severity: important

Full version: boot-floppies 2.3.4-2001-05-31-compact

Partitioning my 30 GB Harddrive with cfdisk resulted
in
a non-bootable system that I wasn't able to make
bootable with lilo without reinstalling. Using fdisk
in
the second install instead of cfdisk revealed that the
partitions were not on cylinder boundries.
repartitioning solved the problem.

(Lilo was using lba32, linear didn't solve the
problem.
Currently, on the newly partitioned drive I'm using
lba32 and compact without a problem).

This maybe a lilo or cfdisk problem but since I'm not
sure I leave it up to the boot-maintainer to move this
to the responsible person.

Gaby


Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie


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

Bug#100996: boot-floppies regress. seriously

[Stephen R Marenka]

On Fri, Jun 15, 2001 at 02:12:02PM +0100, Gaby Schilders wrote:
> Error-message: debootstrap exited with error 1.
> dpkg --force-depends --force-overwrite --force failed.

This problem is because one or more of the packages failed to 
configure. You should be able to look in the logs (or chroot 
/target dselect) and see if you can figure out what broke. 
Then we can get it fixed.

Thanks,

Stephen

-- 
Stephen R. Marenka If life's not fun, you're not doing it right!
<[EMAIL PROTECTED]>

 PGP signature