--- Begin Message ---
- Subject: 2.1.4 install disks seem to work for me on i386
- From: Various
- Date: Sat Jan 9 01:24:14 1999
Topics:
2.1.4 install disks seem to work for me on i386
Re: 2.1.4 install disks seem to work for me on i386
Re: 2.1.4 install disks seem to work for me on i386
----------------------------------------------------------------------
Date: Thu, 7 Jan 1999 00:19:20 -0500
From: Avery Pennarun <apenwarr@worldvisions.ca>
To: debian-boot@lists.debian.org
Subject: 2.1.4 install disks seem to work for me on i386
Message-ID: <[🔎] 19990107001920.C6699@worldvisions.ca>
Content-Type: text/plain; charset=us-ascii
Hi all,
I thought I would mention that I just installed slink over a cable modem
connection using only the files in the 2.1.4 disks-i386 directory, and it
worked great. One of the most painless Debian installations I've ever done
- - I guess we're making good progress.
A couple of minor problems I noticed. Probably you're aware of these
anyway, but I'll mention them while I'm here.
- cfdisk refused to run because the partition table on this (I think brand
new) drive was garbled. I ran normal fdisk (which you cleverly
included on the rootdisk -- thanks!) and deleted all four random
primary partitions, then went back to cfdisk and it was fine.
- I didn't choose the "make debian bootable directly from hard disk"
option. It didn't run lilo, which is what I wanted, but it didn't
even make /etc/lilo.conf, which was kind of surprising when I went
to install it later.
- I chose "Standard Workstation" for my package preselections, and it
wanted to install tetex and ALL THREE versions of emacs. I think
many people don't use latex anymore, but could we at least choose
only one emacs as the default?
http://www.worldvisions.ca/~apenwarr/popcon/results.editors.html
Seems to indicate that xemacs20 is the most popular, with emacs20
fairly close behind and emacs19 seriously losing.
- It didn't install XF86Setup, xterm, or twm by default.
- The setup program asking if I "run my own DNS server" told
/etc/resolv.conf to use 127.0.0.1, but it didn't install named right
away (of course). I had to fix /etc/resolv.conf to use an external
nameserver so apt could find http.us.debian.org to install the BIND
package!
As I said, all minor problems. It's nice to know that even as Debian seems
to become more and more unwieldy, the quality control just gets better.
Have fun,
Avery
- -
To UNSUBSCRIBE, email to debian-boot-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
------------------------------
Date: Thu, 07 Jan 1999 10:23:22 +0100
From: Stephane Bortzmeyer <bortzmeyer@debian.org>
To: Avery Pennarun <apenwarr@worldvisions.ca>
cc: debian-boot@lists.debian.org
Subject: Re: 2.1.4 install disks seem to work for me on i386
Message-Id: <[🔎] 199901070923.KAA11736@ludwigV.sources.org>
Content-Type: text/plain; charset=us-ascii
On Thursday 7 January 1999, at 0 h 19,
Avery Pennarun <apenwarr@worldvisions.ca> wrote:
> - cfdisk refused to run because the partition table on this (I think brand
> new) drive was garbled.
I had the same problem, and I had to fix it in the BIOS (I don't know why but
the geometry was set - wrongly - in the BIOS). cfdisk says nothing, it just
returns, too quickly to read the error messages. Bug #29153 reports a similar
problem and the workaround it suggests seems fine (in partition_config.c):
if ( NAME_ISEXE( "/sbin/cfdisk", &statbuf ) ) {
sprintf(prtbuf,"cfdisk %s",d->name);
} else {
sprintf(prtbuf,"fdisk %s",d->name);
}
boxSuspend();
status=system(prtbuf);
+ if (! status) {
+ boxAlarm ("Suitable message");
+ /* Try fdisk or may be cfdisk -z, but it seems dangerous */
+ }
boxResume();
> - I didn't choose the "make debian bootable directly from hard disk"
> option. It didn't run lilo, which is what I wanted, but it didn't
> even make /etc/lilo.conf, which was kind of surprising when I went
> to install it later.
Well, this can be discussed. The author of bug #31559 seems to disagree with
you.
> - I chose "Standard Workstation" for my package preselections, and it
> wanted to install tetex and ALL THREE versions of emacs. I think
> many people don't use latex anymore,
That's your opinion. Remember it is the only free package to produce paper
documents.
> but could we at least choose
> only one emacs as the default?
Suggestions welcome and I'll update the files. xemacs seems to be a good
choice for a "Standard workstation". I still have problems with emacs20 and
the composed characters since it dropped iso-syntax (no problems with emacs19).
> - It didn't install XF86Setup, xterm, or twm by default.
xterm and xf86setup are serious mistakes (they were in xbase in hamm). I fix
it in the "master" file (in the CVS tree in a few minutes). This will be in
2.1.5, I presume. Thanks for the bug report!
twm, yes. This is a choice (James van Zandt disagreed) because the new X in
slink exploded in several packages and twm was only in a suggested package. I
didn't find any reason to include thi old thing.
> - The setup program asking if I "run my own DNS server" told
> /etc/resolv.conf to use 127.0.0.1, but it didn't install named right
> away (of course). I had to fix /etc/resolv.conf to use an external
> nameserver so apt could find http.us.debian.org to install the BIND
> package!
This is already reported in bug #23337. And I agree with bug #31432. The
default should be to use another nameserver.
- -
http://www.debian.org/~bortz/
- -
To UNSUBSCRIBE, email to debian-boot-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
------------------------------
Date: Fri, 8 Jan 1999 18:45:27 -0500
From: Avery Pennarun <apenwarr@worldvisions.ca>
To: Stephane Bortzmeyer <bortzmeyer@debian.org>
Cc: debian-boot@lists.debian.org
Subject: Re: 2.1.4 install disks seem to work for me on i386
Message-ID: <[🔎] 19990108184527.B18536@worldvisions.ca>
References: <[🔎] 19990107001920.C6699@worldvisions.ca> <[🔎] 199901070923.KAA11736@ludwigV.sources.org>
Content-Type: text/plain; charset=us-ascii
On Thu, Jan 07, 1999 at 10:23:22AM +0100, Stephane Bortzmeyer wrote:
> On Thursday 7 January 1999, at 0 h 19,
> Avery Pennarun <apenwarr@worldvisions.ca> wrote:
>
> > - cfdisk refused to run because the partition table on this (I think
> > brand new) drive was garbled.
>
> I had the same problem, and I had to fix it in the BIOS (I don't know why
> but the geometry was set - wrongly - in the BIOS). cfdisk says nothing, it
> just returns, too quickly to read the error messages. Bug #29153 reports a
> similar problem and the workaround it suggests seems fine (in
> partition_config.c):
I guess. My BIOS geometry was right, but I had to wipe some crazy-looking
partitions in plain fdisk before cfdisk would see it.
Better still if cfdisk would just work (fdisk does) or the boot disks would
run fdisk for you (or ask if you want to) when cfdisk fails.
> > - I didn't choose the "make debian bootable directly from hard disk"
> > option. It didn't run lilo, which is what I wanted, but it didn't
> > even make /etc/lilo.conf, which was kind of surprising when I went
> > to install it later.
>
> Well, this can be discussed. The author of bug #31559 seems to disagree
> with you.
Reading through this bug, I don't think he disagrees with me. I agree that
there should be a way to skip both bootdisk creation and lilo install
(though it should be hard to do it by accident). In fact, I wanted to skip
both of those steps in this case.
However, it should still create the /etc/lilo.conf file anyway, since that
seems to happen non-interactively and may save people grief later when they
finally realize they need a method of booting :)
> > - I chose "Standard Workstation" for my package preselections, and it
> > wanted to install tetex and ALL THREE versions of emacs. I think
> > many people don't use latex anymore,
>
> That's your opinion. Remember it is the only free package to produce paper
> documents.
Yeah, I guess. The popularity-contest does in fact show tex as a pretty
popular set of packages. I noticed that during installation, tetex was one
of the slowest packages (set of packages) to install.
We'll know much more about people's likes and dislikes once Debian 2.1 is
released and the popularity-contest package gets installed by more than just
developers.
(Incidentally, my vote is to include that in most or all package
preselections!)
> > but could we at least choose
> > only one emacs as the default?
>
> Suggestions welcome and I'll update the files. xemacs seems to be a good
> choice for a "Standard workstation". I still have problems with emacs20
> and the composed characters since it dropped iso-syntax (no problems with
> emacs19).
xemacs20 is currently winning by a bit in the popularity contest, followed
by emacs20, and trailed by the much less popular emacs19. People who care
about these things, of course, will be sure to choose their preferred
environment in dselect anyway. People who don't know, probably appreciate
that we choose one for them.
> > - It didn't install XF86Setup, xterm, or twm by default.
>
> xterm and xf86setup are serious mistakes (they were in xbase in hamm). I fix
> it in the "master" file (in the CVS tree in a few minutes). This will be in
> 2.1.5, I presume. Thanks for the bug report!
>
> twm, yes. This is a choice (James van Zandt disagreed) because the new X
> in slink exploded in several packages and twm was only in a suggested
> package. I didn't find any reason to include thi old thing.
XF86Setup looks for twm before it will run, otherwise I wouldn't have
noticed or cared. Unfortunately, there is no dependency in XF86Setup to
that effect but Branden's latest XF86 packages aren't in slink yet, so I
didn't want to bother him.
Have fun,
Avery
- -
To UNSUBSCRIBE, email to debian-boot-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
------------------------------
End of forward6349kvq Digest
****************************
--- End Message ---