Re:That's NOT a 15-pin midi d-sub.
on
X On OSX Now Free
·
· Score: 1
I'm pretty sure that the DVI signals go through the ADC port and that the D-sub connector really is standard VGA, but who cares? I don't want a Cube and I don't care if other people want to go around bashing it.
Ignoring the obvious stuff about hax0red antivirus updates...
Groove looks pretty cool. First the bad news: Right now it's Windows-only, the protocols are undocumented, and there may be patents involved. But the good news is that these guys seem to have a good attitude. They're definitely in it for the long haul, actually thinking their design through (unlike Napster, Gnutella, etc.), and putting in security that would make a cypherpunk proud. And they're promising to release protocol docs so that other apps can interoperate with it.
IPv6 is designed for gross mismanagement.:-) Seriously, they realized that it's much easier to just use longer addresses and waste most of them than to try to conserve artificially scare address space and end up with messy routing tables.
One example of this is the fact that almost all subnets in IPv6 are/64; of course no subnet has that many machines, but it makes things a lot easier.
Also, the powers that be recently carved out a huge chunk of address space for 6to4, so that every IPv4 address can have a/48.
This was mentioned in a previous article about Indrema (I'm too lazy to look it up): if a game is not certified, it will not run. Even if you write your own game, you have to get it certified to run it on your own Indrema console (unless you buy the expensive "developer" box).
If you really want an experience in strong typing, try out Haskell. I know the type checker kicked my ass quite a few times back in freshman CS days...
$800-1000? Even assuming that HomeRF equipment is free, you'd need a pretty big network to have that much of a price difference considering that 802.11 base stations are only $300 and cards are only $100.
That's an interesting idea, but I guess it depends on the definition of a file's "data". If the data is everything that you can get from read(), then storing all the attributes in the file data will cause most apps to think files are corrupted. OTOH, if attributes are contained in a new kind of file data that isn't visible to read(), then I don't see how that's much different from a system like BFS or XFS where an inode can hold as many named attributes as you want.
You can have two different preferred apps for two different files of the same type, because there is a (optional) preferred app attribute on every file.
Actually, permissions are necessary for insecurity - if you didn't have them, people would just be limited to working with their own files and never be aware of any others.
This is true, but sometimes users want to share files. I think per-process namespaces (as in Plan 9, Inferno, Spring, EROS, etc.) are a good compromise that allow some things to be private and some to be shared.
BeOS has creator types (except they're called something like "preferred applications"). Now that I think about it, BeOS probably also uses BFS indices to find an app given its signature; this is cool because the filesystem's indices never get out of sync like the Finder's desktop database can.
The basic problem with file permissions under Unix is that information vital to the use of the file is not stored in the data that you get with read()/write(). This makes it impossible to cleanly store this data on another system or to transfer it. Yes, you can "encode" (or "tar") it, but if you do that, why not just store the encoded version on the disk, and remove a large and complex mess from the OS?
In fact there is absolutly no reason for timestamps to be stored in any way that the OS sees. The data is only used by user-level programs.
My point is that the decision of what metadata should be stored natively by the filesystem is mostly arbitrary; file types are as reasonable as mod times. (Permissions are an exception because they're necessary for system security, but I couldn't resist.)
Slashdot Mirror
I'm pretty sure that the DVI signals go through the ADC port and that the D-sub connector really is standard VGA, but who cares? I don't want a Cube and I don't care if other people want to go around bashing it.
If only the G4 cube had an SVGA connector...
Then what's this "15-pin mini D-Sub VGA connector" on the spec sheet?
Free clue: It has both the weird ADC connector and a standard SVGA connector.
DNS issues...Currently, I can type 192.168.1.100 to get to a machine if the DNS is down... what happens with IPv6? 123.456.789.111.123.456.789.0?
:-)
IPv6 addresses are in hex... I'll let you decide if that's an improvement or not.
Ignoring the obvious stuff about hax0red antivirus updates...
Groove looks pretty cool. First the bad news: Right now it's Windows-only, the protocols are undocumented, and there may be patents involved. But the good news is that these guys seem to have a good attitude. They're definitely in it for the long haul, actually thinking their design through (unlike Napster, Gnutella, etc.), and putting in security that would make a cypherpunk proud. And they're promising to release protocol docs so that other apps can interoperate with it.
This interview at the O'Reilly Network seems to have some interesting technical bits.
Hey, you forgot to include the obligatory link to The X-Windows Disaster. :-)
If you want to use X and Quartz apps at the same time, get WeirdX. It's not fast, but it works.
Yeah, using VNC just so you can run X apps is a kludge; why not just use WeirdX?
Conveniently, there are two articles about this very topic, including instructions for FreeBSD, Debian, and Windows.
IPv6 is designed for gross mismanagement. :-) Seriously, they realized that it's much easier to just use longer addresses and waste most of them than to try to conserve artificially scare address space and end up with messy routing tables.
/64; of course no subnet has that many machines, but it makes things a lot easier.
/48.
One example of this is the fact that almost all subnets in IPv6 are
Also, the powers that be recently carved out a huge chunk of address space for 6to4, so that every IPv4 address can have a
I don't think the cellular phone companies are planning to use mobile IP; I think they already have optimized mobility protocols.
Hardware prices will always drop, but you can't just put things off forever.
This new Amiga uses a PPC processor and supports AGP; what northbridge are they planning on using?
If games are open source, no one will pay subscription fees to play them.
IIRC
This was mentioned in a previous article about Indrema (I'm too lazy to look it up): if a game is not certified, it will not run. Even if you write your own game, you have to get it certified to run it on your own Indrema console (unless you buy the expensive "developer" box).
Strong typing? Pascal? Compiler ass-kicking? LOL!
If you really want an experience in strong typing, try out Haskell. I know the type checker kicked my ass quite a few times back in freshman CS days...
And if ECMA publishes C# as a standard, you're going to have to find a new reason why it is doomed.
$800-1000? Even assuming that HomeRF equipment is free, you'd need a pretty big network to have that much of a price difference considering that 802.11 base stations are only $300 and cards are only $100.
What do you think they compile Mac OS X with? The changes aren't yet merged into the official GCC tree, but they are out there.
That's an interesting idea, but I guess it depends on the definition of a file's "data". If the data is everything that you can get from read(), then storing all the attributes in the file data will cause most apps to think files are corrupted. OTOH, if attributes are contained in a new kind of file data that isn't visible to read(), then I don't see how that's much different from a system like BFS or XFS where an inode can hold as many named attributes as you want.
You can have two different preferred apps for two different files of the same type, because there is a (optional) preferred app attribute on every file.
Actually, permissions are necessary for insecurity - if you didn't have them, people would just be limited to working with their own files and never be aware of any others.
This is true, but sometimes users want to share files. I think per-process namespaces (as in Plan 9, Inferno, Spring, EROS, etc.) are a good compromise that allow some things to be private and some to be shared.
BeOS has creator types (except they're called something like "preferred applications"). Now that I think about it, BeOS probably also uses BFS indices to find an app given its signature; this is cool because the filesystem's indices never get out of sync like the Finder's desktop database can.
See BRoster::FindApp() for some details.
My point is that the decision of what metadata should be stored natively by the filesystem is mostly arbitrary; file types are as reasonable as mod times. (Permissions are an exception because they're necessary for system security, but I couldn't resist.)
Yeah, I don't like swap partitions either; I'm not sure why all the Linux distributions I've seen are using them.