Slashdot Mirror
Ubuntu 9.04 Daily Build Boots In 21.4 Seconds
Pizzutz writes "Softpedia reports that Ubuntu 9.04 Boots in 21.4 Seconds using the current daily build and the newly supported EXT4 file system. From the article: 'There are only two days left until the third Alpha version of the upcoming Ubuntu 9.04 (Jaunty Jackalope) will be available
(for testing), and... we couldn't resist the temptation to take the current daily build for a test drive, before our usual screenshot tour, and taste the "sweetness" of that evolutionary EXT4 Linux filesystem. Announced on Christmas Eve, the EXT4 filesystem is now declared stable and it is distributed with version 2.6.28 of the Linux kernel and later. However, the good news is that the EXT4 filesystem was implemented in the upcoming Ubuntu 9.04 Alpha 3 a couple of days ago and it will be available in the Ubuntu Installer, if you choose manual partitioning.' I guess it's finally time to reformat my /home partition..."
Well my TABLE LAMP boots in 50ms! Beat THAT!
(And to all you electrotech-people, yes, i live in Europe, 50Hz here. You may laugh now.)
"We are the music makers, and we are the dreamers of dreams [...]."
Booted into Ubuntu 9.04 just to say "first post". Let's just say the ubuntu folks still have some work to do.
--------- I have no signature
Sure to be named Masturbating Monkey
You sir get a star. http://haacked.com/images/haacked_com/WindowsLiveWriter/IConfigMapPathIsInaccessibleDueToItsProt_1446B/works-on-my-machine-starburst.png
Flexible bare-metal recovery for Linux/UNIX
No, but at least the people make "wipe" are paranoid too:
From the wipe man page
==
NOTE ABOUT JOURNALING FILESYSTEMS AND SOME RECOMMENDATIONS (JUNE 2004)
Journaling filesystems (such as Ext3 or ReiserFS) are now being used by default by most Linux distributions. No secure deletion program that
does filesystem-level calls can sanitize files on such filesystems, because sensitive data and metadata can be written to the journal, which can-
not be readily accessed. Per-file secure deletion is better implemented in the operating system.
Encrypting a whole partition with cryptoloop, for example, does not help very much either, since there is a single key for all the partition.
Therefore wipe is best used to sanitize a harddisk before giving it to untrusted parties (i.e. sending your laptop for repair, or selling your
disk). Wiping size issues have been hopefully fixed (I apologize for the long delay).
Be aware that harddisks are quite intelligent beasts those days. They transparently remap defective blocks. This means that the disk can keep
an albeit corrupted (maybe slightly) but inaccessible and unerasable copy of some of your data. Modern disks are said to have about 100% trans-
parent remapping capacity. You can have a look at recent discussions on Slashdot.
I hereby speculate that harddisks can use the spare remapping area to secretly make copies of your data. Rising totalitarianism makes this
almost a certitude. It is quite straightforward to implement some simple filtering schemes that would copy potentially interesting data. Bet-
ter, a harddisk can probably detect that a given file is being wiped, and silently make a copy of it, while wiping the original as instructed.
Recovering such data is probably easily done with secret IDE/SCSI commands. My guess is that there are agreements between harddisk manufacturers
and government agencies. Well-funded mafia hackers should then be able to find those secret commands too.
Don't trust your harddisk. Encrypt all your data.
Of course this shifts the trust to the computing system, the CPU, and so on. I guess there are also "traps" in the CPU and, in fact, in every
sufficiently advanced mass-marketed chip. Wealthy nations can find those. Therefore these are mainly used for criminal investigation and "con-
trol of public dissent".
People should better think of their computing devices as facilities lended by the DHS.
==
You may enjoy your 26 seconds of pretending that "this is not really happening" - most other people don't.
Why yes, I do enjoy that very much. I call it "sex".
Oh yeah? Well I optimized my sex down to 23 seconds. Top THAT!
Your ad here.
All this high technology, what ever happened to doing things by hand?
"What if I got hit by lightning while walking with an umbrella? Ban umbrellas! Fight the menace of lightning!" Doctorow
Because Installation of Automatic Updates has completed. Computer will automatically reboot in 5 minutes...
Your comment about a locked screen showing the contents of the desktop is probably related to a screensaver taking a screen capture and using it in the screen saver. This can be fixed by running xscreensaver-demo (I think) program to get the configuration for the screen savers. You may have to install the xscreensaver package to get this program. When it comes up, it will warn you that xscreensaver isn't running -- that's OK, just ignore it. You can still set the options for the various screen savers.
This is necessary because about a year ago (or so) Gnome decided to replace the standard xscreensaver with their own screen saver system. In good Gnome fashion, there are almost no actual configuration options. However, it still actually uses the xscreensaver programs, which have a lot of configuration options, including where to get image sources (that's on one of the tabs). Tell it not to use a screen capture. Personally, I have it use images from my camera directory, so I'll see pictures I've taken in the various screen savers.
Considering that xscreensaver has had this options dialog for a long time, I don't know why Gnome couldn't either use it, or make one like it. But I guess that would expose useful options to users.
You're right that Ubuntu has been fairly bug filled. My personal annoyance with Ubuntu 8.10 comes with Gnome 2.24: they released a version of Gnome with a half re-implemented session management. They ripped out the mostly working implementation and replaced it with a version that cannot save or restore session state! Now, I'm all for replacing poor implementations, which as I've read the previous session management code was. However, it's really bad to take out mostly working code and replace it with a "** (gnome-session-properties:4618): DEBUG: Session saving is not implemented yet!" printout.
"Save the whales, feed the hungry, free the mallocs" -- author unknown
meh, I type my 10+ character password (containing lowercase, uppercase, and numbers) so often that it takes less than 2 seconds.
IDIOT! Now everyone knows your passwd is Ubuntu904
I know your post was supposed to be funny, but while you passed the uppercase, lowercase and number criteria, you failed to pass the 10+ characters criteria mentioned.
"There are no facts, only interpretations." --Friedrich Nietzsche.
you don't see the space there?
All I see is **********. Maybe someone else could post their password so we can check it.
When our name is on the back of your car, we're behind you all the way!
My password is 10 asterisks, you insensitive clod!
Apologies to Dilbert.