Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Linux Software

Linux In the Family Room? 91

njcfm writes: "Ok, you've all heard and seen embedded Linux running in all sorts of useful devices; now with the backing of Intel it can run your home network too!" The story is about UPnP [?] for which Intel has released a Linux toolkit.
This discussion has been archived. No new comments can be posted.

Linux In the Family room?

Comments Filter:
  • Until I have a robot that can make a good ham and cheese sandwich, I would have no use for a remote microwave... or a toaster (what, do I keep it filled with bread (getting stale)?). Windows, shades/drapes/blinds, lights... those sorts of things seem useful, but most kitchen appliances require human intervention to work anyway (prepare the food and place it in the unit - turn over halfway through - baste - etc...).

    What would be the advantage of controlling my uWave from my office? Maybe if it had an automatic popcorn loading mechanism, but even that requires that you monitor the bag closely during the end of the popping. Decent quality video/audio streaming, networking and cooking from a $50-150 device? Hmmm...
  • by verbatim ( 18390 ) on Thursday June 15, 2000 @07:17AM (#1000081) Homepage
    Platform independance.

    Okay, forget PnP, UPnP, whatever.. What we need is the ability to have universal drivers. I know it's probably been said a million times already, but untill such a beast arrives we will still be in the dark ages.

    My thought of device independant drivers verges on the line of the idea behind Java. Every system has things that are in common with all other systems - something plugs into something else (be it a chipset, add-on card, etc) to make something happen (RNG on P2 mobos, sound card, video card, network card, etc). There would be a platform level loader that provides a common, standard interface to a higher-level driver. This driver would be directly portable across any platform for which there is a written loader.

    Currently its like:

    OS -> Driver -> Device

    The OS talks to the driver and the driver controlls the device. The problem being that the Driver has to be in a language the OS can understand as well as the device.

    Here's what I thought (maybe from reading simealr stuff)...

    OS -> Loader -> Device
    |
    Driver

    The loader is called by the OS and uses the instructions of the driver to control the device. The loader is essentially an interpreter for the code in the driver, and since the driver is independant of the OS a company can release ONE driver and hit Linux, BeOS, Windows, whatever... yes, providing that the OS provides an interface for this.

    Is there something like this in the works? Linux would be a great place to piononeer a "universal device driver"... base it on Java, or make something new...

    Bah, whatever ;)

    (if there is something like this I would be very interested in reading up on it)
  • by brandon ( 16150 ) on Thursday June 15, 2000 @06:22AM (#1000082)
    One thing to remember is that with this comes some major security issues. There will have to be some serious security holes totally patched, if that is even possible.

    A question for everyone... What type of work is being done, or needs to be done for home security when the house is on the internet. Is there a company who's working on this? I would hate to have someone breaking into the house by disabling my security system from half way around the world.

    Another question... Does this mean a central computer will control heat, locks, water, power, and ever thing down to childrens toys? I know this would be a good idea, but once again would this be worth the risk? I think not having some of those "features" would be safer for everyone, once again, what does everyone think, or anyone know places with information on these questions?

    --Brandon
  • Kewl to see an article in support of linux, but I usually find that Linux has only token support from ZDNet. Sorta like, "Oh look, I say something pro-Linux today, and I am cool. To cater to the real audience, I will say how wonderful windows is tommorow."
  • All this really amounts to is standard distributed ARP/DHCP protocol. Standards are good ;)

    When a device comes up, it broadcasts "Hey, what IP's are you guys on? I'd like 198.111.21.42 with a hosts entry of 'Jim's Fridge', but I'm flexible! Oh, and by the way, I'm on Ethernet now, but I can use my SiR transciever too! Do I need two IPs?"

    The rest of the devices come up, find an unused IP and assign the name "Jim's Fridge" to their hosts file. The SiR capable machines make a note to activate a connection for devices with that discovery information.

    Simple stuff. Microsoft can't even screw that up!
  • by Anonymous Coward
    Hey- i just rooted your fridge.
  • Oops, I meant this to be formatted like this:

    >>except it's supposed to work with Intel
    >> hardware only

    No, UPnP is not tied to Intel hardware in any way. See www.upnp.org.
  • u guys being programmers and smart people, would you pay money for a service that let u manage code online?
  • Another question... Does this mean a central computer will control heat, locks, water, power, and ever thing down to childrens toys? I know this would be a good idea, but once again would this be worth the risk? I think not having some of those "features" would be safer for everyone, once again, what does everyone think, or anyone know places with information on these questions?

    Jurassic Park, anyone?

    --

  • I remember an AT&T commercial a few years back that showed a lady in a high speed train with a palm device (this was long before Palm), and with a few touches of the stylus, the lights in her home lit up.

    It is important that technology like this be incorporated into the design and building of the house of today (not tomorrow). Did you forget to trun the stove off? Check it and if so, turn it off, from the other side of the world.

    Sure, it poses a threat that someone could crack your toaster to burn your bread every morning, but I would rather have open source software, where such a hole would be noticed quickly, than a proprietary/bianary bundle which will release their security patches quarterly.

  • Why wouldn't they have their own IP's? They'll probably use IP's in the private range. I can't remember exactly what that is (I'm not a network guy), but I know it looks like 192.x.x.x.

    Refrag
  • What percentage of Joe users do you think would be able to install and/or maintain any sort of home network environment with a dozen or more connected devices?

    All Joe user needs is a DCHP enabled firewall device. IIRC some of these are in development right now (or may even be available).

    Something like this isn't too complicated. One plug for modem/broadband, and one ethernet plug for the inside. It can DHCP out 192.168.x.x addresses and IP Masquerade for the machines/devices inside.

  • The microwave could reset its time using NTP or the like.. that would be cool.
  • I had no problem connected my three computers together and getting them to share a cable modem. I just bought LinkSys' Cable/DSL Router with built in firewall (with NAT), DHCP server, and PPPOE (althought I have no idea what I can do with this?), plugged my PC's into it's 4-port switch, and set it up via it's Web based interface.

    Refrag
  • <P>
    Sun's vision was that all of your devices would have just one digital connection, which would (essentially) be a network connection. It's more or less unimportant what that is, though I suspect it'll be closer to IEEE1394 and further from 100bTx or whatever.
    </P>
    <P>
    As per Sun's idea, devices would then register themselves on the network (in much the same way NetBIOS stuff does, except less lame) and they would then appear: Display devices, for example, so when you wanted to play something on the DVD player, it could appear on <EM>any display device in the house</EM>. If you had a compliant application on your PC, this could not only be your television or something, but also a window on your PC. By the same token, you could display a movie (or AVI, or whatever) played on your PC on your television.
    </P>
    <P>
    With today's market-ready technology, the only two transport mediums you could really use for this are 100bTx ethernet or IEEE1394 (Firewire, i.Link, whatever we're calling it today.) The problem with ethernet is that to get enough bandwidth out of it, you need a switched architecture, whereas 1394 is fast enough today. You're still going to need a multiple master architecture even so, since things like digital video are pretty demanding, and switches for 100bTx are expensive, since you can't daisy-chain devices.
    </P>
  • I'll read the specs you refer to, although I don't have the time just this moment.

    What you're saying sound good, though. If I'm not misunderstanding, all UPnP devices of the same type have the same API. So for example, in the case of printers, I assume this means that these printers would no longer be PCL, ESCP, Postscript, etc. - all printers will use the same UPnP-defined API. If this is case, an operating system specific driver would still be needed for that API, but at least there would only be one API to write to.

    If this is the case, though, how would new device features be added without changing the API?
  • "Microsoft in itself does not pose a security risk [but] rather the [risk comes from] dumb 'paper MCSEs'."

    How do you explain L0PHTCRACK: Inside a high-technology company, " L0phtCrack [l0pht.com] 2.5 cracked 90% of the passwords in under 48 hours on a Pentium II/300."

    I doubt the most experienced MCSE could reverse engineer MS's source code and remove that tiny glaring security flaw (you know, access by any SKR1PT K1DDIE to your machine). Not after the DMCA anyways.

    Or the problems with buffer overflows, the Netbios port (hey if you're an mcse, may as well just shut down everything microsoft has implemented, I mean - its your fault its there).

    File & Print sharing, non-encrypted network protocols.

    You can't blame MCSEs for Microsofts mistakes - after all, they were trained by MS.

  • PPPOE is used if your ISP uses PPP over Ethernet (PPPOE) to authenticate you. Usually, adsl companies will do this to reuse their RADIUS infrastructure.

    In your case, you probably don't need it, so you cannot do anything with it.

  • I have a private home network as it is. I just use non-routable IPs. I gateway out when I need to. When I get DSL, I will just install a firewall and NAT.

    All this seems to provide is another way from companies to sell me something I already have.

    Is there something here I am missing?
  • Small, medium, and large, without any of the fine detail in between.
  • by chrome koran ( 177357 ) on Thursday June 15, 2000 @06:28AM (#1000100)
    No matter who creates whatever kind of PnP solution for whatever OS and starts supporting internet (or intranet) appliances, somebody is still going to have to overcome some very large hurdles before mainstream adoption is possible.

    What percentage of Joe users do you think would be able to install and/or maintain any sort of home network environment with a dozen or more connected devices? Remember: they will probably have all these devices connected to the internet using some sort of TCP/IP protocol as well, so they will have two networks running simultaneously with a number of different devices made by different manufacturers trying to communicate with each other.

    haha...HaHa...HAHAHAHAHAHAHA...cough, wheeze...

    Sorry...almost hurt myself there. All I know is it was tricky for me to set up a network in my house using four PCs sharing one cable modem. Networking, firewall, cable network connection through a gateway... Now I'm not a systems guy, but I ain't PC illiterate either. Most people can't even figure out how to add some memory to their machines, much less set up a firewall. I can see it now...the kid down the street is laughing his ass off as he turns your microwave on and off at 5 minute intervals and has your refrigerator order four dozen Tombstone pepperoni pizzas!

    Protocols and OS network interfaces have a long way to go before more than 1% of US households have the capability to manage any such animal as all these guys are envisioning...

  • A lot of this thread seems to suggest that this will make adding peripherals more simple, but we'll still have a problem with the drivers.
    Correct me if I'm wrong, but this is more of a toolkit addition for internet appliances, not network cards. As far as drivers go, that is up to the appliance manufacturer to design it so that "a device would be able to locate, recognize and interact with other UPnP-enabled devices."

    As far as people setting up a personal linux box, this will only make future interactions with UPnP enabled devices more simple.

    What I don't get is that statement about MS having no plans for Linux support?!?! UPnP is the support, not OS type.
  • Um, UPnP is over a century old. The largest, most complex railway switchyard in the world, located in North Platte, Nebraska, was built by Union Pacific in the late 1800s. Thus, UPNP switchyard.
  • NT (aka 2000), 98/95, WinCe
  • You are exactly right. UPnP is Microsoft's response to Sun's Jini(1).

    The difference is this: Jini(1) is proprietary in that it requires all participants to be running on a Java(1) Virtual Machine. Last time I checked, one had to pay a royalty to Sun to use their Jini(1) classes to create a Jini(1) device. I don't know if this has changed.

    UPnP on the other hand is based on protocols. Anyone can participate in UPnP just by implementing the required protocols.

    Another difference is that Microsoft took a much more pro-active approach to getting the ball rolling by defining various standard device types and service types (which are described with XML). There's a lot of stuff in the works, although I don't recall exactly what my NDA permits me to talk about, so I better not say anything about it.

    We were actually working on an implementation of UPnP for Linux when we got word that Intel was going to release an implementation, at which time we shelved it.

    (1) Third party marks and brands are the property of their respective holders.

  • I don't know why nobody's done this yet.

    Well, except that this is the sort of innovative idea that usually comes from Apple, because nobody else has the balls to do it, but this particular idea isn't the sort of thing that Apple would do (they don't need it; Darwin has its own driver model that's supposed to make writing drivers really easy and they should work on all platforms that Darwin suports).

    IANAC and ISAHANADDC (I Am Not A Coder and I Sure As Hell Am Not A Device Driver Coder).

    --

  • That would be cool, but that reminds me of another point I've always wondered about... Most clock radios have a 9v battery for time backup. Works well. I've even seen a couple of VCRs with something like this. Why not all VCRs (people seem to have so much trouble programming them), or in this case, microwaves. Maybe just a light rechargable built in. That's all you need (though I would love it if all the clocks in my house (including the analog clocks) were all synched to cesium...
  • I've spent two months working on a Business Plan on the same exact thing but with SLP instead of UPnP. Now I'm going to have to go see what this UPnP stuff is all about then rewrite parts of it.

    Security isn't too big a deal, you just need to be careful how you go about it. I plan on using a good firewall(is there one???), NAT(Network Address Translation) and DHCP using 10.x.x.x IP addresses (the 10.x.x.x network is unroutable over the Internet). This makes it so that the devices on the network can't directly communicate to the 'net without the NAT server and nothing can speak directly to that device. Plus you only need 1 valid IP address to run the entire network.

    Well, off to do more research for my Business Plan... And hope this doesn't scare off VC money.

    Ps. Anyone want to float me $5 mill or so for my startup? :)
  • UPnP has several IETF drafts [upnp.org], and SLP does not cover the Auto-IP [ietf.org] solved problem.

    I do like the fact that SSDP [ietf.org] utilizes XML [ietf.org] to encode the service data, this makes it extremely flexible.

  • I can just imagine in three years time. A micro$oft spokesperson issuing a statement about how this system is perfectly safe and secure.. that this recent rash of political figures having there gas ovens/furnace turn themselves on but not light for 3 hours late at night was not the work of hacker terrorists.....
  • by Anonymous Coward
    If you don't have an idea what UPnP is, I'd suggest you watch the UPnP summit, happening right now, and being multicast at http://www.upnp.org

    Very interesting stuff.

    Honeywell just showed a UPnP HVAC system.
    Intel just showed a Broadband Gateway control-able via UPnP, and a UPnP media (MP3) server device.
    Lantronix just showed a UPnP Barbeque (seriously!), and motion detector.
    And right now, Broadcom is showing a DVD system that sends DVD content over a home network (Hmmm, that will piss of the MPAA!), and is being controlled by a pocket PC. They're trying to show their technology around QOS.
  • by mholve ( 1101 )
    Is it just me or isn't it a little funny/ironic that Intel chose to announce this while at Microsoft? :)
  • That would be cool, but that reminds me of another point I've always wondered about... Most clock radios have a 9v battery for time backup. Works well. I've even seen a couple of VCRs with something like this. Why not all VCRs (people seem to have so much trouble programming them), or in this case, microwaves.

    One small problem with this is with time zones. My VCR can auto-set its clock via XDS time data that is transmitted on certain channels, and while this has the potential to be a convenient feature, I often find myself having to adjust the clock one hour back. I live in CST and the VCR likes to set itself to EST. No, there isn't a way to tell it what time zone I'm in. Yes, this feature can be disabled, but for some reason it keeps reenabling itself.

    Point is, a similar feature in microwaves/other household items can be handy, but can also be a pain.


    =================================
  • Ahemm..... I already have a linux-based network in my living room. Also in my basement, soon in the kids rooms, etc.

    But, anyway, PnP has worked, and worked well, right out of the box in the past. The machine was called the Apple Macintosh, remember that one? (I should note here that although I've spent a lot of time with macs, I hate the interface. Why should I trashcan diskettes to eject them? Stupid paradigm) Every Apple peripheral I ever hooked up worked right off the bat just fine. Some 3rd party stuff took a little finagling, but nothing comparable to trying to get a non-PnP Sound Blaster to work in a 386.

    --Charlie
  • Well, according to some theories, you'd have the whole house net as a private net, and have them all sync from the same box on the network (firewall/router?). I could see that EST/CST problem... But at least then when they say "coming up at 8" it actually *would* be 8... according to the tv. When I lived on the East Coast, I nearly had myself convinced that everyone should just use EST/EDT throughout the lower 48. Now that I'm in MN, I still think that once in a while. Base all time of of NYC. The only was to live.
  • What about device drivers, though? As others have mentioned, the idea of UPnP is nice for connectivity, but it seems there would still be the need for OS-specific drivers. Will UPnP be accompanied at some point by a platform independent driver architecture?
  • >Now all we need is an opensource Linux version of 'OilChange' with no
    >subscriptions fees. (For those of you who don't know, OilChange
    >monitors your system's drivers and checks the manufacture's websites
    >for periodic updates and will automatically download/install new
    >drivers).

    What the hell for? The Windows "Driver or DLL Of The Week" game doesn't really apply to Linux or the BSD's.
  • Interesting, if lopsided, view.

    1) Just because a company with a history of some half-baked concepts is implementing it, doesn't mean it will be bad. MSCHAPv2 is "secure enough" to foil most attacks. And their proprietary Kerberos increases the security if Win2k networks greatly, even if it's as interoperable with the original Kerberos as a dead pigeon.

    2) I doubt they will do a "member of IP address" thing you mention. Likely it some proprietary network, like a NetBIOS that isn't tunneled (such a beast existed back in the 1980s). The "UPnP" specification probably contains this and other information beyond simple "handshaking."

    As for the security issues, this product is targetted at private LANs which speak a probably non-TCP/IP protocol. While I personally would tend towards public key handshaking with blowfish transport encryption (as well as notification of the user of most actions), I tend towards the paranoid side WRT my encryption and privacy :-) Chances are it won't matter to the home user, as it'll "just work" and work fairly well (if you believe the UPnP claims).
    ---
  • I assume you didn't do your own plumbling or elecrical cabling etc ...Surely I didn't mine.

    Maintenance is a problem, however. An intranet which would require more than a couple of intervention per year would be prompty dumped in the waste bin.

    But the big problem is that people shall find *useful* and convenient things to do with an home intranet. I mean really useful. Not just 'look ma, here is a snapshot of the roast in the oven'.

    Now I can see how a family with two [ or more ] internet-active kids would like an intranet which allows them to share the ISP connection. But most of the other things I ear when talking of inetconnected network appliances do not make much sense to me.

  • Let's see ...
    Toaster + Computer interface + Bluetooth + Speaker + Mad programmer = a Talky Toaster !
    Now all we need is for somebody to come up with plans for a scutter!
  • Linksys just recently added IPSec Passthru to their beta firmware for the router. Do you have any idea what its use is?

    Refrag
  • I dunno, this sounds like Jini [sun.com].

    Can anyone comment on the relative merits of the two technologies?

    IANAC (I Am Not A Coder) but this just sounds like a rehash of the same concept, except it's supposed to work with Intel hardware only.
    --
  • Thw Wired article was pretty cool, and hopefully UPnP will work better than the Plug and Pray of MS' USB stuff for Win98. This is the ultimate way to get Linux more widely accepted. Of course, people will not necessarily know they are using Linux, but since there stuff will actually work it doesn't matter. If the AOL/Gateway Network Computer could impliment this, it could not be easier for most people to use Linux and get onto the Internet.
  • As my husband said on GeekPress [geekpress.com]: I hope this works better than MS's plug-n-pray.

    One question: Will this get around the "where's the device driver?" problem that Linux faces? Or will every uPNP device still need a specifically developed Linux driver? (I suspect that later.)

    -- Diana Hsieh

  • Intel made the announcement at a UPnP summit at Microsoft in Redmond, Wash.

    Hahahhahaha. Enough said. :)
  • This just seems to be a logical realm for Linux. The OS (not just for appliances either) should not be the focus, the Aps should. How often does Windows get in the way of doing something useful? It carries too much baggage due to M$'s "Three sizes cover everything" mentality.
  • by drinkypoo ( 153816 ) <drink@hyperlogos.org> on Thursday June 15, 2000 @05:59AM (#1000126) Homepage Journal

    As far as I can tell, the difference here is that UPnP is likely to go somewhere. :)

    I think that Sun opened their mouth too soon on some of their favorite technology concepts, like having everything in your house speaking java and doing the Jini thing. They should have come up with a large number of prototype devices and a slick UI before ever saying anything; Microwave (This is the easiest, since controlling a microwave basically comes down to bringing ONE circuit high or not), toaster, oven (Preferrably with a camera in it so I can look at my roast), and so on.

    Also, jumping on top of linux support is an excellent move. New JDKs have been slow to appear on linux, I can only assume that new implementations of Jini will be as well. Linux has made huge inroads into the embedded and realtime markets, and ignoring its value as the OS for appliances is too big a mistake to be forgiven. I know that Sun has their own OS to worry about, but they can't make Linux go away, and they had better learn to play well with others.

  • I don't like the idea... PnP has never really worked, it has always been a mess. Adding TCP/IP to PnP will only make it a distributed mess.

    A printer must still have its OS-specific drivers. A scanner? same story. Yes, the peripherials will tell you where they are, and that's a plus... But I don't think our problems will end when everything is automatically recognized.

    Much to the opposite.

    But anyway, users want to be fed in the mouth... Why don't they include a slave techie with each sold system?
  • Isn't that listed as one of the signs of the Second Coming? If we see Micro$oft releasing a bug-fix only, free upgrade of Windows, run for the hills and pray to whatever gods or device drivers you worship! ;)

    -TBHiX-

  • What do you mean by "Three sizes cover everything"?
  • by teraflop user ( 58792 ) on Thursday June 15, 2000 @06:03AM (#1000130)
    The irony is that uPnP is sponsered in part by Microsoft, and that Intel made the announcement at the Microsoft sponsered forum on the Redmond Campus.

    See the announcement here [newsalert.com], and the meeting publicity material on upnp.org [upnp.org].

  • Very true, but it's also obvious. It doesn't mean that some steps shouldn't be taken in this direction, however - you've got to walk before you run and other such cliches.

    --
    These are *MY* opinions.
  • by GrayMouser_the_MCSE ( 192605 ) on Thursday June 15, 2000 @06:03AM (#1000132)
    This definitely bring linux one more step closer to universal use. Anything that can conceal the underworkings of the OS and network configurations is a definite plus (so long as it can be easily bypassed by those who know what they're doing).

    With Gnome and KDE you can have a predefined desktop GUI ready to go on installation. Now you'll be able to get your printers and scanners hooked up automatically. All that's left (if this hasn't been done already) is something similar to MS Internet Connection tool that acts as mini dhcp/dns/proxy server to automatically set up the network.

    Realistically, if Corel's office2000 proves itself (or some other similar office product) and network set up becomes transparent, Linux should gain a huge jump in use.

    Even the peripheral adding will give many home users a much easier time installing the system (I know I had a heck of a time getting my network card working with linux on my first install...)

    Yes, it doesn't do much for people who can already network and do manual installs, but for people who are content with things to just work right with no fuss/no muss, this a *good thing*

  • Could she use linux to run her house? Sure. My TiVo runs linux and has one of the BEST interfaces I've seen on anything.
  • by Anonymous Coward on Thursday June 15, 2000 @06:43AM (#1000134)
    Although the names sound familiar, UPnP is not related to Plug and Play.

    UPnP is also not a Microsoft technology, there are many companies that support the UPnP forum, and yes Microsoft is one of the bigger supporters.

    Similar to both HAVi and Jini, UPnP is just one of the computing industries attempts at simplifying the network of "connected appliances" that will be filling your homes in the future.

    Sony pushes HAVi because they want the CE devices to be king.
    Sun pushes Jini because they want to make licensing money.
    Microsoft and Intel push UPnP because they want an IP based, computer friendly, device discovery and control protocol that doesn't require the fees Sun is demanding.

    Intel is releasing this Linux UPnP SDK because they don't want UPnP to be seen (by the world) as MS only, and they don't want to see Microsoft control the spec, by being the only OS that supports it (when Millennium ships).
  • a printer's drivers can not be embedded in the printer, e.g how linux operates the printer is very different than how windows operates the printer, the driver has to be different for the two OSes.

    However on a machine devoloped only to run one OS, e.g. an appliance would need only one driver and it could be built in, but everything in an appliance is built in anyway.


    Devil Ducky
  • Does anybody have any ideas for obfuscating or introducing security to these new "connectivity" options?

    Just put a firewall between your network and the outside, and deny your fridge access!
    Of course this means that AMD will come out with a version of your fridge that runs faster and cheaper.
    And your Cyrx Toaster will have a tendacy to burn toast since it cooks it with the CPU instead of heating coils.

    To me this is interesting, but I agree with some of the questions of practicality. The best I can see is for notification of events.

    Would it be nice to have your fridge email you when it beaks down, so you know to empty it before everythign spoils. Or have your stove let you know your food is burning, while you are on your computer?

  • The party line is that Intel is an OS agnostic. If supporting Linux/BSD with Open Source will help sell more hardware, then that is what they will do.

    I'm suprised to hear that. One would think that Intel's affinity for industrial secrecy and occasional propensity to market manipulation would have extended to matters outside their normal bailiwick. At the very least, the historical relationship between Intel, IBM, and M$ sets some sort of precedent. OTOH, it is a historical relationship...

    -TBHiX-

  • Is it just me, or isn't this whole PNP thing run my microsloth. If a protocol is going to be used to make devices talk to each other cross platform, from different manufactures, in different settings, with different hardware, shouldn't the protocol for telling them how to talk to each other be developed openly so that it is secure, reliable and flexible? Microsoft's original idea of PnP didn't work. We all know the popular phrase Plug 'n Pray. So what is there to make me belive that if I plug in my couch, it will actually find my coffee machine, huh? I don't want to open my foot-rest and have a coffee pot launched at high velocity towards me from the kitchen because the coffee machine mis-understood the couch's command to open the foot-rest.
  • I can't believe this post disappeared from this thread (but I can't find it since I reloaded - bug? Troller grudge? lost packet?), so I'm responding here:

    The original post said:
    Jeez, that's what I really want. A product called - "You Pee 'N' Pee"

    Don't knock it. An earlier version of this technology ("B.E.E.R.") has enjoyed thousands of years of popularity among geeks/early adopters, and the general/neophyte market segments. It's often one of the first protocols a student learns in college.

    It has already found widespread integration with home entertainment centers (TV viewing, VCR movies, and music) and was a vital enhancement to live sports presentations even before the advent of widespread televised sports.

    BEER is already widespread in the contemporary American kitchen, though underutilized in that setting. (It can take much of the tedium out of elaborate preparation, for examples) Still, would Thankgsgiving be Thanksgiving without Beer? Not in most households!

    Beer is widely used for communications, so much so that some people rarely communicate without using it. It may be the most widely used peering method in modern life. I-buy-U (a beer) is one popular application and Eff-U/Eff-Me often relies on it as well.

    While efforts to integrate it into automotive settings have been -er- 'disappointing', the active developer base who try every day to make this work considerable exceeds the total Linux user base. Changes to the automotive infrastructure have long been planned to make this a more secure activity.

    There are, however, concerns. Integrating child protection features on the USE, PROVIDER, and SERVICE models has raised serious concerns. Tighter access controls have traditionally failed, and if you think NetNanny and CyberParent are worrisome, check out a nanny or parent on Beer.

  • not to mention that whoever it is uses my favorite band's name as an id. they get SOOO many points there alone.
  • Actually, it would be tres cool to have your TV pop up an icon telling you when your toast or home-bake pizza was done.

  • PnP has never worked, eh?

    Let me take a quick inventory of my latest motherboard full of PnP goodness... let's see... LAN card, sound card, video card, SCSI card, video card, six-zillion-button mouse, and even a USB Nikon camera.

    Hell, even most monitors are PnP these days.

    Bitch about MS or Windows all you want, but at least restrict yourself to facts, or reasonable facsimilies thereof. And you kids wonder why the profit-making world still snickers when somebody says the L-word...

  • The actual irony is that you Linux-types are getting so worked up over this, but old Netcraft sez upnp.org is running IIS4. ;)
  • errr...and if i knew i wouldn't have to ask, would i? thank god you didn't mean it though...i was just about to start crying.
  • Intel's been helping with Mozilla for a long while now. For instance, look at all the bugs [mozilla.org] that have been assigned on Bugzilla to people with @intel.com addresses. It wouldn't surprise me in the least if Intel also had people working on other open source projects.

    They have to be working with the source with this type of box, or as some people have pointed out, the living room box just wouldn't be stable enough. Perhaps we should stop thinking of Intel as a hardware company...their marketing mantra of "building blocks of the internet" includes software too.

    -Merlyn42

  • This is something linux could definatly benifit from. A form of plug and play that not only detects the new device, but will goto a internet repository of drivers, and select the correct one based on a device id provided by the new device.

    The Woz suggested something similar to this once, his idea was based on including the driver in some rom on the device. A good idea, but limited because then mfg cost goes up to include a memory chip on the device, and if the driver shipped with the unit is buggy, that can be a problem.

    With an internet based driver warehouse, you could always get the latest driver. There would need to be a new architecture for this, a standard driver interface, that would be compatable across all kernel versions, and possibly even multiple os's. I think there are a few things in the works like this, but if you're going to do it, do it right and make it robust as possible. This is the open source community, there is no reason we should accept any less.

    In this age where net connections are nearly standard, and high speed connections are making there way to the majority, there is no reason we shouldn't make this a reality. And it doesn't have to be LIMITED to downloading drivers over a network, it should also be able to load them the old fassion way from a disk.

    just my 2cents.

    NightHawk

    Tyranny =Gov. choosing how much power to give the People.

  • Once a device's type is known (e.g. printer, camera, HVAC system, etc.), you know how to invoke it's commands because all devices of a given type implement the same command set.

    A UPnP device makes an API available by using the control protocol of UPnP. UPnP control commands are invoked over the network using SOAP. See the UPnP specs at www.upnp.org for details.

  • You may be onto something here... Could Bill Gates actually be Japanese?

    Refrag
  • >>except it's supposed to work with Intel >> hardware only No, UPnP is not tied to Intel hardware in any way. See www.upnp.org.
  • The ZDNet article says this, "UPnP, originally developed by Microsoft Corp., is a technology that allows a number of different kinds of devices to communicate via a network using standard protocols, such as TCP/IP."

    So does Micro$oft control the UPnP spec?

    And if so, I am sure that they would be happy to have a Linux implementation of their specification. Which undoubtedly they would "improve" shortly after a Linux implementation was done.
  • One question: Will this get around the "where's the device driver?" problem that Linux faces? Or will every uPNP device still need a specifically developed Linux driver? (I suspect that later.)

    I'm sure it will still require OS-specific drivers. Plug-and-play basically lets the peripheral tell the OS "Ok, I'm here! Now do something with me."
    --
  • Plug & Play has acheived some stability, but I can just imagine conflicts of PnP device names and the nightmare it's going to cause... still plug and pray? Or will linux finally make sense of automatic hardware configuration?

    ----

  • So, I'd say Linux has been doing fine in my family room for 3 ro 4 months now.
  • by NakNomik ( 21692 ) on Thursday June 15, 2000 @06:06AM (#1000154)
    Here's intels site for upnp:
    http://www.intel.com/ial/upnp/
  • by Ace905 ( 163071 ) on Thursday June 15, 2000 @06:09AM (#1000155) Homepage
    ""UPnP allows (devices) to participate in the same economy ... with the end user not having to understand how to set up an IP address,"

    "Microsoft is building UPnP into its future Windows releases, starting with its Windows Millennium Edition."

    With the future of device connectivity being, "Now you can receive emails from your fridge! And so can the companies that stock it!" -- doesn't this pose a major security risk for 2 reasons.

    1) Microsoft is implementing it.

    2) Interaction between all devices is handled by a standard protocol and each device is seen as a member of the same IP address?

    Does anybody have any ideas for obfuscating or introducing security to these new "connectivity" options?

  • Just today I said something to our MCSE when he was talking about how hard it was to use linux and how it would never take hold in the market place. Now for the funny part, he was at the time installing these cool new network cameras that he has been telling everyone about. Check out this site the camera has linux as it's operating system. http://www.axis.com
  • > The irony is that uPnP is sponsered in part by Microsoft, and that Intel made the announcement at the Microsoft sponsered forum on the Redmond Campus.

    But the real question is, did they insist on covering up all the the iMacs?

    --
  • 1) Microsoft is implementing it

    I'd call that a security issue - but then, you don't need to use their implementation. I for one won't.
    The protocol specs are out in the open, so they can't hide anything evil in there.

    2)Interaction between all devices is handled by a standard protocol and each device is seen as a member of the same IP address?

    That's one of the reasons why we need IPv6 at some time - every device could get its own.

    Besides, it's always your option not to connect the fridge to the outside world while still having it connected to your local network and selected trusted IPs (control the connections to the outside world with ipchains or something similar)...
  • There has been userland PnP for some time, and it's in the 2.3 series kernel. PnP was even enough to get devfs into the kernel.

    So uPnP seems to be some sort of extension of regular PnP. Will this new stuff fit with what we already have, or will it require substantial ripup and roadmap pain?
  • there's no way i'd let linux into my family room...imagine the heinous damage that a beowulf cluster of natalie portmans with hot grits down their pants could do to impressionable young minds

    ...not to mention the annoyance caused by having to stop Phantom Menace halfway through to recompile your kernel with modularized Portman support.
  • "...we'll still have a problem with the drivers."

    Maybe, but the SDK allows manufacturers a good tool for creating drivers for their upnp devices. I suspect that with the introduction of tools like this, manufacturers will be better at supporting linux since they don't have to do so much from scratch.
  • by Raven667 ( 14867 ) on Thursday June 15, 2000 @07:05AM (#1000163) Homepage

    SLP (Service Locator Protocol) seems to already be a good way to detect and locate services automatically on a network. It is a defined standard in RFC2608 [isi.edu] and is used as the basis many networking technologies already (NetWare 5, MS W2K) and can be easily and consistantly configured to support any service type imaginable (it uses URI/URLs as its encoding system). There is already two SLP libraries for Linux, one from Sun under the SCSL and one from Caldera under the GPL [openslp.org].

    Actually, in my limited research, this looks like a really neat way to generally advertise services. You would be able to create something like the Network Neighborhood or an NDS tree (Using SLP and LDAP together) for UNIX. Being able to plug into a network and instantly find out exactally what hosts have what services available without any configuration on your part (info for master DA server can be sent via DHCP) without all the messiness that the SMB browser protocol has (SMB, against all odds, is actually considered a protocol! Ha!) is a Really Good Feature(tm).

  • Jeez, that's what I really want. A product called -

    "You Pee 'N' Pee"

    Almost as good as drinking a lot of water in a short period of time.
  • Just what you've all been waiting for, the UPnP Toaster. Now you too can *actually* asign your toaster an IP address and have it make toast for you.
    No longer is this just a joke, it's a way of life!
    damn.. sometimes we just have some weird technology.


    nerdfarm.org [nerdfarm.org]
  • The party line is that Intel is an OS agnostic. If supporting Linux/BSD with Open Source will help sell more hardware, then that is what they will do. Like this [intel.com] and this [intel.com].
  • Let`s not look so black-n-white at that.

    Both really should be possible.

    -- fm

  • It may not be perfect at first, or ever, but it's still better than nothing.

    M$ PnP was awfull at first, but it's gotten a lot better if you stick with name brand components. I find a lot of PnP issues envolve the end-user not reading the installation directions first--as it to preload new drivers, etc..

    Now all we need is an opensource Linux version of 'OilChange' with no subscriptions fees. (For those of you who don't know, OilChange monitors your system's drivers and checks the manufacture's websites for periodic updates and will automatically download/install new drivers).

    Iota
  • One question: Will this get around the "where's the device driver?" problem that Linux faces? Or will every uPNP device still need a specifically developed Linux driver? (I suspect that later.)

    It is in my understanding that there's no longer a need for drivers on your computer. The driver would be embedded in the device.

    Think about it, nobody updates drivers for a printer so why couldn't those be embeded in the machine?

  • First the judge breaks it up coz he liked the netscape interface and now intel uses its product to screw it. THERE IS JUSTICE IN THIS WORLD!!!!!

"I've finally learned what `upward compatible' means. It means we get to keep all our old mistakes." -- Dennie van Tassel

Working...