Re: mail headers not set (cf question re tar)

On 24/09/2022 02:37, jr wrote: On Thursday, 22 September 2022 at 16:30:05 UTC+1, Max Nikulin wrote: ... Debian mail list archive has a rare mhonarc configuration that adds reply to list action (usually only reply to sender is available) and these mailto: links contain proper In-Reply-To value

Re: question re tar

On Fri, 23 Sep 2022 19:18:35 -0400 The Wanderer wrote: > I think the question was about a way/place/method to manually add such > headers from within Gmail, so that they can be present even when > replying to a message from within the digest, so that replies can be > made correctly while

Re: question re tar

On 2022-09-23 at 16:24, Thomas Schmitt wrote: > Hi, > > jr wrote: > >> I [...] cannot find an obvious (any!) place where headers could be set [...] >> I [...] hope that someone can/will supply Gmail specific instructions > > The normal way to participate is to subscribe your mail address at >

Re: question re tar

Hi, jr wrote: > I [...] cannot find an obvious (any!) place where headers could be set [...] > I [...] hope that someone can/will supply Gmail specific instructions The normal way to participate is to subscribe your mail address at https://lists.debian.org/debian-user/ or by sending a mail to

mail headers not set (cf question re tar)

hi, a single reply re the mail headers issue. On Thursday, 22 September 2022 at 09:20:06 UTC+1, Thomas Schmitt wrote: > ... > Your mails lack headers like "In-Reply-To:" or "References:", ... On Thursday, 22 September 2022 at 09:30:05 UTC+1, Tixy wrote: > ... > For a lot (most?) of us, your

Re: question re tar

On 22/09/2022 14:00, jr wrote: On Wednesday, 21 September 2022 at 17:20:05 UTC+1, Markus Schönhaber wrote: Could you please stop using a mail client that starts a new thread with every message you send? Please use something instead that really creates a reply when you are replying to someone

Re: question re tar

On Thu, 22 Sep 2022 08:00:34 +0100 jr wrote: > ouch. I read the digest, That could be your problem. If you would subscribe as a regular user, rather than to the digests (or in addition to) and reply to those messages, you might solve the problem. -- Does anybody read signatures any more?

Re: question re tar

On Thu, 2022-09-22 at 08:00 +0100, jr wrote: [...] > > [a reply that isn't one] > > > > Could you please stop using a mail client that starts a new thread with > > every message you send? > > Please use something instead that really creates a reply when you are > > replying to someone (i. e.

Re: question re tar

Hi, jr wrote: > I see a single thread only. cannot see "a new thread [started] with > every message", sorry. Your mails lack headers like "In-Reply-To:" or "References:", which should tell the Message Id of the mail to which you answer resp. some or all IDs of the thread. (My "References:" only

Re: question re tar

> That listing almost certainly includes subdirectory names. Hence your > issues. > ... > That's why you're getting duplicates. > ... > As I told you several posts ago, if you're feeding "find" output -- or > in your case, "locate" output, which has the exact

Re: question re tar

han an interactive file listing. It would be better yet to use `find /home/jr -type f -print0` which would output: /home/jr/dir1/file1\0/home/jr/dir2/file2\0 [disclaimer: the rest of this assumes GNU tar; other tar implementations will have different behavior, capabilities, and options] Wh

Re: question re tar

21.09.22, 17:29 +0200, jr wrote: [a reply that isn't one] Could you please stop using a mail client that starts a new thread with every message you send? Please use something instead that really creates a reply when you are replying to someone (i. e. something that sets the

Re: question re tar

ce your issues. You're feeding both a filename *and* its containing directory name to tar. Tar recurses into the directory whose name you have fed it, and then also grabs the file whose name you have fed it. That's why you're getting duplicates. As I told you several posts ago, if you're feed

Re: question re tar

eed a DEMONSTRATION of how it is broken and wrong? > > unicorn:/tmp/x$ mkdir -p sub1/sub2 > unicorn:/tmp/x$ touch sub1/sub2/{file1,file2,'* file3 *'} > unicorn:/tmp/x$ not_safe=$(find . -type f) > unicorn:/tmp/x$ tar cf ../foo.tar $not_safe sure. I'm talking about a working envir

Re: question re tar

On Wed, Sep 21, 2022 at 12:31:58PM +0100, jr wrote: > > > $ tar -cvWf $arcname $fnames > > > > > > where $fnames initially was a list in a variable (this is preparing a > > > shell script), then I switched to storing in those in a file and > > > $ tar

Re: question re tar

me that perhaps the OP did > > > something like this: ... > > > unicorn:/tmp/x$ find . | tar cv --files-from=- -f ../foo.tar > > > > I prefer 'locate' to 'find'. an no guessing involved, as I wrote on > > the 18th, the invocation was: > > $ tar -cvWf $arc

Re: question re tar

On Tue, Sep 20, 2022 at 10:19:50PM +0100, jr wrote: > hi, > > On Tuesday, 20 September 2022 at 12:30:05 UTC+1, Greg Wooledge wrote: > > ... > > With this new information, it occurs to me that perhaps the OP did > > something like this: ... > > unicorn:/tmp/x$

Re: question re tar

hi, On Tuesday, 20 September 2022 at 12:30:05 UTC+1, Greg Wooledge wrote: > ... > With this new information, it occurs to me that perhaps the OP did > something like this: ... > unicorn:/tmp/x$ find . | tar cv --files-from=- -f ../foo.tar I prefer 'locate' to 'find'. an no guess

Re: question re tar

> It seems some files are present multiple times in your list. > > echo text >file.txt > tar cvWf test.tar file.txt file.txt > tar tvf test.tar Sorry, I deleted this message, and then had a thought a few minutes later, so I'm quoting text from the mailing list archive. With th

Re: question re tar

Hi, Max Nikulin wrote: > It seems some files are present multiple times in your list. > tar cvWf test.tar file.txt file.txt Well if it is that easy to create the situation, i can test what happens on restoring the tarball: $ tar cvf test.tar x x x x $ rm x rm: remove regular f

Re: question re tar

On 19/09/2022 02:37, jr wrote: when I saw the links and started investigating, I tried cat for the names, ie $ tar -cvWf $arcname $(cat $fnames) adding one or two file names on the command line works as expected, supplying names from list and or file produces those links. It seems some

Re: question re tar

On Monday, 19 September 2022 at 10:10:05 UTC+1, Thomas Schmitt wrote: > ... > But you could create a small ext filesystem in a file, mount it and make > experiments with it. oh, that's an excellent suggestion. thanks. will do that in the coming days. > > the "machine" is a VM, pre-installed by

Re: question re tar

On Mon, Sep 19, 2022 at 08:24:08AM +0100, jr wrote: > _thank you_. another question, if you don't mind: what will happen > if I extract such an archive on a "normal" computer with ext3/4 > filesystems? (don't want to .. experiment with this) Since none of us can reproduce your archive, only you

Re: question re tar

ake experiments with it. From the view of the Linux kernel the expectable unpacking activities of tar should not be too exotic. I am quite sure that attempts to link a file to itself have happened in the last 25+ years: $ ln x x ln: failed to create hard link ‘x’: File exists > the &

Re: question re tar

hi, On Sun, 18 Sept 2022 at 21:39, Thomas Schmitt wrote: > Will Mengarini wrote: > > Note that the file-type character "h" (the leftmost character in your > > second line of output) isn't documented ... > The 'h' probably comes from {...} > which converts tar fi

Re: question re tar

://sources.debian.org/src/tar/1.34%2Bdfsg-1/src/list.c/#L1188 which converts tar file type LNKTYPE to 'h'. This type is set when dump_hard_link() detects that there is already a file in the archive with the same device and inode number: https://sources.debian.org/src/tar/1.34+dfsg-1/src/create.c

Re: question re tar

* jr [22-09/18=Su 12:59 +0100]: > When I create an archive with '-cvWf' I'm used to finding only the files > specified, but every time I use 'tar' on this Debian, there is a "link" for > each and every file. Why? eg: > -rw--- jr/jr 256 2022-06-1 22:10 .config/pulse/

Re: question re tar

hi, > What kind of file system are the files sitting on? btrfs. the system is the pre-installed (on Chromebooks) Debian VM. > What are the *exact* tar commands that you used, to create the archive, > and to get that partial listing that you gave? initially from a shell script, a

Re: question re tar

On Sun, 18 Sep 2022 12:59:21 +0100 jr wrote: > I hope someone can help me to make 'tar' "behave" as expected. tia. > > when I create an archive with '-cvWf' I'm used to finding only the > files specified, but every time I use 'tar' on this Debian, there is > a "

Re: question re tar

On Sun, Sep 18, 2022 at 12:59:21PM +0100, jr wrote: > when I create an archive with '-cvWf' I'm used to finding only the files > specified, but every time I use 'tar' on this Debian, there is a "link" for > each and every file. why? eg: > -rw--- jr/jr 256 2022-06-

question re tar

hi, I hope someone can help me to make 'tar' "behave" as expected. tia. when I create an archive with '-cvWf' I'm used to finding only the files specified, but every time I use 'tar' on this Debian, there is a "link" for each and every file. why? eg: -rw--- jr/jr

Re: using tar

mick crane [2020-06-15T19:01:32+01] wrote: > I think my memory has packed up. Mine too, and I like GNU's long-option style because I remember them easily. They are also kind of self-documenting code in shell scripts. tar --create --verbose --xz --file archive.tar.xz directory/to_arch

Re: using tar

On Mon, Jun 15, 2020 at 07:30:31PM +0100, mick crane wrote: yes I see that now but without hyphen "f" can be anywhere Yes and no: any of the keys can be in any location, but their arguments must follow the key list in the order that the keys appear. For example: tar cbf 20 fo

Re: using tar

On Mon, Jun 15, 2020 at 02:34:24PM -0500, David Wright wrote: It appears you've also forgotten about man pages as well as google. The man page explains the difference between hyphenated and unhyphenated forms, and helpfully even gives a single example written in both forms: tar cfv a.tar

Re: using tar

On Mon 15 Jun 2020 at 19:30:31 (+0100), mick crane wrote: > On 2020-06-15 19:17, Thomas Pircher wrote: > > mick crane wrote: > > > I thought you put the options after a hyphen with tar ? > > > > Tar accepts 3 styles of options. The style with a single dash is c

Re: using tar

On 2020-06-15 19:17, Thomas Pircher wrote: mick crane wrote: I thought you put the options after a hyphen with tar ? Tar accepts 3 styles of options. The style with a single dash is called the 'UNIX' or 'short-option' style in the man page. "tar -cfvz archive_file.tgz ./directory_to_ar

Re: using tar

On Mon 15 Jun 2020 at 19:24:00 +0100, mick crane wrote: > On 2020-06-15 19:07, Brian wrote: > > On Mon 15 Jun 2020 at 19:01:32 +0100, mick crane wrote: > > > > > I think my memory has packed up. > > > > So has your ability to use a search engine. Try > &g

Re: using tar

On Mon, Jun 15, 2020 at 07:01:32PM +0100, mick crane wrote: > I think my memory has packed up. > I thought you put the options after a hyphen with tar ? > "tar -cfvz archive_file.tgz ./directory_to_archive" > doesn't work. > "tar cfvz archive_file.tgz ./direc

Re: using tar

On 2020-06-15 19:07, Brian wrote: On Mon 15 Jun 2020 at 19:01:32 +0100, mick crane wrote: I think my memory has packed up. So has your ability to use a search engine. Try tar options hyphen Ok I see what the confusion was "f" has to be the last of the options if using hyp

Re: using tar

mick crane wrote: > I thought you put the options after a hyphen with tar ? Tar accepts 3 styles of options. The style with a single dash is called the 'UNIX' or 'short-option' style in the man page. > "tar -cfvz archive_file.tgz ./directory_to_archive" > doesn't work. The `

Re: using tar

On Mon, Jun 15, 2020 at 13:02 mick crane wrote: > I think my memory has packed up. > I thought you put the options after a hyphen with tar ? > "tar -cfvz archive_file.tgz ./directory_to_archive" You do for modern use, but the 'f' has to be the last arg in that incantation. -Tom

Re: using tar

On Mon 15 Jun 2020 at 19:01:32 +0100, mick crane wrote: > I think my memory has packed up. So has your ability to use a search engine. Try tar options hyphen -- Brian.

using tar

I think my memory has packed up. I thought you put the options after a hyphen with tar ? "tar -cfvz archive_file.tgz ./directory_to_archive" doesn't work. "tar cfvz archive_file.tgz ./directory_to_archive" works mick -- Key ID4BFEBB31

Re: HS: tar exclure un dossier a la racine mais pas sous dossier

si tu veux exclure download et titi tar -zcpvf test.tar.gz !(download|titi) Bonne nuit, Le dim. 19 mai 2019 à 22:50, Benoit B a écrit : > > Oups je voulais écrire > > tar -zcpvf test.tar.gz !(download) > Qui archivera : > archive/ > archive/download/ > titi/ > > et e

Re: HS: tar exclure un dossier a la racine mais pas sous dossier

Oups je voulais écrire tar -zcpvf test.tar.gz !(download) Qui archivera : archive/ archive/download/ titi/ et exclu le download du répertoire courent avec !() Le sam. 18 mai 2019 à 09:18, Jérémy Prego a écrit : > > Bonjour, > > Je viens avec une petite question de NOOB sur

Re: HS: tar exclure un dossier a la racine mais pas sous dossier

Bonjour, Voici ma proposition nocturne ! ;) tar --exclude='./download' -zcpvf test.tar.gz !(.) Chez moi la sortie affiche : archive/ archive/download/ download/ titi/ Et pas : ./ ./archive/ ./archive/download/ ./titi/ C'est bien ça que tu veux ? Bonne nuit, Benoit Le sam. 18 mai 2019 à 09

Re: HS: tar exclure un dossier a la racine mais pas sous dossier

> Le dimanche 19 mai 2019, Jérémy Prego a écrit... > > > >> hmmm, donc ça veut dire qu'on peut pas éviter ce "." a la création de >> l'archive directement ? c'est quand même embêtant ... en tout cas, merci >> pour vos réponses jusqu'ici. > > Quel

Re: HS: tar exclure un dossier a la racine mais pas sous dossier

ue tu vois lorsque tu fais le `tar -tv` ? En quoi est ce embêtant ? Lorsque tu décompresses l'archive, tout ce fait correctement, non ? -- jm

Re: HS: tar exclure un dossier a la racine mais pas sous dossier

r pour voir mes >> fichiers. > Essaie en étant dans le répertoire au dessus de toto, puis : > > tar -xzf toto.tar.gz -C toto --exclude ./downloads > tar -tvzf toto.tar.gz > mkdir tata > cd tata > tar -xzf ../toto.tar.gz > hmmm, donc ça veut dire qu'on peut pas évite

Re: HS: tar exclure un dossier a la racine mais pas sous dossier

Bonjour, Le samedi 18 mai 2019, Jérémy Prego a écrit... > le souci avec ma commande, c'est qu'à la création de l'archive, ça crée > un premier dossier "." donc je dois ouvrir ce dossier pour voir mes > fichiers. Essaie en étant dans le répertoire au dessus de tot

Re: HS: tar exclure un dossier a la racine mais pas sous dossier

‘Comprend pas: c’est quoi le problème avec ta commande? Elle n’exclut pas le 1er dossier download, c’est ça? > Le 18 mai 2019 à 09:18, Jérémy Prego a écrit : > > Bonjour, > > Je viens avec une petite question de NOOB sur tar ce matin. J'aimerai > faire quelque chose qui m

Re: HS: tar exclure un dossier a la racine mais pas sous dossier

ossier pour voir mes fichiers. > >> Le 18 mai 2019 à 09:18, Jérémy Prego a écrit : >> >> Bonjour, >> >> Je viens avec une petite question de NOOB sur tar ce matin. J'aimerai >> faire quelque chose qui me parait simple en théorie mais ça me semble >> plu

Re: HS: tar exclure un dossier a la racine mais pas sous dossier

Jérémy Prego writes: > tar --exclude='./download' -zcpvf test.tar.gz . > > j'ai bien essayé de remplacer le point de la fin par un * et d'adapter > mon exclude en conséquence, mais j'ai pas réussi a obtenir le résultat > voulu... > > du coup, j'aimerai mixer les deux. À savo

HS: tar exclure un dossier a la racine mais pas sous dossier

Bonjour, Je viens avec une petite question de NOOB sur tar ce matin. J'aimerai faire quelque chose qui me parait simple en théorie mais ça me semble plus compliqué en pratique. en fait, j'aimerai archiver un dossier mais en excluant un sous dossier mais seulement dans la racine. je m'explique

Re: arquivos .tar e .gz?

as dúvidas pra lista. Em sáb, 2 de fev de 2019 10:24, Daniel Roma < vendedor.softwareli...@gmail.com escreveu: > ola pessoal > esses aqruivos .tar ou gz sao o que, compactados?ou tipo executaveis? > por exemplo, quero baixar o programa pra linux no site, > https://web.archive.org/web/2006

arquivos .tar e .gz?

ola pessoal esses aqruivos .tar ou gz sao o que, compactados?ou tipo executaveis? por exemplo, quero baixar o programa pra linux no site, https://web.archive.org/web/20061102182312/http://www.kompozer.net/ , e tem algumas opções disponiveis. como descompactar ou fazer pra instalar no linux

Re: descomprimir tar .gz en directorio al vuelo

Muchas gracias a todos. La opción que me ha funcionado sin problemas ha sido la de sergio: > > <> > > Por ejemplo > > lo único que en el tar tenía la estructura de directorios, luego he movido la carpeta que quería he borrado el resto y ya. La opción más sencilla: m

Re: descomprimir tar .gz en directorio al vuelo

El 1 feb. 2018 5:41 p. m., "Maykel Franco" escribió: El día 1 de febrero de 2018, 17:28, Galvatorix Torixgalva escribió: > Asi a ojo, se me ocurren varias cosas: > a) algun error en el comando al montar la unidad nfs > b) la unidad nfs esta en

Re: descomprimir tar .gz en directorio al vuelo

El día 1 de febrero de 2018, 17:28, Galvatorix Torixgalva escribió: > Asi a ojo, se me ocurren varias cosas: > a) algun error en el comando al montar la unidad nfs > b) la unidad nfs esta en una maquina con windows?, creo recordar que cuando > windows se "apaga" usando

Re: descomprimir tar .gz en directorio al vuelo

Asi a ojo, se me ocurren varias cosas: a) algun error en el comando al montar la unidad nfs b) la unidad nfs esta en una maquina con windows?, creo recordar que cuando windows se "apaga" usando el modo hibernacion da errores, a ver si es algo de eso c) la unidad nfs esta correcta?, es decir has

Re: descomprimir tar .gz en directorio al vuelo

de febrero de 2018, 14:48, miguel angel gonzalez < mangelgonza...@gmail.com> escribió: > Buenas tardes, > necesito descomprimir un tar gz al vuelo, es decir, que elimine el fichero > origen, el problema que tengo es el espacio, no tengo espacio para tener el > fichero descomprim

Re: descomprimir tar .gz en directorio al vuelo

Si el archivo está en otra máquina, usa un tunel ssh para descomprimirlo. Una búsqueda en Google te daría pistas al respecto. El 1 feb. 2018 9:49 a. m., "miguel angel gonzalez" <mangelgonza...@gmail.com> escribió: > Buenas tardes, > necesito descomprimir un tar gz al vuelo,

Re: descomprimir tar .gz en directorio al vuelo

El 1 de febrero de 2018, 14:48, miguel angel gonzalez <mangelgonza...@gmail.com> escribió: > > Buenas tardes, > necesito descomprimir un tar gz al vuelo, es decir, que elimine el fichero > origen, el problema que tengo es el espacio, no tengo espacio para tener el > fiche

descomprimir tar .gz en directorio al vuelo

Buenas tardes, necesito descomprimir un tar gz al vuelo, es decir, que elimine el fichero origen, el problema que tengo es el espacio, no tengo espacio para tener el fichero descomprimido y el tar.gz en la partición /var y no puedo ampliar el lv, política de empresa. ¿Se os ocurre algo? Gracias

Re: extracting file with xz file tar.....

On 2018-01-26, rhkra...@gmail.com wrote: > On Friday, January 26, 2018 05:50:45 AM Curt wrote: >> On 2018-01-26, David Wright wrote: >> >> Yes, my bad, that is intended for the amanda list, whose new owner is >> >> attempting to emulate yahoo all

Re: extracting file with xz file tar.....

On Friday, January 26, 2018 05:50:45 AM Curt wrote: > On 2018-01-26, David Wright wrote: > >> Yes, my bad, that is intended for the amanda list, whose new owner is > >> attempting to emulate yahoo all those years ago by claiming copyright on > >> everthing the server

Re: extracting file with xz file tar.....

On 2018-01-26, David Wright wrote: >> >> Yes, my bad, that is intended for the amanda list, whose new owner is >> attempting to emulate yahoo all those years ago by claiming copyright on >> everthing the server passes thru. Yahoo got burned at the stake in court >>

Re: extracting file with xz file tar.....

On Friday 26 January 2018 04:52:54 Curt wrote: > On 2018-01-26, Gene Heskett wrote: > > In the meantime I'm trying to train this old dog to delete those 2 > > lines when the message is not aimed at the amanda list. > > Just let us talk to Maurice and we'll work it out with

Re: extracting file with xz file tar.....

On Thursday, 25 January 2018 21:14:24 CET Michael Fothergill wrote: > I ran the tar -xf command: > > root@mikef-PC:/usr/src# tar -xf linux-4.14.15.tar.xz you can use 'a' for automatic and 'v' for verbose. E.g.: tar -axvf linux-4.14.15.tar.xz HTH -- https://github.com/dod38fr/

Re: extracting file with xz file tar.....

On 2018-01-26, Gene Heskett wrote: > > In the meantime I'm trying to train this old dog to delete those 2 lines > when the message is not aimed at the amanda list. Just let us talk to Maurice and we'll work it out with him. > Cheers, Gene Heskett -- “True terror is to

Re: extracting file with xz file tar.....

> > > > > I am trying to extract files from a tar xz file. > > > > > > > > The file is a kernel file. > > > > > > > > I ran the tar -xf command: > > > > [Snipped] > > > > > Cheers, Gene Heskett > > >

Re: extracting file with xz file tar.....

On Thursday 25 January 2018 21:45:46 David Wright wrote: > On Thu 25 Jan 2018 at 19:54:14 (-0500), Gene Heskett wrote: > > On Thursday 25 January 2018 15:51:47 Brian wrote: > > > On Thu 25 Jan 2018 at 15:42:15 -0500, Gene Heskett wrote: > > > [Snipped more] > > > > > > > Cheers, Gene Heskett > >

Re: extracting file with xz file tar.....

On Thu, 25 Jan 2018 20:51:47 + Brian sent: > On Thu 25 Jan 2018 at 15:42:15 -0500, Gene Heskett wrote: > > > On Thursday 25 January 2018 15:14:24 Michael Fothergill wrote: > > > > > Dear folks, > > > > > > I am trying to extract files from a

Re: extracting file with xz file tar.....

On Thu 25 Jan 2018 at 19:54:14 (-0500), Gene Heskett wrote: > On Thursday 25 January 2018 15:51:47 Brian wrote: > > > On Thu 25 Jan 2018 at 15:42:15 -0500, Gene Heskett wrote: > > [Snipped more] > > > > > Cheers, Gene Heskett > > > The above content, added by Maurice E. Heskett, is Copyright 2018

Re: extracting file with xz file tar.....

On Thursday 25 January 2018 15:51:47 Brian wrote: > On Thu 25 Jan 2018 at 15:42:15 -0500, Gene Heskett wrote: > > On Thursday 25 January 2018 15:14:24 Michael Fothergill wrote: > > > Dear folks, > > > > > > I am trying to extract files from a tar xz file. &

Re: extracting file with xz file tar.....

On Thu, Jan 25, 2018 at 10:00:08PM +0100, Michael Lange wrote: > On Thu, 25 Jan 2018 20:14:24 + > Michael Fothergill <michael.fotherg...@gmail.com> wrote: > > > Dear folks, > > > > I am trying to extract files from a tar xz file. > > Why bother with

Re: extracting file with xz file tar.....

On Thu, 25 Jan 2018 20:14:24 + Michael Fothergill <michael.fotherg...@gmail.com> wrote: > Dear folks, > > I am trying to extract files from a tar xz file. Why bother with a command line and not just do it from a gui file manager's context menu? Xfe and pcmanfm and prob

Re: extracting file with xz file tar.....

On 25 January 2018 at 20:33, Greg Wooledge <wool...@eeg.ccf.org> wrote: > On Thu, Jan 25, 2018 at 08:14:24PM +, Michael Fothergill wrote: > > root@mikef-PC:/usr/src# tar -xf linux-4.14.15.tar.xz > > > > Can anyone think of a command that will let me know where

Re: extracting file with xz file tar.....

On Thu 25 Jan 2018 at 15:42:15 -0500, Gene Heskett wrote: > On Thursday 25 January 2018 15:14:24 Michael Fothergill wrote: > > > Dear folks, > > > > I am trying to extract files from a tar xz file. > > > > The file is a kernel file. > > > > I ran

Re: extracting file with xz file tar.....

On Thu, Jan 25, 2018 at 03:42:15PM -0500, Gene Heskett wrote: > running tar xf is asking tar to do something it cannot do, at least not > yet. Says the wheezy user. The newer tar versions will auto-detect the compression type and run the appropriate decompression program. wooledg:~$ t

Re: extracting file with xz file tar.....

ill get back. > > running tar xf is asking tar to do something it cannot do, at least not > yet. > > man xz can be quite educational ;-) > >From tar(1), on a Debian stretch system: -J, --xz Filter the archive through xz(1). I am relatively confident that it was

Re: extracting file with xz file tar.....

Gene Heskett (2018-01-25): > It would help to run the correct unpacker. xz is relatively new, and the > command is: xz -d packagename.xz. If its a tarball, thats what you'll > get back. If it an image for an sd card, that's what you will get back. > > running tar xf is a

Re: extracting file with xz file tar.....

On Thursday 25 January 2018 15:14:24 Michael Fothergill wrote: > Dear folks, > > I am trying to extract files from a tar xz file. > > The file is a kernel file. > > I ran the tar -xf command: > > root@mikef-PC:/usr/src# tar -xf linux-4.14.15.tar.xz > > If you l

Re: extracting file with xz file tar.....

On Thu, Jan 25, 2018 at 08:14:24PM +, Michael Fothergill wrote: > root@mikef-PC:/usr/src# tar -xf linux-4.14.15.tar.xz > > Can anyone think of a command that will let me know where the files > went/confirm it ran properly? Use "tar -xvf ..." to get verbose out

Re: extracting file with xz file tar.....

Michael Fothergill (2018-01-25): > If you look at the date and time then you can see that no directories have > been created with from it in the directory..... tar restores the mtime of extracted files and directories. You need to look at the ctime. Regards, -- Nicolas George signatu

extracting file with xz file tar.....

Dear folks, I am trying to extract files from a tar xz file. The file is a kernel file. I ran the tar -xf command: root@mikef-PC:/usr/src# tar -xf linux-4.14.15.tar.xz If you look at the date and time then you can see that no directories have been created with from it in the directory

problème nom de fichiers avec tar en interopérabilité Linux, Windows, Osx (suite)

Pour en finir avec le précédent message et apporter quelques éclaircissements sur le problème rencontré : Récapitulatif : Archivage avec tar de fichiers comportant des noms accentués. L'archive tar était illisible sous Windows En vérité, le problème ne venait pas de TAR mais du logiciel de

Re: Moving server to new server with tar

On Mon, 8 Jun 2015 16:49:45 -0600 Bob Proulx b...@proulx.com wrote: Lisi Reisz wrote: Bob Proulx wrote: Every file. File by file. I liked this presentation and found it quite interesting.

Re: Moving server to new server with tar

afterward. You would be in the clear. I would still exclude it of course. The possibility of archiving /dev/mem for example makes me nervous. :-) Hehe indeed. I will change the tar command to exclude it completely. http://marc.merlins.org/perso/linux/post_2014-01-06_My-Live-Upgrading

Re: Moving server to new server with tar

On Monday 08 June 2015 23:06:41 Bob Proulx wrote: Every file.  File by file.  I liked this presentation and found it quite interesting.   http://marc.merlins.org/perso/linux/post_2014-01-06_My-Live-Upgrading-Many- Thousands-of-Servers-ProdNG-talk-at-Linux_conf_au-2014.html Unfortunately the

Re: Moving server to new server with tar

Lisi Reisz wrote: Bob Proulx wrote: Every file. File by file. I liked this presentation and found it quite interesting. http://marc.merlins.org/perso/linux/post_2014-01-06_My-Live-Upgrading-Many-Thousands-of-Servers-ProdNG-talk-at-Linux_conf_au-2014.html That one definitely works for

Re: Moving server to new server with tar

Linux4Bene wrote: schreef Bob Proulx: thanks for your reply and the time invested. Much appreciated. It does indeed seem tricky unless you go the full monty and replace the whole installation except for the special dirs like dev as you noted. In my test, I didn't get any strange results in

Re: Moving server to new server with tar

Quoting Lisi Reisz (lisi.re...@gmail.com): On Monday 08 June 2015 23:06:41 Bob Proulx wrote: Every file.  File by file.  I liked this presentation and found it quite interesting. http://marc.merlins.org/perso/linux/post_2014-01-06_My-Live-Upgrading-Many-

Re: Moving server to new server with tar

a problem popping up when the server is in production. Tar command from the backup script on the old server: EXCLUDE=--exclude=proc --exclude=sys --exclude=dev/pts --exclude=backups tar -czpf /backups/full.tar.gz --directory=/ $EXCLUDE / 21 Since /dev is dynamic I exclude /dev from

Re: Moving server to new server with tar

a full tar archive of the old server and start from there. A test on a local VM worked, with some adjustments. Both use Debian 7.8. The services on the old server that need to me moved: - Mail: Postfix, Dovecot, Spamassassin, Clamav, Postgresql, ... - Web: nginx, supervisord, python, php5-fpm

Moving server to new server with tar

Hi, I am in the process of moving my server to another VPS. The goal is to keep the old VPS around and convert it to backup MX DNS amongst other things. I will purchase the new VPS from another company so I can't just copy the vm file/container. As a start, I would do a full tar archive

Re: Excluding a directory from tar

On Mon, 13 Apr 2015 15:36:33 -0500 David Wright deb...@lionunicorn.co.uk wrote: Quoting Petter Adsen (pet...@synth.no): On Mon, 13 Apr 2015 12:12:51 -0500 David Wright deb...@lionunicorn.co.uk wrote: Have fun reading man find, though! petter@monster:~$ man tar | wc -l 540 petter

Re: Excluding a directory from tar

=~/.cache/*. I got it working by creating an empty file in ~/.cache and using the filename as an argument to --exclude-tag-under, but what was I doing wrong when trying to use --exclude? I didn't know tar did that. I thought most people use find to generate the filenames for tar to act

Re: Excluding a directory from tar

Quoting Petter Adsen (pet...@synth.no): On Mon, 13 Apr 2015 12:12:51 -0500 David Wright deb...@lionunicorn.co.uk wrote: Have fun reading man find, though! petter@monster:~$ man tar | wc -l 540 petter@monster:~$ man find | wc -l 1572 :-) Mea culpa. But, in my defence, I think I used

Re: Excluding a directory from tar

--exclude? Maybe the prefix you used (~). Try with tar -cvf /dev/null --exclude=.cache $HOME | less That was, in essence, the command I used, and both you and Vincent are right, the ~ was not expanded. For some reason I was absolutely convinced that I had tried without it, but clearly I

  1   2   3   4   5   6   7   8   9   10   >