similar to: reading old dump backups from 2009

On 11/3/18 3:26 AM, Pete Biggs wrote: >> restore tvf u1_l0_04-29-09_md1.dump Verify tape and initialize maps >> Input is from a local file/pipe >> Checksum error 20311110402, inode 0 file (null) >> restore: Tape is not a dump tape > what does 'file' think the file is - i.e. what does > > file u1_l0_04-29-09_md1.dump u1_l0_04-29-09_md1.dump:?? data

> > restore tvf u1_l0_04-29-09_md1.dump Verify tape and initialize maps > Input is from a local file/pipe > Checksum error 20311110402, inode 0 file (null) > restore: Tape is not a dump tape what does 'file' think the file is - i.e. what does file u1_l0_04-29-09_md1.dump say? > > > Here's a log file from when the backup was done back in 2009: > >

> On Nov 3, 2018, at 06:26, Pete Biggs <pete at biggs.org.uk> wrote: > I don't think dump has changed anything in 20 years or so! And I > certainly can't see it changing such that it can't read old files - > that is, sort of, it's raison d'etre. A bit off topic but... Funny story, at a previous job, my boss was able to extract the data off tapes made in the

Puppet Dashboard 1.2.13 is a maintenance and bugfix release of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.13.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com See the Verifying Puppet Download section at:

>> >> I do not think you can legally make clang a system compiler on >> Windows without licensing headers/libraries from Microsoft. >> So inability to parse all of the SDK headers is a non issue to me, >> can't use them anyway. > > > Care to cite a source? Please don't (either of you) randomly speculate on the legality of clang/LLVM. To be

I think what's been missed is that zapsmall works relative to the absolute largest value in the vector. Hence if there's only one item in the vector, it is the largest, so its not zapped. The function's raison d'etre isn't to replace absolutely small values, but small values relative to the largest. Hence a vector of similar tiny values doesn't get zapped. Maybe the line

Is this expected behavior? > z <- 1:5 > z[1] <<- 0 Error in z[1] <<- 0 : object "z" not found The documentation seems to suggest that z will be found in the global environment and modified accordingly. Best, Hsiu-Khuern.

Hi to all, I initiate in R - Linux and I've some problems to find an editor with R interface as like RWinEdt for WinEdt. Anyone know one? Thanks in advance for your kind cooperation. Best regards Atenciosamente Ana Patricia Martins ------------------------------------------- Serviço Métodos Estatísticos Departamento de Metodologia Estatística Telef: 218 426 100 - Ext: 3210

hello everyone. please bear with me if this is very easy... I have a data set with many trials, and frames within each trial. I would like to pull out one random frame from each trial. here is an example. i have 4 unique trials (file), and various frames within each (time_pred). I would like to randomly sample 4 rows, but 1 from each trial (file). this sample data is called "h"

Well, this is a bit stronger than a proposal; this is "what I plan to do unless people see obvious flaws I missed"... The text comment header is the second (of three) header packets that begin a Vorbis bitstream. It is meant for short, text comments, not arbitrary metadata; arbitrary metadata will be put in a metadata stream, likely an XML stream type. We've discussed this in

Hi,all: I've couple of large tarballs such as www.tar and images.tar. Is it possible to extract a single file or a list of files from a large tarball such as images.tar instead of extracting the entire tarball? How do I extract specific files under Linux / UNIX operating systems? Thanks in advance ~~ -------------- next part -------------- An HTML attachment was scrubbed... URL:

I argue we should spell C++ lambdas (and other function-like variables) like functions, not like variables. - Use verbs, not nouns. - Use lowerCamelCase. Here's a patch that implements the change to the coding standards: https://reviews.llvm.org/D48991 <https://reviews.llvm.org/D48991> Thoughts? -------------- next part -------------- An HTML attachment was scrubbed... URL:

>>>>> Steve Martin >>>>> on Mon, 18 Dec 2023 07:56:46 -0500 writes: > Does mFUN() really need to be a function of x and the NA values of x? I > can't think of a case where it would be used on anything but the non-NA > values of x. > I think it would be easier to specify a different mFUN() (and document this > new argument)

2017-11-15 21:29 GMT+01:00 Richard W.M. Jones <rjones@redhat.com>: > Gandalf, is there an XVA file publically available (pref. not > too big) that we can look at? I can try to provide one, but it's simple: # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 ---------- 0/0 42353 1970-01-01 01:00 ova.xml ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000

Le 17/12/2023 ? 18:26, Barry Rowlingson a ?crit?: > I think what's been missed is that zapsmall works relative to the absolute > largest value in the vector. Hence if there's only one > item in the vector, it is the largest, so its not zapped. The function's > raison d'etre isn't to replace absolutely small values, > but small values relative to the largest.

Does mFUN() really need to be a function of x and the NA values of x? I can't think of a case where it would be used on anything but the non-NA values of x. I think it would be easier to specify a different mFUN() (and document this new argument) if the function has one argument and is applied to the non-NA values of x. zapsmall <- function(x, digits = getOption("digits"),

Hello Samba folks, I have come across a problem with smbclient 3.5.6 when I use the tar 'x' feature. Pathnames that work out to be 100 characters long are extracted incorrectly: bash-3.2$ tar tvf ugh.tar -rw-r--r-- bdavis/Domain Users 137 2012-12-07 13:36:40 a50characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABCD/a49characterpathnameABCDEFGHIJKLMNOPQRSTUVWXYZABC -rw-r--r-- bdavis/Domain Users

Hi all, I want to move a filesystem off of my NT server over to my Network Appliance NFS server to then be shared via Samba. I assume the easiest way to accomplish this would be to use smbtar. Do I then use smbtar to extract the tar file I create with smbtar, or, can I use gnutar? Does it matter? Am I safer sticking with smbtar? I'm guessing that since smbtar is a wrapper around

>>>>> Serguei Sokol via R-devel >>>>> on Mon, 18 Dec 2023 10:29:02 +0100 writes: > Le 17/12/2023 ? 18:26, Barry Rowlingson a ?crit?: >> I think what's been missed is that zapsmall works relative to the absolute >> largest value in the vector. Hence if there's only one >> item in the vector, it is the largest, so its

Le 18/12/2023 ? 11:24, Martin Maechler a ?crit?: >>>>>> Serguei Sokol via R-devel >>>>>> on Mon, 18 Dec 2023 10:29:02 +0100 writes: > > Le 17/12/2023 ? 18:26, Barry Rowlingson a ?crit?: > >> I think what's been missed is that zapsmall works relative to the absolute > >> largest value in the vector. Hence if