out this on debian-devel which may be
enlightening. Here is a thread that I started in June 2004:
http://lists.debian.org/debian-devel/2004/06/msg00443.html
This is not the only thread that has touched on this topic.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: discover1-data
Version: 1.2004.11.27
Severity: normal
The following line appears in pci-26.lst:
12745580sound snd-ens1371 5880 AudioPCI
The actual PCI ID is 1274:5880 so this should be:
12745880sound snd-ens1371 5880 AudioPCI
According to
to remove the OSS
> module and modprobe the alsa module before alsa will work.
Yes.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, 2004-11-30 at 18:33, Christian Perrier wrote:
> Here comes my nightmare : though the sound card in my test box is
> properly detected (modules are loaded), the sound server in Gnome is
> just unable to use it.
What are the names of the modules that are loaded?
What variant of libesd do y
On Tue, 2004-11-30 at 18:12, Sven Luther wrote:
> But make sure you don't fix it for kernel <2.6.8, or things will break again,
> and as sarge will ship with 2.6.8 ...
Yes, in /usr/src/kernel-source-2.6.8/drivers/net/Makefile:
obj-$(CONFIG_MV64340_ETH) += mv64340_eth.o
--
To UNSUBSCRIBE, emai
network connection via Aironet 352 Wi-Fi card on a home WLAN with
a DHCP server. :) Kudos!
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: discover1
Version: 1.7.2
Severity: important
Tags: patch
As it is currently written, discover1 will not ignore files in
/etc/discover.d/ that end in .dpkg-old.
Here is a patch that fixes this.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing'
Package: discover1
Severity: minor
/usr/share/bug/discover1 contains:
exec /usr/share/bug/discover1-data $@
The /usr/share/bug/discover1-data file is in discover1-data so discover1
should Depend on discover1-data.
This is a minor bug because discover1 Depends on libdiscover1 which
Depends o
tags 248923 - woody
thanks
The current /etc/init.d/discover still uses the cut program:
$ grep -n cut discover
129:# No cut(1) without /usr
187:mountsent="$(grep "$CDMOUNT " /proc/mounts | cut -f2)"
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTE
have lately retested with tc-rc2 and did not see the same keyboard and ATI graphic
card errors. I have filed a new install report which is filed as bug #274725.
Br,
Michael
Thomas Hood <[EMAIL PROTECTED]> schrieb am 18.08.04 10:40:18:
>
> On Wed, 2004-08-18 at 00:19, Michael Jos
strange is going on. Perhaps not enough
attention has been paid to the fact that there are multiple variants of
discover in the archive? What happens with the user upgrades from
discover1 to discover?
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
Package: discover1
Severity: normal
update-initrd uses stuff in /usr/
/sbin/$ grep usr update-initrd
cp /usr/share/discover/linuxrc $ROOT/linuxrc
cp /usr/lib/libdiscover.so.1 $ROOT/lib/libdiscover.so.1
cp /usr/share/discover/*.lst $ROOT/share/discover
ln -s . $ROOT/usr
nnot be entered in the
"s:" format.
I will investigate further.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
fixed this in SVN.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
joshk: Please double check the fix I just checked in.
--
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
in resolv.conf should be inserted by resolvconf.
This means that DHCP clients and resolvconf should be enhanced so that
they do insert that line.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Martin Michlmayr wrote:
> d-i made the following /etc/hosts entry:
>
> 127.0.0.1 localhost.localdomain localhost qube
>
> Even though DHCP found my domain (cyrius.com), it is not mentioned
> anywhere. Now "hostname" produces "qube" whereas "hostname -f" gives
> "localhost.localdomain".
tags 267321 wontfix
thanks
I have discussed this matter with Joshua Kwan and we agree that it is
best to leave the installer as it is for now.
Please follow up to #267321.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
switching the nsswitch.conf file.
> This single change would take care of 99% of the problems. Make an
> option during setup, if this machine is a "multiple" config machine,
> then let this get changed.
Also, we should try to find a solution that doesn't require the
servers aren't reachable.
John Summerfield continued:
> If there is no external network, then the behaviour of programs such as
> ping, telnet, ssh are irrelevant. All are of limited use without a
> functioning network.
That isn't entirely true. Some programs use
On Sun, 2004-08-22 at 22:37, VSJ wrote:
> I'd go for the following solution:
[... not to include the hostname as an alias for 127.0.0.1
if the network is configured via DHCP.]
I am beginning to think that we should bite the bullet and do one of
two things. Either,
1. to require software to work
cceeds.
>
> It says - Network Auto Configuration Succeeded.
>
> I do not want the DHCP routine to run, which is why I typed in
> netcfg/disable_dhcp=true
>
> Am I doing something wrong or should I file a bug report ?
I think that this has already been reported in #26624
manual configuration, loops back to DHCP attempt
Could these possibly be related? ;)
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Builds and works for me.
Remember that if this version of pcmcia-cs goes into sarge then
netcfg will have to be modified to mark 16 bit PCMCIA interfaces
as hotpluggable.
--
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, 2004-07-01 at 21:43, Per Olofsson wrote:
> Not that it matters if it's a conffile, the installer isn't bound by
> policy like maintainer scripts. But I think this is wrong. The
> package's behaviour shouldn't change just because it's been installed
> by d-i. I think that the variable should
reopen 248071
reassign 248071 pcmcia-cs
severity 248071 wishlist
retitle 248071 Please make not calling ifup/ifdown the default for sarge
thanks
Per Olofsson wrote:
> Yes, you're probably right. I think the easiest way to implement this
> would be to add a variable to /etc/default/pcmcia and then
" in /e/n/i.
It may be possible to do it using the information in /var/run/stab
and/or in the various /proc files. I don't have a cardbus card so I
can't contribute much to figuring this out.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, 2004-06-28 at 22:47, Osamu Aoki wrote:
> > 2. pcmcia-cs does not ifup/ifdown interfaces on 16 bit PCMCIA cards
> >by default (which requires a change to pcmcia-cs) and hw-detect
> >lists such interfaces in /etc/network/devhotplug (as now).
>
> Yes. This will be nice since these if
tc/network/devhotplug (as now).
Currently, pcmcia-cs ifups/ifdowns interfaces on 16 bit PCMCIA cards
and hw-detect lists such cards in /etc/network/devhotplug, which
is not one of the reasonable options: we shouldn't have hotplug and
cardmgr battling for control of those interfaces.
--
Thomas
TODO
* stage 3:
+ Check whether it works properly with hot plugged network
interfaces. That is, stage 3 should not assume that these
interfaces come up at any particular time but should wait
for networking to become available.
* netcfg:
+ Determine whether the primary interf
Per Olofsson is right. The "auto" statement in /e/n/i makes
S:S40networking bring up the interface referred to. This is
appropriate for interfaces on built-in hardware whose drivers
are loaded and fully initialized prior to S:S40networking and that
should be ifup'ped at boot and not ifdown'ed unt
On Fri, 2004-06-25 at 18:03, Laurens Blankers wrote:
> That would work for me.
>
> However I can imagine a network setup in which computers without a
> hostname are assigned a non-routable IP instead of none at all. How are
> you going to handle that situation?
We can make it so that at question
unmerge 236533
retitle 236533 Please configure dhclient to "send host-name "
severity 236533 wishlist
thanks
On Fri, 2004-06-25 at 00:20, Frans Pop wrote:
> With my setup DHCP does _not_ fail the first time it is tried, as seems to be
> assumed in the code. It succeeds within the first 20% of th
I am confused about all this hostname stuff.
I think that we should stop calling the argument of "send host-name"
a "hostname". Instead let's call it a "host-name". The host-name
can be different from the hostname. See #239591.
I take it we want to do something like this:
Try DHCP
If
The latest module-init-tools eliminates use of /etc/modprobe.conf .
See the changelog.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I suggest that if there are no interfaces then we make it so that
get_interface() doesn't exit but returns with the interface name
pointer equal to NULL. This is detected in main() and causes
get_nonet() to be called, on receiving an error from which the next
state becomes BACKUP; otherwise QUIT.
Package: netcfg
Version: 0.70
Severity: wishlist
It would be helpful to the user who wants to install resolvconf if the
static nameserver information that netcfg writes directly to
/etc/resolv.conf were also written to /etc/network/interfaces in the
format required for it to get included in the dy
Package: netcfg
Version: 0.70
Severity: minor
This is pretty minor, I admit, but the various documents that discuss
options in /etc/network/interfaces have been moving toward a standard of
using hyphens rather than underscores in option names. Either hyphens
or underscores can be used so this cha
In http://lists.debian.org/debian-boot/2004/06/msg01180.html Baptiste
Carvello wrote:
> /etc/network/interfaces is empty
The same problem was reported in #243543 but was reported to have been
fixed already. Please check there to see if you think that the
circumstances are the same.
--
Tho
On Wed, 2004-06-09 at 17:31, Bernd Eckenfels wrote:
> I was under the wrong impression that on kernels, I cant ping 127.0.1.1,
> but at least on 2.6 with no loopback route I am wrong, and it works fine. I
> think that has changed, but I am not sure if it is something to care about.
I can ping 12
On Wed, 2004-06-09 at 19:05, Joshua Kwan wrote:
> Where does 127.0.1.1 fit in to the whole "hostname of system must
> resolve into a usable IP" thing?
I am not aware that the hostname of the system must resolve into
something usable. I am only aware that sudo prints an error
message (which may b
7;:
127.0.0.1 localhost.localdomain localhost
10.1.2.3pingo.pingodom pingo
--
Thomas Hood <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
-Forwarded Message-
From: Greg Folkert <[EMAIL PROTECTED]>
To: DebianDevel List <[EMAIL PROTECTED]>
Subject: Re: /etc/hosts: Two lines with the same IP address?
Date: Tue, 08 Jun 2004 15:11:47 -0400
On Tue, 2004-06-08 at 14:54, Thomas Hood wrote:
> On Tue, 2004-06-08
-Forwarded Message-
From: Greg Folkert <[EMAIL PROTECTED]>
To: DebianDevel List <[EMAIL PROTECTED]>
Subject: Re: /etc/hosts: Two lines with the same IP address?
Date: Tue, 08 Jun 2004 12:03:50 -0400
On Tue, 2004-06-08 at 11:31, Petter Reinholdtsen wrote:
> [Steve Langasek]
> > See other re
-Forwarded Message-
From: Petter Reinholdtsen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: /etc/hosts: Two lines with the same IP address?
Date: Tue, 08 Jun 2004 17:31:04 +0200
[Steve Langasek]
> See other responses for the fix for this; but, er, why would you want
> the canonica
On Tue, 2004-06-08 at 15:48, Andrew Suffield wrote:
> On Tue, Jun 08, 2004 at 02:40:55PM +0200, Thomas Hood wrote:
> > 127.0.0.1 localhost
> > 127.0.0.1 pingo
> The above two lines *must* be precisely equivalent to *one* of the
> following four lines:
>
On Mon, 2004-06-07 at 23:02, Pierre Machard wrote:
> > I can think of a couple of different ways of solving this problem.
> > The first is to eliminate 'pingo' from the 127.0.0.1 line if and
> > only if 'pingo' appears on some other line.
>
> That's what I commited to the subversion tree, but appa
> 127.0.0.1 localhost pingo
> 10.10.0.17pingo.miss-knife.netpingo
On rereading the original message I realize that I overlooked the most
important fact. The hostname, 'pingo', appears on two lines in the
/etc/hosts file. The presence of 'pingo' on the 127.0.0.1 line causes
'loc
On Mon, 2004-06-07 at 15:30, Joey Hess wrote:
> busybox ps does not support any of the options you used, as far as I can
> tell.
>
> This is the d-i initrd. We don't have start-stop-daemon. I think that
> running the code and playing with it on the actual d-i system may have
> better results than m
Package: netcfg
Version: 0.67
Severity: minor
In dhcp.c it would be better to do:
if (access("/sbin/dhclient3", F_OK) == 0)
dhcp_client = DHCLIENT3;
than to do (as currently):
if (access("/var/lib/dhcp3", F_OK) == 0)
at line 79. Checking for the daemon executable is more or less
stand
Package: netcfg
Version: 0.67
Severity: minor
Tags: patch
The killall.sh script uses the following code to find the PIDs of running
DHCP client daemons:
pids=$(ps ax | grep 'udhcpc\|dhclient\|pump' | sed 's/^[
]*\([0-9]*\).*/\1/')
However, (1) this picks up the PID of the grep process itself:
$
Package: netcfg
Version: 0.67
Severity: minor
Tags: patch
Here's a patch that corrects the reference to the pppconfig package.
--- README_ORIG 2004-04-13 09:07:27.0 +0200
+++ README 2004-06-07 10:02:05.0 +0200
@@ -10,7 +10,7 @@
netcfg is written specifically for the debian
an
> or
> 127.0.0.1 debian localhost
This issue was discussed recently on debian-boot. So, d-i guys,
what was finally concluded? After installation, will 'localhost'
or the system hostname appear first on the '127.0.0.1' line in
/etc/hosts?
--
Thomas
> That begs the question: How much experience with Linux and in
> particular, with installing Linux do you have?
I am an experienced GNU/Linux user but this was my first time
running the new Debian installer.
--
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsub
Package: installation-reports
Here is a verbose installation report. I wrote it while installing
sarge after having consulted no documentation.
Let me start by saying that the installation process made a good
impression.
However, there may be room for improvement at any point at which I
report
following lines are desirable for IPv6 capable hosts
# (added automatically by netbase upgrade)
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
our
resolv.conf should be updated automagically.
I am closing #251066 with this message, but please reopen it if
it turns out that there is still a bug somewhere.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> OK, now all d-i packages use ellipsis without spaces
Ah, good. Consistency is best.
> We're now left with tracking down progress bars not using
> ellipsis..:-)
It would be nice if Debian native apps (e.g., dpkg) also followed the
standard.
--
Thomas Hood
--
To UNSUBSC
Update for debian-boot... This bug will be fixed by adding resolvconf
support to dhcp-client. A patch has been prepared and fixed the
problem for the submitter of #248399.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
te that we don't insert spaces
before or after the dots.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
the maintainers of
dhcp-client agree to apply a patch.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ds to be done:
1. Install dhcp3-client instead
2. Don't install resolvconf
3. Add resolvconf support to dhcp-client
I can supply a patch to implement #3 if it is decided that that is
necessary. I haven't worried about getting support into dhcp-client
before because I thought that it had
On Tue, 2004-05-11 at 17:10, Matt Zimmerman wrote:
> Because the debian-installer folks asked the dhcp*-client folks to leave
> things as they are for sarge.
So can & should debootstrap switch to installing dhcp3-client?
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
lace dhcp-client, why isn't it just being
> called dhcp-client, with dhcp2-client kept around if it's really needed?)
Good question for the dhcp-client maintainers.
CC'ing [EMAIL PROTECTED]
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of &quo
ver
dhcp3-client but in that case I'd like to know what the reasons are.
Adding dhcp-client to resolvconf wouldn't be the easiest job;
I haven't bothered doing it because dhcp3-client is the replacement
for dhcp-client and I have assumed that new installs will be using
dhcp3-client
ve", not "serious".
Otherwise the severity should be "normal" or "important".
--
Thomas Hood <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ext2 partition and to boot from Linux
running off a partition. My suggestion is that it be made
possible to install *fully* from an ext2 partition, so
that the installed Debian partition can itself be booted.)
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
67 matches
Mail list logo
