The purpose of the plugin appears to be to allow browsing of advertised http servers.
OTOH, the name resolution is available to all applications on the host, so one can, for instance, use Firefox to browse a site hosted on a MacOS X system provided you know the advertised name of the system. I have no problems seeing the servers on my Linux box (exported using Howl).
I expect it won't be long before someone writes a Firefox XPI which uses Bonjour to allow the same functionality as the IE plugin.
The truth is that there are different schools of thought as to what makes the perfect handtop.
One school believes that it should be a full-fledged portable PC in its own right, incorporating additional PIM functionality. This is the idea which drove a number of designs from the "golden age" of the PDA including the Z-PDA, Newton, and HP LX series. I would argue that the Zaurus ald probably the Psion are from this school. Lots of emphasis on screen larger screens, keyboards, and connectivity is seen here.
The other school holds that the PDA is an extension of the desktop system and, as such, is more of a means of carrying around critical pieces of information (schedule, contacts, etc.). I/O is a function of how to get information into the PDA to carry it back to the PC and data synchronization is the major technology. The Palm OS handhelds probably best represent this school, though the PocketPC's seem to have fallen in here as well.
As for me, I'm used a Zoomer, OmniGo 100, various Newtons, an HP LX-200, and a Palm III. Except for the Palm, the problem has always been data sync which is, for me, a big issue. I curently use a Palm IIIxe which really suits my humble needs well (good sync, long battery life, cheap plentiful accessories (though I still want to get the GPS for it:-)) and will probably ultimately replace it with another Palm.
Heck, go back a bit further and you get the original Gateway Profile- AMD K6/2 400mhz, 15" LCD, built-in 10/100 ethernet, USB, and modem, 2 PC Card slots, and a laptop (tray) CD-ROM or DVD and floppy.
Essentially, it was a laptop flipped into a tablet and put on a pedestal (with the USB ports in the pedestal)
Kind of cool box, though... my nephew still has one and I'm still hoping his mom's firm will retire the one's they are using as Citrix clients.
Ironically, Connectix did briefly make a version of RanDoubler for the PC. IIRC, it was very buggy and quickly killed off.
From its description, Hare appears to combine the functionality of RamDoubler and other utility called MemOptimizer. Similarly, the same company makes a utility called Zoom which sounds a lot like the old StartupDoubler utility for the Mac.
the tone of the register was rather mocking, considering the segway drivers a bunch of rich-asses with to much time on their hands
Which sounds a lot like the traditional view of polo players.
What I thought was interesting was the number of tumbles people were taking off of the Segways, especially considering how much of the design is there to *prevent* that from happening.
Okay, help me out here... I thought that Solaris was basically SVr4 Unix with a bunch of Sun extensions (OpenWindows, etc.). If so, then isn't the core OS tied up somewhere in the whole Novell/Caldera/SCO mess?
Except that the 802.11b vendors seem to have some hardening against microwave ovens built into the drivers and firmware.
I think the scary part of this is supposed to be the fact that one can bring down the network using nothing more than off-the-shelf hardware and a little custom software. Worse, it's hardware that is indistinguishable from what a legitimate user might have.
Let's say, for instance, that I want to bring down the hotspot at my local Starbucks. It would probably be suspicious (or at least funny looking) if I whipped out a modified AP or some kind of UHF transmitter. OTOH, nobody would even notice if I pulled out an iPaq, tapped a couple of times on the screen, and *poof* the network halted.
Now scale up a bit and say I connect to a decent antenna, sit out in the parking lot, and point this at your office... or your hospital...
I'm suprised that no one has mentioned the screen setup that was in the suite in "The Apprentice". From all appearances, they were using a large (42"?) plasma screen as a desktop monitor!
Oddest darn thing... I kept wondering if it was even readable at that distance.
Thus it would seem that if you disagree with the GPL (which SCO has stated publicly on several occasions) you have no right to software licensed under the GPL. However I post to/. and thus IANAL.
Hmm... Is paragraph 5 meant as a statement on whether one accepts the GPL as a concept (which is implied by the nMap action) or as the license for a specific package (nMap vs., say, the Linux kernel).
Admittedly, SCO is in a position where it seems self-contradictory because it so decries the GPL. But I'm not sure that really prevents them from agreeing to distribute one or more packages by that license provided they abide by the GPL in the case of that product.
Actually, I think it has a sort of perverse logic (albeit a nearsighted one). If I understand it correctly, the idea is that when a patch is released, it opens up knowledge of a hole. This is similar to the whole argument about when to release info on a security hole.
The problem with this reasoning is that it assumes the only people writing exploits are lazy/clueless enough to wait for someone to tell them what to exploit. It ignores the fact that there is a community of hackers out there actively looking for the holes.
From the description of Replay Radio, it sounds like it would make for a neat project to add stream buffering and TiVO-like pause/replay/ff to Winamp or XMMS.
Let's see... implement the goback button as a skip back one MP3 frame... buttons to jump to beginning and last frame of buffer...
My own take on this was to discover an NPR station putting out a Shoutcast stream (WPSU) and use streamripper (http://streamripper.sourceforge.net) combined with a cron job. Works well except for the fact that WPSU doesn't put program info in its metainfo.
The Groklaw warning echoes thoughts I had as soon as I heard the comments on the radio about how a competitor could use MS's IP in a competing product.
That said, the conspiracy theorist in me wonders if it's possible that Microsoft orchestrated the leak themselves in the hopes of polluting one or more Open Source products (e.g., Linux Kernel, Wine, etc.) and then later launching a series of SCO-style lawsuits.
Think about it...
Release portions of an older baseline which have already been fixed/replaced (to minimize the hacker potential), but are algorithmically distinctive enough to be recognized if they were used in another product.
Wait for a well-meaning open source user to submit one of the pieces as a patch to the Linux kernel
Scan new kernels for distictive algorithm.
When found
Launch expensive lawsuit at RedHat, Lindows, et al. Demand injunctions against distribution, damages, etc.
Or maybe, I've just read too much SCO-IBM coverage here.
--John
Two years ago, I was given a Latitude XP which had been surplussed by my sister-in-law's company. Good condition for a 5-yr old laptop except that it was missing one of the flipdown feet.
For $10, Dell sold me a replacement foot.
OTOH, the worst has got to be Acer. No parts and no disassembly instructions available.
It was hinted at. I think what it boils down to is that they got religion.
Which would explain a lot of their motivation. One has to wonder if the Cylons see themselves as, homehow, the "chosen ones" and that the extermination of humanity is an attempt to rid the cosmos of a flawed creation of a deity who achieves perfect creation in the creation of the Cylons.
I haven't seen a COE Linux environment, but based on my experience with COE Solaris, I can tell you that the answer is a bit more complicated.
Starting from a bare system, you first install the COTS (Common Off The Shelf) OS (RHAS, in this case). This will likely be a "custom" install since it will likely have some strange partition requirements.
On top of this, you would then install the COE "kernel". This is a core set of COE services, scripts, utilities, etc. Part of this process is the creation of several user accounts (sysadmin, etc) as well as a general lockdown of the box (no root logins allowed, lots of permission changes, etc.) This step will also likely involve installation of package updates to close various security holes.
From there, one would install the various "segments" (COE name for packages) needed to set the box up for a specific usage.
Personally, I'm curious to see if the COE kernel will load on top of a regular RH 8.0. I can see having RHAS for target systems, but it would be nice to be able to use the regular version as a development platform.
It seems like the question with an origins story would be, how old does The Doctor *have* to be? We see him on Earth as an old man, but is there anything which establishes that he went directly there from Gallifrey and/or how long he was there?
As for a passable Hartnell imitation... how about Patrick Stweart ala Ebeneezer Scrooge?
Something is definately bogus with Mike's so-called "review" at PSTWO.NET. Quoting from his review:
He then gave me a sheet of paper which had a scan of an Episode 2 Exhibitor Screening ticket on it, and it read "May 2nd 10 AM - I have 2 tickets if you want them." It took a while to sink in, but yes, I had just been offered 2 tickets to see Episode 2 exactly 2 weeks early!! And I'd be seeing it on the huge Westown Ultrascreen in Waukesha, WI.
The problem is... it is 9:50am EDT on May 2 and, by reckoning, the preview shouldn't even be starting for another hour.
Hmm... anyone for the Psychic Friends Movie Review Network?
Ironically, I've recently started getting spam *from* Korea, mostly adult-oriented. Unfortunately, since it is all written in Hangul (Korean language), there seems to be no way to opt out of it, since I can't read any opt-out instructions.
Firstly, the resemblance to the Akira class never bothered me- I chalked it up to form following function (i.e., an evolutionary design with similar mission profiles). Besides, the pictures on Shiporama make it look more like the Akira is an upside down Enterprise.
The exterior hull appearance of the NX-01 makes sense compared to NCC-1701 when you keep it in context historically. Basically, NX-01 is a prototype so it does not have the "finish" of later ships, also it gets most of its defeneses from a thick, polarizable hull, so gleaming finishes become a detriment. OTOH, by the time of the NCC-1701, shields (and ship technology, in general) have evolved to the point where more emphasis can be placed on aesthetics and comfort. (Look at the size of Pike's quarters.)
By the time of the Enterprise refit, however, TPTB realize that too much time is being spend repainting the hulls and so we have (again) the bare metal look seen in later Trek series.
What bothers me about the NX-01 is the lack of the secondary hull. I understand why it's not there... it's just disorienting not seeing one.
Slashdot Mirror
The purpose of the plugin appears to be to allow browsing of advertised http servers.
OTOH, the name resolution is available to all applications on the host, so one can, for instance, use Firefox to browse a site hosted on a MacOS X system provided you know the advertised name of the system. I have no problems seeing the servers on my Linux box (exported using Howl).
I expect it won't be long before someone writes a Firefox XPI which uses Bonjour to allow the same functionality as the IE plugin.
>>
Obligatory SNL reference...
"With a name like Flucker's, it's got to be good."
Denise Crosby
The truth is that there are different schools of thought as to what makes the perfect handtop.
:-)) and will probably ultimately replace it with another Palm.
One school believes that it should be a full-fledged portable PC in its own right, incorporating additional PIM functionality. This is the idea which drove a number of designs from the "golden age" of the PDA including the Z-PDA, Newton, and HP LX series. I would argue that the Zaurus ald probably the Psion are from this school. Lots of emphasis on screen larger screens, keyboards, and connectivity is seen here.
The other school holds that the PDA is an extension of the desktop system and, as such, is more of a means of carrying around critical pieces of information (schedule, contacts, etc.). I/O is a function of how to get information into the PDA to carry it back to the PC and data synchronization is the major technology. The Palm OS handhelds probably best represent this school, though the PocketPC's seem to have fallen in here as well.
As for me, I'm used a Zoomer, OmniGo 100, various Newtons, an HP LX-200, and a Palm III. Except for the Palm, the problem has always been data sync which is, for me, a big issue. I curently use a Palm IIIxe which really suits my humble needs well (good sync, long battery life, cheap plentiful accessories (though I still want to get the GPS for it
--John
Heck, go back a bit further and you get the original Gateway Profile- AMD K6/2 400mhz, 15" LCD, built-in 10/100 ethernet, USB, and modem, 2 PC Card slots, and a laptop (tray) CD-ROM or DVD and floppy.
Essentially, it was a laptop flipped into a tablet and put on a pedestal (with the USB ports in the pedestal)
Kind of cool box, though... my nephew still has one and I'm still hoping his mom's firm will retire the one's they are using as Citrix clients.
Ironically, Connectix did briefly make a version of RanDoubler for the PC. IIRC, it was very buggy and quickly killed off.
From its description, Hare appears to combine the functionality of RamDoubler and other utility called MemOptimizer. Similarly, the same company makes a utility called Zoom which sounds a lot like the old StartupDoubler utility for the Mac.
>>
Which sounds a lot like the traditional view of polo players.
What I thought was interesting was the number of tumbles people were taking off of the Segways, especially considering how much of the design is there to *prevent* that from happening.
Okay, help me out here... I thought that Solaris was basically SVr4 Unix with a bunch of Sun extensions (OpenWindows, etc.). If so, then isn't the core OS tied up somewhere in the whole Novell/Caldera/SCO mess?
Or am I missing something here?
Except that the 802.11b vendors seem to have some hardening against microwave ovens built into the drivers and firmware.
I think the scary part of this is supposed to be the fact that one can bring down the network using nothing more than off-the-shelf hardware and a little custom software. Worse, it's hardware that is indistinguishable from what a legitimate user might have.
Let's say, for instance, that I want to bring down the hotspot at my local Starbucks. It would probably be suspicious (or at least funny looking) if I whipped out a modified AP or some kind of UHF transmitter. OTOH, nobody would even notice if I pulled out an iPaq, tapped a couple of times on the screen, and *poof* the network halted.
Now scale up a bit and say I connect to a decent antenna, sit out in the parking lot, and point this at your office... or your hospital...
I'm suprised that no one has mentioned the screen setup that was in the suite in "The Apprentice". From all appearances, they were using a large (42"?) plasma screen as a desktop monitor!
Oddest darn thing... I kept wondering if it was even readable at that distance.
Actually, I think it has a sort of perverse logic (albeit a nearsighted one). If I understand it correctly, the idea is that when a patch is released, it opens up knowledge of a hole. This is similar to the whole argument about when to release info on a security hole.
The problem with this reasoning is that it assumes the only people writing exploits are lazy/clueless enough to wait for someone to tell them what to exploit. It ignores the fact that there is a community of hackers out there actively looking for the holes.
From the description of Replay Radio, it sounds like it would make for a neat project to add stream buffering and TiVO-like pause/replay/ff to Winamp or XMMS.
Let's see... implement the goback button as a skip back one MP3 frame... buttons to jump to beginning and last frame of buffer...
Anybody up for writing this?
My own take on this was to discover an NPR station putting out a Shoutcast stream (WPSU) and use streamripper (http://streamripper.sourceforge.net) combined with a cron job. Works well except for the fact that WPSU doesn't put program info in its metainfo.
- Release portions of an older baseline which have already been fixed/replaced (to minimize the hacker potential), but are algorithmically distinctive enough to be recognized if they were used in another product.
- Wait for a well-meaning open source user to submit one of the pieces as a patch to the Linux kernel
- Scan new kernels for distictive algorithm.
When found
- Launch expensive lawsuit at RedHat, Lindows, et al. Demand injunctions against distribution, damages, etc.
Or maybe, I've just read too much SCO-IBM coverage here. --JohnI'll go one better...
Two years ago, I was given a Latitude XP which had been surplussed by my sister-in-law's company. Good condition for a 5-yr old laptop except that it was missing one of the flipdown feet.
For $10, Dell sold me a replacement foot.
OTOH, the worst has got to be Acer. No parts and no disassembly instructions available.
I think he means that it should probably be "whipping the company into shape".
I haven't seen a COE Linux environment, but based on my experience with COE Solaris, I can tell you that the answer is a bit more complicated.
Starting from a bare system, you first install the COTS (Common Off The Shelf) OS (RHAS, in this case). This will likely be a "custom" install since it will likely have some strange partition requirements.
On top of this, you would then install the COE "kernel". This is a core set of COE services, scripts, utilities, etc. Part of this process is the creation of several user accounts (sysadmin, etc) as well as a general lockdown of the box (no root logins allowed, lots of permission changes, etc.) This step will also likely involve installation of package updates to close various security holes.
From there, one would install the various "segments" (COE name for packages) needed to set the box up for a specific usage.
Personally, I'm curious to see if the COE kernel will load on top of a regular RH 8.0. I can see having RHAS for target systems, but it would be nice to be able to use the regular version as a development platform.
For an interesting short story tie-in, take a look at Howard Waldrop's "Heirs of the Perisphere".
t m
FictionWise has an excerpt at:
http://www.fictionwise.com/ebooks/eBook519.h
Take a look and you'll understand the connection.
>>
It seems like the question with an origins story would be, how old does The Doctor *have* to be? We see him on Earth as an old man, but is there anything which establishes that he went directly there from Gallifrey and/or how long he was there?
As for a passable Hartnell imitation... how about Patrick Stweart ala Ebeneezer Scrooge?
>>
Hmm... anyone for the Psychic Friends Movie Review Network?
And thanks to this movie, they (along with Linus, Stallman, etc) all have Bacon Numbers of 3.
Ironically, I've recently started getting spam *from* Korea, mostly adult-oriented. Unfortunately, since it is all written in Hangul (Korean language), there seems to be no way to opt out of it, since I can't read any opt-out instructions.
Anybody else have this problem? Any suggestions?
The exterior hull appearance of the NX-01 makes sense compared to NCC-1701 when you keep it in context historically. Basically, NX-01 is a prototype so it does not have the "finish" of later ships, also it gets most of its defeneses from a thick, polarizable hull, so gleaming finishes become a detriment. OTOH, by the time of the NCC-1701, shields (and ship technology, in general) have evolved to the point where more emphasis can be placed on aesthetics and comfort. (Look at the size of Pike's quarters.)
By the time of the Enterprise refit, however, TPTB realize that too much time is being spend repainting the hulls and so we have (again) the bare metal look seen in later Trek series.
What bothers me about the NX-01 is the lack of the secondary hull. I understand why it's not there... it's just disorienting not seeing one.