Like the SUV driving "soccer mom" who is concerned about the environment and recycles her husband's beer cans but drives a vehicle that gets 7 mpg.
Well, more like 11 MPG, if we're talking SUV's and US Environmental Protection Agency city mileage figures. If she truly wanted to maximize her fuel inefficiency, she'd be driving this VW roadster. (Yes, it's from VW.)
Boutique lifestyles of the nouveau riche. Wealth coming out of their eyeballs but morally bankrupt.
The 60's generation, "meet the new boss, same as the old boss".
I suspect most of "the 60's generation" aren't in that economic class (or above it).
This was the first time-based side channel attack I learned. Within Minix you initially could place a password right at a page boundary and try and login. If there was a page fault before the password was rejected, you knew you had the right character right before the page bound.
That dates back before Minix - Butler Lampson's Hints for Computer System Design speaks of a similar issue in Tenex. (Look for "Tenex" in that paper for the example.)
...it's disappointing to find out that he is not an ex-UC Davis alumnus as the summary implies
The summary speaks of "of a group of ex-UCD photonics researchers"; there's more than one UCD on the planet, and this one is probably University College Dublin.
The founders were from UCD, according to the "about Intune" page. ("Intune was founded in 1999 by two college graduates, John Dunne and Tom Farrell. They were performing research on tunable lasers and their network applications in University College Dublin, Ireland.")
(I hope, for UCD's sake, that their Web designers aren't ex-UCD. Not only do they appear to think that "company" is spelled "copmany", the site is a Flash-infested mess that requires you to pop up several layers of menus, by clicking on little + signs, for each member of the management team whose biography you want to see.)
IIRC, ELF was a SCO standard for x86 *nix interoperability so quite possibly
ELF was originally developed by AT&T for System V Release 4, so it's an "SCO standard" only by virtue of SCO buying out UNIX System Laboratories from AT&T.
To get this working in Microsoft Outlook, you have to install the MobileMe Control Panel for Windows. The hidden gem in all of this is that Apple plans to bring this CalDAV connectivity to Outlook users on MobileMe.
Did they explain how the first sentence necessarily implies the second?
Yeah, I know because Apple nevergivesanything back to the open source community at all!
To be fair, "developed by Apple" in "CUPS is the standards-based, open source printing system developed by Apple Inc. for Mac OS® X and other UNIX®-like operating systems." in the CUPS home page means "Apple hired the guy who created CUPS, and it's now an Apple project", not "Apple were the original developers of CUPS".
The source code is posted on Apple's open source site and is pushed upstream to the GCC repository on a branch. If you want to port the Apple branch to create a cross-compiler from a Linux host, go for it. Nobody's stopping you....
You'd then also need the assembler and linker, but they're also available on opensource.apple.com (look under "Developer Tools" for cctools, which includes the assembler, and ld64).
Then you'd need the libraries with which to link them. That would involve getting Mac OS X binaries somehow.
Then you'd want to try to run your program to make sure it actually works. That'll be a little tricky without a Mac.
And isn't there a question in Topology or metaphysics about whether you can test whether the universe is curved, from the vantage point of a observer trapped within the curved universe?
To how many decimal places? (Yes, it has them. The claim on 137.com that "One hundred thirty-seven is the value of a number called the fine-structure constant." is not true:
XNU operating system is build by Mach 3.0 microkernel,
Well, not all that "micro", really - very large amounts of "kernel" functionality run in kernel mode rather than in userland servers (there are some userland servers that the kernel talks to, but the vast majority of the stuff that runs in kernel mode in UN*Xes with a "monolithic" kernel also run in kernel mode in Darwin (and in Windows NT, speaking of another OS people sometimes say has a "microkernel").
You can get XNU operating system in Darwin package, what actually is XNU + Darwin development tools.
Actually, Darwin is XNU + a pile of kexts (the same thing that's called, for example, "loadable kernel modules" in Linux) plus a bunch of user-mode libraries (starting with libSystem, for which read "libc" in most other UN*Xes) plus a bunch of user-mode programs, including but far from limited to the command-line development tools (Darwin doesn't include Xcode in its entirety).
XNU = Operating system with Mach 3.0 microkernel
No, that's Darwin.
Mac OS X = Apples software system with lots of open source software (CUPS, Apache etc) and XNU operating system running all that.
Don't Journaled filesystems themselves use b-trees?
File systems that use b-trees use b-trees; file systems that don't use b-trees don't use b-trees. Both types of file systems can be journaled or not journaled.
Considering the current hate between Adobe and Apple, I'm a bit surprised myself.
Considering that Mac OS X's Preview app has supported PDFs since Day One, and that iPhone^H^H^H^H^H OS has supported showing PDFs since at least 2.0 (maybe even 1.0), I'm not in the least surprised.
CDMA is 3G. You could even make a decent argument that 3G is CDMA.
A bit more precisely:
2G radio access technologies - time division multiple access as used by GSM and some non-GSM systems, code division multiple access as used by cdmaOne
3G radio access technologies: code division multiple access as used by, for example UMTS (W-CDMA) and CDMA2000
So, at least as I understand it, most if not all of the major 3G air interfaces use code division multiple access. Unfortunately, "CDMA" is used not only to refer to the code division multiple access scheme to let multiple users share the same radio channel, but is also used to refer to the particular protocol stacks cdmaOne and CDMA2000, which include not just the low-level details of how code division multiple access is used, but also protocols layered above the radio layer, many of which probably don't care about the low-level radio details.
...and apple still like to pull that video card lock in carp[sic] so you pay $250-$300 for a old video that cost about $50 - $100 more then the pc ver of it.
Yeah, because it is in Apple's best interests to have peripherals for their computers more expensive? Apple would love it if they could get more video card companies to support their systems with proper support for EFI and drivers that are not abysmal. As Apple's market share increases the market makes this more profitable for peripheral makers, but economy of scale takes a lot to overcome.
Most Apple computers aren't exactly ready to have third-party video cards added. Any Mac with "Book" in the name isn't going to have much of a third-party market for video cards, and I'm not sure about the iMac or Mac mini, either. That leaves the Mac Pro and Xserve, neither of which are, I think, high-volume machines by Apple standards.
Anyone notice Linux share the same syntax of UNIX? Do you know how old UNIX is?
To start Linux even old people like me need to know some history of XENIX, UNIX, SCO, NFS... some of those things remain unformatted text base, console type (not VT100).
GUI is good, but the back is still those things, that why Mac OSX hide them all. Linux need to clean up those history and simplified those things.
I'm not sure what you mean by the "syntax", but:
Mac OS X shares the same libc-level syntax as UNIX (even if it's called libSystem on OS X);
it shares the same command-line interface as well;
the GUI user, and the developer using Cocoa, doesn't have to see that - but to what extent does somebody using, or developing for, say, GNOME or KDE on Linux have to see that?
Anyone that wants to tinker with kernels as a hobby is much better breaking open FreeBSD (a microkernel architecture reduces the learning curve since there are well-defined, stable interfaces between the subsystems)
If so, then why are you recommending FreeBSD, which has a monolithic kernel?
Therein lies the problem. Why were you running an OS originally written for x86 (as in 8086) on a RISC processor?
What, somebody was running MS-DOS or Windows 95 on Alpha? (Windows NT was originally written for the Intel 80860, and later MIPS, and for 32-bit x86, according to this article.)
The Alpha was supposed to run Unix - Tru64 Unix in particular. Running in a proper 64bit environment the Alpha was an incredible chip.
Well, Unix plus OpenVMS, but they both supported a 64-bit environment.
To you it is a computer with wireless. It isn't to the vast majority of consumers, to them it's a phone, PDA and content delivery platform (music and video).
I.e., "the vast majority of consumers" who own an iPhone have never gotten any third-party apps for it (and don't even use Mail or Safari)?
Well if multi tasking is implemented as a series of call backs so that any process that is waiting on data is not consuming clock cycles
iPhone OS is a UN*X; multi-tasking is ultimately implemented as "calls that wait for something to happen end up making a system call and the process blocks".
then there should be no more drain when "multitasking" then when running one application.
...unless, for example, an app is continuously updating the display, showing an animated ad, or displaying a game screen, or.... Perhaps the app would be told "you're going into the background, stop updating the screen (but don't necessarily stop playing audio)".
s far as I can tell using the backgrounder on my jail broken iphone when not actively working most programs still consume cycles.
What indicates that they're consuming cycles, rather than just blocked in a system call?
So almost all of this could be fixed if the wait() call is not properly implemented in the lib.
As per another comment of mine, iPhone OS being a UN*X, wait() is the call you use if you've started a subprocess (fork()/vfork(), posix_spawn()) and you wait to wait for it to exit. There is no single call that is the call to wait for something to happen - there are a whole bunch of blocking system calls such as read(), recv(), recvmsg(), connect(), etc., as well as the usual wait-for-events calls such as select(), poll(), and kevent(), plus the Mach messaging calls. Most apps probably use higher-level APIs that are built atop them.
+5,000,000,000,000 Informative. Do people really think that, unlike what happens on every other frigging UN*X on the planet, processes on iPhone OS would spin in a busy loop when they're waiting for something to happen, rather than just blocking?
Or are you thinking of, say, msleep(), the kernel interface in Darwin for blocking on an event? If that's busted, Mac OS X won't be very happy, either.
Slashdot Mirror
Nearly every Apple *fan* that I've met has been a pretentious prick.
You can probably replace "Apple" with "$PLATFORM" there and the statement will continue to be true.
Like the SUV driving "soccer mom" who is concerned about the environment and recycles her husband's beer cans but drives a vehicle that gets 7 mpg.
Well, more like 11 MPG, if we're talking SUV's and US Environmental Protection Agency city mileage figures. If she truly wanted to maximize her fuel inefficiency, she'd be driving this VW roadster. (Yes, it's from VW.)
Boutique lifestyles of the nouveau riche. Wealth coming out of their eyeballs but morally bankrupt.
The 60's generation, "meet the new boss, same as the old boss".
I suspect most of "the 60's generation" aren't in that economic class (or above it).
This was the first time-based side channel attack I learned. Within Minix you initially could place a password right at a page boundary and try and login. If there was a page fault before the password was rejected, you knew you had the right character right before the page bound.
That dates back before Minix - Butler Lampson's Hints for Computer System Design speaks of a similar issue in Tenex. (Look for "Tenex" in that paper for the example.)
...it's disappointing to find out that he is not an ex-UC Davis alumnus as the summary implies
The summary speaks of "of a group of ex-UCD photonics researchers"; there's more than one UCD on the planet, and this one is probably University College Dublin.
The founders were from UCD, according to the "about Intune" page. ("Intune was founded in 1999 by two college graduates, John Dunne and Tom Farrell. They were performing research on tunable lasers and their network applications in University College Dublin, Ireland.")
(I hope, for UCD's sake, that their Web designers aren't ex-UCD. Not only do they appear to think that "company" is spelled "copmany", the site is a Flash-infested mess that requires you to pop up several layers of menus, by clicking on little + signs, for each member of the management team whose biography you want to see.)
FDM, really? Wouldn't you be using CWDM or DWDM (Course/Dense Wavelength Division Multiplexing) be the right choice with fiber?
Frequency-division multiplexing and wavelength-division multiplexing are the same thing, given that wavelength = speed / frequency.
No, read the POSIX interface standard (or in this case specifically the ELF executable standard).
...which isn't part of POSIX (OS X, for example, uses Mach-O, not ELF, but is still not only POSIX-compliant but licensed UNIX(R).
IIRC, ELF was a SCO standard for x86 *nix interoperability so quite possibly
ELF was originally developed by AT&T for System V Release 4, so it's an "SCO standard" only by virtue of SCO buying out UNIX System Laboratories from AT&T.
To get this working in Microsoft Outlook, you have to install the MobileMe Control Panel for Windows. The hidden gem in all of this is that Apple plans to bring this CalDAV connectivity to Outlook users on MobileMe.
Did they explain how the first sentence necessarily implies the second?
Yeah, I know because Apple never gives anything back to the open source community at all!
To be fair, "developed by Apple" in "CUPS is the standards-based, open source printing system developed by Apple Inc. for Mac OS® X and other UNIX®-like operating systems." in the CUPS home page means "Apple hired the guy who created CUPS, and it's now an Apple project", not "Apple were the original developers of CUPS".
The source code is posted on Apple's open source site and is pushed upstream to the GCC repository on a branch. If you want to port the Apple branch to create a cross-compiler from a Linux host, go for it. Nobody's stopping you....
You'd then also need the assembler and linker, but they're also available on opensource.apple.com (look under "Developer Tools" for cctools, which includes the assembler, and ld64).
Then you'd need the libraries with which to link them. That would involve getting Mac OS X binaries somehow.
Then you'd want to try to run your program to make sure it actually works. That'll be a little tricky without a Mac.
And isn't there a question in Topology or metaphysics about whether you can test whether the universe is curved, from the vantage point of a observer trapped within the curved universe?
Topology, unlikely; curvature isn't a topological property - you can change the curvature of a space without changing its topological properties. Geometry, yes, and, in fact, surfaces (as opposed to lines) can have intrinsic curvature, independent of how they look from outside. No need to summon up metaphysics.
I want to add 137 to it as well.
To how many decimal places? (Yes, it has them. The claim on 137.com that "One hundred thirty-seven is the value of a number called the fine-structure constant." is not true:
iOS actually use XNU operating system.
iOS uses the XNU kernel.
XNU operating system is build by Mach 3.0 microkernel,
Well, not all that "micro", really - very large amounts of "kernel" functionality run in kernel mode rather than in userland servers (there are some userland servers that the kernel talks to, but the vast majority of the stuff that runs in kernel mode in UN*Xes with a "monolithic" kernel also run in kernel mode in Darwin (and in Windows NT, speaking of another OS people sometimes say has a "microkernel").
You can get XNU operating system in Darwin package, what actually is XNU + Darwin development tools.
Actually, Darwin is XNU + a pile of kexts (the same thing that's called, for example, "loadable kernel modules" in Linux) plus a bunch of user-mode libraries (starting with libSystem, for which read "libc" in most other UN*Xes) plus a bunch of user-mode programs, including but far from limited to the command-line development tools (Darwin doesn't include Xcode in its entirety).
XNU = Operating system with Mach 3.0 microkernel
No, that's Darwin.
Mac OS X = Apples software system with lots of open source software (CUPS, Apache etc) and XNU operating system running all that.
That's Darwin (which includes CUPS and Apache; see, for example, the list of components in Darwin) plus a bunch of non-open-source software (some kexts, Carbon, Cocoa, some other libraries, Finder, iTunes, etc.). Oh, and, at least according to The Open Group, it's a UNIX.
iOS = Apples software system to mobile devies with XNU operating system running all.
That's (a subset of) Darwin ported to ARM, plus a bunch of non--open-source software (Springboard, Mobile This That And The Other Thing, etc.).
Don't Journaled filesystems themselves use b-trees?
File systems that use b-trees use b-trees; file systems that don't use b-trees don't use b-trees. Both types of file systems can be journaled or not journaled.
it doesn't do i386
The LLDB Homepage claims otherwise:
LLDB is known to work on the following platforms, but ports to new platforms are welcome:
Considering the current hate between Adobe and Apple, I'm a bit surprised myself.
Considering that Mac OS X's Preview app has supported PDFs since Day One, and that iPhone^H^H^H^H^H OS has supported showing PDFs since at least 2.0 (maybe even 1.0), I'm not in the least surprised.
CDMA is 3G. You could even make a decent argument that 3G is CDMA.
A bit more precisely:
So, at least as I understand it, most if not all of the major 3G air interfaces use code division multiple access. Unfortunately, "CDMA" is used not only to refer to the code division multiple access scheme to let multiple users share the same radio channel, but is also used to refer to the particular protocol stacks cdmaOne and CDMA2000, which include not just the low-level details of how code division multiple access is used, but also protocols layered above the radio layer, many of which probably don't care about the low-level radio details.
...and apple still like to pull that video card lock in carp[sic] so you pay $250-$300 for a old video that cost about $50 - $100 more then the pc ver of it.
Yeah, because it is in Apple's best interests to have peripherals for their computers more expensive? Apple would love it if they could get more video card companies to support their systems with proper support for EFI and drivers that are not abysmal. As Apple's market share increases the market makes this more profitable for peripheral makers, but economy of scale takes a lot to overcome.
Most Apple computers aren't exactly ready to have third-party video cards added. Any Mac with "Book" in the name isn't going to have much of a third-party market for video cards, and I'm not sure about the iMac or Mac mini, either. That leaves the Mac Pro and Xserve, neither of which are, I think, high-volume machines by Apple standards.
Anyone notice Linux share the same syntax of UNIX? Do you know how old UNIX is? To start Linux even old people like me need to know some history of XENIX, UNIX, SCO, NFS ... some of those things remain unformatted text base, console type (not VT100).
GUI is good, but the back is still those things, that why Mac OSX hide them all. Linux need to clean up those history and simplified those things.
I'm not sure what you mean by the "syntax", but:
Anyone that wants to tinker with kernels as a hobby is much better breaking open FreeBSD (a microkernel architecture reduces the learning curve since there are well-defined, stable interfaces between the subsystems)
If so, then why are you recommending FreeBSD, which has a monolithic kernel?
Compiler for Windows
Therein lies the problem. Why were you running an OS originally written for x86 (as in 8086) on a RISC processor?
What, somebody was running MS-DOS or Windows 95 on Alpha? (Windows NT was originally written for the Intel 80860, and later MIPS, and for 32-bit x86, according to this article.)
The Alpha was supposed to run Unix - Tru64 Unix in particular. Running in a proper 64bit environment the Alpha was an incredible chip.
Well, Unix plus OpenVMS, but they both supported a 64-bit environment.
To you it is a computer with wireless. It isn't to the vast majority of consumers, to them it's a phone, PDA and content delivery platform (music and video).
I.e., "the vast majority of consumers" who own an iPhone have never gotten any third-party apps for it (and don't even use Mail or Safari)?
Well if multi tasking is implemented as a series of call backs so that any process that is waiting on data is not consuming clock cycles
iPhone OS is a UN*X; multi-tasking is ultimately implemented as "calls that wait for something to happen end up making a system call and the process blocks".
then there should be no more drain when "multitasking" then when running one application.
...unless, for example, an app is continuously updating the display, showing an animated ad, or displaying a game screen, or.... Perhaps the app would be told "you're going into the background, stop updating the screen (but don't necessarily stop playing audio)".
s far as I can tell using the backgrounder on my jail broken iphone when not actively working most programs still consume cycles.
What indicates that they're consuming cycles, rather than just blocked in a system call?
So almost all of this could be fixed if the wait() call is not properly implemented in the lib.
As per another comment of mine, iPhone OS being a UN*X, wait() is the call you use if you've started a subprocess (fork()/vfork(), posix_spawn()) and you wait to wait for it to exit. There is no single call that is the call to wait for something to happen - there are a whole bunch of blocking system calls such as read(), recv(), recvmsg(), connect(), etc., as well as the usual wait-for-events calls such as select(), poll(), and kevent(), plus the Mach messaging calls. Most apps probably use higher-level APIs that are built atop them.
+5,000,000,000,000 Informative. Do people really think that, unlike what happens on every other frigging UN*X on the planet, processes on iPhone OS would spin in a busy loop when they're waiting for something to happen, rather than just blocking?
I have heard that wait() is broken in the current implementation,
You mean the API for waiting for a subprocess to exit is broken in iPhone OS? launchd probably won't be very happy about that.
Or are you thinking of, say, msleep(), the kernel interface in Darwin for blocking on an event? If that's busted, Mac OS X won't be very happy, either.