Displaying 20 results from an estimated 121 matches for "vaxs".
Did you mean:
vals
2007 Jun 06
3
Using odesolve to produce non-negative solutions
Hello,
I am using odesolve to simulate a group of people moving through time and transmitting infections to one another.
In Matlab, there is a NonNegative option which tells the Matlab solver to keep the vector elements of the ODE solution non-negative at all times. What is the right way to do this in R?
Thanks,
Jeremy
P.S., Below is a simplified version of the code I use to try to do this,
2005 Jan 25
0
Inconsistent ls behavior on smbmount'ed Windows shares
Hi group
When I use [TAB] to finish the file name ls shows the file. When I repeat
the comman with [UP] ls says there's no such file.
Any ideas ?
The same thing on Fedora Core 3 and FreeBSD 5.3,4.9
[root@vax ~]# cat /etc/sysconfig/i18n
LANG="ru_RU.UTF-8"
SUPPORTED="en_US.UTF-8:en_US:en:ru_RU.UTF-8:ru_RU:ru"
SYSFONT="latarcyrheb-sun16"
[root@vax ~]# mount -t
2001 May 31
1
R and SAS
Hi
I'm trying to read SAS-data on VAX/VMS to Windows R using
foreign pakage read.xport and experience some problems.
Following lines are used in SAS to create XPORT file
LIBNAME a ''xxx;
LIBNAME b XPORT '';
PROC COPY IN=a OUT=b;
RUN;
and I succeed in getting file that looks like correct xport
file.However
when typing in R following
2010 Apr 05
20
SAS and R on multiple operating systems
Hi,
This is not meant to be critical of R, but is intended as
a possible source for improvements to R.
SAS needs the competition.
I am reasonably knowledgeable about
R
SAS-(all products including IML)
SAS and R run on
Windows(all flavors)
UNIX(all flavors)
Apple OSs
Does R run on natively (no emulation)?
We have quite a few users on these systems
VAX-VMS
Z-OS (mainframe)
MVS
VM/CMS(IBM)
2015 Jan 14
6
[LLVMdev] Introduction for new consumer of LLVM
Hello,
I'd like to introduce myself, my company, and our upcoming use of LLVM.
My name is John Reagan. I've been working on compilers and assemblers since
1983 (yes, 31 years). Most of that time was spent on compilers for VAX/VMS
(later renamed to OpenVMS), then OpenVMS on Alpha, and OpenVMS on Itanium.
I've also worked with the HP NonStop platform and was directly involved
2019 Oct 01
7
upgrading from CentOS 7 to 8
Your answer has nothing to do with the original question which is related to upgrade method and not condition for reinstalling without loosing data.
Sometimes you need to keep your configuration and want to avoid reconfiguring everything, and reimaging your computer keeping /home is not an option.
Of course having all user files on a separate filesystem helps when reimaging the OS (that what I do
2018 Nov 03
2
Red Hat is Planning To Deprecate KDE on RHEL By 2024
...ip>
> Yeah, there are very few of us that completely skipped
> MS-DOS/MS-Windows/MacOS-Clasic and *never* used a graphical file manager or
> any of the eye-candy that people now believe is "standard" or "normal". I
> went from VMS on a VT<whatever> to a VAXStation 2000 to a VAXStation 3000, to
> DECStation 5000, to Linux, with some time spent on CP/M-68K and OS-9/68000, as
> well as SunOS, IRIX, etc. *I* have never owned a machine running any verison
> of MS-Windows (I did have a box that dual booted MS-DOS and Linux).
>
VTs? How abo...
2020 Jun 15
2
halt versus shutdown
> I'm quite sure that in original Berkeley Unix, as on the VAX 11/780, halt
> was an immediate halt of the CPU without any process cleanup or file system
> umounting or anything. Early SunOS (pre-Solaris) was like this, too.
>
The SunOS 4.1.2 man page for halt says
NAME
halt - stop the processor
SYNOPSIS
/usr/etc/halt [ -oqy ]
DESCRIPTION
halt writes
2016 Jan 18
2
HDD badblocks
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Not new: I can remember seeing DEC engineers cleaning up the contacts
on memory boards for a VAX 11/782 with a pencil eraser c.1985. It's
still a pretty standard first fix to reseat a card or connector.
On 18/01/16 15:47, Matt Garman wrote:
> That's strange, I expected the SMART test to show some issues.
> Personally, I'm still
2007 May 15
1
read.table() can't read in this table (But Splus can) (PR#9687)
On Mon, 2007-05-14 at 23:41 +0200, vax9000 at gmail.com wrote:
> Full_Name: vax, 9000
> Version: 2.4.0, 2.2.1
> OS: 2.4.0: Mac OS X; 2.2.1: Linux
> Submission from: (NULL) (192.35.79.70)
>
>
> To reproduce this bug, first go to the website "http://llmpp.nih.gov/DLBCL/" and
> download the 14.8M data set "Web Figure 1 Data file". The direct link is
>
2019 May 08
3
kickstart compat C7 -> C8
On Wed, 8 May 2019 at 13:48, Valeri Galtsev <galtsev at kicp.uchicago.edu>
wrote:
>
>
> On 2019-05-08 12:28, Stephen John Smoogen wrote:
> > On Wed, 8 May 2019 at 13:24, mark <m.roth at 5-cent.us> wrote:
>
> >>
> > Yep. Minimum for that is going to be about the same as your RESCUE. The
> > other would just be to confirm that the sda has space and
1998 Nov 24
1
Dissapearence of samba servers.
We have a LAN network consisting mostly of Win95 machines, with a couple
of NT boxes and 3 Linux-based Samba servers. Throw in a VAX running
Pathworks and a partridge in a pear tree.
Anyway, it seems that since Monday all three of the Samba boxes have
dissapeared from the browse lists (from the POV of the Windows users).
Typing in \\server only gives a "Network name not found error."
2006 Sep 27
1
Samba for VMS 5.5
Hello,
Is anyone aware of a stable version of Samba for VAX/VMS 5.5-2? I will
use 2.0.3 if that's the only version available, but I've read that there
are several known problems with this particular version.
Thanks
2013 Nov 16
2
[Bug 10272] New: resource fork handling is broken in 3.1.0
https://bugzilla.samba.org/show_bug.cgi?id=10272
Summary: resource fork handling is broken in 3.1.0
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: Mac OS X
Status: NEW
Severity: normal
Priority: P5
Component: core
AssignedTo: wayned at samba.org
ReportedBy: bugzilla-samba at
2008 Apr 14
0
[PATCH] xattrs not set on locked files that already exist on target
Working with rsync 3.0.2, it appears that rsync isn't unlocking files
before setting the file attributes when those files already exist.
This generates error messages on subsequent such as:
rsync: rsync_xal_set: lsetxattr("locked_file","test_xattr") failed:
Operation not permitted (1)
rsync: rsync_xal_clear:
2016 Oct 27
1
PIC and mcmodel=large on x86 doesn't use any relocations
> Message: 4
> Date: Thu, 27 Oct 2016 22:04:28 +0200
> From: Joerg Sonnenberger via llvm-dev <llvm-dev at lists.llvm.org>
> To: llvm-dev at lists.llvm.org
> Subject: Re: [llvm-dev] PIC and mcmodel=large on x86 doesn't use any
> relocations
> Message-ID: <20161027200428.GA2177 at britannica.bec.de>
> Content-Type: text/plain; charset=us-ascii
>
> On
2004 Dec 14
1
CentOS newbie just saying hello
Hi folks,
Just a quick hello having installed CentOS on my first box - an Acer
Altos G310 (P4 2.8GHz, 768MB RAM with 70GB + 300GB storage. The 300GB
unit is a SATA disk which I hope to software (hardware!?) mirror - if
I'm in for any major fun mirroring a SATA drive do let me know now - I
think hardware mirroring is not an option (yet!?) but I haven't checked
this out completely.
This
2019 Oct 01
1
upgrading from CentOS 7 to 8
On Tue, 01 Oct, 2019 at 13:57:19 -0400, MAILIST wrote:
> After 40 years of upgrading many different operating systems,
> Windows (from 3.1 to 10), CentOS 6 to 8, Ubuntu, Fedora, Red Hat,
> AT&T Unix, VAX VMS; I have never observed an upgrade from one major
> version to the next to work. The last one I tried using their "upgrade
> process" was Ubuntu 18 to 19.
2020 Jun 15
2
halt versus shutdown
> fwiw, i've always used 'init 0' to shut down all sorts of unix/linux
> systems.
In EL7/EL8, init is now a symlink as well because everything is
controlled by systemd.
> On old school unix, and I think even early Linux, halt was an
> /immediate/ halt, as in catch fire. might as well hit the power switch.
>
Not quite. Shutdown is a timed thing so you can tell it
2016 Jan 19
2
HDD badblocks
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I suspect that the gold layer on edge connectors 30-odd years ago was
a lot thicker than on modern cards. We are talking contacts on 0.1"
spacing not some modern 1/10 of a knat's whisker. (Off topic) I also
remember seeing engineers determine which memory chip was at fault and
replacing the chip using a soldering iron. Try that on a DIMM!