Comments for Crouse - UID Zero

Comment on Vim encryption , encrypting with vim and blowfish. by admin

admin — Mon, 30 Apr 2012 18:05:50 +0000

Thanks for catching it too. Fixed in the original post. :)

Comment on Vim encryption , encrypting with vim and blowfish. by admin

admin — Mon, 30 Apr 2012 18:05:24 +0000

Fixed… :) Thanks.

Comment on Vim encryption , encrypting with vim and blowfish. by Charles

Charles — Sun, 29 Apr 2012 09:21:34 +0000

Your path to the home directory seems to have a typo:

~/home/YOU/.vimencrypt

I’m sure you know what the problem is there. :)

Comment on Vim encryption , encrypting with vim and blowfish. by Josh

Josh — Sat, 28 Apr 2012 20:55:53 +0000

~/home/YOU/.vimencrypt should be ~/.vimencrypt, nice article though

Comment on Vim encryption , encrypting with vim and blowfish. by sickill

sickill — Sat, 28 Apr 2012 18:12:42 +0000

Awesome! Thx for the tip. Now I don’t have excuse to not encrypt some of my private files I have stored on Dropbox ;)

Comment on Getting colors to work for ls and vim on Solaris 11 by Brian Masinick

Brian Masinick — Sat, 15 Oct 2011 17:48:30 +0000

Good thing that Vim is now available on Solaris! I can still remember the first time I used minicomputer systems in the early eighties running UNIX software. Only the best systems at the time could handle Vi well. I often resorted to using Ed, believe it or not, and it got the job done. Emacs? In the early eighties, forget it!

The first implementation of SunOS on Motorola 68000 tower systems was promising, but for the first few years, it was underpowered too. It did not take long, however, for most systems, Sun certainly included, to take up the Slack… oh wait, we’re not talking about Slackware, or ARE WE?

In 1998 I bought my first home PC, a 100 MHz Micron P100 with 16 MB of memory (I believe I added another stick to bring it up to an amazing 32 MB! I had a 2.1 GB hard drive. By then, Elvis could fly on it, and GNU Emacs also worked great. Sun had Sparc, and soon thereafter, UltraSPARC, and we had plenty of system resources. By the change of the millennium, there really was no good reason NOT to have every editing capability you could ask for. If Emacs could come up in 2-3 seconds, ANY Vi provided virtually instantaneous access to files.

I’ve heard of people editing files a few GB in size, though these DO still stretch the capabilities, not only of the editors, but of virtual memory components. The best ones can actually do it, believe it or not.

Anyway, thanks for the tips; I often do the same thing; I frequently post my favorite scripts and configuration files in public places, both to benefit others and to have a place where I can grab them, so if I access some other computer, as long as it has Internet access (and the freedom to use it), I can get the tools that I want anywhere.

Nice simple configuration, Dave, thanks!

Comment on Bash – some .bashrc functions by jaffar

jaffar — Sat, 14 May 2011 18:17:06 +0000

nice collection , i like the extract function most, saves time and efficient , thanx for sharing

Comment on screenhelp – show notes about screen. by drcouzelis

drcouzelis — Fri, 18 Mar 2011 02:31:59 +0000

Thanks for sharing. I use screen every day, but I pretty much only know the most basic commands. This’ll help me become a master of screen and attract hot women.

Comment on Creating a stable Arch server. by Jim Karsten

Jim Karsten — Mon, 08 Feb 2010 18:04:25 +0000

I am interested in using a similar setup. Is it possible to get a few
more details.

In step 1, how do mirror the current repo? Do you create a local mirror?
http://wiki.archlinux.org/index.php/Local_Mirror

In step 3, what exactly do you do to push the local repo to the stable
repo?

Do you use any of the following tools? yaourt, abs, powerpill,
bauerbill, pkgd, network shared pacman cache.

Thanks,
jim

Comment on Archlinux.me running on kernel26 2.6.32.8-1 by crouse

crouse — Fri, 29 Jan 2010 15:54:38 +0000

2.6.32.6-1 now.

core/kernel26 2.6.32.6-1 (base)
The Linux Kernel and modules
core/kernel26-firmware 2.6.32.6-1 (base)
The included firmware files of the Linux Kernel
core/kernel26-headers 2.6.32.6-1
Header files and scripts for building modules for kernel26