Why does the incorrect get marked as insightful, I wonder? Because it better matches the prevailing groupthink than the truth does? Unix was developed on a standalone PDP box, and it wasn't for ages that a network was glued on. And then it wasn't redesigned with the network in mind, the network support was designed with an extension of the s[tream|ocket]s-based IPC in mind. If you want an OS designed around the network, try looking at UCB Sprite.
...so now we've got ultra-wide bandwidth combined with rapid frequency shifts. That's going to suck up big chunks of the unlicensed broadcast band at a time - I hope no-one's using a microwave (or a wireless router, especially a pre-N one) when I'm transferring my pr0n from my phone to my portable video player...
If you do that then the resource locator is still non-uniform - a direct URL into the middle of a CC transaction sequence is meaningless either way. WebObjects has the ability to store session info in a cookie, there's just no gain.
probably the genius who thought that you might not want other people to have access to, e.g. your one-click settings, your CC details, delivery address and so on. Many online stores rely on URLs accessible only upon presentation of other credentials, including but not limited to session information, valid authentication etc. The URLs are still URLs, but the resource is only accessible under restricted circumstances.
WebObjects URLs with a "/wo/" are session-based; in fact that " zf5gxeMdPL3E3KJeQG51ahhwsC4" stuff is the session ID so you can't go pasting them in places and expecting people to be able to use the URL. If they've got a "/wa/" then they're so-called direct action links, which are fine and can be transferred.
6164000
That's the number of the app instance - and is quite high in this case:-)
No, but if OpenSSH disappears then Apple lose their SSH implementation, or have to ramp up per-user OS X costs in order to fund a licensed SSH which may subsequently get used by only a few percent of their users.
Re:How To Become Root on OS X
on
Sudo vs. Root
·
· Score: 2, Informative
Or sudo -s, for that matter. The root account is disabled insofar as it can't log in - although even that's not quite true...
Hey, if we're thinking of the future, let's not use a fixed-width length field for the string at all! That way, we can never generate a string longer than the permitted length field. Let's just terminate the string by a known character sequence, and guarantee that that sequence doesn't appear in the string itself. We could use the \0 character as the terminator.
To take the specific point of MACs, if UNIX was about giving you the least privilege necessary to get your job done, then the concept of setuid (which gives you *all* the privileges available) would never have existed. Tools like sudo, solaris profiles, SEDarwin/SEBSD and the like have come up to try and plug this privilege leak but fundamentally, Unix has a binary privilege model. You either have none, or you have them all.
More generally, I think it's hard to fundamentally sum up Unix (without using one of the technical definitions, such as "something which implements SUS"); when it comes down to it it's a C language API and a set of tools which implement that API, running a multiuser multitasking OS. I think a good description would be "an OS that one person can grok"...
You've used a couple of Plan 9 and Sprite paradigms, some things which never applied to Unix[*], a load which apply to operating systems in general and an implementation artefact of GNU autoconf. I really hope that's not Unix....
[*]"least privilege" - MACs would predate setuid() if that were the case. For instance
Could you provide the argument which explains, in your opinion, the flaws of EFI? I still wish everyone had gone with IEEE1275, but I'd like to know what's up with EFI.
Well the installer does allow one of installing a particular feature, installing on first use or disabling it, and is damn fine-grained; I assumed that this was similar to what is being discussed WRT to OOo in that if a feature is disabled, it never appears in the menu and the user doesn't have to be presented with it.
It's funny, because when MS tried that with Office (having minimalist menus with only the commonly-used functionality exposed by default, and having install-on-demand features) it was called an abomination...
Currently, yes. But the argument is that if some evil superpower (which, I mean, even Canada is, these days, right?) were controlling things, then the two may diverge in interesting and nuclear-proliferation-causing ways.
I toyed with taking a portable into a couple of the lecture series on my Physics masters - my notebook of choice was the Cambridge Z88. Equation editor be damned; I found it was easy to get quick at typing equations in LaTeX "$$" environments. Take the Z88 home, squirt the file over RS232 to the Linux box, then compile your notes into a pretty PostScript (when I could be bothered; another thing Physics degrees teach you is the ability to read LaTeX equation environments).
I stopped doing it because batteries were more expensive than biros.
True. On the other hand, at the time NeXT bought Apple there was a lot more than computers to Apple. Newton PDAs, clone licensing...I'm not suggesting that the same will happen with Disney, but perhaps some spinning-off might occur.
The problem with Pyramids to my mind is that it relies so much on the "parody of our own world" idea that without some previous set-up, the movie would look like a one-trick pony. Some of the other real-world-ish stuff is far more subtle - the iconographs, clacks, and as this is "news for nerds" Hex needs a big mention too. Pyramids seems to me to be the above idea writ large.
I like the idea of Guards! Guards! being the first of the films, though I actually think that rather than concentrate on the Watch for a series, it would be good to take tangential moves for each film. For instance, you start with the Watch which probably means we've met Vetinari briefly, so take a story he controls like Going Postal next. There's a brief mention of Ridcully there, so go wildly out of sequence and let's have a UU story; maybe one where the witches get some airtime....
Slashdot Mirror
Why does the incorrect get marked as insightful, I wonder? Because it better matches the prevailing groupthink than the truth does? Unix was developed on a standalone PDP box, and it wasn't for ages that a network was glued on. And then it wasn't redesigned with the network in mind, the network support was designed with an extension of the s[tream|ocket]s-based IPC in mind. If you want an OS designed around the network, try looking at UCB Sprite.
No need to use the GNU userland - you could (in principle) have a Gentoo-esque x86-linux-bsd-freebsd system if you like.
...so now we've got ultra-wide bandwidth combined with rapid frequency shifts. That's going to suck up big chunks of the unlicensed broadcast band at a time - I hope no-one's using a microwave (or a wireless router, especially a pre-N one) when I'm transferring my pr0n from my phone to my portable video player...
If you do that then the resource locator is still non-uniform - a direct URL into the middle of a CC transaction sequence is meaningless either way. WebObjects has the ability to store session info in a cookie, there's just no gain.
probably the genius who thought that you might not want other people to have access to, e.g. your one-click settings, your CC details, delivery address and so on. Many online stores rely on URLs accessible only upon presentation of other credentials, including but not limited to session information, valid authentication etc. The URLs are still URLs, but the resource is only accessible under restricted circumstances.
WebObjects URLs with a "/wo/" are session-based; in fact that " zf5gxeMdPL3E3KJeQG51ahhwsC4" stuff is the session ID so you can't go pasting them in places and expecting people to be able to use the URL. If they've got a "/wa/" then they're so-called direct action links, which are fine and can be transferred.
That's the number of the app instance - and is quite high in this case :-)
Specifically, it's Bubble 2.0 (which is AJAX-enabled and speaks XML-RPC and SOAP)
I can't tell you how disappointed I was when I found out my Dad wasn't real; it was just Santa Claus in a funny suit.
You are a Streetfighter II programmer and I claim my five pounds.
No, but if OpenSSH disappears then Apple lose their SSH implementation, or have to ramp up per-user OS X costs in order to fund a licensed SSH which may subsequently get used by only a few percent of their users.
Or sudo -s, for that matter. The root account is disabled insofar as it can't log in - although even that's not quite true...
Hey, if we're thinking of the future, let's not use a fixed-width length field for the string at all! That way, we can never generate a string longer than the permitted length field. Let's just terminate the string by a known character sequence, and guarantee that that sequence doesn't appear in the string itself. We could use the \0 character as the terminator.
To take the specific point of MACs, if UNIX was about giving you the least privilege necessary to get your job done, then the concept of setuid (which gives you *all* the privileges available) would never have existed. Tools like sudo, solaris profiles, SEDarwin/SEBSD and the like have come up to try and plug this privilege leak but fundamentally, Unix has a binary privilege model. You either have none, or you have them all. More generally, I think it's hard to fundamentally sum up Unix (without using one of the technical definitions, such as "something which implements SUS"); when it comes down to it it's a C language API and a set of tools which implement that API, running a multiuser multitasking OS. I think a good description would be "an OS that one person can grok"...
You've used a couple of Plan 9 and Sprite paradigms, some things which never applied to Unix[*], a load which apply to operating systems in general and an implementation artefact of GNU autoconf. I really hope that's not Unix....
[*]"least privilege" - MACs would predate setuid() if that were the case. For instance
Could you provide the argument which explains, in your opinion, the flaws of EFI? I still wish everyone had gone with IEEE1275, but I'd like to know what's up with EFI.
Well the installer does allow one of installing a particular feature, installing on first use or disabling it, and is damn fine-grained; I assumed that this was similar to what is being discussed WRT to OOo in that if a feature is disabled, it never appears in the menu and the user doesn't have to be presented with it.
It's funny, because when MS tried that with Office (having minimalist menus with only the commonly-used functionality exposed by default, and having install-on-demand features) it was called an abomination...
Currently, yes. But the argument is that if some evil superpower (which, I mean, even Canada is, these days, right?) were controlling things, then the two may diverge in interesting and nuclear-proliferation-causing ways.
I toyed with taking a portable into a couple of the lecture series on my Physics masters - my notebook of choice was the Cambridge Z88. Equation editor be damned; I found it was easy to get quick at typing equations in LaTeX "$$" environments. Take the Z88 home, squirt the file over RS232 to the Linux box, then compile your notes into a pretty PostScript (when I could be bothered; another thing Physics degrees teach you is the ability to read LaTeX equation environments). I stopped doing it because batteries were more expensive than biros.
What does that make Hadrian, or Offa, or the first emperor of China then?
Granada and Carlton merged in 2005 to produce the ITV company.
They did in slashdot too.
True. On the other hand, at the time NeXT bought Apple there was a lot more than computers to Apple. Newton PDAs, clone licensing...I'm not suggesting that the same will happen with Disney, but perhaps some spinning-off might occur.
The problem with Pyramids to my mind is that it relies so much on the "parody of our own world" idea that without some previous set-up, the movie would look like a one-trick pony. Some of the other real-world-ish stuff is far more subtle - the iconographs, clacks, and as this is "news for nerds" Hex needs a big mention too. Pyramids seems to me to be the above idea writ large.
I like the idea of Guards! Guards! being the first of the films, though I actually think that rather than concentrate on the Watch for a series, it would be good to take tangential moves for each film. For instance, you start with the Watch which probably means we've met Vetinari briefly, so take a story he controls like Going Postal next. There's a brief mention of Ridcully there, so go wildly out of sequence and let's have a UU story; maybe one where the witches get some airtime....