Sponsored Content
The Lounge What is on Your Mind? What Social Networks Do You Use Regularly? Post 302860255 by bakunin on Saturday 5th of October 2013 10:19:34 AM
Old 10-05-2013
Quote:
Originally Posted by csorhand
Bakunin / Corona668,

Have you tried those smartphones around? theyre like the servers way way back.. four core 2 gb of RAM 32Gb of disk space.

(i'm just jokin) =)
Well, a "server way way back" was not "four core 2gb of RAM" and 32GB disk space was something a datacenter (maybe) had.

The first "server" i worked on was an Apollo/Domain 416 (aka DN100): 2 Motorola 68000 processors and IIRC 4MB RAM. It ran a UNIX derivate called Aegis, which was later renamed to Domain OS. Before that i worked on IBM mainframes, which i am not counting as "servers", because this implies a client/server model which they didn't adhere to - they were single computers with a lot of terminals - as a programmer. Real memory on my very first machine, a (by then already old) IBM 1401 was ~2.5k. Mind you, not the fancy black insects one saw in PCs - Ferrite memory! Not only that every bit counted - it was countable as well.

bakunin
This User Gave Thanks to bakunin For This Post:
 

We Also Found This Discussion For You

1. UNIX for Advanced & Expert Users

Server goes down regularly- Please help

Hi , I need a clarification on an issue that we have been facing for two weeks now. From past one year we had issue with space on our Linux machine on which our application ( View VC, CVS) hosted on it. Due to swap memeory configuration being 0 and very less space on the server, the server... (7 Replies)
Discussion started by: bsandeep_80
7 Replies
BACKUP(8)						      System Manager's Manual							 BACKUP(8)

NAME
backup - backup files SYNOPSIS
backup [-djmnorstvz] dir1 dir2 OPTIONS
-d At top level, only directories are backed up -j Do not copy junk: *.Z, *.bak, a.out, core, etc -m If device full, prompt for new diskette -n Do not backup top-level directories -o Do not copy *.o files -r Restore files -s Do not copy *.s files -t Preserve creation times -v Verbose; list files being backed up -z Compress the files on the backup medium EXAMPLES
backup -mz . /f0 # Backup current directory compressed backup /bin /usr/bin # Backup bin from RAM disk to hard disk DESCRIPTION
Backup (recursively) backs up the contents of a given directory and its subdirectories to another part of the file system. It has two typ- ical uses. First, some portion of the file system can be backed up onto 1 or more diskettes. When a diskette fills up, the user is prompted for a new one. The backups are in the form of mountable file systems. Second, a directory on RAM disk can be backed up onto hard disk. If the target directory is empty, the entire source directory is copied there, optionally compressed to save space. If the target directory is an old backup, only those files in the target directory that are older than similar names in the source directory are replaced. Backup uses times for this purpose, like make. Calling Backup as Restore is equivalent to using the -r option; this replaces newer files in the target directory with older files from the source directory, uncompressing them if necessary. The target directory con- tents are thus returned to some previous state. SEE ALSO
tar(1). BACKUP(8)
All times are GMT -4. The time now is 10:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy