New Enterprise-Level Ubuntu Due This Week

daria42 writes "According to Ubuntu's official release schedule, the next version of its Linux distribution, code-named "Dapper Drake" is due to be released this week, June 1 to be precise. This landmark release will be supported for 5 years (previous versions were only supported for 18 months) and is being touted as ready for enterprise use." From the article: "Dapper Drake will be supported for three years for the desktop version and five years for servers, compared to 18 months for the current 5.10 'Breezy Badger' version. The code release will come after the development process was extended by six weeks in order to improve the reliability of the software."

Comments

Ubuntu dapper drake is cool

[Rinzwind]

It's the 1st Linux both my PC and my laptop accepted without a hitch during install or usage (past month or so). Bluetooth, Wireless connection, Printer HP PSC 2175 (with built-in scanner), wireless mouse (MX 7000), wireless keyboard, Multimedia keys and hibernate/resume all worked out of the box. Firefox as default browser is very nice. Ubuntu did what several redhat and suse installs didn't do: got me away from XP with a SMILE! *does happy dance*

Re:Enterprise? not again!

[wallyhall]

Please, someone correct me if I'm wrong saying this!! I think you've misunderstood the term enterprise, in this contex. Ubuntu Dapper is 100% free, open source software. No propriety 'enterprise' ties (in that sense of the word). It's stable (like Debian Sarge), reliable and comes with everything you'd need, and it's gunna be supported for 5 years, much like RHEL does, which is VERY important to enterprises/businesses etc. I dunno about you, but I don't see how that can really be a bad thing?

VMWare Server Beta, RAID install...

[fnord_uk]

Ah. XP. In case you're missing it, I've just installed the free VmWare Server Beta http://www.vmware.com/download/server/ on Dapper (AMD64), and am ?happily? running XP on it, mostly for running ham radio programs. I'm also going to set up a 32 bit Dapper VM for those few progs that don't compile or run well on the 64 bit platform.

So far, so good. BTW, anyone trying to configure software RAID for their Dapper BETA install, you need to use the alternative install CD image, for the old-style install routine (no live disk built-in). A useful guide is here for setting up a RAID1 configuration
http://users.piuha.net/martti/comp/ubuntu/raid.htm l

Enjoy...

Re:VMWare Server Beta, RAID install...

[Pedersen]

Actually, there's a few differences worth noting.

• VMWare Server does not require a display, Workstation does
• VMWare Server has a web interface for controlling start, stop, and various configuration bits of vmware. Workstation does not
• VMWare Server is still in beta, and as such, the license keys expire periodically. Supposedly, this will not happen when it is released sometime this summer.
• Using the remote console, you can connect to your vmware server hosted machines across the network. With workstation, this is not possible.
• VMWare Server is free. Workstation is not.
• VMWare Server works with (at least) version 2.6.15 of linux kernel. Workstation requires unofficial patches.

So, why would you use Workstation over Server? Support, for one. You can get an actual support contract for Workstation. Whether or not this will be available for Server is unclear at this time. The snapshot manager for Workstation is much more advanced than it is for Server. And, to some degree, Workstation is more convenient on a desktop/laptop than Server.

So, while not a comprehensive list, this gives some idea of the major differences I've noticed using them both.

Last minute bug reports

[wysiwia]

I happen to test around several boot problems the last few weeks I've summarized just here

http://www.ubuntuforums.org/showthread.php?p=10623 67#post1062367

Since these boot problems are quite difficult and probably mean a no go for anybody not a though expert I really hope they were fixed before release. It probably means another delay for a few days but think it's worth.

O. Wyss

Re:six weeks?

[babbling]

Six extra weeks can help a lot.

Linux distributions are unlike most operating systems in that most of the software they use is already written before they start. Most of the work involves putting all of the pieces (known to work correctly on their own) together and ensuring that they still work. There's other things involved too, of course, but my point is that the bulk of Ubuntu is programs that were created as separate projects, and this is how Ubuntu is able to be put together so quickly.

Ship it

[Life700MB]

Don't forget that you can order some ubuntu cds from at shipit.ubuntu.com.


--
Superb hosting 20GB Storage, 1_TB_ bandwidth, ssh, $7.95

Re:Just upgraded

[Knuckles]

Nooo! Please, people, stop recommending this, at least when there is reason to suspect newbies in the vicinity :)

The better way to upgrade is to use the update manager from the System > Administration menu. Once Dapper is released, it will know about it, and offer Breezy users the option to upgrade. As long as Dapper is not yet officially released, you need to run it with the -d switch from the command line to make it upgrade to Dapper: gksudo update-manager -d

Ubuntu has invested quite a bit to make the upgrade patch as smooth as possibly, without requiring users to edit sources.list and such. And there are other problems besides editing sources.list: not every change on the system can be expressed in package dependencies. Sometimes changes have to be made that are too dangerous to attempt automatically during the upgrade, and require manual intervention. E.g., the wiki page for the Breezy upgrade listed several things a user must do (see "Post-Upgrade")

All these things are taken care of now by update-manager

Re:I think it's rather nice too.

[john8472]

Hi,

The Ubuntu drop is native; the machines dual boot after it's all over.

The (very) rough details of how to do it are:

1. Grub for Windows and an initrd image are pushed to the Windows Box.

2. The Windows box is rebooted into Linux, and mounts an nfs share, which contains enough stuff to get most of the install working. The hard drive has its NTFS partition resized, leaving space for the Linux drop.

3. The Linux partitions are created in the newly created free space, and then Linux is set up, with the majority of the packages sourced from an Ubuntu mirror (we proxy through Squid, though as we had some snags using apt-proxy) with a custom pre-seed file.

That's the basics. One of the reasons we need to be able to be able to easily control which o/s to boot into is because most of the PCs run Windows during the day (they are almost all Lab resource workstations at the Uni where I work), and there's a desire to run a Beowulf like setup, out of hours, and during holidays.

We did try FAI, but because of the Windows infrastructure, we can't run a DHCP/TFTP setup, and booting from a floppy on each workstation was too hideous a concept. Also, FAI is a cryptic as a cryptic thing on a particularly cryptic day, and is horrendous (IMHO) to set up.

So far, none of it is documented (at all!) but we will be publishing a "how we did it" once the dapper drop is deployed. Right now, I'm not sure where, but it'll prolly go through the Ubuntu website, somewhere or another.

There have been two of us *involved* in getting it all sorted, but to be honest, I can only bathe in the reflected glory of my colleague at work, because it is he who has been the driving force behind this, and it is he who has carried out the vast majority of the (brain) work. I have been peripheral in this process.