@anw: "Trying to install sarge (woody doesn't have the support for my intel 1000M
ethernet card), plain vanilla x86 hardware: Linux system was previously
installed.  I've tried four or five different releases of sarge, with
different dates, and searched email archives and Google and found (almost)
nothing.  The one thing I found mentioned this error, and was a bug report
that said this was supposed to be fixed, but in all of the releases, up
through September, I'm still getting this, and evidently I'm the only one in
the world.  Someone, please help!!
TIA,
Allen
To UNSUBSCRIBE, email to <email_address> 
with a subject of "unsubscribe". Trouble? Contact <email_address>"
    @pecondon: "<quote>
FYI, you can mix and match Debian distributions and kernels. In particular,
you can install Woody and then upgrade to a kernel that includes support for
your internet card. 
In general, once you have a working installation of Debian, you can upgrade
piecemeal until you have a working version of Sid, *without* *being* *a*
*Debian* *guru*. How far you go from stable to bleeding edge is a matter of
taste and of meeting your requirements for new features vs. stability.
Because Sarge is also testing, versions of Sarge are not really versions, 
more like its current condition on this or that particular date. Sarge is
nearing release as the new 'stable' version of Debian. But, one of the 
last things that gets fixed in a proto-stable version is 'cold-turkey'
install. 
If you are sure that your problem is lack of support for your particular
ethernet card, try first installing Debian without that. Then you have
a functional base for getting that little detail. It may be worth your
while to scavenge an old junk etherenet card (that is supported) just to
get past this.
Also, look carefully at your options during the install process (F-
keys, etc.), it is possible to select different kernel versions during
the initial install.  This may get you what you need.
In general, the Debain way is to install Debian and then when you have
reasonable control over your machine, configure it as you like. 
(just my advice)
Paul E Condon           
<email_address>
To UNSUBSCRIBE, email to <email_address> 
with a subject of "unsubscribe". Trouble? Contact <email_address>"
    @jeremy: "<quote>
To be specific, the latest kernel available in Woody does not include
the drivers for the e1000.  If you have a spare NIC to throw in the
machine, you could install Woody, and then download the kernel source
from kernel.org.
What I did in the same situation was download the latest 2.4 kernel from
testing on a seperate box, burn it to a CD, and then `dpkg -i` on the
machine with the e1000.  When it asked for dependencies, I went back and
copyied those files onto the CD, and tried it again.  There ended up
being 10-12 .deb files to get everything installed.
Once you do that, you could stay with woody, or dist-upgrade to sarge.
Jeremy
To UNSUBSCRIBE, email to <email_address> 
with a subject of "unsubscribe". Trouble? Contact <email_address>"
    @anw: "Well, I didn't see this until after the last post.  I'll get in sync here in
a second!  And, thanks for the response.
	- <snip> -
<quote>
I think so...
I'm using an iso image called sarge-i386-netinst-newest.iso.  I assume this
is the net-install image you are refering to (?).
OK- hopefully, I won't have to go that far, but judging from the error I was
getting, I made the wild assumption that it was a pretty simple syntax error
in a script I could just fix real quick and move on (jafloc- "Just A Few
Lines Of Code" ;-)
I'm not seeing any hardware errors- just that eval syntax error on the
console 3 screen.  On console 1, the install screen, I only get a message
that "deboostrap program exited with an error (return value 2)".  I don't
suppose the fact I'm using logical volumes would affect this?  I *think* I
tried it without, and got the same thing.  What is debootstrap?
I am downloading these images, one at a time, from the earliest to the most
recent, in the hopes that one of them will work.
Thank you Paul.
To UNSUBSCRIBE, email to <email_address> 
with a subject of "unsubscribe". Trouble? Contact <email_address>"
    @pecondon: "<quote>
...
Try the most recent first. Progress at Debian is much better than a random walk!
Paul E Condon           
<email_address>
To UNSUBSCRIBE, email to <email_address> 
with a subject of "unsubscribe". Trouble? Contact <email_address>"
    @anw: "Right.  I guess I was doing them in the wrong order.  I have been dissecting
the install scripts all night (what fun ;>).  The first problem is that in a
function called download_release_indices in the file
/usr/lib/debootstrap/functions, there is a sequence like this:
TMPCOMPONENTS="$(sed -n 's/Components: *//p $reldest)"
for c in TMPCOMPONENTS do ;
	eval "
		case \"\$c\" in
		$USE_COMPONENTS)
			COMPONENTS=\"\$COMPONENTS \$c\"
			;;
		esac
	"
done
It is this eval statement that is bombing out saying it found the unexpected
new line, expected ")" (why it expected a parenthesis, I don't know; it
doesn't look like there are any unbalanced here, but that's what it said).
Anyway, he's obviously building a list of the components, which looks like
it can be things like "main", "contrib", etc.  The string in TMPCOMPONENTS
is "main contrib".  USE_COMPONENTS, set in the main script, debootstrap, is
empty.
So, just for grins, I just commented all that stuff out and set COMPONENTS
to "main".  That moved me right along, back into a function called
download_release (which calls the above function), until it gets to a
section where a variable called "details" is trying to be set, and that's
just awful.  First off, all the path variables, the source path $path and
the destination path, $pkgdest, evaluate to paths that don't even exist on
the CD or the installation ramdisk.  For example, $path, where the files on
the CD are supposed to be, evaluates to
dists/sarge/main/binary-i386/Packages, which doesn't exist.  However, a
dists/sarge/main/debian-installer/binary-i386/Packages *does* exist
(although neither nano nor more can read the Packages file, which is 8000+
bytes, so something is screwy there as well, maybe the inodes are screwed up
or something).  When I hardcode them to what it looks like it wants, the
$details variable winds up empty.  So, I think that somehow when I fixed the
original syntax error, setting that variable to just the value "main" must
not have been what it was looking for and must have had all these cascading
effects, because I don't think the installation script could be THAT buggy.
Tomorrow, I'll download the latest version, and if that doesn't work, start
with woody and upgrade.  I wish there was some documentation on all this.
If I have to start with woody and upgrade, where can I find my ethernet
driver, and where is the documentation on how to load it?
Thanks again,
Allen
<quote>
To UNSUBSCRIBE, email to <email_address> 
with a subject of "unsubscribe". Trouble? Contact <email_address>"
{'source': 'USENET', 'other_information': '{"reply_count": 5, "forum_name": "linux.debian.user.20141229.mbox"}', 'file': 'data/output/usenet-linux.debian.parquet'}