| |||||||||||||
|
| |||||||||||||
up2date prior art?up2date prior art?Posted Mar 23, 2006 16:44 UTC (Thu) by chel (guest, #11544)In reply to: up2date prior art? by dskoll Parent article: Apple patents automatic software updates
Search on apt debian 1998 in google groups shows a number of hits, including a message in linux.debian.bugs.closed on Fri, 24 Apr 1998 12:07:43 +0200 (CEST) about a solved problem in "apt-get -f upgrade"
(Log in to post comments)
up2date yes, apt-get no Posted Mar 23, 2006 16:58 UTC (Thu) by JoeBuck (subscriber, #2330) [Link] up2date is prior art, apt is not. The reason is that Apple is patenting a daemon that runs in the background and alerts the user if updates are available. With apt-get, the user must invoke a command (or have a cron job do it). Honestly, though, I think that this whole class of patents should be disallowed under the "obvious to one skilled in the art" rule. The inventive step between what apt-get does and what up2date does is too small, especially when you consider apt-get invoked by a cron job.
up2date yes, apt-get no Posted Mar 23, 2006 17:37 UTC (Thu) by allesfresser (subscriber, #216) [Link] One thing that jumped out at me when reading through the patent is that the covered mechanism for user notification is only triggered when the user accesses the information for which an upgrade is available, such as when a program is opened, i.e. "A new version of WizBangApp is available. Download update now?" The actual language is as follows: "a notification component that automatically notifies said user, in response to subsequent access by the user of an item of computer information for which a notification flag has been set, of the availability of the upgrade for the accessed computer information and of any other upgrades indicated by any other notification flags set by said monitoring component" In the case of Ubuntu at least, with its Update Manager, the user is notified at times not associated with the access of the affected information. I'm not sure if this would be enough to escape the scope of this patent, but the phrase does jump out more than once. However, the patent does mention down at the bottom of the Description that "It will be appreciated by those of ordinary skill in the art that the present invention can be embodied in other specific forms without departing from the spirit or essential characteristics thereof." In other words, they'll probably try to make it fit everything that pulls updates without specific requests from the user.
up2date yes, apt-get no Posted Mar 23, 2006 18:49 UTC (Thu) by NAR (subscriber, #1313) [Link] the covered mechanism for user notification is only triggered when the user accesses the information for which an upgrade is availableI don't know how up2date works but it seems that the apt-get cronjob isn't covered by this. This patent seems to cover the issue when a web browser notifies the user (upon stumbling over a page containing a flash animation) that a new flash plugin is available.
Breadth, or exception? Posted Mar 24, 2006 1:14 UTC (Fri) by kirkengaard (subscriber, #15022) [Link] "It will be appreciated by those of ordinary skill in the art that the present invention can be embodied in other specific forms without departing from the spirit or essential characteristics thereof."
I would read that more comfortably; patents cover the form, not the idea. "Practitioners will notice that you can implement this idea in other forms."
Or I'd *like* to, but for the "... without departing from the spirit or essential characteristics thereof." It's the "essential characteristics" language that hurts my brain. How much fudge factor is that when you say "Other forms possible", but say "... that will have the same characteristics." :(
up2date yes, apt-get no Posted Mar 23, 2006 17:48 UTC (Thu) by chel (guest, #11544) [Link] If putting a job in a crontab is worth a patent, "ls /usr/bin|wc " shows over 2000 possible patents ;-)
up2date yes, apt-get no Posted Mar 23, 2006 20:38 UTC (Thu) by allesfresser (subscriber, #216) [Link] SSSSSSH! They'll hear you! And then where will we be? :-)
|
|
||||||||||||