Re: Bug? - Boot disks and Kernel Source

[Levi Waldron]

On February 11, 2003 07:42 am, Dave Whiteley wrote:
> There is not a stable package for kernel 2.2.20!

Yes, there are several.  I checked first on my machine with 

apt-cache search kernel-image-2.2.20

then double-checked at http://www.debian.org/distrib/packages by searching 
for kernel-image-2.2.20 under stable, and in both cases got the 
following hits:

stable 
kernel-image-2.2.20-idepci 2.2.20-5   (1360.6k) 
Linux kernel binary image.

stable 
kernel-image-2.2.20-compact 2.2.20-5   (1689.8k) 
Linux kernel binary image.

stable 
kernel-image-2.2.20 2.2.20-5   (5803.3k) 
Linux kernel binary image for version 2.2.20.

stable 
kernel-image-2.2.20-reiserfs 2.2.20-4   (1669.3k) 
Linux kernel binary image for version 2.2.20.


-- 
-Levi


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

Re: Bug? - Boot disks and Kernel Source

[Dave Whiteley]

On Thu, Feb 13, 2003 at 05:30:22PM +1100, Rob Weir wrote:
> On Tue, Feb 11, 2003 at 02:19:03PM +, Dave Whiteley wrote:
> > On Tue, Feb 11, 2003 at 01:34:19PM +, Keith O'Connell wrote:
> > > 
> > > > I see that the boot floppies use a kernel 2.2.20.
> > > > 
> > > > There is not a stable package for kernel 2.2.20!
> > > 
> > >   ?
> > > 
> > >   Yes there is! There is no 2.4.20 though.
> > 
> > 
> > Are you sure!  It is a bit tricky for me to know, as I run my apt
> > source including the testing distribution, and then I do see 2.2.20,
> > however when I look at the stable package lists on debian.org, 2.2.20
> > is missing.
> 
> Are we talking about 2.4.20 or 2.2.20?  2.2.20 is, AFAIK, still the
> default kernel on the boot floppies, and is also available as a
> kernel-source and kernel-image package in woody.  2.4.20 is not, and
> probably never will be available in woody, since it was not released
> until well after woody froze.  Woody does contain both 2.4.18 boot
> floppies and kernel-{image,source} packages though.
> 
> -- 
> Rob Weir <[EMAIL PROTECTED]>   http://ertius.org/

I am talking about 2.2.20.

I was trying to do something with the stable boot-disks, and when I
looked to see what version kernel they used I found 2.2.20.

I then looked at the Debian Packages web site under the stable
distribution, and the source package for 2.2.20 was not listed.

This is no real problem to me as 2.2.20 is available under testing (or
sid?), so my question REALLY was, 
   "Is the fact that 2.2.20 is missing from the stable package list a
   bug?"

Does this make things clear?

Dave

-- 
Dave Whiteley
[EMAIL PROTECTED]
Phone +44 (0)113 343 2059
School of Electronic and Electrical Engineering
The University of Leeds. Leeds, LS2 9JT,  UK


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

Re: Bug? - Boot disks and Kernel Source

[Dave Whiteley]

On Thu, Feb 13, 2003 at 08:53:46AM +0100, Eduard Bloch wrote:
> #include 
> * Dave Whiteley [Tue, Feb 11 2003, 12:42:55PM]:
> 
> > I am trying to generate a new set of boot disks for an old system (see
> > another thread).
> 
> Which Thread? Where? There are dozens of new threads in this ML.

Sorry. That data was omitted, because it is not important for this
topic. I did not want to split discussion of that problem (which is
now solved) over two threads.

> 
> > I see that the boot floppies use a kernel 2.2.20.
> > 
> > There is not a stable package for kernel 2.2.20!
> 
> Archive maintainance Bug in 3.0r1, the packages should still be in the
> pool. New boot-floppies will have 2.2.22, see
> http://people.debian.org/~blade/bf3024/.
> 

Yes, the package is available, but not listed in the stable
distribution on the Debian Packages web page.

This is why I was not sure if this was a reportable bug or not.

Thanks for your reply.

> Gruss/Regards,
> Eduard.
> -- 
> Daten sind Aneinanderreihungen von kleinen Mustern ohne Bedeutung
>   -- aus Mantis Seminararbeit

-- 
Dave Whiteley
[EMAIL PROTECTED]
Phone +44 (0)113 343 2059
School of Electronic and Electrical Engineering
The University of Leeds. Leeds, LS2 9JT,  UK


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

Re: Bug? - Boot disks and Kernel Source

[Eduard Bloch]

#include 
* Dave Whiteley [Tue, Feb 11 2003, 12:42:55PM]:

> I am trying to generate a new set of boot disks for an old system (see
> another thread).

Which Thread? Where? There are dozens of new threads in this ML.

> I see that the boot floppies use a kernel 2.2.20.
> 
> There is not a stable package for kernel 2.2.20!

Archive maintainance Bug in 3.0r1, the packages should still be in the
pool. New boot-floppies will have 2.2.22, see
http://people.debian.org/~blade/bf3024/.

Gruss/Regards,
Eduard.
-- 
Daten sind Aneinanderreihungen von kleinen Mustern ohne Bedeutung
-- aus Mantis Seminararbeit


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

Re: Bug? - Boot disks and Kernel Source

[Rob Weir]

On Tue, Feb 11, 2003 at 02:19:03PM +, Dave Whiteley wrote:
> On Tue, Feb 11, 2003 at 01:34:19PM +, Keith O'Connell wrote:
> > 
> > > I see that the boot floppies use a kernel 2.2.20.
> > > 
> > > There is not a stable package for kernel 2.2.20!
> > 
> > ?
> > 
> > Yes there is! There is no 2.4.20 though.
> 
> 
> Are you sure!  It is a bit tricky for me to know, as I run my apt
> source including the testing distribution, and then I do see 2.2.20,
> however when I look at the stable package lists on debian.org, 2.2.20
> is missing.

Are we talking about 2.4.20 or 2.2.20?  2.2.20 is, AFAIK, still the
default kernel on the boot floppies, and is also available as a
kernel-source and kernel-image package in woody.  2.4.20 is not, and
probably never will be available in woody, since it was not released
until well after woody froze.  Woody does contain both 2.4.18 boot
floppies and kernel-{image,source} packages though.

-- 
Rob Weir <[EMAIL PROTECTED]> http://ertius.org/



msg30447/pgp0.pgp
Description: PGP signature

Re: Bug? - Boot disks and Kernel Source

[Dave Whiteley]

On Tue, Feb 11, 2003 at 01:34:19PM +, Keith O'Connell wrote:
> 
> > I see that the boot floppies use a kernel 2.2.20.
> > 
> > There is not a stable package for kernel 2.2.20!
> 
>   ?
> 
>   Yes there is! There is no 2.4.20 though.


Are you sure!  It is a bit tricky for me to know, as I run my apt
source including the testing distribution, and then I do see 2.2.20,
however when I look at the stable package lists on debian.org, 2.2.20
is missing.



> 
> Keith
> ___   _
>   Keith O'Connell.   -o)
>   Maidstone, Kent. (UK)  /\\
>   [EMAIL PROTECTED] _\_v

Nice Tux!

Dave

-- 
Dave Whiteley
[EMAIL PROTECTED]
Phone +44 (0)113 343 2059
School of Electronic and Electrical Engineering
The University of Leeds. Leeds, LS2 9JT,  UK


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

Re: Bug? - Boot disks and Kernel Source

[Keith O'Connell]

> I see that the boot floppies use a kernel 2.2.20.
> 
> There is not a stable package for kernel 2.2.20!

?

Yes there is! There is no 2.4.20 though.

When are we likely to see 2.4.20?

Keith
___   _
  Keith O'Connell.   -o)
  Maidstone, Kent. (UK)  /\\
  [EMAIL PROTECTED] _\_v


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

Bug? - Boot disks and Kernel Source

[Dave Whiteley]

Is it a bug?

I am trying to generate a new set of boot disks for an old system (see
another thread).

I see that the boot floppies use a kernel 2.2.20.

There is not a stable package for kernel 2.2.20!

Dave


-- 
Dave Whiteley
[EMAIL PROTECTED]
Phone +44 (0)113 343 2059
School of Electronic and Electrical Engineering
The University of Leeds. Leeds, LS2 9JT,  UK


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

JFS boot disks

[Mitchell Smith]

Hi list,

Sorry about the cross post, I wasn't sure which was the correct list for
this question.

I have managed to break a JFS system and was wondering if there are JFS
rescue / root disks available for Debian or will I have to build my own?

I know there are boot disks out there for XFS and Reiser, so thought it
couldn't hurt to ask about JFS before I build my own.

Thanks

>From Mitchell




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

Re: Boot Disks

[Tom Pfeifer]

Keith O'Connell wrote:
> 
> Hi,
> 
> I have clearly misunderstood the making of boot disks and would like some 
> guidance. I made some for each machine here in case or emergency, and thought 
> I would test them, and each one halted with a kernel panic.
> 
> I assumed that a floppy in the drive of a working machine followed by the 
> command "mkboot" as root would create a boot disk from the currently running 
> kernel. The disk booted to a panic.
> 
> I read over the rather small man page and tried the full complement of 
> switches of "mkboot -r /dev/hda3 -i /vmlinuz" but still there is a panic
> 
> I have 2.2.20 and 2.4.28 on each machine, and want to be able to use a floppy 
> to boot one kernel and another floppy to boot another kernel. How do I make 
> these disks?
> 
> I have tried the man pages and the books on the shelf, but I am not getting 
> it. What is the right way to create the floppy disks I want?
> 
> Anyone?
> 
> Keith
> --

There's several ways other than mkboot

One very simple method is to just copy your kernel to the floppy disk
(the raw device), and then set the kernel's root device. Insert the
floppy, *don't* mount it, and then:

cp /boot/your_kernel /dev/fd0
rdev /dev/fd0 /dev/your_root_partition

To check the root device:  rdev /dev/fd0

The kernel will bootstrap itself, mount the root partition and go from
there.

The disadvantage of that method is that it's slow on boot, and you need
one disk for each kernel you might want to boot. It's slow because the
kernel has to uncompress and load itself from the floppy disk.

Another way is if you have Lilo installed, and already have a valid
/etc/lilo/conf for booting off the hard drive. Take that /etc/lilo.conf
and change the boot= parameter to boot=/dev/fd0. Then run 'lilo' with a
floppy disk inserted in the drive. It will write the Lilo boot sector to
the floppy disk. On boot, it will read just the one sector from the
floppy, and do the rest from the hard drive - much faster. And you will
have the same menu as when booting normally.

If you use grub, you can do a similar thing, and can also just make a
generic grub boot disk where you specify the kernel and root partition
interactively from grub's shell. The command to make the generic grub
disk is 'grub-floppy /dev/fd0'. If you like grub, it's not a bad idea
to have one of those around.

Tom


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

Boot Disks

[Keith O'Connell]

Hi,

I have clearly misunderstood the making of boot disks and would like some 
guidance. I made some for each machine here in case or emergency, and thought I 
would test them, and each one halted with a kernel panic.

I assumed that a floppy in the drive of a working machine followed by the 
command "mkboot" as root would create a boot disk from the currently running 
kernel. The disk booted to a panic.

I read over the rather small man page and tried the full complement of switches 
of "mkboot -r /dev/hda3 -i /vmlinuz" but still there is a panic

I have 2.2.20 and 2.4.28 on each machine, and want to be able to use a floppy 
to boot one kernel and another floppy to boot another kernel. How do I make 
these disks?

I have tried the man pages and the books on the shelf, but I am not getting it. 
What is the right way to create the floppy disks I want?

Anyone?

Keith
-- 

  Keith O'Connell.
  Maidstone, Kent. (UK)
  [EMAIL PROTECTED]


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

Re: woody boot disks

[Shaul Karl]

> Hi!
> 
> how can I make the boot and root floppy disks for woody? I was searching the 
> Debian site, but I didn't find anything. Perhaps I am not looking correctly?
> 
> Thanks in advance
> 
> Marcelo
> 


The images for x86 should be on mirrored somewhere under 
dists/woody/main/disks-i386.

Instructions for how to use those images in order to get a usable 
floppy are, for example, at http://www.debian.org/releases/stable/i386/c
h-install-methods.en.html#s-create-floppy .


-- 

Shaul Karl
email: shaulka(at-no-spam)bezeqint.net 
   Please substitute (at-no-spam) with an at - @ - character.
   (at-no-spam) is meant for unsolicitate mail senders only.



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

woody boot disks

[Marcelo Chiapparini]

Hi!

how can I make the boot and root floppy disks for woody? I was searching the 
Debian site, but I didn't find anything. Perhaps I am not looking correctly?

Thanks in advance

Marcelo

-- 
Marcelo Chiapparini
DFT-IF/UERJ
[EMAIL PROTECTED]


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

Re: boot disks (again)

[Joost Kooij]

On Mon, Jul 16, 2001 at 03:09:20PM -0400, [EMAIL PROTECTED] wrote:
> Which file should i use (/vmlinuz or /boot/vmlinuz2.2.17pre19), and how can i 
> make it work?

  dd if=/boot/vmlinuz-2.2.17pre19 of=/dev/fd0
  rdev /dev/fd0 $(rdev | cut -d ' ' -f 1)
  rdev -R /dev/fd0 1

If you're not sure about which vmlinuz to use, make a second bootdisk
with /vmlinuz.  On my system, /vmlinuz is a symbolic link to the file 
in /boot, so there would be no real difference.

Cheers,


Joost

Re: mformat, boot disks

[Guy Geens]

>>>>> "R1nso" == R1nso  <[EMAIL PROTECTED]> writes:

R1nso> the disk created with mkboot does work to boot the system.
R1nso> however, i have made boot disks using basically the method you
R1nso> described (dd and rdev) and they don't work. the only
R1nso> difference between the two methods is that i used dd with a
R1nso> blocksize of 8192 (bs=8192) and then checked to make sure it

The blocksize should not matter.

R1nso> was set to the first partition on the hard disk (rdev /dev/fd0
R1nso> << /dev/hda1), and it was correct, so i didn't need to set it
R1nso> again, right? perhaps i should have mentioned that after
R1nso> printing several dots following 'loading' it began to rapidly
R1nso> print "200" then on a new line "AX: " new line
R1nso> "BX:" and so on until 'DX' another thing I

That looks like a kernel panic: something has made the kernel crash.

Very strange. The same kernel works when booted by LILO. I looked at
mkboot and it doesn't add any flags besides the root device.

R1nso> recently discovered is that there is a file called "vmlinuz" in
R1nso> the root '/' directory. i have also tried dd - ing it to fd0,
R1nso> checking it w/ rdev but only to produce the same results. Which
R1nso> file should i use, and how can i make it work?

/vmlinuz is actually a link to /boot/vmlinuz-x.x.x, so either one
should work. (Do `ls -l /' to see for yourself.)

As far as I can see, you did everything correct. There are two other
options I can think of:

- your floppy drive is defective/strange. LILO manages to work around
  the problem, but the loader built into the kernel doesn't.
- the floppy this you used for the raw kernel image is defective. Try
  a different one.

-- 
G. ``Iggy'' Geens - ICQ: #64109250
Home: <[EMAIL PROTECTED]> - Work: <[EMAIL PROTECTED]>
WWW: http://users.pandora.be/guy.geens/
`I want quality, not quantity. But I want lots of it!'

Re: boot disks (again)

[D-Man]

On Mon, Jul 16, 2001 at 03:09:20PM -0400, [EMAIL PROTECTED] wrote:
| thanks to everyone who helped with my mformat problem, but i am
| still unable to get my boot disks working so i though i'd write
| another e-mail in a little bit greater detail

IMO it is much easier to make a boot disk with grub.  Simply download
ftp://alpha.gnu.org/gnu/grub/grub-0.5.96.1-i386-pc.ext2fs and dump it
to a floppy (doesn't matter if it is formatted or not) with dd.  Then
boot with it.  Read a the sample menu.lst file that is on the floppy
and tweak it to match your system.  You can even copy the kernel (use
cp) to the floppy and tell grub to boot with that one.  Grub's config
file is mostly self-explanatory.  If you have more grub questions,
don't hesitate to ask.  Looking at the ftp site it looks like there is
a new "release" labeled
ftp://alpha.gnu.org/gnu/grub/grub-0.90-i386-pc.ext2fs, but I am using
the older (0.5.96.1) version and have been very happy with it.

HTH,
-D

boot disks (again)

[R1nso13]

thanks to everyone who helped with my mformat problem, but i am still unable 
to get my boot disks working so i though i'd write another e-mail in a little 
bit greater detail

the disk created with 'mkboot /boot/vmlinuz2.2.17pre19" does work to boot the 
system by starting lilo (produces "LILO boot:" at start up)
however, the boot disks made using basically the method described by the 
people responding to my e-mail (dd and rdev) don't work. there is a slight 
difference between what i did and some of the responses though. i used dd 
with a blocksize of 8192 (bs=8192) and then checked to make sure it was set 
to the first partition on the hard disk (rdev /dev/fd0 << /dev/hda1), and it 
was correct, so i didn't need to set it again, right ?
i've also used cp and omittedthe bs argument for dd. i've tried all the above 
on newly formatted disks and used both /vmlinuz and /boot/vmlinuz2.2.17pre19 
with the dd & cp commands
perhaps i should have mentioned that upon rebooting after printing several 
dots following 'loading' the computer began to rapidly print "200" then on a 
new line "AX:" new line "BX:" and so on until 'DX'
the disks were either brand new or formatted w/ superformat or msdos
i've tried every combination of files, format, copying techniques and 
specification of the root device listed above but i have yet to create a 
working boot disk

Which file should i use (/vmlinuz or /boot/vmlinuz2.2.17pre19), and how can i 
make it work?

thanks in advance
-Ransom

Re: mformat, boot disks

[Wayne Topa]

Subject: mformat, boot disks
Date: Sat, Jul 14, 2001 at 08:38:52PM -0400

In reply to:[EMAIL PROTECTED]

Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]):
> I'm running 2.2r3 i-386.
> 
> 1. When I run 'superformat /dev/fd0' the disk is formatted. However, when 
> superformat tries to run mformat to created an msdos file system, I get the 
> error message 
> 'sh: error:command not found'
> or something similar. When i simply type 'mformat' i get a similar error 
> message. Should I worry about this? Even if it is not a problem, why am i 
> getting this message?
> 
VT1 root-2.2r3-prince:~# dpkg -S mformat
mtools: /usr/bin/mformat
mtools: /usr/share/man/man1/mformat.1.gz

Load the mtools package.

> 2. I have successfully made a lilo boot disk using "mkboot 
> /boot/vmlinuz2.2.17pre19". But i have also tried copying the binary to the 
> disk using 'cp' and 'dd'. However, these disks are recognized as system boot 
> disks, but the do not successfully boot linux. When booting for these disks 
> the monitor simply displays "loading" but does not successfully load. 
> Am I copying the wrong file, or will this method simply not work with Debian? 
> Regardless, how can I create a 'normal' boot disk? (one that doesn't use lilo)

dd if=/usr/src/linux/arch/i386/boot/bzImage of=/dev/fd0 bs=512 conv=sync ; sync

Is how I make boot disks.  Floppies are funny tho, so I usually make 2. 
Seems I find a lot of bad floppies.  YMMV

Wayne
-- 
A printer consists of three main parts: the case, the jammed paper
tray and the blinking red light.
___

Re: mformat, boot disks

[Guy Geens]

>>>>> "R1nso" == R1nso  <[EMAIL PROTECTED]> writes:

R1nso> When i simply type 'mformat' i get a similar error message.
R1nso> Should I worry about this? Even if it is not a problem, why am
R1nso> i getting this message?

It means you don't have the mformat command installed. You'll find it
in the mtools package.

Superformat formats a floppy and then puts on a MS-DOS file system.

R1nso> 2. I have successfully made a lilo boot disk using "mkboot
R1nso> /boot/vmlinuz2.2.17pre19". But i have also tried copying the

Does this floppy work to boot your system.

R1nso> binary to the disk using 'cp' and 'dd'. However, these disks
R1nso> are recognized as system boot disks, but the do not
R1nso> successfully boot linux. When booting for these disks the
R1nso> monitor simply displays "loading" but does not
R1nso> successfully load. Am I copying the wrong file, or will this
R1nso> method simply not work with Debian? Regardless, how can I
R1nso> create a 'normal' boot disk? (one that doesn't use lilo)

If you copy the kernel manually, you have to set the root device as
well:
dd if=/boot/vmlinuz2.2.17pre19 of=/dev/fd0
rdev /dev/fd0 /dev/hda1 # <- fill in your root partition here.

-- 
G. ``Iggy'' Geens - ICQ: #64109250
Home: <[EMAIL PROTECTED]> - Work: <[EMAIL PROTECTED]>
WWW: http://users.pandora.be/guy.geens/
`I want quality, not quantity. But I want lots of it!'

Re: mformat, boot disks

[Tom Pfeifer]

One way to make a floppy boot disk that doesn't boot with Lilo...

1) copy your kernel to the (umounted) floppy disk using dd or cp:
   dd if=/boot/your_kernel of=/dev/fd0 
   cp /boot/your_kernel /dev/fd0

2) tell the kernel on the floppy disk where your root partition is:
   rdev /dev/fd0 /dev/your_root_partition

The kernel on the floppy disk will boot itself, and then mount and run
from the root partition on the hard drive.

Tom


[EMAIL PROTECTED] wrote:
> 
> I'm running 2.2r3 i-386.
> 
> 1. When I run 'superformat /dev/fd0' the disk is formatted. However, when
> superformat tries to run mformat to created an msdos file system, I get the
> error message
> 'sh: error:command not found'
> or something similar. When i simply type 'mformat' i get a similar error
> message. Should I worry about this? Even if it is not a problem, why am i
> getting this message?
> 
> 2. I have successfully made a lilo boot disk using "mkboot
> /boot/vmlinuz2.2.17pre19". But i have also tried copying the binary to the
> disk using 'cp' and 'dd'. However, these disks are recognized as system boot
> disks, but the do not successfully boot linux. When booting for these disks
> the monitor simply displays "loading" but does not successfully load.
> Am I copying the wrong file, or will this method simply not work with Debian?
> Regardless, how can I create a 'normal' boot disk? (one that doesn't use lilo)

mformat, boot disks

[R1nso13]

I'm running 2.2r3 i-386.

1. When I run 'superformat /dev/fd0' the disk is formatted. However, when 
superformat tries to run mformat to created an msdos file system, I get the 
error message 
'sh: error:command not found'
or something similar. When i simply type 'mformat' i get a similar error 
message. Should I worry about this? Even if it is not a problem, why am i 
getting this message?

2. I have successfully made a lilo boot disk using "mkboot 
/boot/vmlinuz2.2.17pre19". But i have also tried copying the binary to the 
disk using 'cp' and 'dd'. However, these disks are recognized as system boot 
disks, but the do not successfully boot linux. When booting for these disks 
the monitor simply displays "loading" but does not successfully load. 
Am I copying the wrong file, or will this method simply not work with Debian? 
Regardless, how can I create a 'normal' boot disk? (one that doesn't use lilo)

Re: [users] Re: debian boot disks?

[ktb]

On Thu, May 24, 2001 at 01:01:12AM -0400, MaD dUCK wrote:
> also sprach ktb (on Wed, 23 May 2001 11:56:04PM -0500):
> > You need root.bin, rescue.bin and 1 or more driver disks.  If the disks
> > aren't being read the most likely two problems are a bad or dirty floppy
> > drive and or bad floppy disks.  I assume your following the installation
> > instructions at the debian web-site.
> 
> the disks are being read, i get the debian welcome screen, then
> nothing works. and i tried 5 different floppies on three different
> machines.

I've never had that bad a luck with floppies.  Have you tried dd(ing)
the images from a differnt mirror?  
kent

-- 
 From seeing and seeing the seeing has become so exhausted
 First line of "The Panther" - R. M. Rilke

Re: [users] Re: debian boot disks?

[MaD dUCK]

also sprach ktb (on Wed, 23 May 2001 11:56:04PM -0500):
> You need root.bin, rescue.bin and 1 or more driver disks.  If the disks
> aren't being read the most likely two problems are a bad or dirty floppy
> drive and or bad floppy disks.  I assume your following the installation
> instructions at the debian web-site.

the disks are being read, i get the debian welcome screen, then
nothing works. and i tried 5 different floppies on three different
machines.

martin;  (greetings from the heart of the sun.)
  \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
-- 
"mirrors should reflect a little before throwing back images."
   -- jean cocteau

Re: debian boot disks?

[ktb]

On Thu, May 24, 2001 at 12:16:02AM -0400, MaD dUCK wrote:
> hey all,
> so i tried for the first time to pull up a system without any cdrom,
> just boot disks, and a locally mirrored debian distribution on FTP.
> i got three disks, resuce, boot, and drivers_1. rescue seems to be the
> only bootable one, and i get to a lilo prompt with options "linux",
> "floppy0", "restore", and "ramdisk0". however, all of these yield a
> "Boot failed: please change disks and press a key to continue," after
> which the boot sector is read again. i figure that from this point,
> the root disk is needed, but i could not, for the sake of anything,
> convince debian to boot off the disks from the various ftp sites. any
> hints?

You need root.bin, rescue.bin and 1 or more driver disks.  If the disks
aren't being read the most likely two problems are a bad or dirty floppy
drive and or bad floppy disks.  I assume your following the installation
instructions at the debian web-site.
hth,
kent  

-- 
 From seeing and seeing the seeing has become so exhausted
 First line of "The Panther" - R. M. Rilke

debian boot disks?

[MaD dUCK]

hey all,
so i tried for the first time to pull up a system without any cdrom,
just boot disks, and a locally mirrored debian distribution on FTP.
i got three disks, resuce, boot, and drivers_1. rescue seems to be the
only bootable one, and i get to a lilo prompt with options "linux",
"floppy0", "restore", and "ramdisk0". however, all of these yield a
"Boot failed: please change disks and press a key to continue," after
which the boot sector is read again. i figure that from this point,
the root disk is needed, but i could not, for the sake of anything,
convince debian to boot off the disks from the various ftp sites. any
hints?

martin;  (greetings from the heart of the sun.)
  \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
-- 
scientists will study your brain to learn
more about your distant cousin, man.

Re: Need help in building my own boot disks

[Karsten M. Self]

on Sat, May 19, 2001 at 09:04:27PM -0400, Brian Schramm ([EMAIL PROTECTED]) 
wrote:
> I am running potato with kernel 2.2.19 on it.  I want to build a custom
> kernel that will allow me to boot a new machine with the new netgear
> drivers in it.  I have tryed building the drivers on my machine and just
> copying them over but that does not work.  I am willing to build my own
> disks but when I loaded the boot disks package and read the readme file, I
> tryed doing what it said and failed.  a make check gives back a lot of
> errors and a make release dies too.  
> 
> Please help.  I need to get this machine up this weekend.

I prefer using tanned leather, myself, though I can't decide between
tacks or glue to get the stuff to stick to the soles

Sorry, I just read your post and realized that, spare a decade or so,
your post would be interpreted as something regarding footwear rather
than computers.  "We call'em roller skates, m'boy".

Build your kernel.  Compile in driver support.  Insert blank floppy.

dd if=/vmlinuz of=/dev/fd0

...should do the trick if all you want to do is launch the system and
you've got filesystems, etc., already on it.

-- 
Karsten M. Self http://kmself.home.netcom.com/
 What part of "Gestalt" don't you understand?   There is no K5 cabal
  http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org


pgpilIXMjHyJp.pgp
Description: PGP signature

Re: Need help in building my own boot disks

[Stephen R Marenka]

On Sat, May 19, 2001 at 09:04:27PM -0400, Brian Schramm wrote:
> I am running potato with kernel 2.2.19 on it.  I want to build a custom
> kernel that will allow me to boot a new machine with the new netgear
> drivers in it.  I have tryed building the drivers on my machine and just
> copying them over but that does not work.  I am willing to build my own
> disks but when I loaded the boot disks package and read the readme file, I
> tryed doing what it said and failed.  a make check gives back a lot of
> errors and a make release dies too.  
> 

Here's how to add a custom kernel to the rescue disk which is the boot
disk for Debian boot floppies. Then you should be able to do a normal
install from floppy. (You can still install the base system from the net
or cd later.)

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

Good luck!

Stephen

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

Need help in building my own boot disks

[Brian Schramm]

I am running potato with kernel 2.2.19 on it.  I want to build a custom
kernel that will allow me to boot a new machine with the new netgear
drivers in it.  I have tryed building the drivers on my machine and just
copying them over but that does not work.  I am willing to build my own
disks but when I loaded the boot disks package and read the readme file, I
tryed doing what it said and failed.  a make check gives back a lot of
errors and a make release dies too.  

Please help.  I need to get this machine up this weekend.

Brian


Brian Schramm
[EMAIL PROTECTED]ICQ 104442754  AIM schrammbrian
www.linuxexpert.org

   

Re: Sparc boot disks

[Ethan Benson]

On Sun, Apr 08, 2001 at 07:45:39AM -0400, Roderick Cummings wrote:
> I'm having trouble installing debian on an Ultra E1. I have (several times 
> over the last couple of weeks) downloaded fresh copies of the rescue and 
> driver-1 disk from the sun4u directory, and the root disk as well. I've 
> written them to several different new disks.
> 
> I get through to the part where I install the drivers disk onto the 
> harddrive. It says, "This is disk 1 of 1 in the drv14-sun4u series 
> 27-Nov-2000 13:18 EST, Wrong Disk This is from series drv14-sun4u, You need 
> disk 1 of series the driver series [sic]"
> 
> The rescue and drivers disks should match they both came from the same sun4u 
> directory on ftp.debian.org, and the errors message doesn't make sense.
> 
> What can I try to fix this? I can install on E1's with a CD, but the 2 E1's 
> I have now, do not have a CD rom drive, the drives were stolen by someone 
> from another department. I could probably find a temporary drive, but there 
> must be something wrong with the boot disks or perhaps my brain is out of 
> wack, and I don't realize something obvious.

im not sure about the floppy problem, but an alternate solution is
installing drivers via the single drivers.tgz tarball over the
network.  is the nic supported by the kernel as is? or do you need a
module first?  if you need a module first your stuck figuring out the
floppy problem, if not just tell dbootstrap to fetch the drivers via
http.

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


pgp2eZkMQ8A6F.pgp
Description: PGP signature

Sparc boot disks

[Roderick Cummings]

I'm having trouble installing debian on an Ultra E1. I have (several times 
over the last couple of weeks) downloaded fresh copies of the rescue and 
driver-1 disk from the sun4u directory, and the root disk as well. I've 
written them to several different new disks.


I get through to the part where I install the drivers disk onto the 
harddrive. It says, "This is disk 1 of 1 in the drv14-sun4u series 
27-Nov-2000 13:18 EST, Wrong Disk This is from series drv14-sun4u, You need 
disk 1 of series the driver series [sic]"


The rescue and drivers disks should match they both came from the same sun4u 
directory on ftp.debian.org, and the errors message doesn't make sense.


What can I try to fix this? I can install on E1's with a CD, but the 2 E1's 
I have now, do not have a CD rom drive, the drives were stolen by someone 
from another department. I could probably find a temporary drive, but there 
must be something wrong with the boot disks or perhaps my brain is out of 
wack, and I don't realize something obvious.

_
Get your FREE download of MSN Explorer at http://explorer.msn.com

Re: New Install of Debian: How do i create boot disks???

[Patrick Ouellette]

You can also create boot floppies off the Debian CD.  There should
be a directory on the cd called disks-i386.  It contains the boot
floppy image files.  You will also need the utility rawrite2 from
the dosutils directory (or somewhere on the net like 
ftp.us.debian.org).  

Pat

On Thu, Feb 15, 2001 at 01:58:31PM -0800, Robert Cymbala wrote:
> 
> Hi ~
> Here's a method that installs Debian from floppy disks and
> then from a parallel port CD-ROM device (microSolutions bantam
> backpack).
> 
>   "Debian GNU/Linux on Toshiba T4700ct Notebook"
>   http://www.lafn.org/~cymbala/Debian/t4700ct.html
> 
>   

-- 
===
Patrick Ouellette   
Amateur Radio: KB8PYMi mobile/portable 9  (somewhere in 9 land)
Debian Linux Developer (as time and family permit)
Human? (the jury is still out on this one)
===
GPG Fingerprint: 8577 CFA7 B984 8E58 0D00 79B6 CFDA 9D82 06A7 376E

Re: New Install of Debian: How do i create boot disks???

[Robert Cymbala]

Hi ~
Here's a method that installs Debian from floppy disks and
then from a parallel port CD-ROM device (microSolutions bantam
backpack).

  "Debian GNU/Linux on Toshiba T4700ct Notebook"
  http://www.lafn.org/~cymbala/Debian/t4700ct.html

  

--- "Mahalingam, Sivendiran" <[EMAIL PROTECTED]> wrote:
> hi 
> 
> Does anyone know how to create Debian boot disks?  I am trying to
> install
> Debian for the first time, but I only have a CD distribution, and my
> computer does not have support to boot up from a CD.  Anyone got some
> creative ways to solve this probelm?
> 
> thanks
> 


__
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

Re: New Install of Debian: How do i create boot disks???

[Nathan E Norman]

On Thu, Feb 15, 2001 at 02:28:07PM -0500, Mahalingam, Sivendiran wrote:
> hi 
> 
> Does anyone know how to create Debian boot disks?  I am trying to install
> Debian for the first time, but I only have a CD distribution, and my
> computer does not have support to boot up from a CD.  Anyone got some
> creative ways to solve this probelm?

It's a very dangerous and subversive idea, but you could RTFM:

http://www.debian.org/releases/stable/i386/ch-install-methods.en.html#s-install-floppies
 

-- 
Nathan Norman - Staff Engineer | A good plan today is better
Micromuse Inc. | than a perfect plan tomorrow.
mailto:[EMAIL PROTECTED]   |   -- Patton


pgpKk3sB7Ml72.pgp
Description: PGP signature

New Install of Debian: How do i create boot disks???

[Mahalingam, Sivendiran]

hi 

Does anyone know how to create Debian boot disks?  I am trying to install
Debian for the first time, but I only have a CD distribution, and my
computer does not have support to boot up from a CD.  Anyone got some
creative ways to solve this probelm?

thanks

Re: Boot disks for testing

[David Wright]

Quoting Ray Percival ([EMAIL PROTECTED]):
> Where would one get boot/driver disks for testing on the ftp sites
> there does not appear to be anything under disksi386 under 
> testing.

I think you just install potato and upgrade. I imagine that boot disks
is one of the last things to be made before a distribution is released
(because you don't know what to put in it until then).

Cheers,

-- 
Email:  [EMAIL PROTECTED]   Tel: +44 1908 653 739  Fax: +44 1908 655 151
Snail:  David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA
Disclaimer:   These addresses are only for reaching me, and do not signify
official stationery. Views expressed here are either my own or plagiarised.

Boot disks for testing

[Ray Percival]

Where would one get boot/driver disks for testing on the ftp sites
there does not appear to be anything under disksi386 under 
testing.
Thanks much for any info.

non-english boot disks

[Patrick R. Wade]

I'm trying to set up a machine with a spanish-language version of Debian
as part of a classroom/public Internet access site; but, despite finding
spanish language installation instructions, i can't seem to find spanish
language installation media.  I suppose i could use my english language
installation media and do a bunch of i18n conversion, but i'd be happier
using spanish from the start.  Is there something obvious i'm missing?

-- 
if(rp->p_flag&SSWAP) {
rp->p_flag =& ~SSWAP;
aretu(u.u_ssav);
}

kudos to makers of potato boot disks.

[Adam Shand]

i just used to one to restore my system and they are *VERY* nice.  all the
in built help for various ways they can be used is very helpfull.

thanks!

adam.

2.2.8 boot disks - no colour

[Lindsay Allen]

Greetings,

I get no colour during the installation process and now that installation
is complete mc does not have its familiar blue screen.  TERM=linux and
/etc/terminfo/l/linux is the same as on my other DEb box.

It's not just a colour thing - a new vi screen in full of underscores so
this needs fixing.  Any ideas on where to go from here?

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lindsay Allen   <[EMAIL PROTECTED]>  Perth, Western Australia
voice +61 8 9316 248632.0125S 115.8445E  Debian Linux
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Re: low mem boot disks

[Bruce Sass]

On Sun, 20 Feb 2000, Wakko Warner wrote:

> slink was the last debian dist with lowmem boot disks, where have they gone?

AFAIK, there was nobody around to work on them for potato.

> Don't tell me that the programs have gotten so big they won't work on a
> 2-4mb machine.

It is a manpower, not a technical issue.
Although I could not get slink to install into less than 4M, the kernel
refused to run (IIRC), and was told that the 4M bar could get bumped up 
for newer kernels.


- Bruce

low mem boot disks

[Wakko Warner]

slink was the last debian dist with lowmem boot disks, where have they gone?

Don't tell me that the programs have gotten so big they won't work on a
2-4mb machine.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

Re: big non-boot disks

[brian moore]

On Wed, Feb 02, 2000 at 04:54:30PM -0500, Danny Heap wrote:
> I'm seeing advertisements for IDE drives with over 20 GB capacity.  I
> realize that one of the problems with really large IDE drives has been
> that BIOS doesn't report the geometry properly.

Irrelevant, since the geometry has been a lie for a long time (most
drives have a variable number of sectors per track these days... they lie
to the system to make it look "right").

> However, if I don't plan to install the drive with any bootable
> partitions (as a second slave drive, say), then won't the disk
> geometry be completely understood by the linux kernel, perhaps helped
> out by some boot parameters?

It's unlikely the kernel would need such help.  I have an 18G drive that
my BIOS doesn't even know about and Linux is quite happy with it.  (All
I did was enable the controller in the BIOS... I didn't have the BIOS
probe it and it shows '---' for everything in the list in the BIOS.)

> Also, how do I discover the true disk geometry?  Can I simply read
> what's printed on the drive?

You can't discover the true geometry without a lot of work.  It doesn't
matter anyway, since nothing uses it.

> Some of the large drives I've seen advertised are Maxtor 20.4 GB,
> Seagate 28 GB, Maxtor 36 GB.  And a scsi Seagate 50.1 GB.

They should all work fine on a modern kernel.

-- 
Brian Moore   | Of course vi is God's editor.
  Sysadmin, C/Perl Hacker | If He used Emacs, He'd still be waiting
  Usenet Vandal   |  for it to load on the seventh day.
  Netscum, Bane of Elves.

Re: big non-boot disks

[aphro]

usually yeah, or get the tech specs from the www site from the maker of
the drive.. the only barriers i've found with ide are 540(545?)MB 8GB and
32GB haven't encountered/read about problems with stuff inbetween those,
although i dont doubt there are some really broken bioses out there.

one of systems i built a few months ago with a 37GB ibm drive did not
detect teh drive in the bios, or if it did it didnt show me the geometry
of the drive it was just blank, but for some reason i was still able to
format and install/use it not only as a bootable drive(with a 6GB bootable
partition) but i could (apparently havent really tested it to its full
extent) access all 37GB of the drive. 

and in another case, with a really old computer, the bios stopped
recognizing ANY drives at all, and yet when i booted a linux kernel from
floppy i could read/write/mount drives no problem. it must of bypassed
bios calls to detect the drives, as when i booted to dos and tried fdisk
it said 'no fixed disks present'.

moral of the stories i guess even if the bios can't see the drive right it
still might work :)

nate

On Wed, 2 Feb 2000, Danny Heap wrote:

danny >I'm seeing advertisements for IDE drives with over 20 GB capacity.  I
danny >realize that one of the problems with really large IDE drives has been
danny >that BIOS doesn't report the geometry properly.
danny >
danny >However, if I don't plan to install the drive with any bootable
danny >partitions (as a second slave drive, say), then won't the disk
danny >geometry be completely understood by the linux kernel, perhaps helped
danny >out by some boot parameters?
danny >
danny >Also, how do I discover the true disk geometry?  Can I simply read
danny >what's printed on the drive?
danny >
danny >Some of the large drives I've seen advertised are Maxtor 20.4 GB,
danny >Seagate 28 GB, Maxtor 36 GB.  And a scsi Seagate 50.1 GB.
danny >
danny >Thanks for any help
danny >Danny Heap
danny >[EMAIL PROTECTED]
danny >
danny >
danny >-- 
danny >Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
danny >

[mailto:[EMAIL PROTECTED] ]--
   Vice President Network Operations   http://www.firetrail.com/
  Firetrail Internet Services Limited  http://www.aphroland.org/
   Everett, WA 425-348-7336http://www.linuxpowered.net/
Powered By:http://comedy.aphroland.org/
Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/
-[mailto:[EMAIL PROTECTED] ]--
5:19pm up 167 days, 5:30, 1 user, load average: 1.04, 1.05, 1.06

big non-boot disks

[Danny Heap]

I'm seeing advertisements for IDE drives with over 20 GB capacity.  I
realize that one of the problems with really large IDE drives has been
that BIOS doesn't report the geometry properly.

However, if I don't plan to install the drive with any bootable
partitions (as a second slave drive, say), then won't the disk
geometry be completely understood by the linux kernel, perhaps helped
out by some boot parameters?

Also, how do I discover the true disk geometry?  Can I simply read
what's printed on the drive?

Some of the large drives I've seen advertised are Maxtor 20.4 GB,
Seagate 28 GB, Maxtor 36 GB.  And a scsi Seagate 50.1 GB.

Thanks for any help
Danny Heap
[EMAIL PROTECTED]

Re: Boot disks -- don't

[John Carline]

John Carline wrote:

> Hi All,
>
> Would anyone by any chance know what would make boot disks
> stop working?
>

mumble!  mumble!  curse!

Just in case anyone is interested, I now know.

If the floppy cable is not "perfectly" connected to the motherboard,  it's 
possible
for the drive to read, write, and boot "most disks" correctly - but not all of 
them.
In my case the only disks that didn't work were the disks created with "zdisk 
and
bzdisk" even though the disks could be created.

It only took three checks and finally the disconnecting and reconnecting of the 
cable
to find it.

mumble! mumble! curse!

John


>
> I've got several small hard drives that I plug into my
> computer as /dev/hdd1 and have been playing with different
> configurations and kernels. After testing some modems for a
> friend, none of the boot disks that were created with either
> "make zdisk" or "make bzdisk" work. Instead of the normal
> "Loading"  and a bunch of dots. I get what looks like a cpu
> dump and then after all the dots, the computer reboots.
>
> Looks like this;
>
> loading. 8000
> AX 0204
> BX 
> CX 0006
> DX  ..   (then reboots)
>
> Luckily all the disks that were created during the initial
> installation work - those that have syslink on them. All disks
> created during the compiling of a kernel fail. I even tried
> recompiling my slink/2.2.9 kernel and creating a new bzdisk,
> but it failed also.
>
> Evidently I changed something when I was testing the modems,
> but I sure don't see what.
>
> Any hints would be greatly appreciated.
>
> Thanks
> John Carline
>
> --
>
> Powered by the Penguin
>
> --
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

--

Powered by the Penguin

Boot disks -- don't

[John Carline]

Hi All,

Would anyone by any chance know what would make boot disks
stop working?

I've got several small hard drives that I plug into my
computer as /dev/hdd1 and have been playing with different
configurations and kernels. After testing some modems for a
friend, none of the boot disks that were created with either
"make zdisk" or "make bzdisk" work. Instead of the normal
"Loading"  and a bunch of dots. I get what looks like a cpu
dump and then after all the dots, the computer reboots.

Looks like this;

loading. 8000
AX 0204
BX 
CX 0006
DX  ..   (then reboots)


Luckily all the disks that were created during the initial
installation work - those that have syslink on them. All disks
created during the compiling of a kernel fail. I even tried
recompiling my slink/2.2.9 kernel and creating a new bzdisk,
but it failed also.

Evidently I changed something when I was testing the modems,
but I sure don't see what.

Any hints would be greatly appreciated.

Thanks
John Carline



--

Powered by the Penguin

Re: creating boot disks

[Kent West]

At 07:57 PM 2/12/1999 -0500, [EMAIL PROTECTED] wrote:
>I'm trying LINUX for the first time, and was attracted to the straight to
>the point FAQ on installing this program on low memory machines.
>
>The machine is an old Compaq 4/25 Contura laptop with 4 Megs of ram - 130
>Meg of ram.  I simply want to make it a machine that can access the net
>with a browser like Netscape - or something similar.
>
>I have downloaded the files recommended to their own directories (e.g.
>base14-1.exe) - but have only successfully extracted the first two image
>disks.  I infer from the documenation that 10 in total exist.
>
>After trying to create the third - I get a disk that shows now files in
>Windows 3.1 filemanager.
>
>
>Am I proceeding correctly - or is there something I'm omitting with
>respect to these image disks.
>
>Thanks,
>
>Jim Mastracco
>*
>
>FINDINGS - On The Road  
>
>*
>*

The file "base14-1.exe" should be "base14-1.bin". I don't know if you made
a typo in your message or if you renamed the file during the download.

Assuming you're downloading to a DOS/Windows box, you'll need to download
several files like this (base14-2.bin, etc, drv1440.bin, resc1440.bin) and
you'll need rawrite.exe (or better, rawrite2.exe). Then at a DOS prompt,
you'll use rawrite to copy the disk image to a floppy. IIRC, rawrite2 will
prompt you for the image name (ie base14-1.bin) and the destination (ie
A:), whereas rawrite will expect this info on the command line.

MAKE SURE you have good quality floppies, and if you have any trouble
reading one of them during the install, use another floppy and remake the
image (and again and again until you get one that works - I've known people
who have had to make four attempts before getting a floppy that works -
floppies are notorious for failing on a linux install).

Once you've got all the floppies made (7 I think), pop the first one in and
reboot. This should start the install process.

I would not expect the floppies to be readable by Win3.1's File Mangler (or
any DOS/Win utilities); I believe the floppies are in a special format, but
I'm not certain on this.

Although you can run Linux on a 4 MB machine, you probably won't be able to
run a graphical web browser (like Netscape) on it, because to my knowledge
there are no graphical web browswers for Linux that will run without X
Windows (I wish someone would develop one). By the time you get X and a
browser installed, the machine would perform at less than a crawl. However,
you can run lynx, which is a text-mode browser. It's very limiting in these
days of the www, but it is at least a partial solution.

creating boot disks

[mastracco]

I'm trying LINUX for the first time, and was attracted to the straight to
the point FAQ on installing this program on low memory machines.

The machine is an old Compaq 4/25 Contura laptop with 4 Megs of ram - 130
Meg of ram.  I simply want to make it a machine that can access the net
with a browser like Netscape - or something similar.

I have downloaded the files recommended to their own directories (e.g.
base14-1.exe) - but have only successfully extracted the first two image
disks.  I infer from the documenation that 10 in total exist.

After trying to create the third - I get a disk that shows now files in
Windows 3.1 filemanager.


Am I proceeding correctly - or is there something I'm omitting with
respect to these image disks.

Thanks,

Jim Mastracco
*

FINDINGS - On The Road  

*
*

___
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
or call Juno at (800) 654-JUNO [654-5866]

Re: Hamm Boot Disks

[Norbert Veber]

On Fri, Apr 17, 1998 at 11:44:44AM -0700, [EMAIL PROTECTED] wrote:
> 
>   Is there a semi stable set of hamm boot-disks out yet?  About a
> month ago I tried them and ran into problems with missing perl libraries
> on my run of dselect.

the latest ones (april 14 I think) work fine


pgpfxeBoAhEip.pgp
Description: PGP signature

Hamm Boot Disks

[mike]

Is there a semi stable set of hamm boot-disks out yet?  About a
month ago I tried them and ran into problems with missing perl libraries
on my run of dselect.
TIA,
mike...

Micro$oft, what do you want to spend today?


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

[SOLVED]Re: Create Special Boot Disks??

[Jay Barbee]

Thanks to everybody who replied... you all helped!  I got the new 
rescue disk working...

As the "readme.txt" says on the rescue disk I built a kernel with 
ramdisk and initrd along with the IDE,  SCSI, and filesystem stuff I 
needed.  I did a 'make bzImage' and renamed that kernel image 
"Linux".  I copied this kernel to the floppy, overwriting the other 
one.

Next before I mount the floppy and run /mnt/rdev.sh, I needed to not 
only create the device /dev/ram0 (using /dev/MAKEDEV ram0) I had to 
make the ramdisk module.  After these two things were done, I mounted 
the floppy, ran /mnt/rdev.sh, and unmounted the floppy.

It now boots fine... I do not know if this will solve my problem, but 
I can tweak the kernel later, I know how to create a custom kernel on 
my rescuedisk...

It all seems almost simple in hind sight... !  Thanks again 
all!

--Jay Barbee



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

Re: Create Special Boot Disks??

[finn]

On Wed, 25 Mar 1998, Jay Barbee wrote:

[ snip ]
: The kernel loads fine, but chokes when it gets to the RAMDISK.  Here 
: is the final error:
: 
: RAMDISK: Compressed image found at block 0
: VFS: Mounted root (minix filesystem).
: VFS: Cannot open root device 08:11
: Kernel panic: VFS: Unable to mount root fs on 08:11
: 
: ...I assume it has something to do with my linux box not having 
: /dev/ram0 when running the ./rdev.sh on the rescuedisk.
: 
: Any ideas?

A shot in the dark ... perhaps you need to create /dev/ram0

kepler:~ $ ll /dev/ram0
brw-rw   1 root disk   1,   0 May 19  1997 /dev/ram0

I think the command '/dev/MAKEDEV ramdisk' will do what you want (I
haven't tried it, though, just glanced at the /etc/devinfo file).

--
Nathan Norman
MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD  57104
mailto://[EMAIL PROTECTED]   http://www.midco.net
finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9)



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

Re: Create Special Boot Disks??

[Nils Rennebarth]

On Wed, Mar 25, 1998 at 10:29:40AM +, Jay Barbee wrote:
> I created the image with module support but with out any modules 
> (everything was built into the kernel).  Image was created with 'make 
> bzImage', then I copied bzImage to "linux" and then copied it onto a 
> rescuedisk.  I mounted the new rescue disk on a currently working 
> system and ran /mnt/rdev.sh.  I did get an error from the last line 
> of this script ("rdev /mnt/linux /dev/ram0") which told me 
> "/dev/ram0: No such file or directory".
It appears you need ramdisk support when you run this script too.
Could you try this?

Nils

--
*-*
| Quotes from the net:  L> Linus Torvalds, W> Winfried Truemper   |
| L>this is the special easter release of linux, more mundanely called 1.3.84 |
| W>Umh, oh. What do you mean by "special easter release"?. Will it quit  |
* W>working today and rise on easter? *


pgpAP79RhDtKN.pgp
Description: PGP signature

Re: Create Special Boot Disks??

[Jay Barbee]

> On Tue, 24 Mar 1998, Jay Barbee wrote:
> 
> > If the stock 1.3.1 Rescue disk will not boot up a system with an 
> > Adaptec SCSI controller, do I have any other options for getting this 
> > to work?  Are there special rescue disks out there for this sort of 
> > thing?
> 
> The boot (rescue) disks use syslinux to boot the kernel.  The
> instructions on the disk say you can put any kernel on the disk and name
> it linux.  Then you can use the disk to boot. I had trouble with the
> modules, so you should put all the modules you are going to need for
> install (in my case, I had to have SCSI CD rom support). Then ask on
> this list, they KNOW and WILL help.
> 
> Please look at the rescue disk on an msdos machine and confirm this. I
> had to do this when I booted my system at home with AHA 1542, then later
> AHA 2840 SCSI controllers, but that was back in the Deb 0.93 and 1.1
> days. 

Thanks David for the reply...

I did as instructed, I built a 2.0.33 kernel with all the Adaptec
Controllers and IDE support, I also put in Ramdissk, and initrd as
well as proc, msdos, fat, iso9660, minix, ext2fs, elf, a.out. 

I created the image with module support but with out any modules 
(everything was built into the kernel).  Image was created with 'make 
bzImage', then I copied bzImage to "linux" and then copied it onto a 
rescuedisk.  I mounted the new rescue disk on a currently working 
system and ran /mnt/rdev.sh.  I did get an error from the last line 
of this script ("rdev /mnt/linux /dev/ram0") which told me 
"/dev/ram0: No such file or directory".

The kernel loads fine, but chokes when it gets to the RAMDISK.  Here 
is the final error:

RAMDISK: Compressed image found at block 0
VFS: Mounted root (minix filesystem).
VFS: Cannot open root device 08:11
Kernel panic: VFS: Unable to mount root fs on 08:11

...I assume it has something to do with my linux box not having 
/dev/ram0 when running the ./rdev.sh on the rescuedisk.

Any ideas?

--Jay Barbee


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

Re: Create Special Boot Disks??

[DAVID B. TEAGUE]

On Tue, 24 Mar 1998, Jay Barbee wrote:

> If the stock 1.3.1 Rescue disk will not boot up a system with an 
> Adaptec SCSI controller, do I have any other options for getting this 
> to work?  Are there special rescue disks out there for this sort of 
> thing?

Jay

I see this is your second request. Nobody has answered this, so I'll
hazard a response. If I'm in error, I know someone will correct me ;) 

The boot (rescue) disks use syslinux to boot the kernel.  The
instructions on the disk say you can put any kernel on the disk and name
it linux.  Then you can use the disk to boot. I had trouble with the
modules, so you should put all the modules you are going to need for
install (in my case, I had to have SCSI CD rom support). Then ask on
this list, they KNOW and WILL help.

Please look at the rescue disk on an msdos machine and confirm this. I
had to do this when I booted my system at home with AHA 1542, then later
AHA 2840 SCSI controllers, but that was back in the Deb 0.93 and 1.1
days. 

Lots of luck.

--David

---
   LINUX: the FREE 32 bit OS for [3456]86 PC's available NOW!
David B Teague | Ask me how user interface copyrights & software
[EMAIL PROTECTED] | patents make programing a dangerous business. 

spy counter-intelligence wild porno sex gold bullion Soviet Bosnia 
clipper National Security Council explosion Treasury terrorist Delta 



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

Create Special Boot Disks??

[Jay Barbee]

If the stock 1.3.1 Rescue disk will not boot up a system with an 
Adaptec SCSI controller, do I have any other options for getting this 
to work?  Are there special rescue disks out there for this sort of 
thing?

Thanks,
--Jay Barbee
[EMAIL PROTECTED]


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

Re: debian root boot disks

[dg]

On Wed, 4 Mar 1998, Ronald James McEachern wrote:

> can you direct me to detailed instructions on exact commands and files
> needed to install linux debian on a 1 gig dos partition?

First of all - my two cents - DON'T (in other words DO NOT) install linux on
a DOS partition (which means, that you have to use UMSDOS as your root
fillsystem). You will not be happy with this solution. If you don't want to
re-partition your hard drive, go out and buy another. The 1.2 Gig drives are
cheap (because no one want's them anymore) out there.

Second - here are the URL's:

- Debian GNU/Linux Home Page
http://www.debian.org/

- Debian GNU/Linux User Documentation
http://www.debian.org/doc/

- Debian GNU/Linux Installation Guide (as HTML Document)
ftp://ftp.us.debian.org/debian/stable/disks-i386/current/install.html

I hope this will help you.

Bye

Daniel

--
Daniel Gross eMail: [EMAIL PROTECTED]
Hollarstrasse 2 [EMAIL PROTECTED]
D-85053 Ingolstadt, Germany
--

Collaboration, n.:
A literary partnership based on the false assumption that the
other fellow can spell.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

debian root boot disks

[Ronald James McEachern]

can you direct me to detailed instructions on exact commands and files
needed to install linux debian on a 1 gig dos partition?


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Special boot disks...

[Sébastien Phélep]

Hi,

I'm working as a technician/system/network admin in a french college.
We use Debian as our Linux distributions, with a dual PPro machine as
file/printing/mail server and router.

My problem is that the former installation of Debian on our 35 PCs was
done by someone who was not very used to Un*x, and he installed Debian
in a quite bad way:(.

Last week, there won't be any students working here (holidays... but not
for me yet !), and we have decided to restart a complete installation of
Debian on our machines and servers. As you can imagine, one week is not
enough to create a good server configuration (I expect to last one or
two days with it) and a good client configuration (one day to make it
real clean), and then hardcopy the client disk onto the 34 others
clients with dd...

What I'm looking for is a disk set with which I could start Linux
directly from a diskette, create my partitions on the hard disk,
activate the network and download my sample configuration via NFS (I
hope you can figure out why the Linux partition cannot be used before:
conflicts with libs and utilities). I would then have only to change the
settings for the network configuration of the client PC so-installed.
As I'm in a hurry (and have a lot of work to finish this week), I really
don't have the time to create my own boot/root disks for it (given that
I had not needed these before and by the way don't know how it
works:-((().

If someone has already done such a thing, it would be a great help for
me...
Note: I had a look to the BootDisk-HOWTO, created a boot disk that fit
our configurations and waits for a ramdisk. In fact what I need is the
correct ramdisk, and a little bit of explaination about the way it
works.

Thanks a lot,
Seb.

---
Sebastien Phelep - [EMAIL PROTECTED]


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Building Your own Boot Disks

[Nils Rennebarth]

-BEGIN PGP SIGNED MESSAGE-

On Thu, 21 Aug 1997, Timm Gleason wrote:
> I cannot get the modules to install.
>
>"modprobe: error reading ELF header: no such file or directory"
The new modprobe will complain if informative files like
 BLOCK_MODULES
and the like are contained in /lib/modules/2.x.x/

Throw those out and your modules.tgz will be accepted.
(To make those automatically upgrade your 'kernel-package')


Nils

- -- 
 \  /| Nils Rennebarth
--* WINDOWS 42 *--   | Schillerstr. 61 
 /  \| 37083 Göttingen
 | ++49-551-71626
   Micro$oft's final answer  | http://www.nus.de/~nils

-BEGIN PGP SIGNATURE-
Version: 2.6.3i
Charset: noconv

iQB1AwUBNAKmXFptA0IhBm0NAQGz/QL8DH/IeslLW5+0MEKDdoB/rKZB4V6KkIJQ
dMMxNJmARzSC8mnC5Il8NiB1FgZr2yILg5QG2m2rDY/o2iteuzlbLRGKSzSc/ui8
R6nHDZrPxUXi7fH5iNjLECkAXfyiI9Vw
=oxZX
-END PGP SIGNATURE-


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Building Your own Boot Disks

[Craig Sanders]

On Thu, 21 Aug 1997, Paul Wade wrote:

> On Fri, 22 Aug 1997, Craig Sanders wrote:
> 
> > imo, everyone should compile their own kernel - the boot/rescue floppy
> > is good to install a system with, but a linux box really should have a
> > kernel compiled especially for itwith only the drivers that it needs
> > compiled in (or as modules), no more and no less.
> 
> Often true, but it is better to use kernel-package which builds a Debian
> kernel-image package for this. 

yes. "...compile their own kernel" includes the possibility of using
make-kpkg. in fact, earlier in my message that is exactly what i said i
had done.

my point was that if you want to get the most out of your linux box then
compiling your own kernel is essential.

it doesn't really matter whether that is done with the old "make zlilo ;
make modules ; make modules_install" (or whatever) sequence of commands,
or whether it's done with kernel-package. i happen to think that
kernel-package is much more convenient. some people think otherwise. big
deal, it doesn't matter which way it's done.


> One great reason is that you can build these packages on a machine
> that has all the tools and compiles fast. The resulting .deb file is
> easily installed with dpkg and will take care or making the hard disk
> boot the new kernel (while preserving the previous one) and creating a
> boot floppy.

yes, kernel-package is a great tool.

craig

--
craig sanders
networking consultant  Available for casual or contract
temporary autonomous zone  system administration tasks.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Building Your own Boot Disks

[Timm Gleason]

On Thu, 21 Aug 97 16:51 PDT, Bruce Perens <[EMAIL PROTECTED]> wrote:

>From: [EMAIL PROTECTED] (Timm Gleason)
>> Now not wanting to go backward, especially due to the
>> major modifications done to the kernel we are using
>
>Is that the BESS Internet filter? I hope your product still lets you read
>the list, after the language we've been using on debian-user today :-)
>15-20 a month and Debian in every one? Cool!
>
Yes, we use Linux servers for all of our on-site and redirect proxy
servers. We have been using Debian from the beginning because of the
amount of stability and support available.

>If you're developing big changes to the kernel, please try to contribute
>them back into the main kernel source thread.
>
Most of the hacks into the kernel involve max file descriptors and
inodes to allow for greater simultaneous connections. Almost all of
the modifications we have made the real work has been done by someone
else out there. We can get near 1500 simultaneous connections with the
kernel we currently use.

>> like to know if there is any definitive source of information on
>> building installation disks. The new system that loads base off of a
>> CD is great, but with the modified drivers and kernel, I need to know
>> more about these disks.
>
>Sure. You will need two packages: kernel-package and boot-floppies.
>Kernel-package provides the scripts to build a Debian package from
>your custom kernel and calling them from the command line is trivial.
>Boot-floppies provides the scripts to build the boot floppies, and you
>can easily modify that or just change the packages it installs. You will
>also need a complete copy of the Debian "stable" archive plus your
>modifications, and you will need to read the man page for dpkg-scanpackages
>(in the dpkg-dev package) so that you can add your own packages to the
>"Packages" file for your own archive, so that dpkg and dselect will work with
>it.
>
>Once you've done that, you can install the debian-cd package and generate your
>own bootable CDs with your custom kernel if you wish.
>
Burn our own bootable CD's, wow that would be even better than what we
do now!

Timm Gleason
**
"Programming today is a race between software engineers striving to build 
bigger and better idiot-proof programs, and the Universe trying to produce 
bigger and better idiots. So far, the Universe is winning." - Rich Cook
**
Timm Gleason  --   [EMAIL PROTECTED]  --   [EMAIL PROTECTED]  --  
http://n2h2.com/
N2H2, Creators of Bess -- 1301 Fifth Avenue, Suite 1501--Seattle, WA 98101
**


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Building Your own Boot Disks

[Paul Wade]

On Fri, 22 Aug 1997, Craig Sanders wrote:

> imo, everyone should compile their own kernel - the boot/rescue floppy
> is good to install a system with, but a linux box really should have a
> kernel compiled especially for itwith only the drivers that it needs
> compiled in (or as modules), no more and no less.

Often true, but it is better to use kernel-package which builds a Debian
kernel-image package for this. One great reason is that you can build
these packages on a machine that has all the tools and compiles fast. The
resulting .deb file is easily installed with dpkg and will take care or
making the hard disk boot the new kernel (while preserving the previous
one) and creating a boot floppy.

Manoj even helped me get a shell script going that will rebuild several
custom kernels at a time. His kernel-package is a big help to me as I have
several old machines that would take a few hours to build a kernel on.

+--+
+ Paul Wade Greenbush Technologies Corporation +
+ mailto:[EMAIL PROTECTED]  http://www.greenbush.com/ +
+--+
+ http://www.greenbush.com/cds.html Now shipping version 1.3.? +
+--+


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Building Your own Boot Disks

[Bruce Perens]

From: [EMAIL PROTECTED] (Timm Gleason)
> Now not wanting to go backward, especially due to the
> major modifications done to the kernel we are using

Is that the BESS Internet filter? I hope your product still lets you read
the list, after the language we've been using on debian-user today :-)
15-20 a month and Debian in every one? Cool!

If you're developing big changes to the kernel, please try to contribute
them back into the main kernel source thread.

> like to know if there is any definitive source of information on
> building installation disks. The new system that loads base off of a
> CD is great, but with the modified drivers and kernel, I need to know
> more about these disks.

Sure. You will need two packages: kernel-package and boot-floppies.
Kernel-package provides the scripts to build a Debian package from
your custom kernel and calling them from the command line is trivial.
Boot-floppies provides the scripts to build the boot floppies, and you
can easily modify that or just change the packages it installs. You will
also need a complete copy of the Debian "stable" archive plus your
modifications, and you will need to read the man page for dpkg-scanpackages
(in the dpkg-dev package) so that you can add your own packages to the
"Packages" file for your own archive, so that dpkg and dselect will work with
it.

Once you've done that, you can install the debian-cd package and generate your
own bootable CDs with your custom kernel if you wish.

Thanks

Bruce
-- 
Can you get your operating system fixed when you need it?
Linux - the supportable operating system. http://www.debian.org/support.html
Bruce Perens K6BP   [EMAIL PROTECTED]   510-215-3502


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Building Your own Boot Disks

[Craig Sanders]

On Thu, 21 Aug 1997, Timm Gleason wrote:

> We build many, many Linux boxes (on order of 15 to 20 a month). We
> just received some new disk sets for Debian 1.3.1. We have been using
> 1.2 and kernel 2.0.30. The new disk set comes with the disk images
> having 2.0.29. Now not wanting to go backward, especially due to the
> major modifications done to the kernel we are using, I cannot build a
> boot disk and drivers disk that will do a good install.

up until a month or two ago, i was building about 5 debian boxes
per month.  I just used the boot disks to do the basic install, and
then used dpkg to install my custom compiled kernel (made using
kernel-package's make-kpkg command).

the procedure went something like this:

1. boot install floppy.  install base system, reboot, run dselect, etc.
2. ftp kernel-image-XXX_XXX.deb from another machine on my network.
3. if kernel image is same version as on the install boot/rescue disk 
   then "rm -rf /lib/modules/X.X.X"
4. dpkg -i kernel-image-XXX_XXX.deb

if my custom kernel is a different version to the one on the boot
floppy (usually is), then i do the following as well:

5. make a /vmlinuz.old symlink pointing to the old kernel.
6. edit lilo.conf.
7. run "lilo -t && lilo".

do this and you shouldn't need to mess about with making your own
boot/rescue and drivers disks.


imo, everyone should compile their own kernel - the boot/rescue floppy
is good to install a system with, but a linux box really should have a
kernel compiled especially for itwith only the drivers that it needs
compiled in (or as modules), no more and no less.



> The kernel, drivers and base all install fine, however, I cannot
> specify which modules I wish to use. The installation of them fails. I
> receive an error message as follows:
> 
> "modprobe: error reading ELF header: no such file or directory"

your modules.tgz may have the old (and now incompatible) *_MODULES text
files in the /lib/modules/X.X.X directory. try:

find /lib/modules -name "*_MODULES" 

if they are there, then delete them by typing:

find /lib/modules -name "*_MODULES" | xargs rm

if this solves the problem, then create a new modules.tgz based on this.


craig


--
craig sanders
networking consultant  Available for casual or contract
temporary autonomous zone  system administration tasks.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Building Your own Boot Disks

[Timm Gleason]

We build many, many Linux boxes (on order of 15 to 20 a month). We
just received some new disk sets for Debian 1.3.1. We have been using
1.2 and kernel 2.0.30. The new disk set comes with the disk images
having 2.0.29. Now not wanting to go backward, especially due to the
major modifications done to the kernel we are using, I cannot build a
boot disk and drivers disk that will do a good install.

First, I have changed the kernel out on the 1.3.1 boot/rescue disk and
ran rdev.sh on it. I replaced the sys_map.gz  and edited the
install.sh so that VERSION=2.0.30.

I replace the modules.tgz on the drivers disk with a modules.tgz that
contains an updated tulip driver and all other modules have been
compiled under 2.0.30.

In the past this is all that i have had to do to get the disks
working, now with this new version of the Debian installer, I cannot
get the modules to install.

The kernel, drivers and base all install fine, however, I cannot
specify which modules I wish to use. The installation of them fails. I
receive an error message as follows:

"modprobe: error reading ELF header: no such file or directory"

While I have managed to klop something together that works, I would
like to know if there is any definitive source of information on
building installation disks. The new system that loads base off of a
CD is great, but with the modified drivers and kernel, I need to know
more about these disks.

Timm Gleason
Hardware Engineer
N2H2, Inc.
**
"Programming today is a race between software engineers striving to build 
bigger and better idiot-proof programs, and the Universe trying to produce 
bigger and better idiots. So far, the Universe is winning." - Rich Cook
**
Timm Gleason  --   [EMAIL PROTECTED]  --   [EMAIL PROTECTED]  --  
http://n2h2.com/
N2H2, Creators of Bess -- 1301 Fifth Avenue, Suite 1501--Seattle, WA 98101
**


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: 'Frozen' boot disks

[Richard L Shepherd]

On Sun, 13 Apr 1997, Paul Wade wrote:

> The reason I put this copy up was for testing. For the first round of
> testing, people were picking them up from sites that only had modem
> bandwidth. Yes, ftp.debian.org is the authoritative source. If you want to
> play with the new toys before the store opens, you can pick them up at my
> site.

OK, that's cool then.  I have no problems with that.  I'll just keep doing
what I am.  I'm glad to have that clarified ;-)

8<--->8
Richard Shepherd ([EMAIL PROTECTED])
8<--->8

Re: 'Frozen' boot disks

[Paul Wade]

The reason I put this copy up was for testing. For the first round of
testing, people were picking them up from sites that only had modem
bandwidth. Yes, ftp.debian.org is the authoritative source. If you want to
play with the new toys before the store opens, you can pick them up at my
site.

On Mon, 14 Apr 1997, Richard L Shepherd wrote:

> On Sat, 12 Apr 1997, Paul Wade wrote:
> > 
> > 4/6/97 I put a copy at ftp.greenbush.com, look in /pub/bodisks. The files
> > are dated by time of transfer, but they are the 4/4 set.
> > 
> > > I have the same problem.  I had thought it may be because I mirror a
> > > mirror (which in turn may not directly mirror ftp.debian.org) and so my
> > > mirror was effectively a few days behind.  However I just checked on
> > > ftp.debian.org and it really is empty so
> > > 
> > > Where are they then?
> 
> So my next question then is: is not ftp.debian.org the authoritative
> source for the Debian Distribution?  i.e. I seek to maintain a mirror of
> ftp.debian.org thinking that this will ensure I have an up-to-date Debian
> Distribution for my linux fans.  Am I doing the right thing?
> 
> 8<--->8
> Richard Shepherd ([EMAIL PROTECTED])
> 8<--->8
> 

+--+
+ Paul Wade Greenbush Technologies Corporation +
+ mailto:[EMAIL PROTECTED]  http://www.greenbush.com/ +
+--+
+ http://www.wtop.com/What does W.T.O.P. mean? +
+--+

Re: 'Frozen' boot disks

[Martin Schulze]

On Apr 14, Richard L Shepherd wrote

> > 4/6/97 I put a copy at ftp.greenbush.com, look in /pub/bodisks. The files
> > are dated by time of transfer, but they are the 4/4 set.
> > 
> > > I have the same problem.  I had thought it may be because I mirror a
> > > mirror (which in turn may not directly mirror ftp.debian.org) and so my
> > > mirror was effectively a few days behind.  However I just checked on
> > > ftp.debian.org and it really is empty so
> > > 
> > > Where are they then?
> 
> So my next question then is: is not ftp.debian.org the authoritative
> source for the Debian Distribution?  i.e. I seek to maintain a mirror of
> ftp.debian.org thinking that this will ensure I have an up-to-date Debian
> Distribution for my linux fans.  Am I doing the right thing?

You're quite corerct.  ftp.debian.org is the authoritative Debian
mirror for users. (for developers and ftp.debian.org there is also
master.debian.org, but that doesn't matter).  Unfortunately at this
moment our incoming directory isn't processed.  I believe that some
organisatoric (sp?) issues have to be finished first.

Please mirror ftp.debian.org or one of its mirrors.

Sometimes ftp.debian.org is one or two days behind master.debian.org.
I don't know why - this shouldn't happen...

Regards,

Joey


-- 
  / Martin Schulze * Debian GNU/Linux Developer * [EMAIL PROTECTED] /
 / http://www.debian.org/  http://home.pages.de/~joey/

Re: 'Frozen' boot disks

[Richard L Shepherd]

On Sat, 12 Apr 1997, Paul Wade wrote:
> 
> 4/6/97 I put a copy at ftp.greenbush.com, look in /pub/bodisks. The files
> are dated by time of transfer, but they are the 4/4 set.
> 
> > I have the same problem.  I had thought it may be because I mirror a
> > mirror (which in turn may not directly mirror ftp.debian.org) and so my
> > mirror was effectively a few days behind.  However I just checked on
> > ftp.debian.org and it really is empty so
> > 
> > Where are they then?

So my next question then is: is not ftp.debian.org the authoritative
source for the Debian Distribution?  i.e. I seek to maintain a mirror of
ftp.debian.org thinking that this will ensure I have an up-to-date Debian
Distribution for my linux fans.  Am I doing the right thing?

8<--->8
Richard Shepherd ([EMAIL PROTECTED])
8<--->8

Re: 'Frozen' boot disks

[jacek]

Use ftpsearch to find the Disks...

Just type in 1997-04-04 and let it search...and there they are..!!

Hope this helps...Jacek

Re: 'Frozen' boot disks

[Brandon Mitchell]

I put a copy on my linux box.  I got it directly from Dale's computer,
which has a slow link.  I've been working on configuring everything, so if
there is something wrong, feel free to let me know.

ftp://128.239.205.139/pub/bhmit1/

It's a 100M ethernet, so you'll get it quick, but it's turned off at
night.  I'll leave it on later if someone is downloading though.

Enjoy,
Brandon

-
Brandon Mitchell E-mail: [EMAIL PROTECTED]
  Homepage: http://www.geocities.com/SiliconValley/7877/home.html
  PGP Key: finger [EMAIL PROTECTED]   

"We all know Linux is great...it does infinite loops in 5 seconds."
--Linus Torvalds

On Sun, 13 Apr 1997, Richard L Shepherd wrote:

> > Is anyone else having trouble finding the disks for 1.3?  I'd appreciate 
> > any 
> > pointers.  The 'bo/disks-i386/1997-04-04/' directory seems to be empty.

Re: 'Frozen' boot disks

[Paul Wade]

4/6/97 I put a copy at ftp.greenbush.com, look in /pub/bodisks. The files
are dated by time of transfer, but they are the 4/4 set.

On Sun, 13 Apr 1997, Richard L Shepherd wrote:

> On Sat, 12 Apr 1997, Lamar Folsom wrote:
> 
> > Is anyone else having trouble finding the disks for 1.3?  I'd appreciate 
> > any 
> > pointers.  The 'bo/disks-i386/1997-04-04/' directory seems to be empty.
> 
> I have the same problem.  I had thought it may be because I mirror a
> mirror (which in turn may not directly mirror ftp.debian.org) and so my
> mirror was effectively a few days behind.  However I just checked on
> ftp.debian.org and it really is empty so
> 
> Where are they then?
> 
> 8<--->8
> Richard Shepherd ([EMAIL PROTECTED])
> 8<--->8
> 

+--+
+ Paul Wade Greenbush Technologies Corporation +
+ mailto:[EMAIL PROTECTED]  http://www.greenbush.com/ +
+--+
+ http://www.wtop.com/What does W.T.O.P. mean? +
+--+

Re: 'Frozen' boot disks

[Richard L Shepherd]

On Sat, 12 Apr 1997, Lamar Folsom wrote:

> Is anyone else having trouble finding the disks for 1.3?  I'd appreciate any 
> pointers.  The 'bo/disks-i386/1997-04-04/' directory seems to be empty.

I have the same problem.  I had thought it may be because I mirror a
mirror (which in turn may not directly mirror ftp.debian.org) and so my
mirror was effectively a few days behind.  However I just checked on
ftp.debian.org and it really is empty so

Where are they then?

8<--->8
Richard Shepherd ([EMAIL PROTECTED])
8<--->8

'Frozen' boot disks

[Lamar Folsom]

Is anyone else having trouble finding the disks for 1.3?  I'd appreciate any 
pointers.  The 'bo/disks-i386/1997-04-04/' directory seems to be empty.

TIA
-- 
Lamar Folsom
[EMAIL PROTECTED]
http://www.cs.uidaho.edu/~fols9488
"Life is wasted on the living."  - The Master

Help Tecra 720CDT and fixed boot disks...

[Robert Nicholson]

Well it looks like we've got a boot disk problem again.

I'm trying to boot from my rescue disk from the rex-fixed distribution
from say last Thursday and even though I used this to install Debian on
my desktop successfully. Something is very wrong with the Tecra.

Basically it gets all the way through to the configuration of the
network and I've selected _no_ because I'll use Dave Hinds PCMCIA_CS
stuff. 

Anyway, it's constantly flashing.

/tmp/dinstall.11 26 Syntax Error: Unterminated Quoted String.

This I guess it what will happen whenever you say no to are you
connected to a network.

Anybody?


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]

Re: ncftp. Current boot disks

[Bruce Perens]

From: Ioannis Tambouras <[EMAIL PROTECTED]>
> The symbolic link ftp://ftp.debian.org/debian/rex/disks-i386/current
> is pointing at 1996-11-28/, instead of 1996-12-7/. I think that is
> incorrect.

Once the mirror is up to date it will point at 1996-12-8. Note that's 8,
not 7. The 1996-12-7 disks were seriously broken.


Bruce
--
Bruce Perens K6BP   [EMAIL PROTECTED]
Finger [EMAIL PROTECTED] for PGP public key.
PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6  1F 89 6A 76 95 24 87 B3 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]

Re: ncftp. Current boot disks

[Christian Hudon]

On Sun, 8 Dec 1996, Ioannis Tambouras wrote:

> 
>   I need clarification on two issues:
[nsip]
> 
>   * I need to file a bug report for ncftp-2.4.2: the get -R command is not
> excecuted, I only get the prompt for the next command.
> Few days ago I was looking at a debian bug list. Now that I need to
> check if this bug is reported, I cannot find it. The debian-faq.txt
> directed me to a debian-bugs/ archieve, but there was nothing there!
> Where can I browse for previous bug reports?

Point your favorite web browser to http://www.debian.org/ . One of the
items in the list is the web version of the bugs archive.

  Christian



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]

ncftp. Current boot disks

[Ioannis Tambouras]

  I need clarification on two issues:

  * The symbolic link ftp://ftp.debian.org/debian/rex/disks-i386/current
is pointing at 1996-11-28/, instead of 1996-12-7/. I think that is
incorrect.

  * I need to file a bug report for ncftp-2.4.2: the get -R command is not
excecuted, I only get the prompt for the next command.
Few days ago I was looking at a debian bug list. Now that I need to
check if this bug is reported, I cannot find it. The debian-faq.txt
directed me to a debian-bugs/ archieve, but there was nothing there!
Where can I browse for previous bug reports?


Ioannis Tambouras
[EMAIL PROTECTED]
PGP 512/D042DD45, West Palm Beach, Florida


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]

Re: special boot disks

[Lazaro . Salem]

 It is true. only a brief description is given. but you may want to read 
 the config files with which the special kernels were created. They are in 
 the same directory as the special-kernel packages.
 I also remember reading some (brief) info in the FAQ (not too much)
 lazaro <[EMAIL PROTECTED]>


__ Reply Separator _
Subject: special boot disks
Author:  debian-user@lists.debian.org at cclink
Date:23.09.96 19:12


In preparing for debian 1.1 installation I find that the standard installation 
boot disk does not support the hardware I have. I have found a variety of 
special boot disks in /buzz/special-kernels, but no description of the 
hardware configurations each supports. Where on the debian ftp site will I 
find such descriptions?
Thanks for any help.
Richard
 
 

special boot disks

[Richard Sevenich]

In preparing for debian 1.1 installation I find that the standard installation
boot disk does not support the hardware I have. I have found a variety of
special boot disks in /buzz/special-kernels, but no description of the
hardware configurations each supports. Where on the debian ftp site will I
find such descriptions?
Thanks for any help.
Richard

Re: Custom installation boot disks?

[Paul Christenson]

On Tue, 17 Sep 1996, Bruce Perens wrote:

> If I'm not mistaken, the generic kernel will install on a 2940. It's the
> AIC7XXX series of chips, and aic7xxx.o is built into the generic kernel.

It does.  I was at the office and had the generic disk set with me.  Said
'what the heck' and found it works.
 
> It's always best from a performance standpoint to create your own custom
> kernel.

I always do.  However, after installing, I found that the 'ne' module
would hang the system when trying to find my PCI card (io=0x6200).  Since
the kernel installation package does not come on my CD (Infomagic Linux
Developer's Resource, 9/96 Debian 1.1.4), I had to recompile the kernel
the old way, but with NE2000 support built in.  That works fine.

Now that I have my network back, I can ftp the modules needed.

Thanks to all for their help.

Re: Custom installation boot disks?

[Bruce Perens]

If I'm not mistaken, the generic kernel will install on a 2940. It's the
AIC7XXX series of chips, and aic7xxx.o is built into the generic kernel.

It's always best from a performance standpoint to create your own custom
kernel. If you can allocate the space to install the kernel sources and
the tools necessary to build them, go ahead and do so. The generic kernel
is built for the '386, and has a number of linked-in drivers that you don't
need, and probably has the wrong IP options selected for your application.

You should be able to get the system running well before Thursday.

Thanks

Bruce Perens

Re: Custom installation boot disks?

[Susan G. Kleinmann]

Hi Paul --

You asked:
> I need to create a custom installation boot disk to install Debian on a
> system at work.  This is a custom server, with a SCSI main drive on an
> Adaptec 2940UW controller.  Once I get the main drive supported and the
> base installed, I can finish it from there.
> 
> I've heard here that the custom kernels available do not work.  Can they
> be made to work, or would creating my own be better?  (I have a working
> Debian machine at home.)  Where are the docs hiding to create my own
> install boot disks?
> 

If I were you, I'd just make my own.
Here's what to do:
Fetch the latest kernel.  I use tsx-11.mit.edu, and get the latest
version from /pub/linux/sources/system/v2.0
I think the latest version is 2.0.20.

If you unzip and untar the kernel into, say, /usr/local/src/linux-2.0.20,
then cd to that directory.

Install the Debian package kernel-package.

(Even though you're not supposed to, I then) execute make config.

Execute:  make-kpkg kernel_image
This will make a .deb file which includes the kernel and modules.

Install the Debian package boot-floppies (which is in the devel section).

Then run bootdisk.sh.  It takes three arguments:
-- the full path name of the .deb file containing your kernel
-- the device name for your floppy, e.g., /dev/fd0
-- the number of blocks on your floppy, e.g., 1440

If you forget, just execute bootdisk.sh with no arguments, and then
you'll get reminded from a Usage statement.

There are scripts in there to make a rootdisk and basedisks as well, but
you can just as easily use the rootdisk and basedisks provided at any
Debian archive.

HTH,
Susan Kleinmann

Custom installation boot disks?

[Paul Christenson \[N3EOP\]]

I need to create a custom installation boot disk to install Debian on a
system at work.  This is a custom server, with a SCSI main drive on an
Adaptec 2940UW controller.  Once I get the main drive supported and the
base installed, I can finish it from there.

I've heard here that the custom kernels available do not work.  Can they
be made to work, or would creating my own be better?  (I have a working
Debian machine at home.)  Where are the docs hiding to create my own
install boot disks?

Speed is important here; I have to have this machine operational by
Thursday morning.

-- 
 +---+ .
 | Technical Support Engineer, Cyclades Corporation  |
 | 800/88-CYCLADES (882-9252) or (510)770-9727, x258 |
 | Maker of High Performance Multiport Serial Cards  |
 +---+

Re: Problems with 11-6 boot disks

[Bruce Perens]

> > - /etc/kbd/config has CONSOLE=
> >   which results in a symlink /console -> /dev/console which sucks.
> >   Putting 'CONSOLE=tty0' fixes it. Then again, if you run
> >   '/usr/lib/kbd/config' it's all wrong again (taking the defaults).
> > 
> I also have this problem over and over. On top of that it prevents the correct
> keyboard map to be loaded. So I have to guess until I get the right keyboard
> again and can then proceed to correct this.

Fixed in June 16 floppy set.

Bruce

Re: Problems with 11-6 boot disks

[Bruce Perens]

> ae adds a ^M at the end of newly inserted lines.

Fixed in June 16 floppy set. Install the new ae package if you still
need ae.

> Whoa! "Configuring serial portsWild interrupts found: 7 15"
> Please don't do this to me! That's my GUS, also my printer, and my
> secondary IDE controller (which, at the moment, has no active IDE
> devices online). /etc/rc.boot/0serial loads up loads of crap, trying
> to configure cua0 - cua32 or similar...

Uh-oh. That is indeed very optimistic. Please file a bug report with
debian-bugs.

> Wouldn't it be better if the serial module was included by default?

Yes, probably.

> Installation via dftp is broken.. "can't find Carp.pm" (it's referenced
> from vars.pm) (dselect / A / ftp)

Fixed in June 16 boot set.

> I don't have a gateway on my single-computer network (I do have an
> Ethernet card, yes, don't ask). /etc/init.d/networks puts a line:
>   GATEWAY=none
> but then adds a route to it, which results in a hostname lookup
> failure during boot.

Oops. Please file a bug report with debian-bugs.

> /etc/kbd/config has CONSOLE=

Fixed in June 16 boot set.

> Ok.. for the rest: it's smooth. It looks neat - much more neat than
> Slackware, or even RedHat.

> Two more things I'd Like To See (tm):
> - Ask if you really want to mkfs the partition

You mean "mkfs", or the installation floppy menu system? The menu system
does ask for confirmation.

Bruce