Slashdot Mirror
Ubuntu 8.10 (Intrepid Ibex) Released
SDen writes "Bang on target, the new version of Ubuntu Linux is available for our downloading pleasure. Amongst various changes it sports updates to the installer, improved networking, and a new 'Mobile USB' version geared towards the blossoming netbook market. Grab a copy from the Ubuntu website, and check out Linux Format's hands-on look at the Ibex."
Grab a copy from the Ubuntu website ...
TorrentFreak has a great tutorial on using BitTorrent to upgrade to Intrepid Ibex. Odds are high that the default servers in sources.list are going to be taxed pretty heavily today so this might be useful to a lot of people.
... *cough* *cough*
Now if only Microsoft & Apple could harness & effectively utilize the power of p2p
My work here is dung.
Torrents:
Desktop - AMD 64
http://releases.ubuntu.com/releases/8.10/ubuntu-8.10-desktop-amd64.iso.torrent
Desktop - i386
http://releases.ubuntu.com/releases/8.10/ubuntu-8.10-desktop-i386.iso.torrent
I am downloading both of these, they are quite fast. Seeders are increasing by leaps and bounds!
I'm not sure on your issue, but the network manager has had some serious work done:
http://www.ubuntu.com/testing/intrepid/alpha5#Network Manager 0.7
Mod me down, my New Earth Global Warmingist friends!
Comment removed based on user account deletion
This version of Ubuntu works better on the EEEPC than Hardy did. They have included alot of eeepc modules so less tweaking is needed. If you have a 701 with 4gb, compressing /usr will give you a
at least 1gb free space, possibly 2gb. I used this tutorial too do it:
http://po-ru.com/diary/linux-liposuction-or-xubuntu-in-under-a-gig-on-the-eee-pc/
The tutorial works on Xubuntu and Ubuntu, possibly Kubuntu but I haven't tried that. Read the comments on that page for extra help.
Based off the screenshots, the desktop looks to me like a bloody faceprint on a cave wall.
Or is it significant of "Bang Head Here" when configuration works like 8.04?
I'm a beginner trying to make the switch from Vista to Ubuntu, but for the past two weeks and about 5-10 failed attempts, I've been trying to get my AR5007 wireless card to work in Ubuntu 8.04 to no avail. Will an AR5007 card work with 8.10 right out of the box? Or else I'm not going to bother with it if I can't even get a internet connection. Most user-friendly distribution of Linux my ***...
Isn't that exactly the kind of situation something called the "Live CD" was invented?So that you could check out whether all your hardware works before you install.Or was that too newbie for you?
You know that GTK bug where if your mouse cursor is on a button and the button becomes greyed out so you can't click it and then it becomes normal again but your mouse cursor has been in it the whole time but now you can't click the button even though it's normal now so you have to move your mouse pointer OUT of the button and then back into it again to get the button to work? You know that bug? The one that makes you want to rip out your hair and scream?
Well it's fixed. Whoever is the awesome person who fixed that is my hero. Someone give that person a fucking cookie.
I can't seem to even get through to download the torrent.
I wish you luck. My upgrade doesn't recognize my sound card, Pidgin starts but displays nothing, and Totem hangs (MPlayer does work). And the network configuration tool shows both wired and Bluetooth links, but it doesn't seem to actually use the Bluetooth link for data (even if I disconnect the wired LAN cable). Sure do look purty, though.
Again Intrepid seems to take the progression of and Linux desktops in general: abandon the traditional and well proven unix ideology, where simple tools do well defined tasks well. Instead things "Just work" meaning that when they don't work, they "Just don't work" and the only solution is to wait for new release. Yes yes, you have the source, but hacking around all of the "Just works" bugs isn't isn't very feasible even if one had the programming knowledge.
I've been using the prerelease versions of Intrepid for about a month and have witnessed again few cases of the new bloat-methodology.
For example the NetworkManager has been around for a while destroying an architecture that could be comfortably tweaked in command line and config files. Of course I don't have anything against GUIs that simplify this, but in the same time the command line usage has been stripped.
A great example is the new touted 3G automation, which does work quite nicely. However, for more experienced user it seems quite weird as there's no options to set up the network interface or serial device to use. Of course it turns out that this only works on USB devices that are somehow autoprobed probably by HAL (which itself has configurations that few mortals can edit by hand). And this leading the system not supporting 3G over Bluetooth, even if I'd set up the rfcomm serial device myself.
Another amazing way for "Just works" methodology is to write them in the DE itself, not as separate programs. For example in GNOME there's a applet to kill a misbehaving GUI program by clicking it's window (ie a xkill replacement). But of course it runs as part of gnome-panel process (or something like that). Well, when the kill cursor is on it prevents switching VTs (WHY!?) and also jams the whole screen in the process. Now of course the solution is to SSH to the box (because VT switch is prevented) and kill the offending process from command line. But with the new way to do things, there's no single process to kill.
And other great thing is the gconf. Sure it's nice to use from programmer's point of view, but of course it's practically unusable otherwise. With the GUI-editor there's change to find the proper configuration field in reasonable time, but using CLI is nearly impossible. Sure it uses ASCII files to store the data, but these are in some horrible illegible non-commented XML format nesting several directories deep with some "overlaying" stuff so that the offending parameter can be where ever.
It's a fun way to spend time trying to config your screen through gconf when Gnome has decided to screw up your display using XRandr.
These kinds of situations are already everywhere and getting more common by every distribution and DE release. In no time the big open desktop distros reach the "Just doesn't work" level of Windows and OSX.
Please don't get me wrong. I like the new stuff that makes computers simple to use (like automatic networking setup etc). But it really shouldn't be done in expense of flexibility and ability to fix things manually _when_ the automated stuff breaks.
I don't want to share my now limited bandwidth for some commercial company to give out updates.
And you paid how much for your copy of Ubuntu? Yeah, I thought so.
Besides, if you're on comcast, your "now limited bandwidth", isn't all that limited. For 99.99% of comcast customers, it's practically unlimited, which isn't all that much worse. If you use so much bandwidth that you routinely approach the cap, maybe you aught to upgrade to a commercial service. Also, they actually appear to be using legitimate QoS these days, to appropriately set p2p data as low priority, instead of using the retarded policy of resetting torrent connections.
Constitutional rights may be respected, repealed, or modified; but they must never be ignored.
If I have 3 Apples why the hell do I want Ubuntu?
Well, it sucks that you had that experience. Next time, try the live CD and make sure things are working -- if it works there, you know it can work with the full install.
:)
As for your commentary, let me point out two things.
1- Lack of standard, reducing support available and compatibility consensus.
I'd argue there's far more standards and compatability in Gnome and Ubuntu than for Windows. From a user perspective, Windows allows any executable installer to basically vomit anywhere it wants -- sure, go ahead and muck with the registry, install three systray icons, a quicklaunch shortcut, a desktop shortcut, and two start menu entries. Which might be named after the manufacturer, or maybe the product, or maybe the parent company. Who knows? There's no standard way of doing it -- it's just that users have been trained to accept it. In Gnome, basically everything gets filed so it's never more than one click away, and it's always under a sane, general heading. "Internet", "Games", "Graphics", "Office", whatever.
Same with installation of new stuff. Want a CD burner for Windows? Google "cd burner software" or similar, tromp through eight or nine results looking for one that doesn't look sketchy, isn't crippled trialware, and that you're reasonable sure won't install some spyware or other. Download it, run the installer, agree to weird EULAs and maybe it'll work. Maybe not -- maybe it was XP only and you have Vista, or vice versa. And unless you really know what you're doing, you can't be sure it didn't stealthily install some crapware alongside it. Finally, clean up the mess it left behind when installing (extraneous icons, shortcuts, start menu entries, etc).
Ubuntu? Open Synaptic and click whatever you want. Then ignore it. It'll download, configure, and install without any further interaction, and there's accountability for who made it and where it is coming from. You're done.
2- Linux Geeks expecting average joe to spend time (which he doesn't have) browsing at forums for his answers, often "on his 2nd computer" (which he doesn't have either).
No one expects this. And honestly I have never, ever had trouble with drivers on any machine, on any distro -- including random ones like DSL, Puppy, or other ones I just want to use for experiments. The sole exception has been wireless Broadcom stuff...and that headache stopped over a year ago with the Restricted Drivers manager.
Compare this to Windows, where I've never gotten an install to work the first time. A clean install of Windows will not have drivers for your wireless or ethernet, sound card, video card, and probably a few other things. You either have to have some sort of recovery CD, which Joe User doesn't have lying around, or you have to have...a second computer, so you can go to dell.com or whatever, and download the drivers. Then install them one at a time, by hand. And clean up the mess they leave behind, again.
I guess my point is that Linux in general and Ubuntu does a much, much better job at hardware detection and driver handling. Windows is essentially incapable of it, and either way, if you're Joe User, you don't know how to fix Windows problems any more effectively than Linux problems, so it's kind of a null point.
No, I think the real reason Ubuntu doesn't have a solid base of home users is because the overwhelming majority of users just buy a computer that has Windows already on it, and stop thinking about it right then. They see no reason to switch because to most people, "Windows" IS a computer, and the only other option is to buy a Mac. So they put up with Windows' endless annoyances and nagging because it's what they're used to, and are blissful in their ignorance.
mirrorshades radio -- darkwave, industrial, futurepop, ebm.
If I have Ubuntu why the hell do I want 3 Apples?
I have the problem that caused a huge amount of discussion here before, where the disk in the laptop repeatedly parks and then wakes a few seconds later to write something. I have used up about 1/3 of the lifetime limit on the disk for these parks. I have updated from Feisty to Gibbon and Hardy and it is still there.
I have a script to turn off the disk timeout to fix this. However I have to run it manually every time I unsleep the machine. I have followed the instructions to install it in init.d and power on/off but it appears to have no effect. Either it is not run or it's changes are undone after it is run. This is very frustrating and I see absoltely zero information about this.
I heard there was some analysis about why Windows does not have this problem, and it was determined that Windows reads the disk *continuously* until it sleeps. This led the manuafacturers to adjust the timeout very small so it is, in effect, a fast "Windows is sleeping" detector. Now it appears that Linux is using the disk far less often, but not zero, so the result is worse for the disk. It would be really cool if Linux actually stopped reading the disk at all when nothing is happening, but I realize this is difficult, so I think an acceptable solution is to replicate how Windows acts.
In any case, despite all the yakking about this earlier, I see no comments. Have they addressed this or not? Is it ever going to be fixed? Or can somebody tell me how to debug the init stuff and find out why my script has to be run manually?