07-11-2019
Quote:
Yes and Thanks.
I made that video for that exact reason, so provide a quick history to the new generation of UNIX and Linux users who are not familiar with the great history.
In addition, I plan a video covering from 1999 to 2019 about the evolution of UNIX into macOS, using the same format.
Great, I Will look forward for the evolution video of UNIX!
9 More Discussions You Might Find Interesting
1. News, Links, Events and Announcements
Link describe the Step by step formation of Unix
http://perso.wanadoo.fr/levenez/unix/
Also:
- History
- Author of First Unix C Language
- Unix Family research Tree
- BSD and Sun History chart
- Technical Comparison between Unix Diffrences (4 Replies)
Discussion started by: killerserv
4 Replies
2. UNIX for Dummies Questions & Answers
Hi. I am new here, and this is my first post at the UNIX.com forums. I have read the book Fire in the Valley: The Making of the Personal Computer, and I noticed that neither UNIX nor Linux was mentioned once in the book. Why is this? What was UNIX's place in the early days of personal computers?
... (6 Replies)
Discussion started by: elendil
6 Replies
3. UNIX for Dummies Questions & Answers
I tried looking for the answer online and came up with only a few semi-answers as to why file and directory names are case sensitive in Unix. Right off the bat, I'll say this doesn't bother me. But I run into tons of Windows and OpenVMS admins in my day job who go batty when they have to deal... (3 Replies)
Discussion started by: deckard
3 Replies
4. UNIX for Advanced & Expert Users
Hi techies,
I have a doubt upon the command history utilities in Unix ...
As far as I know, history stores the event number and command for upto
that many number of previous commands executed in the HISTSIZE variable ... my doubt here is can we get the time in which these commands were... (3 Replies)
Discussion started by: Sabari Nath S
3 Replies
5. Solaris
is there any way to determine the last command entered on a unix machine???
Thanx (3 Replies)
Discussion started by: mm00123
3 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I'm working on two flavours of unix namely HP-UX and sun solaris.
In HP-UX, for executing the previous commands, i use the arrow keys. But on sun solaris this is not working.
Can anyone explain how to use history feature effectively in sun solaris os?
Thanks (4 Replies)
Discussion started by: venkatesht
4 Replies
7. UNIX and Linux Applications
Hi everybody Im Megadrink!!!
This is my first thred.
Ive recently been introduced to Unix and i was interested in Unix's History. Can anyone give me a breif History On Unix. Just when it was invented/released. Maybe someother cool things about it.
Thx for the information in advance!! :D (2 Replies)
Discussion started by: Megadrink
2 Replies
8. Shell Programming and Scripting
commands to view the history file in unix.
I am not sure whether it is bash_history.sh (1 Reply)
Discussion started by: ramkumar15
1 Replies
9. What is on Your Mind?
The Dark Years of UNIX (2003 - 2011) | A Decade Lost to Legal Battles | UNIX and Linux Legal Attacks
https://youtu.be/ILH5CVYdl8w
Here is the second video in the "history of unix" short videos. The first video was on the "great history of UNIX" and this second video covers the "years of... (7 Replies)
Discussion started by: Neo
7 Replies
LEARN ABOUT DEBIAN
devel::repl::plugin::outputcache
Devel::REPL::Plugin::OutputCache(3pm) User Contributed Perl Documentation Devel::REPL::Plugin::OutputCache(3pm)
NAME
Devel::REPL::Plugin::OutputCache - remember past results, _ is most recent
SYNOPSIS
> 21 / 7
3
> _ * _
9
> sub { die "later" }
sub { die "later" }
> _->()
Runtime error: later
DESCRIPTION
Re-using results is very useful when working in a REPL. With "OutputCache" you get "_", which holds the past result. The benefit is that
you can build up your result instead of having to type it in all at once, or store it in intermediate variables. "OutputCache" also
provides "$_REPL->output_cache", an array reference of all results in this session.
Devel::REPL already has a similar plugin, Devel::REPL::Plugin::History. There are some key differences though:
Input vs Output
"History" remembers input. "OutputCache" remembers output.
Munging vs Pure Perl
"History" performs regular expressions on your input. "OutputCache" provides the "_" sub as a hook to get the most recent result, and
"$_REPL->output_cache" for any other results.
Principle of Least Surprise
"History" will replace exclamation points in any part of the input. This is problematic if you accidentally include one in a string, or
in a "not" expression. "OutputCache" uses a regular (if oddly named) subroutine so Perl does the parsing -- no surprises.
CAVEATS
The "_" sub is shared across all packages. This means that if a module is using the "_" sub, then there is a conflict and you should not
use this plugin. For example, Jifty uses the "_" sub for localization. Jifty is the only known user.
SEE ALSO
"Devel::REPL", "Devel::REPL::Plugin::History"
AUTHOR
Shawn M Moore, "<sartak at gmail dot com>"
COPYRIGHT AND LICENSE
Copyright (C) 2007 by Shawn M Moore
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.14.2 2010-05-08 Devel::REPL::Plugin::OutputCache(3pm)