Install parameters
Stew, RC1, trying to do an FTP install. PowerComputing Powercentre 120, 112MB RAM, 2GB HD, onboard net. First, I can't even get the installer to work properly unless I specify root=/dev/ram3 second, if I do that, I get corrupted video. Third, if I put install-text before or after the root command, the installer won't work properly (it complains about the FS being read only) Any ideas ?
Re: MOL 0.9.68
On Sat, 22 Mar 2003, Christian Walther wrote: > Stew, what sources are you using to build mol-0.9.68-3mdk.ppc.rpm (and > -2mdk and kmods for benh-7mdk and benh-9mdk)? I'm having a problem with > it that its author Samuel Rydh says has been fixed in the release > 0.9.68 version (keyboard behaving as if keys were still down after > releasing them in Mac OS X, see > http://lists.maconlinux.org/pipermail/mol-general/2003-March/ > 001368.html). > Saw that post. It's the tarball Samuel announced, I think. > My original idea was trying to compile the release 0.9.68 myself, but I > can't do that because I don't have the kernel headers for benh-9mdk in > /usr/src/linux/include. I've looked at kernel-benh-2.4.20-9mdk.src.rpm, > but it doesn't look to me as if I could easily get these headers out of > it (Do all these patches have to be applied? The README says something > about not placing stuff in /usr/src/linux... is that applicable? I > don't have anything in /usr/src/linux.). > If you build kernel-benh from the source rpm, and then leave the tree in your rpm/BUILD dir, the mol-kmods-benh should build against that. That is how I've been doing it, since I'm not shipping kernel-benh source or headers. All the appropriate srpms should be on my web space. If you do make any progress with the OS/X keyboard issue, I'd like to hear about it. I don't have OS/X myself to test it. Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/ppcFAQ.php3 IRC: irc.freenode.net #cooker-ppc Archives: http://marc.theaimsgroup.com/?l=mandrake-cooker-ppc&r=1&w=2
MOL 0.9.68
Stew, what sources are you using to build mol-0.9.68-3mdk.ppc.rpm (and -2mdk and kmods for benh-7mdk and benh-9mdk)? I'm having a problem with it that its author Samuel Rydh says has been fixed in the release 0.9.68 version (keyboard behaving as if keys were still down after releasing them in Mac OS X, see http://lists.maconlinux.org/pipermail/mol-general/2003-March/ 001368.html). My original idea was trying to compile the release 0.9.68 myself, but I can't do that because I don't have the kernel headers for benh-9mdk in /usr/src/linux/include. I've looked at kernel-benh-2.4.20-9mdk.src.rpm, but it doesn't look to me as if I could easily get these headers out of it (Do all these patches have to be applied? The README says something about not placing stuff in /usr/src/linux... is that applicable? I don't have anything in /usr/src/linux.). -Christian
Re: Networking Difficulty in RC1 (fix and another problem)
If you're using dhcpcd (and that's pretty standard) the nameserver
IP-adresses will be placed in the /etc/resolv.conf (together with
search
domain). Only if you specify the option -R this file will not be
changed
by dhcpcd. Look for dhcpcd in the ps aux listing to see which options
are used.
Apparently I'm not using dhcpcd but dhclient. Some debugging shows that
/sbin/dhclient-script, which (among other things) should rewrite
/etc/resolv.conf, is the culprit. I can fix the problem by changing
lines 23-31 of /sbin/dhclient-script from
function make_resolv_conf() {
if [ -n "$new_domain_name" -a -n "$new_domain_name_servers" ]; then
echo search $new_domain_name >/etc/resolv.conf
for nameserver in $new_domain_name_servers; do
echo nameserver $nameserver >>/etc/resolv.conf
done
[[ -x /sbin/update-resolvrdv ]] && /sbin/update-resolvrdv
fi
}
to
function make_resolv_conf() {
if [ -n "$new_domain_name" -o -n "$new_domain_name_servers" ]; then
echo >/etc/resolv.conf
if [ -n "$new_domain_name" ]; then
echo search $new_domain_name >/etc/resolv.conf
fi
if [ -n "$new_domain_name_servers" ]; then
for nameserver in $new_domain_name_servers; do
echo nameserver $nameserver >>/etc/resolv.conf
done
fi
[[ -x /sbin/update-resolvrdv ]] && /sbin/update-resolvrdv
fi
}
because for me, $new_domain_name is empty while
$new_domain_name_servers contains the DNS addresses. Linux gurus out
there, are these changes reasonable? Do they break anything?
Once I put a name server address into
/etc/resolv.conf, everything works, but according to man resolv.conf,
this isn't the recommended way.
Where did you find that? I read in the man-pages that /etc/resolv.conf
is not necessary if you're running a nameserver on the local machine,
which to my opinion is not reasonable for a desktop machine.
man resolv.conf says "On a normally configured system, this file should
not be necessary. The only name server to be queried will be on the
local machine, the domain name is determined from the host name, and
the domain search path is constructed from the domain name." Apparently
its author doesn't consider machines not running a nameserver "normally
configured". This lead me to believe that running a local nameserver
was the normal way of dealing with DNS in linux.
While playing around with the DHCP stuff, I came across another
weirdness: Whenever my machine is being configured by DHCP, its
hostname is "x1-6-00-03-93-ce-13-e6". This contains the hardware
address of the ethernet interface, but where does it come from? The DNS
hostname for the IP address provided by DHCP is something like
"dclient80-218-137-66.hispeed.ch". When logging into Gnome, this causes
an error dialog about not being able to look up an IP address for
"x1-6-00-03-93-ce-13-e6". When I'm not connected to the network, the
hostname is "localhost".
-Christian
