how about using initrd-inject?
https://lists.fedoraproject.org/pipermail/virt/2011-January/002508.html
--
Eero
2013/8/8 Oguz Yilmaz <oguzyilmazlist@xxxxxxxxx>
> As you can see from my post in kickstart list, this method will not work.
>
> --
> Oguz YILMAZ
>
>
> On Thu, Aug 8, 2013 at 8:11 PM, Manish Kathuria <
> mkathuria@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
> > On Thu, Aug 8, 2013 at 9:03 PM, Oguz Yilmaz <oguzyilmazlist@xxxxxxxxx
> > >wrote:
> >
> > > Actually I have tried lots of things. As far as I see, this is not as
> > > simple as a symlink. Anaconda C application find CDROM according to
> some
> > > info provided by kernel. Also, Anaconda stage1 has a very limited debug
> > > option. I have possibilities to recompile kernel with some options or
> run
> > > kickstart with some kernel arguments. My original problem can be found
> at
> > > the following mailing list thread:
> > >
> > >
> > >
> >
> http://article.gmane.org/gmane.linux.redhat.kickstart.general/9616/match=%5D
> > >
> > >
> > > --
> > > Oguz YILMAZ
> > >
> > >
> > > On Thu, Aug 8, 2013 at 6:23 PM, Manish Kathuria <
> > > mkathuria@xxxxxxxxxxxxxxxxxxxxx> wrote:
> > >
> > > > On Thu, Aug 8, 2013 at 8:39 PM, Oguz Yilmaz <
> oguzyilmazlist@xxxxxxxxx
> > > > >wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > I have a problem with older version of anaconda linux installer. I
> > have
> > > > > upgraded kernel in my distro, but, when this anaconda boot with new
> > > > 3.4.52
> > > > > kernel, can NOT find cdrom. As far as I understand, this is because
> > the
> > > > new
> > > > > kernel recognize cd drive as srX, scdX instead of older hdX with
> > > 2.6.18.
> > > > At
> > > > > the moment I can not upgrade anaconda and forced this kernel to
> > > recognize
> > > > > it as before.
> > > > >
> > > > > Are there any kernel command line argument, kernel config or
> > something
> > > > else
> > > > > for kernel 3.4.52 to recognize this cdrom as hdX?
> > > > >
> > > > > Best Regards,
> > > > >
> > > > > --
> > > > > Oguz YILMAZ
> > > > >
> > > >
> > > > I think you need to write some udev rules to name the device
> > differently.
> > > > Refer to the following:
> > > >
> > > > https://www.kernel.org/pub/linux/utils/kernel/hotplug/udev/udev.html
> > > > http://www.linuxforu.com/2012/06/some-nifty-udev-rules-and-examples/
> > > > http://www.reactivated.net/writing_udev_rules.html
> > > >
> > > > HTH,
> > > > --
> > > > Manish Kathuria
> > >
> > >
> > If you have references to cdrom in your kickstart file, as you have
> > mentioned in that forum, try to change them to match the device name
> being
> > assigned by the kernel.
> >
> > --
> > Manish Kathuria
> > _______________________________________________
> > CentOS mailing list
> > CentOS@xxxxxxxxxx
> > http://lists.centos.org/mailman/listinfo/centos
> >
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
