Date: Sun, 15 Jan 2006 00:19:17 -0800 From: je killen <jekillen@prodigy.net> To: freebsd-questions@FreeBSD.org Subject: Re: Re FreeBSD v 6.0 (boxed cd set) Message-ID: <09851fb4ce2386d27a9a6522e7bd42f1@prodigy.net> In-Reply-To: <90c9d42f5ede53a46d977d3a8ad7eaf5@prodigy.net> References: <c14753a9e71e62c316262e50b39255d0@prodigy.net> <1137223650.8726.30.camel@lmail.bathnetworks.co.uk> <90c9d42f5ede53a46d977d3a8ad7eaf5@prodigy.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 14, 2006, at 12:01 PM, je killen wrote: > > On Jan 13, 2006, at 11:27 PM, Robert Slade wrote: > >> On Sat, 2006-01-14 at 01:01, je killen wrote: >>> (On e-Machine with Intel Sempron processor and 256 mb memory). >>> I'm not able to log into x via kdm as root and not able to su to root >>> when in Gnome (or KDE for that matter). >>> It also goes through what seem to be excessive sleep cycles (two >>> lasting at least a minute apiece) during the boot process >>> to establish the system's name. >> >> Sounds like it is trying to contact a dhcp server and then timing out. >> What does messages or your error logs say? They are in /var/logs couldn't find error log here but I gave it a FQDN in rc.conf and that solved the name delays. >> >>> It refused ssh from my Mac OSX machine (It starts sshd on boot, which >>> also takes a noticeable amount of time) >> >> Check your sshd setup, see man sshd, there are some defaults set in >> the >> conf file there which are causing the restriction. found it in inetd.conf, just a matter of commenting a few lines; one for ftp (which is on my system, I thought so.) and the other for sshd. >> >>> What ftp server is recommended for FreeBSD? (There doesn't seem to be >>> any provided by default install) see above. >> >> You should have been asked if you wanted a ftp server during >> installation. The default is ftp. There are others in the ports >> though. >> See the handbook. >> >>> How do I tell it who it really is? (Is it trying to contact a DNS >>> server and/or /etc/hosts ?) >> >> The host name etc is set in /etc/rc.conf. Again you should have set >> this >> during installation. You can re run the installation process just type >> sysinstall. named is on the system but there's no configuration, just resolv.conf for resolver. I also had the machines own IP address set to default router when it should have at least been the http proxy server I use to get on the net. >> >>> How can I get set up to su to root in a console window? (Or do I have >>> to learn to live with it?) >> >> The default allows only members of the wheel group to su to root. Did it. Now I get into the machine from another host on the network and can su to root in console window. >> >>> If I can't get set up to su to root in a console window, how can I >>> log >>> into an x session as root? >> >> You should be able to log on as root and run an x session as root (not >> recommended). In the kdm login window as soon as it read root as the user name it informed me that root logins aren't allowed. >> >>> (Does it have to do with security levels, or who is a member of the >>> 'wheel' group? Even Mac OSX only allows sudo -- and it is based on >>> FreeBSD, isn't it?) >> >> See above. There could also be an issue with security, it depends how >> you set it during install. >> >>> >>> Thanks >>> JK >>> This is definitely the most active list I've subscribed to (203 total >>> e-mail load yesterday when usually 30 -50 per day with 3 other tech >>> related list subscriptions) >> >> JK Welcome, >> >>> From your questions you are new :-), I was some 5 months ago. >>> Most of >> the answers can be got from the handbook. I've tried to give you some >> pointers to help, but not too much as you do need to become familiar >> with the basics. There are a number of resources about, Google helps >> too. Be prepared for a number of reinstalls :-). you're right. I was just having a spell of laziness. >> >> A couple of pointers - try asking one question at a time and use a >> meaningful subject. That way your problem is likely to standout in the >> number of messages. >> >> I would also suggest that we you get the basic system working, you >> update it, your CDs are likely to be at 6.0R there has been some >> updates >> since. I would suggest that you stay with the 6.0 branch for now. >> >> Good luck. >> >> Rob > > Thanks > JK >> >> >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?09851fb4ce2386d27a9a6522e7bd42f1>