psypher: “... can anyone point me to a really good live cd howto that
would apply to hardy but which uses grub as a bootloader instead of
syslinux?”
I use GRUB in building all my UFDs. Not an expert, but I do it and write up a
how-to for others. I'm currently updating this for Hardy, but it's
I don't know the extent this would help you guys, but ...
Short version: I (and others, but not everyone) found that to make this
work best, and specifically to ensure persistence, it helps to use ext3
for the casper-rw partition (and I have used ext3 for both partitions
this time with 8.04: the
I use GParted Live CD to partition and format everything :)
(haven't used CLI for such for a long time, but I'm sure someone here does)
--
[hardy] livecd: keyword "persistent" results in busybox and (initramfs)
https://bugs.launchpad.net/bugs/219192
You received this bug notification because you
For me, same as reported by waxhell (above). Issue with: Kubuntu 7.10 on UFD,
Live Persistent.
I've tried using ext3 and I get the same segmentation fault. I did not test
the extent of data corruption using ext3 (vs ext2), but I suspect it will show
up upon repeated re-boots.
I have also seen
As waxhell also reported, it seems to be working better with casper-rw
formatted as ext3 instead of ext2. In fact, everything thus far seems
fine after 4 re-boots and conducting persistent activity each time. But
I do get some messages:
When I log out and re-boot from the live persistent session
Ron Z, that's not the case for my experience with this bug (corrupt
files already there somehow)--it's clearly a shutdown issue for me &
have seen this elsewhere, too.
btw,
As for the flash drive, if I have a working, bootable flash drive (e.g., live
persistent Kubuntu 7.10), I clone it easily w
I'm sending the files you requested. Hope this flies -- I'm new at this.
Mike
** Attachment added: "dmesg"
http://librarian.launchpad.net/6479737/dmesg.log
--
Restart doesn't work in Kubuntu 6.10
https://launchpad.net/bugs/75051
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
uname -a
Linux mike-desktop 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686
GNU/Linux
** Attachment added: "lspci"
http://librarian.launchpad.net/6479736/lspci-vvnn.log
--
Restart doesn't work in Kubuntu 6.10
https://launchpad.net/bugs/75051
--
ubuntu-bugs mailing list
ubuntu-bug
There's the info you requested (above). Please note that I did apply
the "fix" mentioned above quite some time ago. I found that fix at the
Kubuntu forum.
Also, in the kernel update, 2.6.17-11 I did NOT have this problem.
(I logged into the "old" 2.6.17-10 to get the files you asked for.)
Of c
Brian:
That's correct: no problems with 2.16.17-11. (The problem was only with
2.16.17-10.)
Thanks,
Mike Anderson
- Original Message -
From: "Brian Murray" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2007 11:40 AM
Subject: [Bug 75051] Re: Restart doesn't wor
Public bug reported:
(I'm new to Linux)
I downloaded and installed Kubuntu 6.10 on 11-18-06.
If I try to click the Re-start button (in the shutdown menu from
K-menu), it looks like it is going to re-start, but actually the screen
just goes black and sits there . . . until I manually press the res
Public bug reported:
(I'm new to Linux)
I downloaded and installed Kubuntu 6.10 on 11-18-06.
If I try to click the Re-start button (in the shutdown menu from
K-menu), it looks like it is going to re-start, but actually the screen
just goes black and sits there . . . until I manually press the res
Just a general comment as I stumble on this "bug" report:
I have routinely installed GRUB 2 to various partition boot sectors
(as with sudo grub-install /dev/sdxn), and never had a problem using that to
chainload the partition. I do, however, get that Warning message
(This is a Bad Idea, etc.).
Me, too.
With both 1.97 beta3 and beta4. Dual boot/two drives. 70-second delay.
The "problem installation":
Dual booting two hard drives (on an Intel D915GAVL mobo).
GRUB 2 is installed to the MBR of sda, and sda is the first BIOS boot drive.
The Kubuntu 9.10 OS (where /boot/grub is) is on sdb2
A user shouldn't have to change the boot order to get the new-and-
improved GRUB to work reasonably well.
Many users have Windows on a first-in-BIOS HDD "sda" and boot from that
HDD by installing GRUB to its MBR, in preference to maintaining their
Windows on a non-first HDD (requiring devicemap an
"Windows update shouldn't at all affect this."
Actually, I've only been told this and read it from rabbit Windows
users, just hearsay; namely that after certain updates that also tamper
with their boot/bootmanager, they find problems with their dual booting
and have to re-install GRUB to fix it.
16 matches
Mail list logo
