Editing Talk:1168: tar
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 35: | Line 35: | ||
tar -bvzx for a tar.bzip2 .... wait... no... argh... I've always just trusted my fingers.. --[[Special:Contributions/59.167.191.93|59.167.191.93]] 10:14, 1 February 2013 (UTC) | tar -bvzx for a tar.bzip2 .... wait... no... argh... I've always just trusted my fingers.. --[[Special:Contributions/59.167.191.93|59.167.191.93]] 10:14, 1 February 2013 (UTC) | ||
: Will '''tar -?''' be valid everywhere?. [[User:Arifsaha|Arifsaha]] ([[User talk:Arifsaha|talk]]) 19:32, 1 February 2013 (UTC) | : Will '''tar -?''' be valid everywhere?. [[User:Arifsaha|Arifsaha]] ([[User talk:Arifsaha|talk]]) 19:32, 1 February 2013 (UTC) | ||
− | |||
− | |||
tar -lvvb archive.tar.bz | tar -lvvb archive.tar.bz | ||
Line 55: | Line 53: | ||
:Yeah, all standard Unix installations should have man installed. But many mini installations don't, so these days Google is the standard backup.[[User:CityZen|CityZen]] ([[User talk:CityZen|talk]]) 14:58, 1 February 2013 (UTC) | :Yeah, all standard Unix installations should have man installed. But many mini installations don't, so these days Google is the standard backup.[[User:CityZen|CityZen]] ([[User talk:CityZen|talk]]) 14:58, 1 February 2013 (UTC) | ||
− | |||
Randall's joke is spot on, as usual. I've been using UNIX for nearly 30 years. Windows User's solution is elegant. Before Google there was the <code>man</code> command. In all seriousness, productivity on a UNIX box can be greatly enhanced simply by keeping good notes. I keep patterns of all sorts of UNIX commands handy so I don't have to look them up. As Wikipedia implies, <code>tar -tf</code> (I prefer <code>-t<b>v</b>f</code>) should be memorized because one quickly learns that one should ''always'' inspect tarballs before unpacking them. ''– [[User:Tbc|tbc]] ([[User talk:Tbc|talk]]) 14:11, 1 February 2013 (UTC)'' | Randall's joke is spot on, as usual. I've been using UNIX for nearly 30 years. Windows User's solution is elegant. Before Google there was the <code>man</code> command. In all seriousness, productivity on a UNIX box can be greatly enhanced simply by keeping good notes. I keep patterns of all sorts of UNIX commands handy so I don't have to look them up. As Wikipedia implies, <code>tar -tf</code> (I prefer <code>-t<b>v</b>f</code>) should be memorized because one quickly learns that one should ''always'' inspect tarballs before unpacking them. ''– [[User:Tbc|tbc]] ([[User talk:Tbc|talk]]) 14:11, 1 February 2013 (UTC)'' | ||
Line 91: | Line 88: | ||
The quickest tar command with valid syntax would be "tar t". Every switch after the first command letter is optional. Even the initial dash is optional. [[Special:Contributions/85.24.234.35|85.24.234.35]] 11:03, 19 February 2013 (UTC) | The quickest tar command with valid syntax would be "tar t". Every switch after the first command letter is optional. Even the initial dash is optional. [[Special:Contributions/85.24.234.35|85.24.234.35]] 11:03, 19 February 2013 (UTC) | ||
:(That would also be a command that is valid in every known tar version throughout the universe.) | :(That would also be a command that is valid in every known tar version throughout the universe.) | ||
− | |||
The tar command actually has a unique syntax in unix. Classicly, it's first parameter is a subcommand (letter) followed by zero or more option letters. (And I think the subcommand had to be first.) Parameters for the options follow in sequence after that, in the same order the options where listed. Then, for the 'c' subcommand, an input filename list follows. This syntax was rather painful when you had perhaps 5 different option letters each with parameters, but this was a normal enough occurance when you specified the tape drive, tape block size, tape length, and a few others I can't even remember. Early implementations would have a file listing tape configurations so you could pick one and all its parameters with a single digit. In any case, it should be noted that a dash ('-') was actually NOT ALLOWED on the parameters. More recent versions of tar have attempted to add the more common unix option parsing, but still support the dash-less form. Having said all that, I tend to prefer "tar xvzf filename.tar.gz" and "tar tvzf filename.tar.gz". [[User:Divad27182|Divad27182]] ([[User talk:Divad27182|talk]]) 20:18, 23 February 2013 (UTC) | The tar command actually has a unique syntax in unix. Classicly, it's first parameter is a subcommand (letter) followed by zero or more option letters. (And I think the subcommand had to be first.) Parameters for the options follow in sequence after that, in the same order the options where listed. Then, for the 'c' subcommand, an input filename list follows. This syntax was rather painful when you had perhaps 5 different option letters each with parameters, but this was a normal enough occurance when you specified the tape drive, tape block size, tape length, and a few others I can't even remember. Early implementations would have a file listing tape configurations so you could pick one and all its parameters with a single digit. In any case, it should be noted that a dash ('-') was actually NOT ALLOWED on the parameters. More recent versions of tar have attempted to add the more common unix option parsing, but still support the dash-less form. Having said all that, I tend to prefer "tar xvzf filename.tar.gz" and "tar tvzf filename.tar.gz". [[User:Divad27182|Divad27182]] ([[User talk:Divad27182|talk]]) 20:18, 23 February 2013 (UTC) | ||
Line 100: | Line 96: | ||
Kernel panic – not syncing: Attempted to kill init!"? [[Special:Contributions/173.245.56.105|173.245.56.105]] 03:50, 14 July 2015 (UTC) | Kernel panic – not syncing: Attempted to kill init!"? [[Special:Contributions/173.245.56.105|173.245.56.105]] 03:50, 14 July 2015 (UTC) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |