On Lu, 23 aug 10, 07:20:25, Stephen Powell wrote:
>
> in /etc/lilo.conf. Note that there is another symlink which also points to
> ../../sda. It starts with "scsi". You don't want to use that one, because
> it only exists when using the libata drivers. The one which starts with "ata"
> will ex
On Mon, 23 Aug 2010 05:13:56 -0400 (EDT), David Baron wrote:
>
> Thanks. This, of course, simply reeds of the /dev/disk/by-uuid symlinks.
> These only refer to partitions, but the boot= goes to disk MBR, i.e. /dev/hda
> or /dev/sda without any partition number. How do I get that one?
To obtain t
On Sunday 22 August 2010 20:51:07 debian-user-digest-requ...@lists.debian.org
wrote:
> > LVM Uses such a system quite nicely. Question is where I get the UUID's
> > for the two items not in LVM, the /boot and the /root? (Got to get this
> > right the first try ... )
>
> blkid(8) in package util-
On Du, 22 aug 10, 19:04:19, David Baron wrote:
>
> LVM Uses such a system quite nicely. Question is where I get the UUID's for
> the two items not in LVM, the /boot and the /root? (Got to get this right the
> first try ... )
blkid(8) in package util-linux
> (Such a system should be quite movea
> On Sun, 22 Aug 2010 06:39:15 -0400 (EDT), David Baron wrote:
> > Googling found the second alternative. The new sda names are for ALL
> > hard disks, SATA, IDE, SCSI, no matter.
> >
> >
> >
> > So there seems to be no way to keep the two variations, i.e. kernels
> > using the deprecated and th
On 2010-08-22 12:39 +0200, David Baron wrote:
> Googling found the second alternative. The new sda names are for ALL hard
> disks, SATA, IDE, SCSI, no matter.
>
> So there seems to be no way to keep the two variations, i.e. kernels using
> the
> deprecated and the new PATA around. fstab must us
On Sun, 22 Aug 2010 06:39:15 -0400 (EDT), David Baron wrote:
> Googling found the second alternative. The new sda names are for ALL hard
> disks, SATA, IDE, SCSI, no matter.
>
> So there seems to be no way to keep the two variations, i.e. kernels using
> the
> deprecated and the new PATA around
On Friday 20 August 2010 10:04:54 David Baron wrote:
> I built this kernel for first time with new PATA rather than the old
> deprecated drivers. These are compiled-in, no initrd. Get cannot find block
> error, [2,22] or something like that.
>
> Possibilities:
> 1. Need to compile in VIA's driver
On Sat, 21 Aug 2010 15:02:26 -0400 (EDT), David Baron wrote:
>
> The MB of the current machine is an older "AOpen" with a VIA chipset.
> The new one will be a Winsonic with Intel chipset. That has both SATA and IDE
> and my current disks will be placed on the IDE as now.
I don't have any first-h
On Friday 20 August 2010 12:18:11 debian-user-digest-requ...@lists.debian.org
wrote:
> > I built this kernel for first time with new PATA rather than the old
> > deprecated drivers. These are compiled-in, no initrd. Get cannot find
> > block error, [2,22] or something like that.
> >
> >
> >
> >
Am 20.08.2010 09:30, schrieb David Baron:
I built this kernel for first time with new PATA rather than the old
deprecated drivers. These are compiled-in, no initrd. Get cannot find block
error, [2,22] or something like that.
Possibilities:
1. Need to compile in VIA's driver as well. Not doing th
David Baron put forth on 8/20/2010 2:04 AM:
> I built this kernel for first time with new PATA rather than the old
> deprecated drivers. These are compiled-in, no initrd. Get cannot find block
> error, [2,22] or something like that.
>
> Possibilities:
> 1. Need to compile in VIA's driver as well
I built this kernel for first time with new PATA rather than the old
deprecated drivers. These are compiled-in, no initrd. Get cannot find block
error, [2,22] or something like that.
Possibilities:
1. Need to compile in VIA's driver as well. Not doing this prevented DMA
access using deprecated
13 matches
Mail list logo
