Sponsored Content
The Lounge What is on Your Mind? Vintage!!! Jimmy Page/Jeff Beck/Eric Clapton-Stairway to Heaven Post 303042846 by Neo on Wednesday 8th of January 2020 11:19:33 AM
Old 01-08-2020
Vintage!!! Jimmy Page/Jeff Beck/Eric Clapton-Stairway to Heaven

You must watch this music video.

Jimmy Page/Jeff Beck/Eric Clapton-Stairway to Heaven

Code:
https://youtu.be/wKlEVtA_TGQ

Long before there was surveillance capitalism, Google, FB and dystopian social media, there was Jimmy Page!

This is how it all "used to be" before mankind was reduced to ones and zeros .....


Vintage!!! Jimmy Page/Jeff Beck/Eric Clapton-Stairway to Heaven-jimmy_pagejpg


Don't miss this! It is "must watch and listen"... .trust me.
This User Gave Thanks to Neo For This Post:
 

5 More Discussions You Might Find Interesting

1. What is on Your Mind?

Jimmy Neutron

For those people wondering who Jimmy Neutron is, he is a boy genius. Jimmy Neutron is also one of the only 3-D cartoon shows on the television. It originally started out as small, two-minute shorts on Nickelodeon. They were pretty old, about ten-years-old. Most of them were about invention... (0 Replies)
Discussion started by: Danny_10
0 Replies

2. Filesystems, Disks and Memory

How to mount and read vintage scsi HDD

I started on another thread and full story can be seen here: https://www.unix.com/security/91428-how-reset-root-password-old-unix-system-v.html But my situation turned to land on this thread now. I have old scsi HDD out of the UHC UNIX System V Rel. 4.0 Version 3.6 box. And need to read... (1 Reply)
Discussion started by: 82026
1 Replies

3. UNIX Desktop Questions & Answers

Vintage unix

Hi, this my be a weird request but I'm wondering if it's possible to instill a vintage unix (like early 1980's) onto a laptop or desktop. If so how I would I go about downloading and installing? I'm mainly wanting to do this as an little porject and some funsies for me. Thanks. (11 Replies)
Discussion started by: dado00
11 Replies

4. What is on Your Mind?

Anyone Running Vintage UNIXen?

Like SunOS, AT&T Unix or anything else of that era... anything running MGR as a graphics subsystem? I'd enjoy hearing from people that may have used MGR back in the day. I have something of a collection of 32bit Suns sun4c, sun4m, sun4d etc..nothing bigger than an 8 way 85Mhz SS1000E though. The... (0 Replies)
Discussion started by: cb88
0 Replies

5. UNIX for Advanced & Expert Users

Extended vs vintage

I am having issues with the MOS (my oracle support) page. I downloaded the new critical patch and oct patchset. for solaris 10 64. However, I noticed that that the Entitlement class read vintage instead of extended in which we bought the service. can anyone tell me the difference? it is safe... (0 Replies)
Discussion started by: goya
0 Replies
FSVS - URL format(5)						       fsvs						      FSVS - URL format(5)

NAME
Format of URLs - FSVS can use more than one URL; the given URLs are overlaid according to their priority. FSVS can use more than one URL; the given URLs are overlaid according to their priority. For easier managing they get a name, and can optionally take a target revision. Such an extended URL has the form ['name:'{name},]['target:'{t-rev},]['prio:'{prio},]URL where URL is a standard URL known by subversion -- something like http://...., svn://... or svn+ssh://.... The arguments before the URL are optional and can be in any order; the URL must be last. Example: name:perl,prio:5,svn://... or, using abbreviations, N:perl,P:5,T:324,svn://... Please mind that the full syntax is in lower case, whereas the abbreviations are capitalized! Internally the : is looked for, and if the part before this character is a known keyword, it is used. As soon as we find an unknown keyword we treat it as an URL, ie. stop processing. The priority is in reverse numeric order - the lower the number, the higher the priority. (See url__current_has_precedence() ) Why a priority? When we have to overlay several URLs, we have to know which URL takes precedence - in case the same entry is in more than one. (Which is not recommended!) Why a name? We need a name, so that the user can say 'commit all outstanding changes to the repository at URL x', without having to remember the full URL. After all, this URL should already be known, as there's a list of URLs to update from. You should only use alphanumeric characters and the underscore here; or, in other words, w or [a-zA-Z0-9_]. (Whitespace, comma and semicolon get used as separators.) What can I do with the target revision? Using the target revision you can tell fsvs that it should use the given revision number as destination revision - so update would go there, but not further. Please note that the given revision number overrides the -r parameter; this sets the destination for all URLs. The default target is HEAD. Note: In subversion you can enter URL@revision - this syntax may be implemented in fsvs too. (But it has the problem, that as soon as you have a @ in the URL, you must give the target revision every time!) There's an additional internal number - why that? This internal number is not for use by the user. It is just used to have an unique identifier for an URL, without using the full string. On my system the package names are on average 12.3 characters long (1024 packages with 12629 bytes, including newline): COLUMNS=200 dpkg-query -l | cut -c5- | cut -f1 -d' ' | wc So if we store an id of the url instead of the name, we have approx. 4 bytes per entry (length of strings of numbers from 1 to 1024). Whereas using the needs name 12.3 characters, that's a difference of 8.3 per entry. Multiplied with 150 000 entries we get about 1MB difference in filesize of the dir-file. Not really small ... And using the whole URL would inflate that much more. Currently we use about 92 bytes per entry. So we'd (unnecessarily) increase the size by about 10%. That's why there's an url_t::internal_number. Author Generated automatically by Doxygen for fsvs from the source code. Version trunk:2424 11 Mar 2010 FSVS - URL format(5)
All times are GMT -4. The time now is 06:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy