Once you have received correspondence, it is yours to do with as you please. For instance, the New York Post this week printed a letter from New York State Comptroller and gubernatorial candidate Carl McCall's letter to the CEO of Verizon (on McCall's stationery) on the front page. It was quite a nice hatchet job as well, if I do say so myself.
Granted, you could be sued, but the odds are that the plaintiff will be laughed out of court.
I remember seeing some PBS special about the G. Dead and how Jerry Garcia came from the Blue Grass tradition where at live shows they would have these open patch bays where you could plug in a recorder and tape the whole show.
Metallica is another band that has done just that, though you generally have to be a member of their fan club (which costs $40/year) to have a shot at getting the seats where you can do that. They've also been known to go to bat for the tapers.
Their objection was over Napster allowing distribution of studio releases.
Thanks for the info, but i have one more question. Does this make cooker at least semi-stable? Like i know its probably not totally tested to be bug free but is at least not hacked apps and drivers?
Cooker is quite stable... in the past six months, I can think of only one occasion where I hosed anything important (an issue with X Font Server). In that case, the Cooker mailing list was able to provide a workaround (commenting out a line in XF86Config-4) before fixed packages made it my way.
Would I use it on a workstation? Yeah, I do. Would I use it on a mission-critical server? No way.
If you're going to run Cooker, at least subscribe to the Mandrake changelog list, so you know what's been uploaded.
For the most part, Cooker does not have alpha-level software (as tagged by the upstream maintainers). We run a stable kernel and all that goodness (some apps do use patches from CVS).
Maybe it uses devfs? devfsd will try to modprobe everything you try to access in/dev. If you're feeling really curious, you could replace modprobe with a wrapper shell script and write the output of pstree to a file from it.
Yeah, Mandrake uses devfs, which is something that more distros should definitely do. It's only been in the kernel for a couple of years.
that's all good and well, but Mandrake have gone on record saying that they don't make decent cash from the boxed versions, and would rather people downloaded and then joined their club. Still, the DVD will save all those swaps...
They actually make the most money if you buy a DVD from their store, especially if you buy the ProSuite with every new version (twice a year, iow).
Before executing this, you should make sure that urpmi's package db is sane (adding media should do this, but it doesn't always do it properly).
# urpmi.update Cooker
Also, after syncing to Cooker to bootstrap your way into 9.0, you have a choice: you can either run Cooker full time after this (Cooker is fairly stable... things aren't constantly breaking) or you can choose to essentially treat it as a 9.0. If you choose the former, you don't have to do anything. If you choose the latter, you should remove Cooker as a source for packages (otherwise security updates could get hairy). To do this, just issue the following at a shell:
# urpmi.removemedia Cooker
Also, I can't stress this enough, but this trick will only work until Cooker development starts up again and new packages get uploaded. Also, if you downloaded RC3, there's probably no need to download 9.0 final... the only changes seem to be in the installer; no packages have changed.
Can you explain cooker to me. I know what makes it the sme as the rest but how is it different? I find some of the info on cooker to be obscure so can you please explain it or link to a good beginner explanation of cooker?
Basically Cooker is Mandrake's development/testing branch, somewhat like Debian Sarge (or Woody before Woody went stable). When a Mandrake developer finishes packaging something, they upload it to Mandrake's internal cooker mirror and then it propagates through the publically accessible mirrors. For this reason, the packages in Cooker change constantly, though there will be the occasional burst (such as when gcc was upgraded to 3.1 and then to 3.2 or when perl was upgraded to 5.8 and then to a thread-enabled perl) when a lot of packages get upgraded.
When Mandrake makes a release (beta or final), they basically just take a snapshot of what Cooker is on a given day (generally a few days before the release is announced), do a bit more testing on that frozen Cooker and then declare it to be a stable release.
For the few weeks before a final release, Mandrake will freeze Cooker, which essentially means that only bugfixes will be accepted.
Mandrake Update is designed for deployment of security updates after release.
These instructions are for the commandline... I've not used the new GUI front-ends to urpmi.
1) Find a mirror that has Cooker... many mandrake mirrors do.. if your mirror has a directory named "mandrake-devel", you're in business.
2) Find where that mirror keeps its RPMs... in most cases it will be in path-to/mandrake-devel/cooker/i586/Mandrake/RPMS. Also find where the file "base/hdlist.cz" is, relative to the RPMS directory. In most cases, this will be../base/hdlist.cz
As root, issue this command (assuming that your mirror is an ftp mirror):
At this point, you can auto-install any packages which have changed by issuing:
# urpmi --media Cooker --auto-select
You can also use rpmdrake to do the upgrade (rpmdrake is "Configure | Packaging | Install Software" in the Mandrake menu system).
Please note that, due to some changes in package names and improvements made to urpmi between 8.2 and 9.0 betas, it is questionable whether Mandrake 8.2 can be upgraded to 9.0 in this manner.
So it comes down to either wait 8 hours for it to compile (portage), or wait 8 hours to figure out the dependencies (rpm), or wait 8 months for someone to package it (deb).
Or:
Download Mandrake and use urpmi or it's graphical front-end, the redesigned rpmdrake, to automatically figure out dependencies. There's even talk of hacking urpmi to support automatic compilation of source on a per-package basis (so you can compile X but not other packages).
Since I'm running low on CD-Rs, and I wanted to install Mandrake tonight, can anyone tell me what changes there have been between rc3 and the final release?
If you sync to Mandrake Cooker tonight, you'll have 9.0. To do this, add a Mandrake Cooker mirror (there are many to choose from) as a urpmi source and do a urpmi --auto-select from a shell.
Since Netscape and the last few remaining proprietary applications have been removed, Mandrake Linux 9.0 is a "100% Free Software" product. This means that everyone is granted the right to access the sources, modify and redistribute the software. This also means that Mandrake Linux 9.0 can be deployed on as many machines as desired.
Mandrake tagged the final release RC3 while it was heading out to the mirrors. It will be renamed once all the mirrors get it and then officially announced.
Slashdot Mirror
You, sir, are a fucking idiot.
Once you have received correspondence, it is yours to do with as you please. For instance, the New York Post this week printed a letter from New York State Comptroller and gubernatorial candidate Carl McCall's letter to the CEO of Verizon (on McCall's stationery) on the front page. It was quite a nice hatchet job as well, if I do say so myself.
Granted, you could be sued, but the odds are that the plaintiff will be laughed out of court.
But Scotty used a Mac...
"Computer.... computer...."
"Oh, a keyboard, how quaint."
Metallica is another band that has done just that, though you generally have to be a member of their fan club (which costs $40/year) to have a shot at getting the seats where you can do that. They've also been known to go to bat for the tapers.
Their objection was over Napster allowing distribution of studio releases.
Cooker is quite stable... in the past six months, I can think of only one occasion where I hosed anything important (an issue with X Font Server). In that case, the Cooker mailing list was able to provide a workaround (commenting out a line in XF86Config-4) before fixed packages made it my way.
Would I use it on a workstation? Yeah, I do. Would I use it on a mission-critical server? No way.
If you're going to run Cooker, at least subscribe to the Mandrake changelog list, so you know what's been uploaded.
For the most part, Cooker does not have alpha-level software (as tagged by the upstream maintainers). We run a stable kernel and all that goodness (some apps do use patches from CVS).
Me troll?
Never in a million years...
It figures that a jarhead would get confused by all the "Reply to This" links on the page....
(n/t)
...USA Today, the newspaper that specializes in boiling down complex issues into six sentences, knows anything about physics. Yeah, um... right.
Hell, Kuro5hin got added as a news site (even the diaries), so Poliglut should be able to.
Try emailing news-feedback AT google.com to get your site added. It may not have a high rating, but it will be indexed.
Yeah, Mandrake uses devfs, which is something that more distros should definitely do. It's only been in the kernel for a couple of years.
As for supermount... well... I won't go there...
They actually make the most money if you buy a DVD from their store, especially if you buy the ProSuite with every new version (twice a year, iow).
The US Marines: the military branch for those who couldn't play with the big boys
Q: What is this page supposed to stand for?
Jesus Christ... I think my brain is fried...
Minor error in the above correction:
You should run urpmi.update after running urpmi.addmedia
Sawfish (the default wm in GNOME 1.x and some distros' GNOME 2.x) is actually a very light wm. GNOME is bloated because of the panel and Nautilus.
Minor error in the above post...
Before executing this, you should make sure that urpmi's package db is sane (adding media should do this, but it doesn't always do it properly).
Also, after syncing to Cooker to bootstrap your way into 9.0, you have a choice: you can either run Cooker full time after this (Cooker is fairly stable... things aren't constantly breaking) or you can choose to essentially treat it as a 9.0. If you choose the former, you don't have to do anything. If you choose the latter, you should remove Cooker as a source for packages (otherwise security updates could get hairy). To do this, just issue the following at a shell:
Also, I can't stress this enough, but this trick will only work until Cooker development starts up again and new packages get uploaded. Also, if you downloaded RC3, there's probably no need to download 9.0 final... the only changes seem to be in the installer; no packages have changed.
Basically Cooker is Mandrake's development/testing branch, somewhat like Debian Sarge (or Woody before Woody went stable). When a Mandrake developer finishes packaging something, they upload it to Mandrake's internal cooker mirror and then it propagates through the publically accessible mirrors. For this reason, the packages in Cooker change constantly, though there will be the occasional burst (such as when gcc was upgraded to 3.1 and then to 3.2 or when perl was upgraded to 5.8 and then to a thread-enabled perl) when a lot of packages get upgraded.
When Mandrake makes a release (beta or final), they basically just take a snapshot of what Cooker is on a given day (generally a few days before the release is announced), do a bit more testing on that frozen Cooker and then declare it to be a stable release.
For the few weeks before a final release, Mandrake will freeze Cooker, which essentially means that only bugfixes will be accepted.
Mandrake Update is designed for deployment of security updates after release.
These instructions are for the commandline... I've not used the new GUI front-ends to urpmi.
1) Find a mirror that has Cooker... many mandrake mirrors do.. if your mirror has a directory named "mandrake-devel", you're in business.
2) Find where that mirror keeps its RPMs... in most cases it will be in path-to/mandrake-devel/cooker/i586/Mandrake/RPMS. Also find where the file "base/hdlist.cz" is, relative to the RPMS directory. In most cases, this will be ../base/hdlist.cz
As root, issue this command (assuming that your mirror is an ftp mirror):
At this point, you can auto-install any packages which have changed by issuing:
You can also use rpmdrake to do the upgrade (rpmdrake is "Configure | Packaging | Install Software" in the Mandrake menu system).
Please note that, due to some changes in package names and improvements made to urpmi between 8.2 and 9.0 betas, it is questionable whether Mandrake 8.2 can be upgraded to 9.0 in this manner.
Or:
Download Mandrake and use urpmi or it's graphical front-end, the redesigned rpmdrake, to automatically figure out dependencies. There's even talk of hacking urpmi to support automatic compilation of source on a per-package basis (so you can compile X but not other packages).
If you sync to Mandrake Cooker tonight, you'll have 9.0. To do this, add a Mandrake Cooker mirror (there are many to choose from) as a urpmi source and do a urpmi --auto-select from a shell.
From the presentation:
Woo hoo!
Mandrake tagged the final release RC3 while it was heading out to the mirrors. It will be renamed once all the mirrors get it and then officially announced.
EA owns the 007 license now (and has since Tomorrow Never Dies). They do release some games from that license on the GameCube.
It will be "rare" to have games from them that are "well done"!
Actually, you got second post.