TZUTC: -0600   
   MSGID: 1038.fido_linux@1:123/115 245c0819   
   REPLY: 1:105/420 df9aa51f   
   PID: Synchronet 3.18c-Linux master/b3b4d332a Jan  2 2021 GCC 5.5.0   
   TID: SBBSecho 3.12-Linux master/b3b4d332a Jan  2 2021 GCC 5.5.0   
   COLS: 80   
   BBSID: PALANT   
   CHRS: ASCII 1   
   NOTE: Synchronet msgeditor $Revision: 1.175 $   
     Re: Re: *nix Licenses   
     By: paul lee to Richard Falken on Wed Jan 06 2021 08:18 pm   
      
    >  RF> You'd get helpful answers if you told us what the product is.   
    >    
    > Thanks... some of the responses here were just attacks, or I didn't understa   
    > their replies.   
    >    
    > I do a bunch of projects marrying antiques with current tech. I refurbish ol   
    > record-player consoles into current hi-fi equipment. I either use the origin   
    > amplifier, or a current Tube-amp and marry it with a raspberry pi and some   
    > open-source software (rpi-fruibox) that I have the license to distribute.   
    >    
    > I just wonder about using the underlying Linux OS. Am I allowed? I guess I n   
    > to pass the license to my lawyer, which sucks because... $100 for an hour.   
    >    
    >    
    >    
    > |07p|15AULIE|1142|07o   
    > |08.........   
      
   Ok, so you plan to sell an appliance and need a firmware for it.   
      
   Long story short:   
      
   If your appliances use modified Linux or GNU components, you must release the   
   source code. This is: if your appliance uses a modified kernel, a custom   
   patched version of bash or whatever, you must release the source code of that   
   component. Since your business model is selling hardware, this should be no big   
   deal anyway.   
      
   If you appliance uses unmodified Linux / GNU components, then you need not to   
   worry. You may incorporate propietary extensions to your firmware - say, a   
   propietary GUI - without releasing the code, as long as your extensions don't   
   represent a modification of GPL licensed components. ie: you can distribute a   
   bash script under a propietary license as long as you don't modify bash itself   
   .   
      
   Beware many Linux distributions include non-free components, so you'll have to   
   strip those out if you want to redistribute them.   
      
   You can still release the source code of your firmware and have a successful   
   product.- The Linksys that paved the way for the creation of OpenVRT come to   
   mind.   
      
   --   
   gopher://gopher.richardfalken.com/1/richardfalken   
   --- SBBSecho 3.12-Linux   
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)   
   SEEN-BY: 1/120 123 15/0 16/101 18/0 19/36 20/4609 50/13 90/1 103/705   
   SEEN-BY: 105/81 106/127 201 116/18 116 120/331 340 123/0 25 35 40   
   SEEN-BY: 123/50 115 131 140 150 160 170 180 190 755 124/5016 128/2   
   SEEN-BY: 135/300 153/105 135 141 757 802 6809 7001 7715 154/10 203/0   
   SEEN-BY: 218/700 221/0 6 222/2 226/30 227/114 702 229/101 424 426   
   SEEN-BY: 229/452 550 616 664 1016 1017 230/150 152 240/77 1120 5138   
   SEEN-BY: 240/5411 5824 5832 5853 249/206 317 400 250/1 261/38 100   
   SEEN-BY: 261/1466 266/512 267/67 155 275/100 280/464 5003 282/1031   
   SEEN-BY: 282/1056 288/100 291/100 111 292/854 8125 299/6 310/31 317/3   
   SEEN-BY: 320/119 219 322/757 335/364 340/400 341/66 342/17 200 396/45   
   SEEN-BY: 423/120 633/280 640/1321 712/848 770/1 801/161 189 2320/105   
   SEEN-BY: 2432/390 2452/250 2454/119 3634/0 12 15 27 30 50 119 4500/1   
   SEEN-BY: 5020/400 545 715 1042 1477 4441 5025/3 5030/1957 2404 5037/7   
   SEEN-BY: 5053/58 400 5066/18 5080/102 5095/20   
   PATH: 123/115 3634/12 261/38 153/757 221/6 5020/545 280/464 240/5832   
   PATH: 229/426