01-03-2013
Standard input (stdin) normally comes from your keyboard. Many programs ignore stdin.
E.g.
cat filename never reads its standard input; it reads the files directly. But without file names on the command line, UNIX commands that need input will usually read stdin.
Standard input normally comes from your keyboard, but the shell can redirect stdin from a file. This is handy for UNIX commands that can't open files directly.
E.g.
mail user@domain.com < filename. To mail a file use
< filename to tell the shell to attach the file, instead of your keyboard, to mail's standard input.
sed can read file directly, so no need to redirect stdin from a file. I hope this helps.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hello,
i'm looking for the sources of the old, original unices (v3 preferred). could someone point a link? (2 Replies)
Discussion started by: fdarkangel
2 Replies
2. UNIX for Dummies Questions & Answers
All,
I have worked with UNIX for quite a while but never with raid. My section has just taken control of 3 servers each with different configurations and all running raids. My question for everyone is can you recommend any books that I can purchase or web sites that deal specifically with how to... (1 Reply)
Discussion started by: 3grls=1hd8
1 Replies
3. Linux
I"m installing my ATI card in FC4. I'm going off of instructions that i've found. The firs step says that i need my kernel sources which i've got then it says that i've gotta unpack them so i can make links to the file later. My kernel sources that i've got are .src.rpm I've installed them but... (1 Reply)
Discussion started by: byblyk
1 Replies
4. Linux
Hi guys!
I have a problem to create a makefile when using 2 types of sources.
Suppose we have sources at master_source folder:
- 1.c
- 2.c
and also we have sources at platform_source folder:
- 1.c
I really need to use platform_source folder because there is many of them (one folder with... (8 Replies)
Discussion started by: borzh62
8 Replies
5. SuSE
Hi all.
I have an issue with kernel patching.
My system: OpenSuse 10.2, kernel version: 2.6.18.2.
I've downloaded the patch from kernel.org - 2.6.26. I've invoked the following command:
"patch -p1 -f < patch-2.6.26" (-f - because some files are not exist. to automatically skip this issues).... (2 Replies)
Discussion started by: Vourhey
2 Replies
6. News, Links, Events and Announcements
So, I was browsing groklaw.net, and I was surprised to read that Pamela Jones was reading the copyright notices in the UnixWare 7.1.1 source code files...
Groklaw - Santa Cruz Listed Novell as Owning the Copyrights in 1999
How can that be? Are the UnixWare 7.1.1 sources available to the... (1 Reply)
Discussion started by: pepinox
1 Replies
7. Solaris
Everyone knows the project LFS (Linux from scratch), it is a book-assembly instructions GNU / Linux from source code. I managed to gather, then my knowledge of GNU / Linux grew, learned many new commands, edit config-files, base packages, kernel, etc. ..
Now I would like also to explore... (0 Replies)
Discussion started by: Geekon
0 Replies
8. Debian
I'm just interested to know how your sources.list look like. I got some repositories witch give some errors and I would like to clean it up.
and when I do apt-get update I get few lines showing errors like 404 , this is how my list look like:
# deb cdrom:/ squeeze main
# deb cdrom:/... (0 Replies)
Discussion started by: zdorian
0 Replies
9. Programming
I am working in IT company working for banks.I find hardly to get technology about bank IT on the internet.Consider banks all using Unix, I think I can get some help here.
Recommend some sits or books about bank IT will be very helpful!! (0 Replies)
Discussion started by: hhdzhu
0 Replies
LEARN ABOUT CENTOS
git-hash-object
GIT-HASH-OBJECT(1) Git Manual GIT-HASH-OBJECT(1)
NAME
git-hash-object - Compute object ID and optionally creates a blob from a file
SYNOPSIS
git hash-object [-t <type>] [-w] [--path=<file>|--no-filters] [--stdin] [--] <file>...
git hash-object [-t <type>] [-w] --stdin-paths [--no-filters] < <list-of-paths>
DESCRIPTION
Computes the object ID value for an object with specified type with the contents of the named file (which can be outside of the work tree),
and optionally writes the resulting object into the object database. Reports its object ID to its standard output. This is used by git
cvsimport to update the index without modifying files in the work tree. When <type> is not specified, it defaults to "blob".
OPTIONS
-t <type>
Specify the type (default: "blob").
-w
Actually write the object into the object database.
--stdin
Read the object from standard input instead of from a file.
--stdin-paths
Read file names from stdin instead of from the command-line.
--path
Hash object as it were located at the given path. The location of file does not directly influence on the hash value, but path is used
to determine what Git filters should be applied to the object before it can be placed to the object database, and, as result of
applying filters, the actual blob put into the object database may differ from the given file. This option is mainly useful for hashing
temporary files located outside of the working directory or files read from stdin.
--no-filters
Hash the contents as is, ignoring any input filter that would have been chosen by the attributes mechanism, including the end-of-line
conversion. If the file is read from standard input then this is always implied, unless the --path option is given.
GIT
Part of the git(1) suite
Git 1.8.3.1 06/10/2014 GIT-HASH-OBJECT(1)