Well, I'm sure Mac owners who want *more* RAM buy PC RAM. However, in some systems this isn't an option. For instance, you cannot open an iMac without violating the warranty... you'd need to pay an Apple tech. to put the RAM in for you... I don't know if they're restrictive about what manufacturers they're allowed to install but I could see Apple doing that;)
In any case, Apple ships computers using their own (branded) RAM... it would be cost effective to build a machine from scratch using regular PC components... you can benefit from things like the highly competitive market for memory right now, among other things.
Well, I wasn't suggesting so much that Yellow Dog would do it, but that someone else _could_ do it, and easily... the prices for these briQ nodes are OK if you're trying to conserve rackspace (i.e. a renderfarm type environment.)...
But, single system users, OTOH, would presumably fetch a better deal insofar as hardware pricing goes: for instance, a lot of cash can be saved using "PC" RAM over Apple's ridiculously overpriced RAM (PC100 or 133 RAM and Apple's RAM are basically identical-- costs aside)... also, you could make individual choices regarding hard drives, video cards, sound cards, etc.
A reasonably priced clone product would also, of course, challenge Apple to lower its prices... or offer more enticing value-adds.
Insofar as the MacOS goes, either the hardware manufacturer could ship a shrinkwrapped OS from Apple (as a parent post contemplated) or have the end consumer purchase a copy of the OS independently... a bit more hassle, but, people might be willing to do it if the price is right.
One of the biggest barriers to entry to becoming a "Mac user" tends to be the high cost of a decent system. You can get an iMac for pretty cheap, as far as things go, but, for the same price you can get a significantly more customized (& probably faster) Intel-based system.
The closed hardware platform has always let Mac users sleep easy in that all Mac hardware always has 100% plug-n-play support... but, still, there are those of us who'd like to *build* a Mac... or get a Mac with the specs of a G4 tower for significantly less...
Anyways, the site linked-to above and noticed they mentioned these briQ's are capable of Mac-on-Linux...(obviously...) but then it hit me: why not develop some superbly lightweight Linux distro that was basically just a bootloader for MacOS 8.6 (hopefully OS X eventually) -- you could avoid the annoying proprietary ROM issue, by using a software ROM legitimately from the 8.6 CD (which you buy legitimately.)
Give it a nice, graphical interface... Enter the consumer priced Mac clone...
Well... not in Canada:) Or in parts of Europe. I'd venture to say only States in the US would outlaw something of that sort. The US tends to be absurdly pro-rich, of course, so it's not so surprising.
In Canada, you can make copies of your music for personal use legally. We have a levy imposed on the sales of blank media to serve as a royalty when those tapes are used to "pirate" music.
...the brutal slaughter and ruination of innocent people's lives in the Taliban's Afghanistan or Western ignorance as to what's actually happening over there.
I mean even the harshest critics of the Taliban regime here on Slashdot are pretty much saying: "Yeah, well, that's what right wing religious nuts will do... ban the internet and treat women poorly." Poorly?
Yes, well, I'd love to see (strike that -- I possess an utter loathing to see) what you'd consider falls into the "horrendous" or "godawful atrocity" category... yanno, what with "poor treatment" being the routine public stonings, executions, rape, torture, and mind control to which women in that country are subjected daily for "crimes" as little as... oh I dunno... learning to read or perhaps leaving the house not completely coccooned in oppresive clothing and under the supervision of male relatives? Women are bludgeoned to death for that, there. Or how about the fact that women were forced out their workplaces and any property forfeit to male relatives? Or, that greatly due to this, there aren't enough health care workers in the country to help aide the sick... and there are plenty of sick, now, since the Taliban's utter mismanagement of national econmics has caused widespread famine and a total disintegration of what social services existed there. Or that suicide rates for oppressed women in Afghanistan have skyrocketed thanks to their brutal treatment. Let's not forget! of course, that non-Muslims and their homes are branded in yellow and ostracized...
If this is "poor" treatment of women and of human life in general -- I can't, to be honest, wrap my brain around your concept of what's really going on... this is, as one of my good friends once put it -- WHOLESALE FUCKING GENOCIDE. "Poor" treatment?? I've never read anything more disgusting in my life.
Good gods, I wish we in the west would get a clue. We've got a regime committing atrocities on par with the horrors of Nazi Germany and we sit back and say... Meh. Poor treatment. This too shall pass. Fuck, we're arrogant hypocrits.
Or, how about something that doesn't include the letter "K," at all? Perhaps I hold the unpopular point of view, here, but... The KDE folks with their KOffice, KDevelop, Kate, Killustrator, Kword, Konsole, Klipper, et cetera ad nauseum, is wearing this "k" motif just a little thin... don't you think?
Sure, that's possible -- but VNC doesn't do this by default. You need to install something like
x0rfbserver to do it. Basically, x0rfbserver captures the regular X framebuffer and serves it out using the RFB (Remote Framebuffer) protocol. Thus, you can bring up a presently running X session remotely using a regular VNC client -- more in the style of WinVNC. By default, Xvnc does not behave like this...
VNC is great for a lot of things: for instance, if you want to connect and control a presently running session (a la WinVNC or VNC through x0rfbserver), or if you want to, say, control an X desktop from a Mac or Windows machine that doesn't have (and you can't install) an X server. It all depends what you want to do, I suppose.
Since the machines to which you're connecting are running X clients, you might as well use X. X is a network transparent windowing system, after all, this is what it was designed to do... a rudimentary way to get started would be to SSH to the remote machine, setenv DISPLAY your_local_ip:display and run xterm.
The neat part is, of course, that your local window manager & decorations will be used -- so there's no reason to be minimalist with eye candy as is the case with VNC: window management & drawing, etc. is all done locally.
It further solves your problem with copy & paste because the remote X apps will be treated just like local ones.
Lastly, if you find the performance sluggish, there are several ways you can decrease the bandwidth neccessary to make network X possible.
Beyond SSH tunnelling (which is a good idea anyways:)), the two that spring to my mind are LBX and DXPC. LBX (Low Bandwidth X) is probably the simplest to configure & use -- it's included with XFree86 (4.x at least.)
On the remote machine, simply type:
lbxproxy -display local_machine:display:1
now, set your DISPLAY variable to:1 on the remote machine. that's that. X will now use LBX compression -- there's noting to configure locally as the local X server will automatically decompress the stream for you.
DXPC (Differential X Protocol Compressor) is a little more complicated as it requires a proxy on both sides. Search Google for setting up DXPC -- there's plenty of HOWTOs & FAQs on the subject out there.
All in all, using X for this purpose will integrate better with your local desktop as well as make the integration between your remate apps & your local ones seemless.
In Canada, you take a bachelor's degree in something (usually a BA) before applying to law school, where you earn an LL.B. You can take the bar following this.
After that there are Master's programs (LL.M.) and several avenues of doctoral study including the SJD (Juris Scientiae Doctor... which I mistook for the JD mentioned in the article), D.Jur (Doctor of Jurisprudence), DCL (Doctor of Civil Law) and the DD.L (Doctor of Laws.)
JD stands for "Juris Doctor." There are plenty of lawyers out there who don't have their Doctorate in Law. Where I'm from, at any rate, you need only your LLB (as well as other requirements, yes, but, scholastically speaking) to take the bar exam.
If this fellow expects his JD it means he's been studying law for at least 6 years and has probably earned a degree before entering law school in the first place. He's not lay:)
BRx.
Gods you fiends! Here's your changelog...
on
XFree 4.1.0 Out
·
· Score: 5
For the impatient....
Recent Changes to the XFree86 4.1 branch
Below is a recent extract from the XFree86 change log for the 4.1 branch. The full change log can be found in the XFree86 source tree (xc/programs/Xserver/hw/xfree86/CHANGELOG).
XFree86 development code can be accessed directly from the CVS repository. Information about this can be found on our CVS page.
XFree86 4.1.0 (2 June 2001)
619. Disable PCI resource conflict checking for Linux/Alpha (Jay Estabrook).
XFree86 4.0.99.902 (1 June 2001)
618. Fix Linux xf86GetPciSizeFromOS() parsing when the kernel is 64 bit
and any base or size is larger than 32 bits in magnitude (#4732,
David S. Miller).
617. Make XDarwin ddx pass up proper right and middle mouse button numbers
and fix mouse button 5 (Christoph Pfisterer and Torrey T. Lyons).
616. Restore backwards compatibility from 4.0.[2,3] to 4.1.0 for
the i810, r128 and radeon DRI drivers (Gareth Hughes).
615. Fix a problem when using patterns of horizontal lines with the mga
video overlay (#A.442, Ewald Snel).
614. Xinstall.sh updates and bug fixes (David Dawes).
613. Remove duplicate XineramaLibrary section in X11.tmpl (#4731,
Mike Harris).
612. Enable building DRI for Linux/ppc, and fix a drm-related bug
for Linux/ppc (#4728, 4730, Michel Dänzer).
611. Document Options for the r128 and fbdev drivers (#4727, 4729,
Michel Dänzer).
610. Add a BuildBindist switch which causes a file containing the XFree86
version number to be installed in ProjectRoot, include this in
the Xbin bindist tarballs, and turn on this switch in the bindist
host.def files. The purpose is to allow the installer script to
easily identify which version the bindist tarballs are (David Dawes).
609. Resync bindist and Xinstall.sh with changes made for 4.0.3 (David Dawes).
608. Fix the Shape extension's XShapeCombineMask to handle cases where
src_mask is None according to the spec. This reportedly fixes an
X server crash (#4715, Huver).
607. Make sure -UXF86DRI is after -DXF86DRI when compiling vfb/miinitext.c
(#4714, Frederic Lepied).
606. Fix ATI Radeon driver on Alpha. Seems as though the BIOS doesn't
like Re-POSTing and memory setup gets confused. (Jay Estabrook, Jeff
Weidemeier)
605. Fix build for Cygwin/XFree86 (#4711,#4713 Harold Hunt).
604. Fix problem with Xinstall.sh on Darwin 1.3.x (#A.431, Stefan Pantos).
603. Update Xinstall.sh and Darwin bindist directories to optionally
install Quartz support and to add an x86 distribution (Torrey T. Lyons).
XFree86 4.0.99.901 (29 May 2001)
602. Add missing return value for miSetPixmapDepths() (#4708,
ISHIKAWA Mutsumi).
601. Fill in the v4l man page template with some useful information (#4707,
Gerd Knorr).
600. Fix FFB OpenGL SwapBuffers (#4705, David S. Miller).
599. Work around a problem building the rstart specs doc with a symlinked
build tree (David Dawes).
598. Remove SPARC-specific byte-swapping code that would not work on older
SPARC CPUs (part of #4653, David S. Miller).
597. NULLify mapVidMem() and remove DEV_MEM #define for Linux/SPARC
(#4651, David S. Miller).
596. Fix Glint 300SX+Delta support. Add faster 500TX text acceleration
based on other code (Alan Hourihane).
595. Fixing MTRR split code (hopefully) (Egbert Eich).
594. Fixing coredump when doing vbeFree() twice: S3 Virge and C&T
(Egbert Eich).
593. Fixing HWCursor for mga driver in fbdev mode (Egbert Eich).
592. Fix xmh's use of XtNewString() with getenv (#4694, Tim Waugh).
591. Xdm/PAM fixes: leave it to PAM to observe whether or not an account
is locked, and reinitialize credentials after calling initgroups(),
because sometimes the credentials pam_setcred() gives are in the
form of group membership (#4693, Mike Harris).
590. Add an encodings file for standard box drawing characters for
VT100-compatible terminals (#4691, Juliusz Chroboczek).
589. Fix warnings when building mieq.c (#4689, Adam Sulmicki).
588. Fix some bugs in the cz and sk entried in XKB's keymap/xfree86 file
(#4692, Ivan Pascal).
587. Add 'hr' entries to XKB's keymap/xfree86 and rules/xfree86.lst files
(#4687, Nerijus Baliunas).
586. Include in shape.h to get Region typedef (#4686,
Adam Sulmicki).
585. Acceleration fixes for GLINT Permedia1 (Alan Hourihane).
584. Ensure glint driver chips don't exceed the specified virtual sizes.
(Alan Hourihane).
583. Remove all VGA'isms from the glint driver, it doesn't need them
(Alan Hourihane).
582. Support the Delta in the glint driver, needed for boards that have
the Delta connected to the rasterizer, as it acts as an arbiter for
the bus. Resolves acceleration troubles. (Alan Hourihane).
581. Add an lv entry to XKB's keymap/xfree86 file (#4685, Nerijus Baliunas).
580. Fix some typos in XKB's xfree86.lst file (#4684, Nerijus Baliunas).
579. Add DDXOSVERRORF ifdefs to the XFree86 ddx code that make use of the
OsVendorVErrorFProc feature (#4678, Michel Dänzer).
578. Convert the r128 driver's "UseBIOSDisplay" option into a more general
"Display" option (#4678, Michel Dänzer).
577. Treat GL_POINT like GL_POINTS and GL_LINE like GL_LINES in the sunffb
DRI driver (#4677, David S. Miller)
576. Fix bsdLib.rules and bsdLib.tmpl problems that show up when
X11ProjectRoot is defined (#4676, Johnny C. Lam).
575. Fix Trident XVideo colorkey at depth 15, 24 (Alan Hourihane).
574. Fix a typo in the lv XKB description, and fix things so that it gets
installed (#4675, 4679, Andris Pavenis).
573. Fix some apm driver bugs, including one that prevented acceleration
from working (#4674, Loïc Grenié).
572. Fix 555 (depth 15) palette handling in the i810 driver (#4673,
Andrew C. Aitchison).
571. [SECURITY] Fix authentication issues with mmap() on drm devices
(Jeff Hartmann).
570. Add euro locales and some other missing locales to locale.alias and
locale.dir (#4662, 4665, 4667, Mike Harris).
569. Fix Romanian XKB map (#4664, Mike Harris).
568. Spell Portuguese correctly in XKB lst files (#4663, Mike Harris).
567. Fix new ioperm calls in lnx_video.c for Alpha that are not needed
(Jay Estabrook).
566. Fix problems with assembler file dependencies when using gccmakedep
with the build (Frederic Lepied).
565. Finish DRI resync, including tdfx driver updates for textured video
support (VA Linux Systems).
564. Fix formatting of max clock reported by DDC (Marc La France).
563. Update Japanese localization of XDarwin help file (Toshimitsu Tanaka).
562. Update XDarwin man pages, help files, and version info. Add option to
build XDarwin.app bundle for deployment (Torrey Lyons).
XFree86 4.0.99.900 (18 May 2001)
561. Add an XKB description for Latvian (lv) keyboards (#A.411, Ilya Ketris).
560. Resync with DRI CVS trunk (VA Linux Systems).
559. Savage driver updates, including compiler warning fixes, document
the "ShadowStatus" option in the man page, and fix an argument
mismatch between ShadowWait and SavageWaitQueue (#4661, Tim Roberts).
558. Update the wacom driver to add a "ScreenNo" option to allow a tablet
to be attached to a screen in a multi-head setup, and to add auto-
detection of USB line and max parameters of USB tablets (#4640,
Frederic Lepied).
557. Add a README file that has information about enabling the extra buttons
on the IBM Rapid Access keyboard (#4639, Dennis Bjorklund).
556. Fix some Slovene/Slovak confusion in locale.dir/locale.alias files
(#4638, Kamil Toman).
555. New XKB keymaps for cz and sk (#4634, 4637, Kamil Toman).
554. Updates for the iso8859-2 Compose file (#4634, Kamil Toman).
553. Check V_CSYNC in the r128 driver, and fix building with R128_DEBUG
enabled (#4631, Michel Dänzer).
552. Mesa 3.4.2 (and later) import.
551. More build & warning fixes (Marc La France).
550. Fix bug that caused hardware cursors to be temporarily moved during mode
switches (Marc La France).
549. Optimise HARDWARE_CURSOR_AND_SOURCE_WITH_MASK case (Marc La France).
548. Move xf86CursorScreenRec definition into xf86CursorPriv.h
(Marc La France).
547. Fix BIOS retrievals in MGA driver (Marc La France).
546. Fix ATIProbe() for newer Rage128 and Radeon chips (Marc La France).
545. Add temporary workaround in ATI driver for interrupts that occur on
PowerPC's upon PCI master-aborts (Marc La France).
544. Update XDarwin to use fb and support Render (Torrey Lyons).
543. Back out sunleo conversion to fb. This driver is too heavily dependent
on cfb32 for a simple fb conversion (Marc La France).
542. Miscellaneous build/warning fixes (Marc La France).
541. More prep work for SunOS (Marc La France).
540. Fix libXft build on SunOS (Marc La France).
539. Another makedepend bug fix (Marc La France).
538. Fix use of xftcache utility during !UseInstalled builds (Marc La France).
Few people have the balls to walk into an office and take over a network drop. Few would be gutsy enough to jimmy the lock on a wiring closet door or cabinet.
This is precisely why the tactic is effective. So few people are gutsy enough, people don't disbelieve you when you say you're a consultant, or the Cable Company Technician, or whatever it is. Most people aren't prepared for that sort of trechery, as it were;).
The United States Government can not have Copyright Protection? What about State governments?
Here in Canada, our government can (and does) have copyright protection -- this extends to Provincial governments as well... Crown Corporations -- such as Canada Post or the Canadian Broadcasting Corporation -- may own copyrights.
Parliament can copyright under The Queen's Printer for Canada (the provinces do it under "The Queen's Printer for Ontario" or whatnot, as far as I'm aware.) For instance, there are many documents published by the Government (or by Parliament) that are free for public distribution but subject to particular terms. These documents are (c) the Queen's Printer (for Canada or for the Province.)
Presumably if the government or some entity established by Parliament released software for the public's use under the GPL the reliance on copyright would be satisfied.
MAC stands for "Media Access Control" as well, I'm sure, as any number of other things.
'Mac' cf. "Macintosh" -- Get it? Apple. Macintosh Apples. Yes, see, I'm sure you are now suitable impressed. "Mac" it is not an acronym for anything and it is certainly not meant to be capitalized. Notice how the operating system is called "MacOS" and not "MACOS" or "MAC-OS."
Just so you know:) I mean, I hate to nitpick, but, these sorts of things give me headaches.
Hm. Everything you've said *might* be true, except for the fatal flaw -- GNU/Linux is not UNIX.
I hate to come off sounding like some loathed semantics fiend, but, c'mon.
Linux is not an "operating system." At least, not alone. It is a kernel. The GNU System + Linux = a POSIX-compliant, UNIX-like, UNIX-compatible operating system. Further, GNOME is GNU, not Linux. GNOME runs on non-Linux-based operating systems.
Remember what GNU stands for, again? "GNU's Not Unix..."?
GNU/Linux isn't UNIX and doesn't claim to be UNIX. While conceptually based on UNIX, it was written from scratch. Therefore, it has no "hereditary" claim to being UNIX. Further, I don't remember it being certified by the Open Group as being "UNIX." So the claim that Linux is at all a UNIX, let alone the preferred flavour thereof, is rather silly.
This isn't really capital E "Evolution." At least in the Darwinian sense. Darwin's evolution was about how things would randomly change and the thing that was the "best" in its environment would prevail over things which were not the "best" in the same environment. Darwin's evolution was driven purely by chance, the qualitative best naturally selected because in the end it prevailed. So the quantitative best is the prevailing mutation merely because it prevails. These "evolving circuits" seem a bit more predetermined than capital E evolution has in mind. O'course, by strict dictionary evolution (that is, "the steps leading up from one thing to another.") I suppose it qualifies;)
Oh, please. If I had a quarter for every time I heard some crazy American mention taxpayers and tax dollars to secure an argument I'd be in a much higher tax bracket than I am now;)
The American tax dollars which ``founded'' the early ARPANET and the meagre impact those dollars had on the wallets of individual Americans is insignificant in comparison to the vast contributions of the US domestic private sector and the international private & public sectors. There's no comparison.
"Copyright" is the right of an author or his to print and publish his literary or artistic work, exclusively of all other persons. (That's just the loose dictionary definition.)
A trademark is a "peculiar or distinguishing mark or device affixed by a manufacturer or merchant to his goods, the exclusive use of which is recognized by law."
At the very least the intent of these mechanisms are greatly different.
A copyrighted work has merit or value in and of itself -- it is being copyrighted to protect the interest of the author/performer/creator to distribute his/her work as an artistic work.
A trademark, OTOH, is a mark denoting a particular manufacturer for the purposes of commercially identifying its product from all other similar products.
So... no, the stylized "smile" as protected by copyright is not the same thing as -- and has a different legal effect than -- the stylized "smile" as a trademark.
No, you could probably still sue Monsanto. Monsanto is the origin of the seeds. It could be argued that they had a duty of care to prevent these seeds from contaminating other crops.
But it's much more complicated than that, I'm sure. For instance, what sort of licence agreement does the distributor have with the grower? Are the seeds and their produce owned by the farmer or licenced to the farmer by the distributor/manufacturer? Further what waiver of rights does the manufacturer disclaim? And what duties to the end-farmers take on under the contract?
I have to agree with this assessment in full. I am actually very dismayed that the Courts did not rule differently. Patent law is, for the most part, a very silly law -- at best, and a very dangerous and tyrannical one -- at worst.
I'm not sure at what point humanity broke down and decided that someone can `own' an idea. That someone can own easily replicable processes -- self replicable and self distributing, even.
I mean, it seems like an fine concept when we're talking about a transistor radio or some other unnecessary and altogether unary, tangible product that an inventor toiled over and deserves compensation for -- but, look at the ever domesticised `extreme.'
We're talking, now, about a *plant.* A life form. Something that reproduces of its own accord. Moves of its own accord. Takes root of its own accord. Some scientist, somewhere, discovered how to make this plant more resistant to herbicide... and now, these plants -- which are now naturally occuring and free to propagate as all other living entities -- are illegal to possess without the legal standing of a corporate contract.
Isn't the ludicrousness of the aforementioned so plainly obvious to everyone? Doesn't it make you want to rise up in revolt?
*sighs*
What shocks me is how many people out there defend corporate activity like this... or how many people delude themselves into thinking they have a fair bite at the riches these corporations reap. It's like everyone's lined up to take their turn as the next tyrant.
Pardon me, but, for want of any more concise expression: fuck that.
Except that there are far fewer individuals using the open-source versions, statistically. So it's proportional. For each bit more money and bandwidth AOL has, GAIM has fewer users... I know it's not quite that biased against GAIM users, but, nonetheless -- you don't need near the computing power to serve the [relatively small] AIM-using open source community as you do the [comparatively huge] AIM-using Windows/MacOS community.
"Don't get me wrong. I'm as infuriated by these actions as anyone, and I think the big-shot CEOs who make these decisions should be hung."
Should be *hanged.*
Grammar aside, that's a bit of hyperbole. There are far worse cliques of hypercapitalists living and breeding in our society, who cause much greater damage and suffering in the world than AOL... AOL isn't responsible for building sweat-shops that force children to toil needless for nothing more than the manufacture of American shoes. AOL isn't responsible for raping third-world countries and exploiting the resoures and damaging the local economies of far away places.
AOL is "exploiting" (that is to say, pissing off) relatively well-off internet users. For that, they deserve stiff opposition, but, there are others much more deserving of the hanging.
I mean, where is the IETF "located"? Could they not simply adopt their IDN system everywhere *other* than the US?
The problem I find with software patents today is that they are valid only in the United States: yet nobody seems to realize this! There's a whole big world out there beyond the Yanks-to-the-South and I see no reason to penalize the rest of the Internet by somehow accepting this sort of crap coming out of the States.
The IETF ought to adopt whatever Internet Standards it likes. If this prohibits Internet standards from being implemented in the States this will be just another reason for network users in the States to oppose software patents.
I don't think the right attitude is to accomodate hypercapitalism and the erosion of our rights: but to simply ignore the US. They will either give up their notions of intellectual property and become standards compliant with the rest of us, or, not. If not? Their loss.
The Internet functions best on open and accepted standards... not on closed, proprietary protocols.
Rogers@Home promises ~3Mbits asynchronously divided into a 50KB/s upstream and ~300-350KB/s downstream.
Downloads easily match T1 speeds, depending on the network location of the other host... plus, one of my friends has a screenshot of one day where he was downloading something like 12 files files at 150KB/s each... so, it seemed pretty impressive in aggregate;)
There's a lot of bollocks about "cable modem capping" over here... that the modem itself is somehow preventing full utilisation of bandwidth... (i.e. more upstream...)
I still think regulations should be put into place preventing DSL and Cable providers from asynrchonously provisioning bandwidth -- their AUPs prevent servers and other things from running off what is otherwise just as fast as a T1 line... and, if the technology were fully applied much much faster... (what was that I heard? 52Mbits?)
Slashdot Mirror
Well, I'm sure Mac owners who want *more* RAM buy PC RAM. However, in some systems this isn't an option. For instance, you cannot open an iMac without violating the warranty... you'd need to pay an Apple tech. to put the RAM in for you... I don't know if they're restrictive about what manufacturers they're allowed to install but I could see Apple doing that ;)
In any case, Apple ships computers using their own (branded) RAM... it would be cost effective to build a machine from scratch using regular PC components... you can benefit from things like the highly competitive market for memory right now, among other things.
BRx.
Well, I wasn't suggesting so much that Yellow Dog would do it, but that someone else _could_ do it, and easily... the prices for these briQ nodes are OK if you're trying to conserve rackspace (i.e. a renderfarm type environment.)...
But, single system users, OTOH, would presumably fetch a better deal insofar as hardware pricing goes: for instance, a lot of cash can be saved using "PC" RAM over Apple's ridiculously overpriced RAM (PC100 or 133 RAM and Apple's RAM are basically identical-- costs aside)... also, you could make individual choices regarding hard drives, video cards, sound cards, etc.
A reasonably priced clone product would also, of course, challenge Apple to lower its prices... or offer more enticing value-adds.
Insofar as the MacOS goes, either the hardware manufacturer could ship a shrinkwrapped OS from Apple (as a parent post contemplated) or have the end consumer purchase a copy of the OS independently... a bit more hassle, but, people might be willing to do it if the price is right.
BRx.
Bad form to reply to yourself, but, I meant to say: "Give it a nice, graphical installer..." ;)
Back to your regularly scheduled program...
BRx.
One of the biggest barriers to entry to becoming a "Mac user" tends to be the high cost of a decent system. You can get an iMac for pretty cheap, as far as things go, but, for the same price you can get a significantly more customized (& probably faster) Intel-based system.
The closed hardware platform has always let Mac users sleep easy in that all Mac hardware always has 100% plug-n-play support... but, still, there are those of us who'd like to *build* a Mac... or get a Mac with the specs of a G4 tower for significantly less...
Anyways, the site linked-to above and noticed they mentioned these briQ's are capable of Mac-on-Linux...(obviously...) but then it hit me: why not develop some superbly lightweight Linux distro that was basically just a bootloader for MacOS 8.6 (hopefully OS X eventually) -- you could avoid the annoying proprietary ROM issue, by using a software ROM legitimately from the 8.6 CD (which you buy legitimately.)
Give it a nice, graphical interface... Enter the consumer priced Mac clone...
BRx.
Well... not in Canada :) Or in parts of Europe. I'd venture to say only States in the US would outlaw something of that sort. The US tends to be absurdly pro-rich, of course, so it's not so surprising.
In Canada, you can make copies of your music for personal use legally. We have a levy imposed on the sales of blank media to serve as a royalty when those tapes are used to "pirate" music.
BRx.
I mean even the harshest critics of the Taliban regime here on Slashdot are pretty much saying: "Yeah, well, that's what right wing religious nuts will do... ban the internet and treat women poorly." Poorly?
Yes, well, I'd love to see (strike that -- I possess an utter loathing to see) what you'd consider falls into the "horrendous" or "godawful atrocity" category... yanno, what with "poor treatment" being the routine public stonings, executions, rape, torture, and mind control to which women in that country are subjected daily for "crimes" as little as ... oh I dunno ... learning to read or perhaps leaving the house not completely coccooned in oppresive clothing and under the supervision of male relatives? Women are bludgeoned to death for that, there. Or how about the fact that women were forced out their workplaces and any property forfeit to male relatives? Or, that greatly due to this, there aren't enough health care workers in the country to help aide the sick... and there are plenty of sick, now, since the Taliban's utter mismanagement of national econmics has caused widespread famine and a total disintegration of what social services existed there. Or that suicide rates for oppressed women in Afghanistan have skyrocketed thanks to their brutal treatment. Let's not forget! of course, that non-Muslims and their homes are branded in yellow and ostracized...
If this is "poor" treatment of women and of human life in general -- I can't, to be honest, wrap my brain around your concept of what's really going on... this is, as one of my good friends once put it -- WHOLESALE FUCKING GENOCIDE. "Poor" treatment?? I've never read anything more disgusting in my life.
Good gods, I wish we in the west would get a clue. We've got a regime committing atrocities on par with the horrors of Nazi Germany and we sit back and say... Meh. Poor treatment. This too shall pass. Fuck, we're arrogant hypocrits.
BRx.
BRx.
VNC is great for a lot of things: for instance, if you want to connect and control a presently running session (a la WinVNC or VNC through x0rfbserver), or if you want to, say, control an X desktop from a Mac or Windows machine that doesn't have (and you can't install) an X server. It all depends what you want to do, I suppose.
BRx.
The neat part is, of course, that your local window manager & decorations will be used -- so there's no reason to be minimalist with eye candy as is the case with VNC: window management & drawing, etc. is all done locally. It further solves your problem with copy & paste because the remote X apps will be treated just like local ones.
Lastly, if you find the performance sluggish, there are several ways you can decrease the bandwidth neccessary to make network X possible. Beyond SSH tunnelling (which is a good idea anyways :)), the two that spring to my mind are LBX and DXPC. LBX (Low Bandwidth X) is probably the simplest to configure & use -- it's included with XFree86 (4.x at least.)
On the remote machine, simply type:
lbxproxy -display local_machine:display :1
now, set your DISPLAY variable to :1 on the remote machine. that's that. X will now use LBX compression -- there's noting to configure locally as the local X server will automatically decompress the stream for you.
DXPC (Differential X Protocol Compressor) is a little more complicated as it requires a proxy on both sides. Search Google for setting up DXPC -- there's plenty of HOWTOs & FAQs on the subject out there.
All in all, using X for this purpose will integrate better with your local desktop as well as make the integration between your remate apps & your local ones seemless.
BRx.
Ah, indeed.
... which I mistook for the JD mentioned in the article), D.Jur (Doctor of Jurisprudence), DCL (Doctor of Civil Law) and the DD.L (Doctor of Laws.)
:)
In Canada, you take a bachelor's degree in something (usually a BA) before applying to law school, where you earn an LL.B. You can take the bar following this.
After that there are Master's programs (LL.M.) and several avenues of doctoral study including the SJD (Juris Scientiae Doctor
I didn't realise the US used a different system
BRx.
JD stands for "Juris Doctor." There are plenty of lawyers out there who don't have their Doctorate in Law. Where I'm from, at any rate, you need only your LLB (as well as other requirements, yes, but, scholastically speaking) to take the bar exam.
If this fellow expects his JD it means he's been studying law for at least 6 years and has probably earned a degree before entering law school in the first place. He's not lay :)
BRx.
Recent Changes to the XFree86 4.1 branch
Below is a recent extract from the XFree86 change log for the 4.1 branch. The full change log can be found in the XFree86 source tree (xc/programs/Xserver/hw/xfree86/CHANGELOG).
XFree86 development code can be accessed directly from the CVS repository. Information about this can be found on our CVS page.
XFree86 4.1.0 (2 June 2001)
619. Disable PCI resource conflict checking for Linux/Alpha (Jay Estabrook).
XFree86 4.0.99.902 (1 June 2001)
618. Fix Linux xf86GetPciSizeFromOS() parsing when the kernel is 64 bit
and any base or size is larger than 32 bits in magnitude (#4732,
David S. Miller).
617. Make XDarwin ddx pass up proper right and middle mouse button numbers
and fix mouse button 5 (Christoph Pfisterer and Torrey T. Lyons).
616. Restore backwards compatibility from 4.0.[2,3] to 4.1.0 for
the i810, r128 and radeon DRI drivers (Gareth Hughes).
615. Fix a problem when using patterns of horizontal lines with the mga
video overlay (#A.442, Ewald Snel).
614. Xinstall.sh updates and bug fixes (David Dawes).
613. Remove duplicate XineramaLibrary section in X11.tmpl (#4731,
Mike Harris).
612. Enable building DRI for Linux/ppc, and fix a drm-related bug
for Linux/ppc (#4728, 4730, Michel Dänzer).
611. Document Options for the r128 and fbdev drivers (#4727, 4729,
Michel Dänzer).
610. Add a BuildBindist switch which causes a file containing the XFree86
version number to be installed in ProjectRoot, include this in
the Xbin bindist tarballs, and turn on this switch in the bindist
host.def files. The purpose is to allow the installer script to
easily identify which version the bindist tarballs are (David Dawes).
609. Resync bindist and Xinstall.sh with changes made for 4.0.3 (David Dawes).
608. Fix the Shape extension's XShapeCombineMask to handle cases where
src_mask is None according to the spec. This reportedly fixes an
X server crash (#4715, Huver).
607. Make sure -UXF86DRI is after -DXF86DRI when compiling vfb/miinitext.c
(#4714, Frederic Lepied).
606. Fix ATI Radeon driver on Alpha. Seems as though the BIOS doesn't
like Re-POSTing and memory setup gets confused. (Jay Estabrook, Jeff
Weidemeier)
605. Fix build for Cygwin/XFree86 (#4711,#4713 Harold Hunt).
604. Fix problem with Xinstall.sh on Darwin 1.3.x (#A.431, Stefan Pantos).
603. Update Xinstall.sh and Darwin bindist directories to optionally
install Quartz support and to add an x86 distribution (Torrey T. Lyons).
XFree86 4.0.99.901 (29 May 2001)
602. Add missing return value for miSetPixmapDepths() (#4708,
ISHIKAWA Mutsumi).
601. Fill in the v4l man page template with some useful information (#4707,
Gerd Knorr).
600. Fix FFB OpenGL SwapBuffers (#4705, David S. Miller).
599. Work around a problem building the rstart specs doc with a symlinked
build tree (David Dawes).
598. Remove SPARC-specific byte-swapping code that would not work on older
SPARC CPUs (part of #4653, David S. Miller).
597. NULLify mapVidMem() and remove DEV_MEM #define for Linux/SPARC
(#4651, David S. Miller).
596. Fix Glint 300SX+Delta support. Add faster 500TX text acceleration
based on other code (Alan Hourihane).
595. Fixing MTRR split code (hopefully) (Egbert Eich).
594. Fixing coredump when doing vbeFree() twice: S3 Virge and C&T
(Egbert Eich).
593. Fixing HWCursor for mga driver in fbdev mode (Egbert Eich).
592. Fix xmh's use of XtNewString() with getenv (#4694, Tim Waugh).
591. Xdm/PAM fixes: leave it to PAM to observe whether or not an account
is locked, and reinitialize credentials after calling initgroups(),
because sometimes the credentials pam_setcred() gives are in the
form of group membership (#4693, Mike Harris).
590. Add an encodings file for standard box drawing characters for
VT100-compatible terminals (#4691, Juliusz Chroboczek).
589. Fix warnings when building mieq.c (#4689, Adam Sulmicki).
588. Fix some bugs in the cz and sk entried in XKB's keymap/xfree86 file
(#4692, Ivan Pascal).
587. Add 'hr' entries to XKB's keymap/xfree86 and rules/xfree86.lst files
(#4687, Nerijus Baliunas).
586. Include in shape.h to get Region typedef (#4686,
Adam Sulmicki).
585. Acceleration fixes for GLINT Permedia1 (Alan Hourihane).
584. Ensure glint driver chips don't exceed the specified virtual sizes.
(Alan Hourihane).
583. Remove all VGA'isms from the glint driver, it doesn't need them
(Alan Hourihane).
582. Support the Delta in the glint driver, needed for boards that have
the Delta connected to the rasterizer, as it acts as an arbiter for
the bus. Resolves acceleration troubles. (Alan Hourihane).
581. Add an lv entry to XKB's keymap/xfree86 file (#4685, Nerijus Baliunas).
580. Fix some typos in XKB's xfree86.lst file (#4684, Nerijus Baliunas).
579. Add DDXOSVERRORF ifdefs to the XFree86 ddx code that make use of the
OsVendorVErrorFProc feature (#4678, Michel Dänzer).
578. Convert the r128 driver's "UseBIOSDisplay" option into a more general
"Display" option (#4678, Michel Dänzer).
577. Treat GL_POINT like GL_POINTS and GL_LINE like GL_LINES in the sunffb
DRI driver (#4677, David S. Miller)
576. Fix bsdLib.rules and bsdLib.tmpl problems that show up when
X11ProjectRoot is defined (#4676, Johnny C. Lam).
575. Fix Trident XVideo colorkey at depth 15, 24 (Alan Hourihane).
574. Fix a typo in the lv XKB description, and fix things so that it gets
installed (#4675, 4679, Andris Pavenis).
573. Fix some apm driver bugs, including one that prevented acceleration
from working (#4674, Loïc Grenié).
572. Fix 555 (depth 15) palette handling in the i810 driver (#4673,
Andrew C. Aitchison).
571. [SECURITY] Fix authentication issues with mmap() on drm devices
(Jeff Hartmann).
570. Add euro locales and some other missing locales to locale.alias and
locale.dir (#4662, 4665, 4667, Mike Harris).
569. Fix Romanian XKB map (#4664, Mike Harris).
568. Spell Portuguese correctly in XKB lst files (#4663, Mike Harris).
567. Fix new ioperm calls in lnx_video.c for Alpha that are not needed
(Jay Estabrook).
566. Fix problems with assembler file dependencies when using gccmakedep
with the build (Frederic Lepied).
565. Finish DRI resync, including tdfx driver updates for textured video
support (VA Linux Systems).
564. Fix formatting of max clock reported by DDC (Marc La France).
563. Update Japanese localization of XDarwin help file (Toshimitsu Tanaka).
562. Update XDarwin man pages, help files, and version info. Add option to
build XDarwin.app bundle for deployment (Torrey Lyons).
XFree86 4.0.99.900 (18 May 2001)
561. Add an XKB description for Latvian (lv) keyboards (#A.411, Ilya Ketris).
560. Resync with DRI CVS trunk (VA Linux Systems).
559. Savage driver updates, including compiler warning fixes, document
the "ShadowStatus" option in the man page, and fix an argument
mismatch between ShadowWait and SavageWaitQueue (#4661, Tim Roberts).
558. Update the wacom driver to add a "ScreenNo" option to allow a tablet
to be attached to a screen in a multi-head setup, and to add auto-
detection of USB line and max parameters of USB tablets (#4640,
Frederic Lepied).
557. Add a README file that has information about enabling the extra buttons
on the IBM Rapid Access keyboard (#4639, Dennis Bjorklund).
556. Fix some Slovene/Slovak confusion in locale.dir/locale.alias files
(#4638, Kamil Toman).
555. New XKB keymaps for cz and sk (#4634, 4637, Kamil Toman).
554. Updates for the iso8859-2 Compose file (#4634, Kamil Toman).
553. Check V_CSYNC in the r128 driver, and fix building with R128_DEBUG
enabled (#4631, Michel Dänzer).
552. Mesa 3.4.2 (and later) import.
551. More build & warning fixes (Marc La France).
550. Fix bug that caused hardware cursors to be temporarily moved during mode
switches (Marc La France).
549. Optimise HARDWARE_CURSOR_AND_SOURCE_WITH_MASK case (Marc La France).
548. Move xf86CursorScreenRec definition into xf86CursorPriv.h
(Marc La France).
547. Fix BIOS retrievals in MGA driver (Marc La France).
546. Fix ATIProbe() for newer Rage128 and Radeon chips (Marc La France).
545. Add temporary workaround in ATI driver for interrupts that occur on
PowerPC's upon PCI master-aborts (Marc La France).
544. Update XDarwin to use fb and support Render (Torrey Lyons).
543. Back out sunleo conversion to fb. This driver is too heavily dependent
on cfb32 for a simple fb conversion (Marc La France).
542. Miscellaneous build/warning fixes (Marc La France).
541. More prep work for SunOS (Marc La France).
540. Fix libXft build on SunOS (Marc La France).
539. Another makedepend bug fix (Marc La France).
538. Fix use of xftcache utility during !UseInstalled builds (Marc La France).
feast and enjoy.
-bacchusrx.
This is precisely why the tactic is effective. So few people are gutsy enough, people don't disbelieve you when you say you're a consultant, or the Cable Company Technician, or whatever it is. Most people aren't prepared for that sort of trechery, as it were ;).
BRx.
The United States Government can not have Copyright Protection? What about State governments?
Here in Canada, our government can (and does) have copyright protection -- this extends to Provincial governments as well... Crown Corporations -- such as Canada Post or the Canadian Broadcasting Corporation -- may own copyrights.
Parliament can copyright under The Queen's Printer for Canada (the provinces do it under "The Queen's Printer for Ontario" or whatnot, as far as I'm aware.) For instance, there are many documents published by the Government (or by Parliament) that are free for public distribution but subject to particular terms. These documents are (c) the Queen's Printer (for Canada or for the Province.)
Presumably if the government or some entity established by Parliament released software for the public's use under the GPL the reliance on copyright would be satisfied.
BRx.
You shouldn't capitalize "Mac."
:) I mean, I hate to nitpick, but, these sorts of things give me headaches.
MAC stands for "Media Access Control" as well, I'm sure, as any number of other things.
'Mac' cf. "Macintosh" -- Get it? Apple. Macintosh Apples. Yes, see, I'm sure you are now suitable impressed. "Mac" it is not an acronym for anything and it is certainly not meant to be capitalized. Notice how the operating system is called "MacOS" and not "MACOS" or "MAC-OS."
Just so you know
BRx.
(being a Grammar Nazi, today.)
Hm. Everything you've said *might* be true, except for the fatal flaw -- GNU/Linux is not UNIX.
I hate to come off sounding like some loathed semantics fiend, but, c'mon.
Linux is not an "operating system." At least, not alone. It is a kernel. The GNU System + Linux = a POSIX-compliant, UNIX-like, UNIX-compatible operating system. Further, GNOME is GNU, not Linux. GNOME runs on non-Linux-based operating systems.
Remember what GNU stands for, again? "GNU's Not Unix..."?
GNU/Linux isn't UNIX and doesn't claim to be UNIX. While conceptually based on UNIX, it was written from scratch. Therefore, it has no "hereditary" claim to being UNIX. Further, I don't remember it being certified by the Open Group as being "UNIX." So the claim that Linux is at all a UNIX, let alone the preferred flavour thereof, is rather silly.
BRx.
This isn't really capital E "Evolution." At least in the Darwinian sense. Darwin's evolution was about how things would randomly change and the thing that was the "best" in its environment would prevail over things which were not the "best" in the same environment. Darwin's evolution was driven purely by chance, the qualitative best naturally selected because in the end it prevailed. So the quantitative best is the prevailing mutation merely because it prevails. These "evolving circuits" seem a bit more predetermined than capital E evolution has in mind. O'course, by strict dictionary evolution (that is, "the steps leading up from one thing to another.") I suppose it qualifies ;)
BRx.
Oh, please. If I had a quarter for every time I heard some crazy American mention taxpayers and tax dollars to secure an argument I'd be in a much higher tax bracket than I am now ;)
The American tax dollars which ``founded'' the early ARPANET and the meagre impact those dollars had on the wallets of individual Americans is insignificant in comparison to the vast contributions of the US domestic private sector and the international private & public sectors. There's no comparison.
BRx.
Copyright applies differently.
"Copyright" is the right of an author or his to print and publish his literary or artistic work, exclusively of all other persons. (That's just the loose dictionary definition.)
A trademark is a "peculiar or distinguishing mark or device affixed by a manufacturer or merchant to his goods, the exclusive use of which is recognized by law."
At the very least the intent of these mechanisms are greatly different.
A copyrighted work has merit or value in and of itself -- it is being copyrighted to protect the interest of the author/performer/creator to distribute his/her work as an artistic work.
A trademark, OTOH, is a mark denoting a particular manufacturer for the purposes of commercially identifying its product from all other similar products.
So... no, the stylized "smile" as protected by copyright is not the same thing as -- and has a different legal effect than -- the stylized "smile" as a trademark.
BRx.
No, you could probably still sue Monsanto. Monsanto is the origin of the seeds. It could be argued that they had a duty of care to prevent these seeds from contaminating other crops.
But it's much more complicated than that, I'm sure. For instance, what sort of licence agreement does the distributor have with the grower? Are the seeds and their produce owned by the farmer or licenced to the farmer by the distributor/manufacturer? Further what waiver of rights does the manufacturer disclaim? And what duties to the end-farmers take on under the contract?
Tricky business....
BRx.
I have to agree with this assessment in full. I am actually very dismayed that the Courts did not rule differently. Patent law is, for the most part, a very silly law -- at best, and a very dangerous and tyrannical one -- at worst.
I'm not sure at what point humanity broke down and decided that someone can `own' an idea. That someone can own easily replicable processes -- self replicable and self distributing, even.
I mean, it seems like an fine concept when we're talking about a transistor radio or some other unnecessary and altogether unary, tangible product that an inventor toiled over and deserves compensation for -- but, look at the ever domesticised `extreme.'
We're talking, now, about a *plant.* A life form. Something that reproduces of its own accord. Moves of its own accord. Takes root of its own accord. Some scientist, somewhere, discovered how to make this plant more resistant to herbicide... and now, these plants -- which are now naturally occuring and free to propagate as all other living entities -- are illegal to possess without the legal standing of a corporate contract.
Isn't the ludicrousness of the aforementioned so plainly obvious to everyone? Doesn't it make you want to rise up in revolt?
*sighs*
What shocks me is how many people out there defend corporate activity like this... or how many people delude themselves into thinking they have a fair bite at the riches these corporations reap. It's like everyone's lined up to take their turn as the next tyrant.
Pardon me, but, for want of any more concise expression: fuck that.
BRx.
Except that there are far fewer individuals using the open-source versions, statistically. So it's proportional. For each bit more money and bandwidth AOL has, GAIM has fewer users... I know it's not quite that biased against GAIM users, but, nonetheless -- you don't need near the computing power to serve the [relatively small] AIM-using open source community as you do the [comparatively huge] AIM-using Windows/MacOS community.
BRx.
"Don't get me wrong. I'm as infuriated by these actions as anyone, and I think the big-shot CEOs who make these decisions should be hung."
Should be *hanged.*
Grammar aside, that's a bit of hyperbole. There are far worse cliques of hypercapitalists living and breeding in our society, who cause much greater damage and suffering in the world than AOL... AOL isn't responsible for building sweat-shops that force children to toil needless for nothing more than the manufacture of American shoes. AOL isn't responsible for raping third-world countries and exploiting the resoures and damaging the local economies of far away places.
AOL is "exploiting" (that is to say, pissing off) relatively well-off internet users. For that, they deserve stiff opposition, but, there are others much more deserving of the hanging.
Let's get our priorities straight here.
BRx.
...isn't this more of a USA problem?
[rant]
I mean, where is the IETF "located"? Could they not simply adopt their IDN system everywhere *other* than the US?
The problem I find with software patents today is that they are valid only in the United States: yet nobody seems to realize this! There's a whole big world out there beyond the Yanks-to-the-South and I see no reason to penalize the rest of the Internet by somehow accepting this sort of crap coming out of the States.
The IETF ought to adopt whatever Internet Standards it likes. If this prohibits Internet standards from being implemented in the States this will be just another reason for network users in the States to oppose software patents.
I don't think the right attitude is to accomodate hypercapitalism and the erosion of our rights: but to simply ignore the US. They will either give up their notions of intellectual property and become standards compliant with the rest of us, or, not. If not? Their loss.
The Internet functions best on open and accepted standards... not on closed, proprietary protocols.
[/rant]
BRx.
Rogers@Home promises ~3Mbits asynchronously divided into a 50KB/s upstream and ~300-350KB/s downstream.
;)
Downloads easily match T1 speeds, depending on the network location of the other host... plus, one of my friends has a screenshot of one day where he was downloading something like 12 files files at 150KB/s each... so, it seemed pretty impressive in aggregate
There's a lot of bollocks about "cable modem capping" over here... that the modem itself is somehow preventing full utilisation of bandwidth... (i.e. more upstream...)
I still think regulations should be put into place preventing DSL and Cable providers from asynrchonously provisioning bandwidth -- their AUPs prevent servers and other things from running off what is otherwise just as fast as a T1 line... and, if the technology were fully applied much much faster... (what was that I heard? 52Mbits?)
BRx.