i ignored that on first glance at it as it seemed to only apply to a proud new tool available in gnome, or selinux or doc issues, but in looking there anyway it does seem to reveal they want us to use bugzilla. <div class="gmail_quote"> On Thu, Aug 5, 2010 at 1:39 PM, Marhn Fullmer <<a href="mailto:mhfullme@ncsu.edu">mhfullme@ncsu.edu</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> HI, <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Beta_2_Release_Notes/" target="_blank">http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Beta_2_Release_Notes/</a> -> "A. Reporting Issues for Red Hat Enterprise Linux 6 Beta " hth, marhnyi >>> gregwm <<a href="mailto:rhelv6-beta-list@greatlakedata.com">rhelv6-beta-list@greatlakedata.com</a>> 08/05/10 2:07 PM >>> <div><div></div><div class="h5">should i consider items sent to this list to be adequately brought to redhat's attention? fine with me to consider rhel6 unready for prime time and just not worry about it personally, but i am curious if the problems i've reported on this list get to the developers attention in due time, or if that will only happen if i report them via some other channel? On Sun, Aug 1, 2010 at 6:55 PM, gregwm <<a href="mailto:rhelv6-beta-list@greatlakedata.com">rhelv6-beta-list@greatlakedata.com</a>>wrote: > i'm trying to do remote installs onto 2 sun x2100 m2's and a sun x2100 in a > datacenter. both m2's get stuck "Waiting for NetworkManager to configure > eth0"(or eth1)..."There was an error configuring your network interface." > the x2100 does not get caught there, it asks for the nfs server > information, but it can't seem to find the server nfs directory. when > retrying, it seems images/install.img always gets appended to the directory > name, but adding those names at the nfs server doesn't help (lacking a LOM > the x2100 is thus stuck until human hands are available). here's what i > give via either grub or pxe: > > - r6.vmlinuz initrd=r6.initrd.img lang=en_US keymap=us ksdevice=eth1 > netmask=255.255.255.240 gateway=192.168.0.245 dns=192.168.0.244 > ip=192.168.0.246 hostname=bleep quiet panic=30 vnc vncpassword=foo askmethod > > if there's a better way for me to be trying to do this please let me know. > however running rhel5 remote installs on the same machines in the same > environment and with the same inputs does not encounter any of these > problems. </div></div></blockquote></div>