dann frazier wrote:
> On Mon, Mar 19, 2007 at 09:30:14AM +0100, Andrea Righi wrote:
>> the idea to copy the distro specific udev configuration is great, but
>> it's not so simple to realize. The main problem is that potentially
>> a generic udev config can require a lot of packages, and we can't
>>
Hi all:
I would just like to report that following dann's suggestions I have
code which copies udev configuration from the OS to the initrd and it
worked fine under Fedora Core 7 Test 2 (which uses 2.6.20 kernel).
It does copy a lot of configurations that may not be relevant, so we
may consider t
On Mon, Mar 19, 2007 at 09:30:14AM +0100, Andrea Righi wrote:
> the idea to copy the distro specific udev configuration is great, but
> it's not so simple to realize. The main problem is that potentially
> a generic udev config can require a lot of packages, and we can't
> include all the possible
dann frazier wrote:
> On Fri, Mar 16, 2007 at 12:28:05AM -0700, Bernard Li wrote:
>> Hi dann:
>>
>> On 3/14/07, dann frazier <[EMAIL PROTECTED]> wrote:
>>
>>> This is probably a distro-specific udev config, so kernel-rev only
>>> isn't enough info. Right answer is to use the distro's udev config.
>
On Fri, Mar 16, 2007 at 12:28:05AM -0700, Bernard Li wrote:
> Hi dann:
>
> On 3/14/07, dann frazier <[EMAIL PROTECTED]> wrote:
>
> >This is probably a distro-specific udev config, so kernel-rev only
> >isn't enough info. Right answer is to use the distro's udev config.
>
> I guess this would wor
Hi dann:
On 3/14/07, dann frazier <[EMAIL PROTECTED]> wrote:
> This is probably a distro-specific udev config, so kernel-rev only
> isn't enough info. Right answer is to use the distro's udev config.
I guess this would work with UYOK, but is there a way to also "solve"
this for the default ramdi
On Wed, Mar 14, 2007 at 01:21:20AM -0700, Bernard Li wrote:
> Hi Allan:
>
> Okay, figured it out -- I guess starting with 2.6.20, all HDs are treated as
> 'sdX', so if SystemImager thinks that your HD is 'hdX' then you will get the
> kernel panic when the client boots.
>
> The workaround for now,
Hi Allan:
Okay, figured it out -- I guess starting with 2.6.20, all HDs are treated as
'sdX', so if SystemImager thinks that your HD is 'hdX' then you will get the
kernel panic when the client boots.
The workaround for now, is to boot the imaged client into rescue mode,
modify /boot/grub/menu.ls
