17,279 reputation
22257
bio website stratigery.com
location Denver, CO
age 53
visits member for 4 years, 1 month
seen 3 hours ago

My first computer was a Radio Shack Color Computer 3 - 6809-based, running OS-9 Level II. It could run 32 processes at once, due to bank-switching a whole 1 Meg of memory.

After that, I got an AT&T 3b2, also known as a Convergent Safari. This was a Motorola 68010-based desktop.

Then, I graduated to a NeXT black&white "slab". I bought a used SPARCStation IPC in 1995, and put NetBSD 0.9 on it. I ran NetBSD on the IPC and a SPARCStation 10 until 2002.

I've been using Linux since 1997, starting with a DEC Alpha-based UDB, and downgrading to a x86 PC in 2002.

I run Arch linux, on my server and my laptop.


Aug
11
answered Malloc and Paging
Aug
9
awarded  Nice Answer
Jul
31
comment How do pwd and . determine the current path differently?
In Unix, Linux and other filesystems, an inode number is actually a file's identifier to the operating system. Depends on the filesystem, but there's usually a very quick way to go from inode number to the disk block that the inode lives. The inode itself is the on-disk structure representing a file: ownership, permissions, which data blocks contain file's data, access times, etc. A directory is just a mapping from a textual name to an inode number, the quick lookup of disk block from inode number allows the OS to get data and metadata quickly.
Jul
31
answered How do pwd and . determine the current path differently?
Jul
31
awarded  Great Answer
Jul
30
answered How to determine what instructions a process is executing?
Jul
29
comment What is #@(#) in Kornshell syntax
@MaxVernon - you're welcome. I personally love this kind of question, as it exposes actual practices to a wider community, and it lets me mine my memory for whatever absurditites it has retained. If I might editorialize: "@(#)" saved me a few times in High Ritual production environments in the past. Why hasn't it survived? Knowing what versions got compiled together seems like valuable info.
Jul
29
answered What is #@(#) in Kornshell syntax
Jul
28
comment Difference between Unix OS Types
OSX is derived from Mach 2.5, with a thin layer of BSD compatibility on top. I'm not so sure it's FreeBSD, it might actually be BSD 4.4 lite or whatever that last BSD release was.
Jul
28
comment Linux kernel manual build: resulting binary is 10 times larger than precompiled binaries
I don't know about modules. That was one question I had before I recommeded make vmlinuz.
Jul
28
answered Linux kernel manual build: resulting binary is 10 times larger than precompiled binaries
Jul
26
answered why bash increment: `n=0;((n++));` return error?
Jul
21
comment Updating PHP to Gaurd Against Mayhem Malware
@Boundless - the code I got, which is identical to what Virus Bulletin reports (virusbtn.com/virusbulletin/archive/2014/07/vb201407-Mayhem) only uses simple PHP - fopen()/fclose() is about as exotic as it gets. The dropper code does call system(), which runs a command via the shell, so you could potentially disable system(): cyberciti.biz/faq/… Like I wrote above, the PHP it uses is nothing special.
Jul
21
answered Updating PHP to Gaurd Against Mayhem Malware
Jul
20
awarded  Nice Question
Jul
18
comment Low level system call
@saurav1405 - you can look at the source to find out, but for Musl libc, you can look at http://git.musl-libc.org/cgit/musl/tree/src/unistd/read.c - it's in C, but it uses a macro that I trace to the file src/thread/x86_64/syscall_cp.s. The macro expands into in-line assembly. So I'm not sure what to call it: "written in assembly" or "written in C with a line or two of assembly". Probably the latter.
Jul
16
answered System calls source code
Jul
16
answered Low level system call
Jul
10
answered Why Nethogs won't see the PID of the processes the generating some NFS traffic?
Jul
2
awarded  Curious