New to everything - Ports.

K

kasumi

Hello. ;)

Well, as already said, I'm quite new to everything related to FreeBSD, but I've been using PCBSD several months.

I'm currently running Slackware here, because of the missing software I'd like to switch to FreeBSD now, I've already read about the ports and packages.

OpenBSD was the system running on my server once, I downloaded the ports from the University in Erlangen, everything worked fine for me. But for some reason the server broke down.

I want to use FreeBSD on a Desktop PC (2,8 Quad, 4GB RAM) and the first question is; How do I install applications? What's the command for downloading the ports? Please name a server in Europe, no too far away from Austria. ;D

On OpenBSD, I had to cd to the right directory and run "make install" in order to make the software running. The most important thing for me would be a Desktop, either GNOME or Fluxbox/Openbox. I couldn't really understand the handbook, so I'm posting in this forum..

Please help,

kasumi
 
So, everything runs now, but now I fail on configuring the Internet connection in sysinstall.

Host, Domain, IPv4 Gateway, Name Server.......... what are these?
 
All of that config depends on the network setup you have. The gateway is the device which grants you access to the internet for example.
 
Code: 
# ifconfig

em0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
 options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
 ether 08:00:27:68:dd:fc
 media: Ethernet autoselect (1000baseT <full-duplex>)
 status: active
lo0: flags=8808<LOOPBACK,MULTICAST> metric 0 mtu 16834
 options=3<RXCSUM,TXCSUM>

Well... how do I configure everything? :(
 
Code: 
# sysinstall

then select Configure, then Networking and then Interfaces which will show you a dialog how you want to configure your network interface.
 
in /etc/rc.conf
Code: 
ifconfig_em0="123.123.123.123 netmask 255.255.255.0"
defaultrouter="123.123.123.1"
replace 123.123.123.123 with your IP
replace 123.123.123.1 with your ISP gateway

in /etc/resolv.conf
Code: 
nameserver 123.123.123.1
nameserver 123.123.123.2
Here IPs are IPs of your ISP DNS servers

If you don't have static IP, then simply in /etc/rc.conf add
Code: 
ifconfig_em0="DHCP"

More info in handbook, rc.conf(5) and ifconfig(8)
 
When I enter "ee rc.conf" and change something, I get the following error message: "unable to create file rc.conf"
 
kasumi said:
When I enter "ee rc.conf" and change something, I get the following error message: "unable to create file rc.conf"
Click to expand...

You need to be root user. If your in wheel you can change your user with the switch user command su()
 
Why did I do what?

And what wheel do you mean? Well... /etc/sudoers does not seem to exist, if that is what you're talking about.
 
kasumi said:
Why did I do what?

And what wheel do you mean? Well... /etc/sudoers does not seem to exist, if that is what you're talking about.
Click to expand...

don't run chmod on those files.

log off your user and log on as root

then you can run your editor.

consider putting your user in the wheel group so you can switch to root from your user in the future.
 
And what wheel do you mean? Well... /etc/sudoers does not seem to exist
Click to expand...
You must install sudo from ports and after edit sudoers file on /usr/local/etc
Logout and login as root.
Code: 
cd /usr/ports/security/sudo
make install clean
after:
Code: 
cd /usr/local/etc
ee sudoers
Put user on sudoers. Log out and login as user. Use sudo for your jobs :)
 
You should really read the handbook :)

If there is no sudoers file like in Linux, you can get the port for sudo from the ports directory.
 
kasumi said:
# chmod 777 rc.conf
chmod: rc.conf: Read-only file system

What now? >.< I'm getting disappointed.
Click to expand...

First: FreeBSD is not a funny-looking Linux. Some things are different. Keep this in mind.

Second: a read-only filesystem is usually due to yanking the power without shutting down. Boot normally and wait, and the system will automatically repair the filesystems.

Third: after the initial install, don't use sysinstall any more. It's built for installing, and if you use it for maintenance, it will surprise you in unpleasant ways.

Fourth: log in as root, or use "su -". sudo is unnecessary at this stage (and many stages).

Fifth: don't 'chmod 777' anything. It is a failure waiting to happen.

Sixth: do one thing at a time. Get your Ethernet card to obtain a DHCP lease before going on to other things. The Handbook covers this and many other things, but if you try to do them all at once it's almost always doomed to failure. Accomplish one thing, then move on to the next. Race car drivers don't drive fast at first, either.
 
When I boot FreeBSD, the last message is:

Code: 
Enter full pathname of shell or RETURN for /bin/sh:
And when I hit enter, I get the #, waiting for my commands.
 
It's booting to single user mode. Did you do that on purpose or was there an error?

Standard way of dealing with single user mode:
Code: 
fsck -y
mount -u /
mount -a -t ufs
swapon -a
 
You must log in or register to reply here.
Back
Top