New answers tagged history
-1
dmesg (display message or driver message)
From Wikipedia, the free encyclopedia
25
I think it stands for "diagnostic messages", as per the older man page (referenced here too).
dmesg - system diagnostic messages
Dmesg looks in a system buffer for recent kernel diagnostic messages and reproduces them on the standard output
One of the oldest references appears to be a man page revision by Kirk McKusick dating back from 1985.
8
I think the dmesg command just stands for display messages. The FreeBSD manpages seem to share this view:
dmesg -- display the system message buffer
2
The ones used today is mainly from release X11R4. See below. That is: not only by name but also by definition.
Looking at Wikipedias entry on X11 color names it states that they
were defined by Bob Scheifler of MIT's Laboratory for Computer Science.
As he lead out the birth of X back in 1984 that is probably correct – but
the reference has no such claims.
...
3
The first application that I ever came across that could play .wav or .mp3 files was sox. It was available on Solaris 2.5.1 when I first found out about it. I believe it predates that as well.
I was using sox in 1997.
The wikipedia page has it pegged at 1991. Incidentally the app is named SoX, for Sound Exchange.
excerpt from history section of wikipeidia ...
2
There probably was no "first for Linux", the Linux kernel has been supplemented with userland programs collected from all over the place from the very start, the overwhelming majority of it originally developed for some propietary Unix system or one of the BSDs, and even in some case ported over from other operating systems. Much of this happened in ...
1
I have not followed closely the history, but there was no big bang, only evolution. There were large software repository on the net in the early nineties,
and probably even in the eighties. The archive CTAN for TeX started in 1992. Hobbes for OS/2 started around the same time, I think. There were some for Linuxes, for BSD Unices, for Windows, for TCL/Tk ... ...
4
RMS (the founder of GNU and original author of gcc and emacs) has a nice summation of the etymology of hacking including how it came to have a pejorative meaning. The pejorative one continues to be the most titillating to most people, while the non-perjoritive one has, as RMS says, strong anti-authority overtones, so most people will conflate them, because, ...
7
Absolutely. To cite RFC 1392:
hacker
A person who delights in having an intimate understanding of the
internal workings of a system, computers and computer networks in
particular. The term is often misused in a pejorative context,
where "cracker" would be the correct term. See also: cracker.
And as so correctly addressed by the ...
3
Yes, he is. Hacker has several definitions, see here: http://en.wikipedia.org/wiki/Hacker
0
I'm going to guess that to ensure things could be typed fast (and more importantly, spelt out loud quickly), everything was limited to six characters - as mentioned above. This wouldn't have been a filesystem limitation, just common convention. 'lib' could be added to the beginning of a name to indicate it was a library, and other appendages could also be ...
7
The semantics and the usual glyphs for these characters have changed
(several times) during the last 50 years.
The six-bit predecessors of ASCII contained various multi-purpose characters,
including one single quote-like
character, which was used for anything that had some similarity with
a quote: opening quote, closing quote,
apostrophe, or (by ...
2
Output like that is generated by makeinfo from Texinfo sources. Texinfo can also render to other formats like PDF, so it needs to be more expressive than ASCII. Maybe to avoid throwing away semantics, makeinfo encodes quotes like that, so you can see what is opening and closing quotes.
Example: If you couldn't see the difference, I can imagine I'd be a bit ...
1
Here’s a handy trick — add this line to ~/.inputrc (creating the file if necessary):
Control-x: shell-expand-line
Note you could also either of the following to expand only history, or your aliases, or both:
Control-x: history-expand-line
or
Control-x: alias-expand-line
or
Control-x: history-and-alias-expand-line
This was gleaned ...
4
shell-expand-line (\e\C-e) expands command substitutions in bash.
$ bind -p|grep shell-ex
"\e\C-e": shell-expand-line
$(!!)\e\C-e would run the previous command again and insert the output:
"\eo": "$(!!)\e\C-e"
It also expands other command substitutions, but there is no command like shell-expand-word.
In bash 4.0 or later you could also enable ...
2
I'd use a function:
gotofile () { pushd "$(find . -name "$1" -printf "%h\n")"; }
Change "." to some directory as appropriate ("~" perhaps)
4
fc -s runs the previous command again:
alias cdlast='cd "$(dirname "$(fc -s 2> /dev/null)")"'
Or use eval "$(history -p !!)":
alias cdlast='cd "$(dirname "$(eval "$(history -p !!)")")"'
3
You can use an alias.
alias cdlast='cd "$(dirname "$(eval $(history -p !!))")"'
Make sure you have the double quotation marks in there. Those prevent the results of the command substitutions from being split into separate words if they have spaces and interpreted as wildcard patterns if they have special characters such as * and ?.
Top 50 recent answers are included
