Re: policy on GPL'd drivers?

From: Steve Kargl (sgk_at_troutmask.apl.washington.edu)
Date: 05/29/03

  • Next message: Chris Shenton: "DELL CERC amr RAID card beeping, dead drive? how to diagnose/fix?" 
    Date: Wed, 28 May 2003 20:18:58 -0700
To: "Daniel O'Connor" <doconnor@gsoft.com.au>

    On Thu, May 29, 2003 at 09:20:23AM +0930, Daniel O'Connor wrote:
    > On Wed, 28 May 2003 23:58, Steve Kargl wrote:
    > > > > Because there are other, more elegant ways of dealing with these
    > > > > things. I don't like /usr/local/src anything, which was the main
    > > > > complaint.
    > > >
    > > > If there are more elegant solutions I would like to know what they are.
    > > >
    > > > I agree it isn't a great solution, but I can't see what is better.
    > >
    > > For GPL modules, put them in src/sys/gnu. If you don't
    > > want bloat, then use cvsup and a refuse file to not
    > > retrieve the sys/gnu. See the discussion that occurred
    > > many years ago when maestro3 support was committed to
    > > the tree.
    > >
    > > For non-viral licensed code, put it in its proper
    > > place in the sys/ hierarchy. Then use a WANT_XXX=yes
    > > knob in the /etc/make.conf to cause XXX to be built.
    >
    > You are describing how it happens now, not WHY it happens like that.

    The WHY is obvious. The modules
       (1) get rebuilt with the kernel.
       (2) get installed with the kernel.
       (3) get moved to /boot/kernel.old when a new kernel is installed.
       (4) *Ideally*, if an API changes, the modules will be updated
           by the developer/committer who breaks the modules; otherwise,
           a person experiencing the breakage can ask for the commit to
           be backed out. (Note, the *ideally* acknowledges that 64-bit
           platforms seem to suffer API breakage more than ia32).

    > I think the existing solution has problems, and would prefer some external
    > hooks for 3rd party modules.

    If you mean "third party modules without available sources", then
       (1) The module should work for whatever -RELEASE i for which it was built.
       (2) If you upgrade the OS, the module may or may not work.
           (a) If it works, well aren't you lucky.
           (b) If it doesn't work, then
               (i) Ask the vendor for an update.
               (ii) Hack around the breakage.
               (iii) Downgrade to the *PROPER* -RELEASE. 

    -- 
Steve
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
  • Next message: Chris Shenton: "DELL CERC amr RAID card beeping, dead drive? how to diagnose/fix?"

    Relevant Pages

    • powerpc: Add flattened device tree documentation
      ... The flattened device tree is the only supported way of booting ... +order to avoid the degeneration that had become the ppc32 kernel entry ... +the presence of a device-tree whose format is defined after Open ... + present if the processor is a SOC. ...
      (Linux-Kernel)
    • Re: RFC: Starting a stable kernel series off the 2.6 kernel
      ... > kernel upgrade depends on a new wpa_supplicant package. ... I've broken stuff by upgrading glibc, upgrading X, upgrading KDE... ... Automating the patch flow allowed entire subsystems to be effectively ... maintain a tree and merge with linus, and back then the -ac tree was very ...
      (Linux-Kernel)
    • [PULL] A few documentation updates
      ... I have a few updates queued up in my documentation tree: ... Process continues until the kernel is considered "ready", ... +the path relative to the current process's filesystem root. ...
      (Linux-Kernel)
    • Re: [PATCH] delete devfs
      ... been merging patches at a rate of about 10MB/month. ... Andrew would like to see a 2.6 tree which continues to change ... In his vision of the future, the kernel.org kernel will be the most ... keeps the developers happy and gets new code out to users quicker. ...
      (Linux-Kernel)
    • Re: threshold_init_device/kobject_uevent_env oops
      ... BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 ... Does this happen on just Linus's tree? ... Can you send me a .config file for this? ... will look at AMD64 Bios and kernel porting guide for Fam 10h again.. ...
      (Linux-Kernel)