First off- apologies for the length of this off-topic post to the digest
users. For the rest of the list judicious use of the 'D' key is advised :)
Chris,
I'm happy to take this off-line, feel free to e-mail me directly.
On Fri, Feb 17, 2017 at 04:46:12PM -0700, Chris Trask wrote:
> I found that TERMINAL was the routine that is similar to DOS shell.
OK... I'm already making assumptions... These things are a natural
command line environment where the GUI is an add-on. I'd decided that
you must have already had a CLI screen up. :)
> So, I used your suggestion to edit the configuration file, and it
> worked fine except that I still have no network configuration.
Did you do anything else after that? If not, only the config file has
been changed... The system, or in this case the 'user' application,
will re-read the config file only when it is told to. e.g at boot, or
when a "kill 1 <process-id>" is issued.
A simple reboot might solve this for you, or while the system is live
(from a forum post
https://forums.linuxmint.com/viewtopic.php?f=42&t=92488 ):
sudo service network-manager stop
sudo rm /var/lib/NetworkManager/NetworkManager.state
sudo service network-manager start
I'm not sure if the middle one is required - as I would have expected
any state files to be deleted at stop (and the command will throw an
error) - but then again, given the way some of this stuff is written,
it might be critical to success!.
> I'm wondering if I should assume that specific drivers are needed and
> use the driver CD for this laptop. I'll try that later.
Drivers are specific to the kernel version, and exist as a series of
loadable modules somewhere in the boot path. it's unusual for a module
for supported hardware not to already be there. To add support for
newer hardware it's usual to need to do a version upgrade, but if it
says your laptop (or network/wifi chipset) is supported it should all be
there already. You may, however, need to tell the system to load the
kernel modules you need.
Linux/UNIX is a complete change in mindset from windows, being a DOS
user from way back you should already have almost all the tools you need
- many of the DOS interactions work in the terminal window(s). Once you
throw on the Xorg and the window manager (I'm assuming KDE here) GUI, it
has more in common with W3.11 than the later W... versions :) (IMHO)
PC-DOS was a direct ripoff of the CP/M user interface, which copied a
lot of the useful features of UNIX. Things like 'more', <, |, >, and ^C
all work as expected in a CLI/terminal window.
The documentation manuals are usually all there, also (but some of them
are simply indecipherable :) ) To use it, use the command "man <xxxx>",
e.g.:
"man ls"
"man more"
With Linux/UNIX you have a LOT more control over what is happening, and
consequently have a lot more responsibility for taking care of business.
With many of these distros they are set up to go 'out of the box' for a
few typical setups, but not much needs to change for the less-typicals.
None of it is really that hard, but there is a lot of it. It can't be
that bad, as there is a LOT of Linux in use out there. As a result
there is a lot of help out there, though (but you need a functional
machine/internet for accessing it).
davidt
--
_________________________________________________________________
Options: http://lists.thomasclausen.net/mailman/listinfo/olympus
Archives: http://lists.thomasclausen.net/mailman/private/olympus/
Themed Olympus Photo Exhibition: http://www.tope.nl/
|