I also bought RAM for my dual G4 from Crucial... it works just fine with the latest firmware. However, I bought the RAM that was specifically labelled for G4 PowerMacs, which was like $10 more than the generic PC one (for a 256MB DIMM).
There are no precedences, the permissions are checked for your currend UID and GID, and if what you're trying to do isn't permitted to either, you get an error.
No, the most specific permission takes precedence: user > group > other. For example, if I'm user khym in group people, I will not be able to access this file:
The Mach microkernel runs on PowerPC... Apple didn't have to port all of FreeBSD's kernel to PPC. Anyways, as Apple's developer info says, "The BSD portion of the Mac OS X kernel is derived from FreeBSD, a version of 4.4BSD that offers advanced networking, performance, security, and compatibility features."
>> but Jon Bosak of Sun was the leader of the working group creating XML...
> Well ain't that just fascinating. Jon Bosak of Sun created SOAP?
> Funny, I don't see his name on the credits.
Ah, I see you have reading comprehension problems. Perhaps you might try reading SoftwareJanitor's post slowly and carefully. Especially the part that says "creating XML". Then go and read this. Pay careful attention to the part that says:
Jon Bosak, Sun (Chair)
> I rest my case, you don't know what you are talking about.
On the other hand, if I remember correctly, I switched from whatever non-X windowing system Sun was using (can't remember the name) directly to X with TWM sometime in the late 80's.
Sun-stools:) (okay, suntools:) Yeah, I hated that too... switched to X11 and twm and used that for many years. Then about a year or so ago, I got tired of everyone having a cooler-looking X desktop than me, so I use windowmaker now:)
I guess none of y'all have read the 4.4BSD daemon book... McKusick's bio mentions that he and Allman are a couple and describes their online wine cellar:)
According to the FAQ at http://linuxsh.sourceforge.net/, they're still working on a WinCE bootloader (which happens to be based on NetBSD's pbsdboot). There's a difference between Linux running on a SH3 evaluation board and Linux running on the HP Jornada.
So, if you want a free Unix for your Jornada, but can't wait for Linux, there's NetBSD. Which also happens to run on the SH4.
I used that machine for a numerical analysis course... apparently, UT made a custom OS for it to do the load-sharing (UT-2D); I assume it was based on the original OS though. The thing I remember the most about it was that it treated all files as tapes, and after you compiled your fortran program or whatever, you had to rewallx to rewind all of your files in order to read them again (if you wanted to recompile your program, for example). Rather annoying:) That machine was later renamed dinosaur.cc.utexas.edu, and served as a print server for a while, before it was finally decomissioned.
Like the TCP/IP stack? Take a look at tcp_stdurg. You can use it to turn off the RFC793 behavior and instead use the incorrect BSD behavior. You have to do this to interoperate with the broken BSD derived stacks out there. man 7 tcp on a linux box, and read the RFC if you don't believe me.
Heh, maybe you should read it... BSD uses the RFC793 behavior, but that was changed in RFC961.
RFC793 says, "The urgent pointer points to the sequence number of the octet following the urgent data."
RFC961 came along a few years later and amends that, saying, "Urgent: Page 17 is wrong. The urgent pointer points to the last octet of urgent data (not to the first octet of non-urgent data)."
BSD didn't invent its own standard; it followed the standard that was in place at the time. As to why they don't switch to the new standard, I don't know... backwards compatibility, I suppose.
I think NetBSD's package system works on Linux... (and Solaris too). The non-NetBSD support isn't well-documented though, and I haven't tried it myself... Take a look at the messages in this thread if you're interested.
Today, Network Appliance, Sun, and a few others hide TRAM technology in their core storage products. Network appliance uses TRAM in a different way, though. They hold the NFS rpc requests in memory, not the disk blocks. Their WAFL filesystem is journaled and can come up quick on its own, so it doesn't require the TRAM. They use it to respond to requests quickly, yet still give the client the semantic that the operation is 'safe' or committed to disk. To deal with the journaled filesystem, they use RAID striping.
It wasn't a RamFAST though... that's a SCSI card. You're probably thinking of the RamKeeper (IIgs-only, plugged into the memory expansion slot, and your memory card piggybacked onto it), or the RamFactor with RamCharger (worked on the II+ and up, battery was a big external thing).
Well, I was hoping that'd go without saying, but maybe I'm expecting too much:) A Win3.x app that doesn't run on Win3.x isn't worthy of being called a Win3.x app... it's a broken, buggy, non-app:)
There were representatives from both parties present at each counting table. They only counted votes they could agree on, those where the intent was clear.
No, that's not exactly how it worked... if both parties agreed on a ballot, it was counted. If they disagreed, it was put into a pile of disputed ballots, which were then reviewed by the canvassing board. (Which in the counties in question were either all Democrat, or majority Democrat). Personally, I thought the Palm Beach canvassing board (and especially that judge, whose name I now forget) were really fair. Of course, Gore wasn't happy with 'em and kept taking them to court to try to force them to count the ballots the way Gore wanted 'em counted.
FYI, California and Utah are both part of the same country. Yet, they have different laws. Why do you think that all laws are uniform throughout a country?
Well, while the code hasn't made it into any releases yet, NetBSD supports SMP in some form on x86, alpha, macppc, and sparc. Perhaps others too...
I also bought RAM for my dual G4 from Crucial... it works just fine with the latest firmware. However, I bought the RAM that was specifically labelled for G4 PowerMacs, which was like $10 more than the generic PC one (for a 256MB DIMM).
However, gasoline vapor in air will. In Real Life, even. That's how internal combustion engines work.
How about you fix it yourself?
No, the most specific permission takes precedence: user > group > other. For example, if I'm user khym in group people, I will not be able to access this file:
----rw-rw-1 khympeople95 Apr 15 04:05 somefile
Well, there's Taiwan, although that depends on whether or not you consider it a country, or just a Chinese province.
The Mach microkernel runs on PowerPC... Apple didn't have to port all of FreeBSD's kernel to PPC. Anyways, as Apple's developer info says, "The BSD portion of the Mac OS X kernel is derived from FreeBSD, a version of 4.4BSD that offers advanced networking, performance, security, and compatibility features."
Bzzt. Microsoft doesn't want you to think any such thing. Personal Web Server
The OS X userland code is based closely on a recent FreeBSD distribution.
Actually, you have that backwards... I've heard that the kernel is based on FreeBSD. As for the userland stuff:
[localhost:~] root# uname -a
/bin/cat:
/usr/bin/who: /bin/* /sbin/* /usr/bin/* /usr/sbin/* | wc -l /bin/* /sbin/* /usr/bin/* /usr/sbin/* | wc -l /bin/* /sbin/* /usr/bin/* /usr/sbin/* | wc -l
Darwin localhost 1.3 Darwin Kernel Version 1.3: Thu Mar 1 06:56:40 PST 2001; root:xnu/xnu-123.5.obj~1/RELEASE_PPC Power Macintosh powerpc
[localhost:~] root# ident `which cat`
$NetBSD: cat.c,v 1.18 1998/07/28 05:31:22 mycroft Exp $
[localhost:~] root# ident `which who`
$NetBSD: who.c,v 1.6 1997/10/20 03:20:29 lukem Exp $
[localhost:~] root# grep -l NetBSD
134
[localhost:~] root# grep -l FreeBSD
8
[localhost:~] root# grep -l OpenBSD
15
The majority of the binaries have NetBSD RCS IDs...
[localhost:~] root# ident `which ps`
/bin/ps:
$FreeBSD: fmt.c,v 1.13 1998/12/07 10:25:48 bde Exp $
$FreeBSD: keyword.c,v 1.23 1999/01/26 02:38:09 julian Exp $
$FreeBSD: print.c,v 1.33 1998/11/25 09:34:00 dfr Exp $
$FreeBSD: ps.c,v 1.25 1998/06/30 21:34:14 phk Exp $
ps is one of the few binaries from FreeBSD... perhaps because it's looking at kernel data structures?
They do exist though... for example, http://www.intur.net/agreement.htm
> Well ain't that just fascinating. Jon Bosak of Sun created SOAP?
> Funny, I don't see his name on the credits.
Ah, I see you have reading comprehension problems. Perhaps you might try reading SoftwareJanitor's post slowly and carefully. Especially the part that says "creating XML". Then go and read this. Pay careful attention to the part that says:
> I rest my case, you don't know what you are talking about.
The same could be said for you.
NetBSD: All your platform are belong to us.
(or NetBSD: All your architecture are belong to us.)
Sun-stools :) (okay, suntools :) Yeah, I hated that too... switched to X11 and twm and used that for many years. Then about a year or so ago, I got tired of everyone having a cooler-looking X desktop than me, so I use windowmaker now :)
I guess none of y'all have read the 4.4BSD daemon book... McKusick's bio mentions that he and Allman are a couple and describes their online wine cellar :)
So, if you want a free Unix for your Jornada, but can't wait for Linux, there's NetBSD. Which also happens to run on the SH4.
I used that machine for a numerical analysis course... apparently, UT made a custom OS for it to do the load-sharing (UT-2D); I assume it was based on the original OS though. The thing I remember the most about it was that it treated all files as tapes, and after you compiled your fortran program or whatever, you had to rewallx to rewind all of your files in order to read them again (if you wanted to recompile your program, for example). Rather annoying :) That machine was later renamed dinosaur.cc.utexas.edu, and served as a print server for a while, before it was finally decomissioned.
Heh, maybe you should read it... BSD uses the RFC793 behavior, but that was changed in RFC961.
RFC793 says, "The urgent pointer points to the sequence number of the octet following the urgent data."
RFC961 came along a few years later and amends that, saying, "Urgent: Page 17 is wrong. The urgent pointer points to the last octet of urgent data (not to the first octet of non-urgent data)."
BSD didn't invent its own standard; it followed the standard that was in place at the time. As to why they don't switch to the new standard, I don't know... backwards compatibility, I suppose.
I think NetBSD's package system works on Linux... (and Solaris too). The non-NetBSD support isn't well-documented though, and I haven't tried it myself... Take a look at the messages in this thread if you're interested.
Yeah, the article said that :)
It wasn't a RamFAST though... that's a SCSI card. You're probably thinking of the RamKeeper (IIgs-only, plugged into the memory expansion slot, and your memory card piggybacked onto it), or the RamFactor with RamCharger (worked on the II+ and up, battery was a big external thing).
Well, I was hoping that'd go without saying, but maybe I'm expecting too much :) A Win3.x app that doesn't run on Win3.x isn't worthy of being called a Win3.x app... it's a broken, buggy, non-app :)
Don't Windows 3.x apps run under Windows 3.0 or 3.1 by definition?
The OpenBSD SMP branch is probably just waiting for code from NetBSD (where SMP is being worked on.)
No, that's not exactly how it worked... if both parties agreed on a ballot, it was counted. If they disagreed, it was put into a pile of disputed ballots, which were then reviewed by the canvassing board. (Which in the counties in question were either all Democrat, or majority Democrat). Personally, I thought the Palm Beach canvassing board (and especially that judge, whose name I now forget) were really fair. Of course, Gore wasn't happy with 'em and kept taking them to court to try to force them to count the ballots the way Gore wanted 'em counted.
FYI, California and Utah are both part of the same country. Yet, they have different laws. Why do you think that all laws are uniform throughout a country?