On Sat, 04 Sep 2010 15:18:40 -0400 (EDT), David Baron wrote:
>
> Using the Debian rescue CD, I installed the linux-image-2.6.32-5 and linux-
> base from Sid.
>
> The install edited my fstab and lilo.conf files for me, putting in the UUID
> numbers for everything except lilo.conf boot=. I left th
Using the Debian rescue CD, I installed the linux-image-2.6.32-5 and linux-
base from Sid.
The install edited my fstab and lilo.conf files for me, putting in the UUID
numbers for everything except lilo.conf boot=. I left that as-is /dev/sda but
both variations, UUID and ata-ID had previously wor
> You should be able to install lvm on Knoppix. If you can't and have> access
> to the net, you can download a Debian/Fedora/Ubuntu live cd,> install lvm,
> and mount your LVslvm is on Knoppix. However, support for it is not build
> into the kernel so it cannot mount them. I also cannot chroot--
On Wed, 25 Aug 2010 12:24:15 -0400 (EDT), Tom H wrote:
> On Wed, Aug 25, 2010 at 5:58 AM, wrote:
>>
>> I made changes recommended by replies to my original message since I have no
>> idea what the drive's /dev files will be called on the new system. Low and
>> behold, I get the error on booting b
On Wed, Aug 25, 2010 at 5:58 AM, wrote:
>
> I made changes recommended by replies to my original message since I have no
> idea what the drive's /dev files will be called on the new system. Low and
> behold, I get the error on booting both older 2.6.32 and new 2.6.34 kernels!
> It starts to boot
On Wed, 25 Aug 2010 05:58:11 -0400 (EDT), d baron wrote:
>
> I made changes recommended by replies to my original message since I have
> no idea what the drive's /dev files will be called on the new system.
> Low and behold, I get the error on booting both older 2.6.32 and new
> 2.6.34 kernels! I
On 8/25/2010 4:58 AM, d_ba...@012.net.il wrote:
I made changes recommended by replies to my original message since I have no
idea what the drive's /dev files will be called on the new system. Low and
behold, I get the error on booting both older 2.6.32 and new 2.6.34 kernels! It
starts to boo
I made changes recommended by replies to my original message since I have no
idea what the drive's /dev files will be called on the new system. Low and
behold, I get the error on booting both older 2.6.32 and new 2.6.34 kernels! It
starts to boot up just fine but then panics at the root device w
8 matches
Mail list logo