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.
Ok. I've used Debian for quite some time -- although I started with Slackware years back -- and it's been awhile since I attempted anything without a package manager!
I grabbed a copy of Slackware Disc 1 and installed a basic, console-only Slackware.
First snag...WiFi. I live in a busy neighbourhood full of students eager to grab "free" internet off a WEP-encrypted wireless router, so WPA is a must. Well, /etc/rc.d/rc.inet1.conf didn't seem very happy to play...
I have three Linux Servers running Samba shares in them. All are meant for different purpose. For administrative purpose and running some utilities in these servers\shares from Windows XP system, we use "net use Drive: \\ServerName\ShareName" command to map the share as a drive. During the process for each server we are to enter username and password. Is there a way by which I use my windows username and password for the logon.
Note: The Samba username and password are similar...
The short answer could have been "utilize analog and digital inputs" but my case here is quite old system having only one input.
I didn't really look into this question until I had to, today.
Some days before, when I was experiencing troubles with sound in Steam I installed pulseaudio and during search for it noticed "network" word in description. So I thought maybe I can set it up so I will send sound from second computer to first(over gigabit home LAN), which...
When you write scripts dealing with setting up or analyzing network interfaces you will eventually run into the task of converting a netmask from one format into another.
Typically, the setup of an ethernet TCP/IP network interface consists of an IP address, a netmask, and a broadcast address. Unfortunately for you as a novice, the two tools ifconfig and ip show the same (or similar) information in a different format.
Everybody has a different idea of how to get connected. More and more people only look for automagic network connections or fancy GUIs to accomplish their bidding, but that's not me. So, in the interests of old hardware and always knowing exactly where I'm getting a connection, here's my methodology.
This involves modifying /etc/network/interfaces and the use of some simple bash scripting. Pertinent info on the networking process can be found in the Debian Reference Manual, chapter...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.