Yes, i understand that it's a driver for BIOS magic that i'd rather not
use.
When you create a RAID from the BIOS it does a RAID1 or whatever on the
entire array using all the drives you select. You cant do a partial bios
raid setup as this is illogical.
Is there a usage scenario where this
Interesting, thanks for the info. Sorry to flog this to death.
Online ubuntu docs with respect to dmraid are definitely somewhat
scattered and of varying levels of authority. From a naive newer is
better perspective, the page you mention was last edited 2008-08-06,
long before jaunty went live,
I want to reiterate that the original bug was reported against the
_alternate_ install cd. If i understand correctly, the alternate
install cd is required to install using any raid functionality. The
initramfs installed by the alternate cd included mdadm, which was
unexpectedly difficult to
Just to reiterate, I achieved the desired results described in the
original bug after extensive research, trial and error before i filed
the bug.
To get rid of dmraid you just don't install it. The live cd doesn't
have the dmraid package preloaded
Ok. But that's not at issue. The alternate
Public bug reported:
I just finished installing a freshly downloaded jaunty alternate install
cd using mdadm partitions in linux as a dual-boot with windows, leaving
windows in it's factory-fresh fakeraid partition(s). The only
difficult part was getting rid of dmraid.
I first shrank the
I agree. Total regression from circa 2005! Frustrating.
Now we've seen that it's possible to build an image where the token
works a la Jon Packard. Would filing a new bug help get it into the
official package?
2009/4/16 Przemysław Kulczycki przemekkulczy...@gmail.com:
Is it really so hard to
Just to be clear -
This bug is *not* fixed. Upgrading via command line and completely
breaking a working system is not very cool. System critical bugs that
are open for years doesn't bother me half as much as serious bugs
erroneously marked as fixed...
--
Device-mapper errors: dm-linear,
What is the bug number of the original bug? A known issue by whom?
--
nautilus not starting as root when empty cd/dvd is inserted
https://bugs.launchpad.net/bugs/245931
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
It's a little hard to believe the upstream bug is over 6 years old.
Bounty, anyone? I'd put up $5.
Judging by the response of google to gnome-terminal --tab-with-
profile=, and the upstream bug page (
http://bugzilla.gnome.org/show_bug.cgi?id=83203 ) , there's plenty of
room to improve the docs
I tried JohnBender's suggestion, and noticed that a bunch of files were
owned by root. Is there any reason they should be owned by root? On a
whim, I found that the following solved all the problems described
above:
sudo chown -R myusername.myusername .mozilla/firefox
--
Firefox 3 bookmarks
Why is this an invalid bug? Does downgrading nautilus constitute a solution as
mentioned on forums? Is the nautilus-share module part of the problem here?
Some
comment from the triage-er as to status assignment might be useful to users.
Running as root or user, I'm seeing nautilus crash
FIXED - sort of.
I just upgraded BIOS and kernel, and was still having trouble. I
discovered the following restores FN-Home/End functionality as long as
it's run _after_ X starts... No dice if I put it in /etc/rc.local, and I
can't change permission of a /proc file to let .xinitrc do it:
# Happy
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/198476 for lots
of useful info that might be related. I have a T61 that I got working
thusly.
--
LCD Brightness buttons do not work on Thinkpad X61 Tablet
https://bugs.launchpad.net/bugs/172985
You received this bug notification because
Is this bit of news from Debian Live perhaps relevant?
http://debian-live.alioth.debian.org/
2007-05-24: casper is dead, long lives live-initramfs
Forked casper. [...]
--
toRam or copy2Ram (run ubuntu live from ram)
https://bugs.launchpad.net/bugs/25496
You received this bug notification
Yes, the title change seems appropriate:
anacron-controlled crons not running on always-on machines
I may have misdiagnosed my own problems - the cited thread is the
only documentation i've so far found explaining ubuntu's relationship
be cron, anacron, and cron.daily.
Should the title of
just tried again, still not working. this bug seriously limits the
usefulness of all the ubuntu live disks...
looks like we'll have to use damn small linux for testing and thin
clients until this gets fixed.
--
toRam or copy2Ram (run ubuntu live from ram)
https://bugs.launchpad.net/bugs/25496
I just got hit by this when upgrading a modified dapper server to edgy
from commandline using apt-get.
I successfully completed apt-get upgrade but choked on apt-get dist-upgrade.
Looking in /usr/share/locale, I see my locale no longer present.
I'm able to continue by prepending my commandline
I experienced this same problem with X packages on upgrade from dapper
to edgy using CL apt-get.
dpkg -i --force-overwrite worked for me, thanks sooo much!
--
File overwrite problem
https://bugs.launchpad.net/bugs/78974
You received this bug notification because you are a member of Kubuntu
I just tried, toram not working :(
Using casper 1.87 and, i think, 20070417 i386 livecd.
--
toRam or copy2Ram (run ubuntu live from ram)
https://bugs.launchpad.net/bugs/25496
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
19 matches
Mail list logo
