Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
I tried for a day to get Linux installed on my Mac. I thought Boot Camp would be perfect; it repartitioned the drive nicely, but I couldn't get Linux to load. I couldn't delete the Windows partition, couldn't remake it as a Linux partition. Eventually gave up. Is there a way to do this?
The best part: It is "Gold" as in , I have a perfect installation. Something goes wrong, and I got back to the LVM snapshot where it was pristine. This never happened, but sometimes, instead of uninstalling stuff I need to test, I just rollback any way. It runs wonderfully on one E3-1260L core and 512MB RAM.
This is exactly how Windows XP should be used these days, and it works perfectly fine. XP for Win32 functionality, the rest on Linux.
You can finally print mirrors with this, apparently. Quite cool
Thank you. I just couldn't understand it; although clearly the clues were there and you interpreted them correctly.
So the UV light goes through the bottom window, through the oxygen-rich zone that will not polymerize. When the light gets through that zone, it polymerizes the resin. The polymerized resin must block the light from going deeper into the liquid resin.
If you have a thick part, though, I wonder if this could work? New unpolymerized resin would have to flow into the gap between the hardened part and the window, and this 'dead zone' is only microns thick. Now, I do believe that most 3D printed parts aren't solid blocks; but this could be a limitation.
Still, looks quite cool. I am sure that I'm not alone wanting to build stuff with it!
The drive's media wear indicator ran out shortly after 700TB, signaling that the NAND's write tolerance had been exceeded. Intel doesn't have confidence in the drive at that point, so the 335 Series is designed to shift into read-only mode and then to brick itself when the power is cycled. Despite suffering just one reallocated sector, our sample dutifully followed the script. Data was accessible until a reboot prompted the drive to swallow its virtual cyanide pill.
Who thought this was a good idea? If the drive thinks future writes are unstable, good for it to go into read only mode. But to then commit suicide on the next reboot? What if I want to take one final backup, and I lose power?
I suspect that we could persuade those caches to flush to RAM, simply by exhausting the number of possible lines for that address - if the cache is set-associative. Of course modern processors have multiple levels of cache, so that makes it harder.
This is sort of self-contradictory, so I don't really need to respond to it directly. I just want to point one thing out. I can't afford to work for any company as less than a C-level employee. It would be a salary cut from my current business.
Not to mention that I'd not like it.
An AC talking about balls. Pathetic.
Right. I didn't even bother responding to the taunts.
Coward really means coward. I am sorry for the folks who are afraid that their employer will take a dislike of what they post, but for them we have handles.
I can't say I'm happy about what's happened to Debian. Having Ubuntu as a commercial derivative really has been the kiss of death for it, not that there were not other problems. It strikes me that the kernel team has done better for its lack of a constitution and elections, and Linus' ability to tell someone to screw off. I even got to tell him to screw off when he was dumping on 'Tridge over Bitkeeper. Somehow, that stuff works.
IMO, don't create a happy inclusive project team full of respect for each other. Hand-pick the geniuses and let them fight. You get better code in the end.
This actually has something to do with why so many people hate Systemd. It turns out that Systemd is professional-quality work done by competent salaried engineers. Our problem with it is that we're used to beautiful code made by geniuses. Going all of the way back to DMR.