> In the end, I hope to have the whole system building using automake
> and configure, so that one can create a custom installer by giving
> various options to configure. :)
cdebconf already uses autoconf. i'd really prefer not to use automake if
we can. it adds way too much abstraction and in my
Hello, I am trying to install Debian 2.2r2 from scratch (bootable CDROM
or floppies) but the 2.2.18pre21 kernel is (most of the time ~95%) not
able to recognize my SCSI drives. Here is the interesting part of the
kernel log (booting with Rescue compact floppy) :
PIIX4: IDE controller on PCI
On Fri, Jan 05, 2001 at 04:12:58PM -0700, Gerry Wiener wrote:
> Package: base
>
> Linux amber 2.2.17 #1 SMP Thu Sep 7 11:35:24 MDT 2000 i686 unknown
>
> I initially reported the bug below to the Python 2.0 bug list. The
> author of Python responded by mentioning that he thinks it is a
> problem
Pentium II PC 350MHz
64MB RAM
All hardware already runs Caldera Linux 2.4 OK.
Hi - Please can you help ???
I am trying to replace Caldera Open Linux 2.4 with Debian 2.2r2 (from
official CDs). I want to use the exisiting partitions. Dbootstrap
doesn't let me get past
"Configure Device Driver Mo
Tollef Fog Heen wrote:
> do {
> debconf->command(debconf, "fset", DEBCONF_BASE "http/hostname", "seen", "false");
> debconf->command(debconf, "INPUT", "critical", DEBCONF_BASE "http/hostname", NULL);
> debconf->command(debconf, "GET", DEBCONF_BASE "http/hostname", NULL);
> } while (debconf->value
Package: base
Linux amber 2.2.17 #1 SMP Thu Sep 7 11:35:24 MDT 2000 i686 unknown
I initially reported the bug below to the Python 2.0 bug list. The
author of Python responded by mentioning that he thinks it is a
problem with the libc thread code. I wanted to make sure the bug was
reported.
Package: base
Version: 2.2
After installing the debian 2.2 with the UDMA66 patch, I reboot as
instructed and receive the following message:
/bin/sh: exec: /sbin/termwrap: cannot execute: No such file or directory
This message repeats several times, then I receive:
INIT: Id "1" respawning too f
* Tollef Fog Heen
| * Joey Hess
|
| | Tollef Fog Heen wrote:
| | > Shouldn't the retriever be persistent and requiring a hostname and a
| | > directory?
| |
| | You need to read up on how debconf works. The "persistance" you are
| | advocating == an infinite loop. GET commands always return t
im starting to get into the partitioning side of of things.
Ive started with this small routine that parses /proc/mounts into
debconf. I figure ill do one that parses /proc/partitions and then one
to get known filesystems. With those three lots of information in
debconf format and mount functions
Anthony Towns wrote:
> If you want minimal, just install the "important" packages. If you
> want _really_ minimal, just install the "required" packages.
Before telling people to do this could you please fix all the wrong
priorities in testing and unstable? [ Or at least the ones regarding
standar
Van,
For the ltmodem.o driver support there have been an evolution of fixes
which you can read in some more detail at
http://walbran.org/sean/linux/linmodem-howto-all.html
1) Through kernel version 2.2.4
insmod -f ltmodem.o
the 2.2.2 compiled ltmodem.o binary sufficed.
2) This failed with
Hi,
I recently bought a Tecra 8100 which includes a Lucent linmodem. Lucent released a
binary-only driver for this modem by the time of kernel 2.2.12. Unfortunately with
later version of the kernel, it didn't work. Yesterday I found the reason why and
patched the 2.2.18 kernel source tree.
I
12 matches
Mail list logo
