...works but the shell can be started in 4 different ways. And each way behaves a little differently regarding /etc/profile, ~/.profile and ~/.shrc (or wherever ENV is pointing to).
Invocation
If no arguments are present and if the standard input of the shell is
connected to a...
...TERM=${TERM:-xterm}
export TERM
PAGER=less
export PAGER
# set ENV to a file invoked each time sh is started for interactive use.
ENV=$HOME/.shrc; export ENV
# Query terminal size; useful for serial lines.
if [ -x /usr/bin/resizewin ] ; then /usr/bin/resizewin -z ; fi
# Uncomment to display...
Just for future reference, one can also define the alias in the user's .shrc file, who connects to the host via ssh. They can then elevate privilages with
su instead of su - if typing two more characters is a big deal 😄.
I apologize for the simplicity of this question, the answer to which is probably going to be as simple.
I made an entry in /root/.shrc for an alias like la='ls -alh'. Once I source this file, it does work. However, I have to source this file every time I su to root via ssh. I need this alias to...
I connect via SSH from a FreeBSD 14.3 computer from the command line. I don't have a graphical environment. But on all other computers with other OS (Manjaro, Mint, MX etc) the prompt line is normal, that's the problem
Connect to computer with Manjaro:
ssh pal@10.44.44.44
The authenticity of...
...In your case, the parameters are "=5", which also makes no sense.
My hunch: Whatever program configures your prompt on whatever version of Linux (CachyOS?) is using unsupported escape sequences. Look at where your prompt is set, typically .profile or .bashrc or .shrc or something like that.
...appropropriate contents.
I would like to know more about the dynamics behind these different behaviours. I tried to have more or less equal .shrc,.bashrc,
.profile and .login files. I'm sure this has something to do with environment variables but if someone asked me I could not say why...
Thank you!
I guess most of the files listed are ones I've edited, so I think it looks mostly OK? Maybe except /usr/lib/libncursesw_real.a ...
No ZFS, unfortunately.
I use emacs editing mode:
# cat .shrc
#
# .shrc - bourne shell startup file
#
set -o emacs
The effect is repeated on the FreeBSD console, where TERM=xterm, and when connecting via ssh, TERM=st-256color. I set TERM=xterm, but nothing changed.
Dear VladiBG :
thanks for your guide . how to configure my VT cursor to lightgreen ? thanks. i have read this content , but i can't find it . and try add below line in my .shrc
cursor_foreground_green=8
i am not sure is that right . please help me . thanks.
...export XIM_ARGS="--daemonize --xim"
2....way: this is best way fellow ibus guide..
$echo $SHELL
sh
NOte: sh shell configure was ~/.shrc ...it's not .cshrc ..
$ pkg info -D ibus
ibus-1.5.31_1:On install:
ibus installation finished. To use ibus, please do the following:
If you are using...
...located in /usr/local/SYSENV/etc/shells/common.tcshrc do the same for sh shell creating a symlink of file /usr/local/SYSENV/etc/shells/common.shrc in /etc/profile.d.
The script also initialize pkg (bootstrap) and set the package repository to latest, install git from packages, create the...
FWIW in Linux I use `/etc/environment`.
I have this line that I have appended to all three of /etc/profile /usr/share/skel/dot.profile $HOME/.shrc:
export FOO='bar'
And using a Vagrant box of FreeBSD 14 I can see `FOO` in `env` or just by:
$ vagrant ssh
$ printf 'FOO = "%s"\n' "${FOO}"
FOO...
There are several ways to start the graphical environment after login at the first prompt or through a session manager:
https://forums.freebsd.org/threads/calling-startx-in-shrc-freebsd-11-1.64866/
https://forums.freebsd.org/threads/start-x-at-login.90260/
A 'wadnows-bossbox' is known...
...to newbies that struggle to bond with vi. I appreciate you very much. You have taught me alot in just a few posts. I somehow forgot about .shrc and .profile in the ocean of information that i've been absorbing lately. I use the defaul sh shell (Bourne shell, i think it is called.) I am happy...
Another tip regarding the editor, edit ~/.shrc and/or ~/.cshrc (depends on the shell you're using) and set the EDITOR variable to ee. Commands like visudo, vipw and many more respect the EDITOR environment variable and will open with that editor instead of the default vi.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.