Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
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.
Click Here to receive this Complete Guide absolutely free.
downloaded & installed - although, minor note: had to reinstall with additional features, because the default settings didn't stick the MinGW Shell in the Programs folder
When I attempt to run syslinux from the win32 folder, a small cmd.exe style box pops up very briefly, runs a flash of text, then disappears.
So, I must profess confusion with how to proceed.
I'm also having issues with using WinImage to process the following instructions, although I did create Drive:\...\boot\syslinux\ by making the new folders at location, at least to give myself a reference point, if naught else.
Advice would be very appreciated.
Last edited by .Clockwork.; 11-22-2011 at 06:00 AM.
I run Slackware on almost any of my machines: ASUS eeePC 701 (Celeron M 900MHz, downclocked to 630MHZ, 512MB), Compaq 615 (dual-core Athlon, 4GB), my workstation/gaming rig (Phenom II X6, 8GB)
No need to stick to a server with Slackware. You should really be fine with Slackware on your netbook, may be KDE will be a bit slow with 1GB RAM, but it should fly with XFCE or one of the WMs.
I also only have a 3gig flash drive to work with as my source to install from.
That is no problem at all, just use dd to copy the USB boot image to it and point it to a mirror near you at install time for getting the packages to install.
Love the various stats you gave for comparison, and thank you for the advice concerning an environment friendly with my limited RAM.
Also, something I forgot to include in my initial inquiry: should I write down the information needed for access to the wireless signal I use for my internet? How does Slackware handle detection of wireless internet signals? It's too easy to get used to auto-detection, for that. :/
I never tried to make a network based install using a wireless adapter, don't know if that will work.
For managing wireless once you have installed Slackware there is wicd in the /extra part of the mirrors/DVD.
I don't want to use the network as the basis for the install, but internet via wireless is my only option. I don't necessarily expect Slackware to install with wireless detection, but I want to have my ducks aligned, and preferably before the "knife" is taken to Windows 7, once and for all.
Definitely scribbling a note about wicd, though.
Last edited by .Clockwork.; 11-20-2011 at 06:03 AM.
That sounds quite lovely, Sycamorex; thank you for the input. And your "symbol" indicates your OS as "linuxslackware." Without meaning to be assumptive, that sounds like Slackware does have wireless detection on install?
What I had in mind was to take another, smaller flash drive (1gig), and prepare for the "gutting" process by selecting a few, additional things to compile, post-installation? Though, been out of the loop for long enough that I don't know what comes standard. I'd expect that Slackware would include less than other distributions, which I find exciting, but I want to be as prepared, in advance, as much as possible.
The recommended way of installing slackware is to do the full installation (+4GB) it'll leave you with a functional desktop. For most people, however, (myself included) it's not enough. That's when www.slackbuilds.org comes in. It's a website full of slackbuilds (slackware installation scripts for hundreds of additional programs and libraries).
It gets even better. You can then install sbopkg, a slackbuilds browser which will make the whole process quicker and less time consuming.
edit: I forgot to add Alien Bob's slackbuilds and packages.
I'm very intrigued by this, in particular, because it sounds like it would substantially reduce the need to save additional packages to my other flash drive before gutting out Windows:
So I took Slackware’s “usbimg2disk.sh” script (which I incidentally wrote too) and expanded its functionality. What is new? The script can now copy the Slackware setup files, kernels and packages all to a regular USB thumb drive, if that has a minimum of 2GB free space available.And it still retains its original functionality (to create a bootable installer as long as there is 30 MB of available free space on the stick).
So... any input/advice from experienced "Slackers" concerning this?
Leftover Chinese Food: check
Brain Power: ~72%, recharging
Will re-tackle Alien Bob's page concerning wireless & networks in a little bit. Meanwhile, input from any experienced Slackware users would be very much loved.
As mentioned in the edited title: I also would like more information concerning the "setup files, kernels and packages," so I know what (if anything) else I should be considering preparing, in advance. This would probably be in regards to what all is offered at www.slackbuilds.org.
[Edit]More details may by found in the official announcement and in the release notes. For a complete list of included packages, see the package list.
I am also perusing *these* sections, as well. I prefer firsthand user-input for fleshing out available information, though. [/Edit]
Last edited by .Clockwork.; 11-21-2011 at 12:20 PM.
Before making concerns about the setup files, kernels and packages I would just go for the full install, see what you get with it and then ask here if you need additional software or have problems setting something up. Slackware is not that hard to install, just go for it.