Q
Q
Q
Q
Q
Q
Q
Q
Q
Q
Q
Q
Question
That
kernel because setuid scripts are almost always a security hole
want to know why read the FAQ for comp
Question
The `free
buffer cache
much memory is really free add the `buffers
The disk buffer cache tends to grow soon after starting Linux up
load more programs and use more files and the contents get cached
will stabilise after a while
Question
This is quite a common symptom of a failure to cache the additional
memory
Sometimes you have to enable caching of certain regions in your BIOS
setup
new memory area which is currently switched off
common on a
Sometimes the RAMs have to be in certain sockets to be cached
Sometimes you have to set jumpers to enable the caching
Some motherboards don
of cache than they expect
problem
If in doubt
because the documentation is inadequate you might like to post a message
giving *all* the details
other Linux users can avoid it
Question
You are probably using non
passwords
If so
program(s) in question
(amongst other places):
tsx
This is the source code; you will probably find the binaries in
Question
You probably have the same problem as in Q
won
If you are using shadow passords you should put an asterisk in the
password field of /etc/passwd for each account
doesn
account and let anyone in
Question
You may not have any swap enabled
Linux to page out bits of data programs aren
to make more room for other programs and data
keep data in memory and throw away in
paged straight from the filesystem) and so less and less program is in
memory and everything runs very slowly
See the Installation HOWTO and the Installation and Getting Started Guide
[Q
of how to set up a swap partition or swapfile; see also Q
isn
Alternatively you may have too little real memory
than all the programs you
disk instead and thrash horribly
so many things at once or to buy more memory
memory by compiling and using a kernel with less options configured
Q
You can tell how much memory and/or swap you
command
cat /proc/meminfo
If your kernel is configured with a ramdisk this is probably wasted space
and will cause things to go slowly
not to allocate a ramdisk (see the LILO documentation or type man rdev)
Question
You probably have some permission problems
/etc/nologin
If the latter put rm
Otherwise check the permissions on your shell
appear in error messages
all the way back up the tree to the root directory
Question
You probably sent some binary data to your screen by mistake
^V^[c (that
Linux distributions have a command reset that does this
Question
Reboot from an emergency floppy or floppy pair
boot
mirrors) or the MCC installation boot floppy
rescue disk creation packages on sunsite
/pub/Linux/system/Recovery
kernel on them
filesystems
Get to a shell prompt and mount your hard disk with something like
mount
Then your filesystem is available under the directory /mnt and you can fix
the problem
down to / first or it will say it
From:http://tw.wingwit.com/Article/program/Oracle/201311/18664.html