[Bug 480870] Review Request: crda - An 802.11 wireless regulatory compliance daemon

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=480870





--- Comment #4 from Bill Nottingham <notting at redhat.com>  2009-01-22 15:57:39 EDT ---
(In reply to comment #3)
> I chose the "v" version of the crda tarball because those had later dates than
> the equivalent non-"v" versions.  I made the assumption that this was the new
> release policy for the project.

Just using whichever they're using would work - I find it odd that they have
both tarballs.

> I'm happy to change the spec summary -- how about "Regulatory compliance daemon
> for 802.11 wireless networking"?

Sounds good.

> I will move and rename the udev rules.  Any suggestions for choosing a numeric
> priority?

It probably doesn't make a big difference. If nothing else is acting on
regulatory events, pick an earlier number and you may want to add
OPTIONS+="last_rule"; this (theoretically) would speed up processing some.

> The point about /usr being mounted later is a good one.  I don't know how
> realistic a NFS-mounted /usr over wireless is, but it probably makes sense to
> allow for wireless networking and all allowed channels even when /usr isn't
> mounted.  Are there any other guidelines differentiating /lib versus /usr/lib?

With NetworkManager on /usr, we don't really support nfs-over-wireless - my
main concern is whether these events are going to be generated on driver load
or similar activities on startup, and will then get 'missed' if /usr isn't
there yet. If that's not the case, it's probably fine.

> Realistically I don't know how much difference it makes -- I don't
> think either crda or wireless-regdb are likely to be spun very often, and crda
> is not such a big package as to discourage revving it when wireless-regdb
> changes -- thoughts?

If updates aren't going to be that often, it's not a big deal. I was just
worried about if there is going to be a 'monthly' spin of the regdb or
something similar that the updates might start to add up.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.