Search Results

I'd also like to point out that the techniques in the newer kernels that actually have the fairly good core reporting for x86 style CPUs still won't work well for really old dubious x86 processors...

cat /proc/stat will show more specific info ... :)

Yes - a lot of difference.

Try this command

egrep 'core id|physical id' /proc/cpuinfo | tr -d "\n" | sed s/physical/\\nphysical/g | grep -v '^$' | sort | uniq | wc -l

"make install" will use the default location for a systemwide install... if you install for a specific user you have to create the directories inside the users homedir and give "make install" the...

Another way to skin the cat in this case would be to use ACLs

It doesn't just need to have the right permissions, it also needs to belong to the right owners.

There's also more than one way to skin a cat.

What is the folder's ownership right now? What is...

Try the following commands out, and let us know if vi editor becomes more user-friendly:

#TERM=vt100 ; export TERM
#EDITOR=vi ; export EDITOR
#clear

Cheers
Momin

Please tell us what sort of terminal you are using (in some detail), and the value of $TERM, $EDITOR and $VISUAL (not all may be set).
The keyboard mapping for vi is normally handled through map...

For Solaris 10 you must first use UTF-8 to display multibyte characters like this

$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"...

vi was not designed for a regular keyboard. vi was designed for this (http://en.wikipedia.org/wiki/File:KB_Terminal_ADM3A.svg), and retains the resulting weird key-combos to this day.

when you will use vi,

you should use some special keys in keyboard.
for example

for insert you have to press "i" first.
when you need to change something you have press r
to delete line...