search for: invoving

Two small problems with 2.2.0p1 on BSD/OS 4.0.1, both invoving the internal entropy collector: 1) The ``ls'' commands in ssh_prng_cmds.in all use -n, which isn't valid on BSD/OS and thus caused them all to fail when fixprogs checked them. BSD/OS does, however, have a -T flag which gives complete timestamp information (month, day, year, hour, minu...

If a move toward machine-independent representation seems reasonable, it may be worth looking at some of the binary data exchange formats used by nasa and others, CDF http://nssdc.gsfc.nasa.gov/cdf/cdf_home.html netCDF http://www.unidata.ucar.edu/packages/netcdf/index.html HDF http://hdf.ncsa.uiuc.edu/ There may also be something useful in the "Scientific Data Format Information

Hey all!! Sorry about the crosspost but this invoves CUPS and Samba issues. [Samba 2.2.8 / CUPS 1.1.8 / Redhat 7.2 std] I have encountered a small problem (which is due to my own slipup more than anything else). I have "Windows 2000" versions of the Adobe postscript drivers installed on many of my 2000 machines. Now I am wanting to use the CUPS drivers which are "Windows 2000 or

Abs et al, Ok, so I have just gone and re-read the docs again. My language was a more absolute than it should have been; *however*, I was still correct for the cases under discussion. From ?UseMethod (emphasis mine) An R object is a data object which has a ?class? attribute (and this can be tested by ?is.object?). A class attribute is a character vector giving the names of the

> you had seemed to be presenting it as something new in 3.5.3. I would be surprised if the behavior doesn't go all the way back to whenever head.function was added. My bad. I'm just surprised I've never noticed these problems before. > S3 classes have no formal definitions at all > I'm not sure what is clear about that, or what class hierarchy you're talking about

Experts, We've just migrated from samba 2.2.8a to samba 3.0.20b in a very large corporate environment. Everything was really fine in our lab, but we began experiment serious load problems on the productive servers the morning after the procedure took place. I'll try (briefly) to describe the characteristics of the scenario: Resources: Old Environment: Hardware: