March 23rd, 2002, 08:56 AM
Missing libXext.so.6 for vim
Just installed FreeBSD for the 1st time. When I tried to use vim I got the following message:
/usr/libexec/ld-elf.so.1: Shared object "libXext.so.6" not found
Would anyone tell me what I should do to fix the problem. I installed vim during installation of the OS!
March 23rd, 2002, 10:13 AM
locate for me says,
and then in linux compat, so my guess is that you have not installed X or your lib path is off.
March 23rd, 2002, 12:05 PM
Yeah, i didnt install any X components! There are 2 vim packages, 1 is vim, 1 is vim-lite. I should install vim-lite for command-line only enivronment?
March 23rd, 2002, 04:53 PM
>>Should I install vim-lite for command-line only enivronment?
Yes. I have no X windows but use vim and installed the vim-lite package - works fine. (I also had the problem you did when I first installed vim full by mistake)
March 24th, 2002, 02:29 AM
Thanks for your answers and very helpful!
Now I have to customize the shell, ah.. !
March 26th, 2002, 04:13 AM
I have noticed a couple of library files that were installed in
4.4 are not installed by default on 4.5. After searching around, I see alot of users have been having a problem with missing libraries as well, and have had to manually load them also.
I've had a couple of "could not find" messages that occured in 4.5, but did not occur in 4.4.
Does FreeBSD "retire" libaries after a certain amount of time? These particular libraries were 3.x compatibility libraries, that's why I'm thinking they were not loaded by default.
March 27th, 2002, 12:41 AM
For what it's worth, here's my .cshrc file:
lots of these items might not be applicable to you (especially*** the alias section!), but hopefully it'll give you some ideas.
alias ls ls -F
alias h history 10000
alias j jobs -l
alias untargz tar zxvf $1
alias psgrep "ps auxww | grep $1"
# these commands all depend on personal setup:
alias vi vim
alias eject "eject -v acd0"
alias cdcontrol cdcontrol -f /dev/acd0c
alias dagrab dagrab -d /dev/acd0c
alias shlightc shlight //win95/c_rive /mnt/smb.c
alias shlightd shlight //win95/d_rive /mnt/smb.d
alias shlighte shlight //win95/e_rive /mnt/smb.e
# Set a $DATE vbl:
setenv DATE `date "+%Y%m%d%H%M%S"`
# NOTE THIS IS USEFUL IF YOU WANT TO DO:
# at the command line to create a file called
# anameofafile200203261200.txt (if today is march 26 2002 midday :)
# A righteous umask
# do man csh and search for 'umask' to find out about this
# will change from machine to machine... tip: make good use of ~/bin!!!
set path = ($HOME/bin /sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin /usr/local/bin /usr/X11R6/bin)
# these are usful, PAGER especially - this sets the man pager to less
# instead of default 'more'
setenv EDITOR vi
setenv PAGER less
setenv BLOCKSIZE K
if ($?prompt) then
# An interactive shell -- set some stuff up
#set prompt = "[%n %/] # "
set prompt="[%P] %n@%m %/# "
set history = 1000
set savehist = 1000
set mail = (/var/mail/$USER)
# don't wake parents up in middle of night:
# HOUR=echo `date '+%H'`
# if($HOUR < 08) then
# echo "hour is < 08"
# if(`date '+%H'`<08) then
# set nobeep
if ( $?tcsh ) then
set watch= ( 0 any any )
bindkey "^W" backward-delete-word
bindkey "^B" delete-word
bindkey -k up history-search-backward
bindkey -k down history-search-forward
bindkey "^N" insert-last-word
bindkey "^B" backward-word
bindkey "^F" forward-word
Especially nice I find is the 'set watch' line, which basically sets csh up to watch who logs into the server and announce it at in the shell. The bindkey settings are entirely up to you and may seem odd at first, but I find them indispensible now - basically to repeat a command from the history, start typing the first few chars of the commandline, hit <up-arrow> and the history-search will cycle through all recently used commands in the history stack starting with the letters you typed. I find this much more useful than the default history setting which only cycles chronologically through last commands.
A useful .exrc file for you to (for vim - note I don't some of these set items work in vanilla vi):
Anyone got any other useful vi/csh rc settings???
set nu ai history=1000 sw=4 ignorecase ts=4 more ul=1000
March 27th, 2002, 08:53 AM
>> alias shlightc shlight //win95/c_rive /mnt/smb.c
Why run sharity-light when smbfs in 4.X-STABLE can do it much better all the way?
March 27th, 2002, 03:20 PM
Hi freebsd - I did build a kernel with support for SMB in it:
but when it came to finding mount_smbfs I had real problems. I installed the source for sbin as suggested in the various documents relating to the installation of support for smb, but have had no joy in finding/building mount_smbfs as yet in the sources I did have. As we speak I'm cvsupping src-all, so I'll try making sbin again and see how it goes.
options SMBFS #SMB/CIFS filesystem
options NETSMB #SMB/CIFS requester
options NETSMBCRYPTO #encrypted password support for SMB
options LIBMCHAIN #mbuf management library
shlight seems nice given it's not native smb, more like nfs faking it(!), I only get the odd err and it's not so bad all in all for my home lan.
By the way I'm new to cvsup - once I've cvsupped src-all, do I have to follow chapter http://munkboxen.mine.nu/doc/handbook/makeworld.html (chapter 19 of handbook, in case my machine isn't online when you read this!) to the letter and make world, or can I just build individual parts (ie just src.sbin). If so it's time to learn a bit about dump and backup first - is this the tool of choice for across the wire backups or should I go for rsynch?
Many thanks for your comments,
March 27th, 2002, 07:09 PM
>> can I just build individual parts (ie just src.sbin)
Yes and No. You can't for smbfs though.
>> it's time to learn a bit about dump and backup first
Really, cvsup+buildworld isn't that hard. You also don't need to do any backup first because FreeBSD keeps reinventing the wheel for buildworld just trying to be newbie-friendly.
March 27th, 2002, 07:20 PM
As it goes, I've just hashed the damn thing up by running out of space on /usr underestimating the size of src-all. Not too happy about it, but anyway - what is the best way to go about getting back space from /usr/src (ie what can I safely delete from /usr/src in order to free up more space on /usr without damaging future cvsups)?
Also is there any way of telling how much space each sup 'class' takes up (ie ports, docs, share, etc) prior to installation? I can't seem to find this info anywhere.
Thanks in advance,
March 27th, 2002, 07:47 PM
You can move your /usr/src to somewhere else that has plenty of disk space. You just need to make sure to update the symlink of /sys to its new path.
Or if you have another box, just play around with NFS.
As far as what's safe to remove in /usr/src, I don't recommend to do that at all.
March 28th, 2002, 03:54 PM
Ok, cheers for that - I'll have a go at moving /usr/src to an nfs partition on another machine.