Mark Seger wrote:
> now the bad news - after my system rebooted it started to reimage again
> and si_netbootmond IS running. I then took a look in /var/log/messages
> and saw the following:
>
> Dec 19 11:12:09 cag-dl380-01 kernel: application bug: rsync(17523) has
> SIGCHLD set to SIG_IGN but
good news adn bad news...
The good news is this worked fine without yuok, which makes me wonder
what was so different in this version that it could see the disks and
the older, 3.8.1 couldn't - I'd think that's pretty basic stuff. Anyhow
I'm not going to worry about it if you're not. I'm happ
Mark Seger wrote:
> I should probably know better but I don't, even though I've been using
> SystemImager for a very long time and now I'm faced with a kernel that
> can't see my hard drive and so need to get UYOK working. The
> documentation implied that it just worked yet SI insists on loadin
It's coming back to me, because I'm pretty sure I had gotten this to
work at one time... I put a hard link in my /tftpboot directory to the
images in /usr/share/systemimager/boot/x86_64/myimage/kernel and
initrd.img and verified those files listed in /tftpboot are indeed the
same size.
Then I
I should probably know better but I don't, even though I've been using
SystemImager for a very long time and now I'm faced with a kernel that
can't see my hard drive and so need to get UYOK working. The
documentation implied that it just worked yet SI insists on loading
BusyBox. Is there some
