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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

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...

It's been some time since I did any work on that old laptop. I've been away on holiday and then very busy.
So this evening I tried to get my head back into configuring eth0.
I've come up with a couple of ideas and tried them to no avail. Here goes -

A friend found a suitable power supply. So the laptop is up and running again.
I haven't done any more than hunt around on the 'net, in forums and news groups, and read Slackbook and more from Absolute BSD. All very useful stuff but I haven't found an answer that satisfies my need to understand what's going on.
I could simply ask on the forums what files I need to edit and how, but that wouldn't be entirely satisfactory unless it came with an explanation of what's going on.
...