From: Bron Gondwana <brong@fastmail.fm>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
netdev@vger.kernel.org, yi.zhu@intel.com,
jketreno@linux.intel.com, akpm@osdl.org
Subject: Re: Recent wireless breakage (ipw2200, iwconfig, NetworkManager)
Date: Tue, 6 Mar 2007 11:24:57 +1100 [thread overview]
Message-ID: <20070306002457.GA7078@brong.net> (raw)
In-Reply-To: <20070305211425.GR16722@waste.org>
On Mon, Mar 05, 2007 at 03:14:25PM -0600, Matt Mackall wrote:
> On Mon, Mar 05, 2007 at 04:46:09PM +0100, Tomasz Torcz wrote:
> > > That's not the point. The point is that Debian/unstable as of _this
> > > morning_ doesn't work. For reference, I'm running both the latest
> > > releases of both hal (0.5.8.1-6.1) and network-manager (0.6.4-6). And
> > > there are people telling me I need a copy of HAL out of git that
> > > hasn't even been released for Debian to package. Debian isn't the
> > > problem here.
> >
> > hal 0.5.9-rc1 (released, not from git) should work. It will be
> > problably released soon and picked by sane distributions. Debian is very
> > irritating corner case.
>
> Presumably the -rc1 stands for "release candidate". Which means "not
> yet released". And when did it show up? 04-Mar-2007 at 18:31. That's
> right, YESTERDAY. Almost a full month after Greg's commit.
>
> For the last time, DEBIAN IS NOT THE PROBLEM.
Can I please second this (having been burned by hell that was udev of
the 0.5ish era) - Greg, please try to make changes in a cross-compatible
way so that versions of userspace and kernel are not so closely
dependant on tracking each other. The whole 2.6.8 -> 2.6.12 series of
kernels and associated udevs are fraught with race conditions where
upgrading one but not the other will leave your machine unbootable.
I read the "manifesto" for udev showing how crap devfs was, it was
broken, it could never be fixed etc - yet my experience was that devfs
systems "just worked"[tm] and udev was very dangerous. My thinking is
going to be tarnished by that for a while and my mental image of udev
is "unreliable POS". I'm hoping enough good experiences with udev might
make me feel less scared whenever I have to deal with it.
Similarly, I'm hoping I don't have to think "oh shit, will this break
boot" every time I upgrade either a kernel or hal version for the next
year, because it would really suck to do that all over again. It
contributes to the meme that linux is unreliable and perpetually
unstable.
Regards,
Bron.
next prev parent reply other threads:[~2007-03-06 0:24 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 22:08 Recent wireless breakage (ipw2200, iwconfig, NetworkManager) Matt Mackall
[not found] ` <20070304220857.GH23311-1tnLUEbcrg3YtjvyW6yDsg@public.gmane.org>
2007-03-04 23:39 ` Johannes Berg
2007-03-05 0:25 ` Matt Mackall
[not found] ` <20070305002550.GI23311-1tnLUEbcrg3YtjvyW6yDsg@public.gmane.org>
2007-03-05 0:45 ` Andrew Morton
[not found] ` <20070304164525.349f9589.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2007-03-05 1:05 ` Adrian Bunk
2007-03-05 0:46 ` Ian McDonald
2007-03-05 1:17 ` Greg KH
[not found] ` <20070305011729.GB7681-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2007-03-05 11:20 ` Johannes Berg
2007-03-05 12:59 ` Theodore Tso
2007-03-05 18:58 ` Greg KH
2007-03-05 19:55 ` Matt Mackall
2007-03-05 22:39 ` Greg KH
[not found] ` <20070305223900.GA7676-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2007-03-06 3:07 ` Matthew Garrett
2007-03-05 23:05 ` Jeffrey Hundstad
[not found] ` <20070305185813.GA31465-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2007-03-05 23:40 ` [2.6.21 patch] unconditionally enable SYSFS_DEPRECATED Adrian Bunk
[not found] ` <20070305234052.GR3441-HeJ8Db2Gnd6zQB+pC5nmwQ@public.gmane.org>
2007-03-06 0:07 ` Greg KH
[not found] ` <20070306000722.GA11436-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2007-03-06 0:35 ` Adrian Bunk
[not found] ` <20070306003541.GT3441-HeJ8Db2Gnd6zQB+pC5nmwQ@public.gmane.org>
2007-03-06 0:41 ` Greg KH
2007-03-06 1:30 ` Matt Mackall
[not found] ` <20070306013020.GN23311-1tnLUEbcrg3YtjvyW6yDsg@public.gmane.org>
2007-03-06 1:56 ` Greg KH
2007-03-06 13:20 ` Johannes Berg
2007-03-06 15:55 ` Dan Williams
2007-03-06 2:48 ` Greg KH
[not found] ` <20070306024850.GA24477-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2007-03-06 3:04 ` Matt Mackall
2007-03-06 3:39 ` Matt Mackall
[not found] ` <20070306033947.GQ23311-1tnLUEbcrg3YtjvyW6yDsg@public.gmane.org>
2007-03-06 4:03 ` Greg KH
[not found] ` <20070306040350.GA25783-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2007-03-06 6:10 ` Matt Mackall
2007-03-06 19:01 ` Greg KH
[not found] ` <20070306061009.GR23311-1tnLUEbcrg3YtjvyW6yDsg@public.gmane.org>
2007-03-06 20:05 ` Greg KH
2007-03-06 0:35 ` Recent wireless breakage (ipw2200, iwconfig, NetworkManager) Johannes Berg
2007-03-05 1:16 ` Greg KH
2007-03-05 6:42 ` Matt Mackall
2007-03-05 7:02 ` Greg KH
2007-03-05 7:13 ` Matt Mackall
2007-03-05 15:46 ` Tomasz Torcz
2007-03-05 21:14 ` Matt Mackall
2007-03-06 0:24 ` Bron Gondwana [this message]
2007-03-06 0:37 ` Greg KH
2007-03-06 0:56 ` Theodore Tso
2007-03-06 1:08 ` Andrew Morton
2007-03-06 1:17 ` Greg KH
2007-03-06 1:38 ` Andrew Morton
2007-03-06 1:10 ` Greg KH
2007-03-05 21:58 ` Joel Becker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070306002457.GA7078@brong.net \
--to=brong@fastmail.fm \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).