Re: 2.1.4 install disks seem to work for me on i386
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/
Reply to: