Re: Vector Linux
- From: Aragorn <aragorn@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 09 Sep 2009 16:21:20 +0200
On Wednesday 09 September 2009 13:58, someone identifying as *Dr. Deb*
wrote in /alt.os.linux:/
<quoting re-arranged to interleaved replying for clarity>
Aragorn wrote:
On Wednesday 09 September 2009 05:12, someone identifying as *Dr.
Deb* wrote in /alt.os.linux:/
Downloaded a copy and it looks good. However, do not install on a
HD with another distro you want to be able to access, or Windows for
that matter---without making sure you set all mount points for the
partitions in GParted when the installer gives you access to it.
And your reason for saying that would be... what exactly? One
*always* needs to set up mountpoints, and for any already installed
system alongside which you choose to install a(nother) GNU/Linux
distribution, the additional mountpoints can be created/configured
either during installation or afterwards.
The beauty of a UNIX system is its transparency and general
uniformity. The administrator of a UNIX system can always set up the
system exactly how they want it and when they want it, and it's for
most part using all the same configuration files. Local filesystems
are always set up in */etc/fstab,* across all GNU/Linux distributions
and across all UNIX family operating systems.
The reason for making the statement on the mounting of the partitions
is that not all Linux OS's require you to get in and do ALL of the
mount information. For several generations of different OS's that I
am familiar with, the Windows partition (assuming you have one) has
been an auto mount.. Not so with Vector - so the "heads up."
Well, okay, maybe Vector Linux does not automatically detect and set up
your Windows partitions for you during installation, but it is trivial
to change this with an editor.
The other problem I had was that it would not log out of User
without freezing up. You could either reboot or shut down the
computer fine. But if you wanted to log out and log in as another
user, lock up, every time.
Then this is probably due to the fact that you're using a display
manager and thus a graphical login screen. In spite of the eyecandy
factor of a graphical login screen, I always advise people to use a
character mode login console instead and start X manually. That's
one less process running with root privileges.
As for the GUI, when you load the LiveCD of Vector, you are defaulted
into an Ice gui, no choice. When you then install off the LiveCD,
you load from the default gui - no choice. After the install, you
have no choice to boot into Root [...
Not in the display manager login screen, no, and most distributions set
it up that way by default so as to prevent people from running a GUI as
root, because that can and does often lead to mistakes that jeopardize
the stability or integrity of the system.
However, every GNU/Linux distribution I know of comes with all virtual
consoles enabled, so you need only press /Ctrl+Alt+F_something/ -
where /F_something/ is one of the function keys from /F1/ to /F6/ - to
get to a character mode login console. And normally, with the
exception of some hardened systems and the various Ubuntu siblings, you
can log in as root there, and then you will be greeted with a /bash/
prompt, or whatever the default shell will be.
...] and if you try to log out of the default (and only choice for
loading Vector) gui the system locks.
That which locks is most likely just the GUI, but not the underlying
kernel - it would be symptomatic of a hardware problem if that were the
case - and you should normally always be able to get out of a locked-up
GUI by using the "magic /SysRq/" keys - a "system request" is formed by
pressing and holding both the /Alt/ key and the /Prtsc/ key, or
whatever other function key on your keyboard has "SysRq" on it, and
then pressing any of the "magic keys".
Here's a brief description of the ones you might need - there are more:
R = sets keyboard in XLATE mode ("unRaw")
S = emergency /sync/ between the VFS and physical filesystems
E = terminates all processes in the current runlevel except
for /init/
I = sends a SIGKILL to all running processes in the current
runlevel except for /init/
U = emergency remount of all filesystems in read-only mode
B = reboot - same as pressing the reset button on the chassis
You can memorize the above sequence through the mnemonic "Raising Skinny
Elephants Is Utterly Boring". Be sure to allow a few seconds between
each of the system requests so as to give the kernel the time to do its
thing properly.
In addition, with GNU/Linux being a true multi-user platform - like all
UNIXes, and totally unlike Windows - you do not need to log out of the
normal user account in order to log in again on another virtual console
or even remotely over /ssh./ The system was designed to allow multiple
logins from the same or different user accounts simultaneously and to
multitask between the processes started from each individual login
session.
The most common mistake newbies make is to think of a computer and an
operating system the way Microsoft has indoctrinated and conditioned
them. People used to Microsoft Windows will typically assume all the
properties and quirks of Windows to be the properties and quirks of any
computer operating system, and this is grossly wrong.
GNU/Linux is an entirely different kind of operating system and does not
behave the way Windows does, nor is it a single-user operating system
in which the multiple user accounts are just a bolted-on afterthought.
UNIX was developed from the ground up as a multi-user platform for
minicomputer hardware, and unlike Windows, it is an open and for most
part standardized architecture. You should learn to take advantage of
its power and rid yourself of all the Microsoftisms. ;-)
--
*Aragorn*
(registered GNU/Linux user #223157)
.
- References:
- Vector Linux
- From: Dr. Deb
- Re: Vector Linux
- From: Aragorn
- Re: Vector Linux
- From: Dr. Deb
- Vector Linux
- Prev by Date: Re: Vector Linux
- Next by Date: Re: good KDE distro
- Previous by thread: Re: Vector Linux
- Index(es):
Relevant Pages
|
