06-06-2018
Funny question, wget has nothing to do with installing GIT...
now we cant really reply on installation since it will depend of architecture, OS s I suppose each may have a package with their install procedure
About wget, is it because you are blocked ( in private lan, firewall ?)?
7 More Discussions You Might Find Interesting
1. AIX
Hello,
I recently installed GIT 1.8.1 on my AIX 6.1 machine referring to AIX Open Source Packages | Main / git website and am facing a few issues with it.
Now if I login as root and issue git commands like git --version I get the response as shown : git version 1.8.1And I have tried creating... (4 Replies)
Discussion started by: gaugeta
4 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I'm fairly new to the git command and I'm trying to figure out how to check if your local clone is up to date with the master. I know you can do the same thing on packages with apt-get by using update and then upgrade. Is there something similar with git? (0 Replies)
Discussion started by: silverdust
0 Replies
3. Red Hat
Hi,
I am trying to install git on RHEL 6. From the research I have done I should be able to just say:
sudo yum install git
but it is not working (it says no package git is available). I am fairly new to linux and cannot figure this out.
Thanks for any help you can provide. (7 Replies)
Discussion started by: dsabol
7 Replies
4. OS X (Apple)
I meant to type in:
man git-add //no space
but I typed this in instead:
man git -add // space between git and -add
There were all these spewing out; not quite sure what I did. I am new to unix and the terminal. Does anyone know what man git -add does and how do I undo... (2 Replies)
Discussion started by: BuDop
2 Replies
5. Solaris
I need to be able to run git commands on a solaris 10 box, the git server is a Linux rh 6.9 , but I can not find much info out there on a git client for solaris 10.
Is it just a pkgadd, or and install tar? or is there even any support for Solaris 10 git? My reading so far had not turned much up. ... (1 Reply)
Discussion started by: rrodgers
1 Replies
6. Red Hat
trying to add git link to my computer as root and getting error message
git clone https://github.com/xxxxxxx/xxxxx.sh
bash: git: command not found
Please use CODE tags as required by forum rules! (3 Replies)
Discussion started by: DOkuwa
3 Replies
7. UNIX for Beginners Questions & Answers
i am running solaris 10 and they want GIt on there.
The instructions that I found on line want me to use pkgutil which i don't have either.
Most packages that i have installed come from the cd and are labeled SUNW...
I see one instruction to add
pkgadd -d http://get.opencsw.org/now
... (4 Replies)
Discussion started by: goya
4 Replies
LEARN ABOUT MOJAVE
git-shell
GIT-SHELL(1) Git Manual GIT-SHELL(1)
NAME
git-shell - Restricted login shell for Git-only SSH access
SYNOPSIS
chsh -s $(command -v git-shell) <user>
git clone <user>@localhost:/path/to/repo.git
ssh <user>@localhost
DESCRIPTION
This is a login shell for SSH accounts to provide restricted Git access. It permits execution only of server-side Git commands implementing
the pull/push functionality, plus custom commands present in a subdirectory named git-shell-commands in the user's home directory.
COMMANDS
git shell accepts the following commands after the -c option:
git receive-pack <argument>, git upload-pack <argument>, git upload-archive <argument>
Call the corresponding server-side command to support the client's git push, git fetch, or git archive --remote request.
cvs server
Imitate a CVS server. See git-cvsserver(1).
If a ~/git-shell-commands directory is present, git shell will also handle other, custom commands by running "git-shell-commands/<command>
<arguments>" from the user's home directory.
INTERACTIVE USE
By default, the commands above can be executed only with the -c option; the shell is not interactive.
If a ~/git-shell-commands directory is present, git shell can also be run interactively (with no arguments). If a help command is present
in the git-shell-commands directory, it is run to provide the user with an overview of allowed actions. Then a "git> " prompt is presented
at which one can enter any of the commands from the git-shell-commands directory, or exit to close the connection.
Generally this mode is used as an administrative interface to allow users to list repositories they have access to, create, delete, or
rename repositories, or change repository descriptions and permissions.
If a no-interactive-login command exists, then it is run and the interactive shell is aborted.
EXAMPLE
To disable interactive logins, displaying a greeting instead:
$ chsh -s /usr/bin/git-shell
$ mkdir $HOME/git-shell-commands
$ cat >$HOME/git-shell-commands/no-interactive-login <<EOF
#!/bin/sh
printf '%s
' "Hi $USER! You've successfully authenticated, but I do not"
printf '%s
' "provide interactive shell access."
exit 128
EOF
$ chmod +x $HOME/git-shell-commands/no-interactive-login
To enable git-cvsserver access (which should generally have the no-interactive-login example above as a prerequisite, as creating the
git-shell-commands directory allows interactive logins):
$ cat >$HOME/git-shell-commands/cvs <<EOF
if ! test $# = 1 && test "$1" = "server"
then
echo >&2 "git-cvsserver only handles "server""
exit 1
fi
exec git cvsserver server
EOF
$ chmod +x $HOME/git-shell-commands/cvs
SEE ALSO
ssh(1), git-daemon(1), contrib/git-shell-commands/README
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-SHELL(1)