SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
# Config information for eth0:
IPADDR[0]="192.168.0.206"
NETMASK[0]="255.255.255.0"
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""
# Default gateway IP address:
GATEWAY="192.168.0.1"
This snippet is from my file, where I've set the IP address, and the netmask, and any references to DHCP are left blank
And if you need to set it using a command you can use ifconfig (man ifconfig for further help). But the way cavalier said is the "correct" one in Slackware
It might be a good idea to enter your changes into '/etc/hosts', and if you played around with the name of your machine, '/etc/HOSTNAME'. However, to do everything that should be done, use '/sbin/netconfig'.
What GUI? Slackware provides a bunch of GUIs. Note that netconfig is an ncurses tool which I believe also falls in the category of GUI. If there are other GUI tools, I would still use netconfig. It's the right tool for the job, though editing the files with vi is nice, too (but not a GUI).
Yes Damon Spector there's a GUI, I worked long time ago with a Fedora server and I remember there was one, I think it was called just Network Settings or Ethernet Settings (I could add/remove/configure the network cards I had in that little app too).
Just on topic, this is a Slackware forum, and often in Slackware things are done by editting text files and that's why you're going to see these suggestions about editing files that I think you won't have in Fedora (ifconfig applies to all distributions, same for /etc/resolv.conf and route).
shilo: ncurses is more graphical than vi? i think that, by definition, neither are at all graphical. i fail completely to see how you're drawing that distinction. perhaps you mean that editing a file in vi lacks a scripted user interface...?
Sure, fire up netconfig in a terminal from an X session. The first thing you see is a screen to enter your hostname. At the bottom, there are two "buttons", OK and Cancel.
Now for the gui trick, click Cancel with your mouse. Seems like a GUI to me. vi is not a GUI because you need to know commands to control vi itself. With ncurses, you do not need to know how to control the script. It functions identically to a GUI. You've got text input boxes, selection buttons, etc. You are able to click buttons with your mouse, use the arrow keys to move around, etc.
Looks like a GUI, acts like a GUI, I say it is a GUI.
What do you think? I'm really intersested in knowing, because I just started wondering, when is something a GUI? define:graphical over at google is interesting.
***EDIT***
Almost forgot, there is an easy to use GUI tool in Dropline Gnome. Don't know if that helps you at all.
If you happen to be using Dropline Gnome, it's "Gnome Menu Button -> System Tools -> Network Tools". It's really handy. You can configure your network interfaces (set static or dhcp, set ip address, gateway, subnet), view packet transfer statistics, ping addresses, , port scan servers, run finger, do whois lookups, view routing table info, view active network services, etc. It's really handy. It's laid out really nicely, too.
This is a total thread derail
As I understand it, a graphical user interface is something that actually has graphics. There were applications such as 'edit' in DOS, which had GUI-esque features, but nobody said that they had GUIs. The mouse-clickery in netconfig is an adaptation to use in a window manager -- a GUI.
The term GUI has nothing to do with the use of a mouse or the requirement of command knowledge; it has to do with graphics, hence the acronym.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.