similar to: 9GB Drives Show Up as 4GB

What is the best way to automatically start smb upon reboot on Solaris 2.6? Thanks in advance, Doug Smith

v2 -> v3: - Drop gnulib fallback.

It started out as "this'll be just a simple fix ..." and turned into something a bit over-engineered in the end. Here it is anyway. Rich.

v1 -> v2: - Removed the f_type field from StatVFS.statvfs structure. - New function StatVFS.filesystem_is_remote, written in C. [Thinking about it, this should probably be called ?is_network_filesystem?, but I can change that before pushing]. - Use statvfs instead of fstatvfs, and statfs instead of fstatfs. - Rejigged the comments in builder/builder.ml to make them simpler

Hi all, I''ve got overlapped and offset support in both nread and nwrite. The only thing left before I want to release this (as 0.4.0) is to get NO_BUFFERING to work. Unfortunately, I can''t get it to work. Park, I looked at that site you sent (and borrowed some code from it), but I don''t see anything special happening for NO_BUFFERING. I thought it required

Hi all, I committed win32-driveinfo 0.1.0 to CVS. What is it? =========== A class for getting information of drives Synopsis ======== include Win32::DriveInfo (sectorsPerCluster, bytesPerSector, numberOfFreeClusters, totalNumberOfClusters, freeBytesAvailableToCaller, totalNumberOfBytes, totalNumberOfFreeBytes) = getDriveSpace(''c'').to_a

Hi all, First, I just realized I''ll need to go back and fix some of the prototype declarations for windows-pr. The callback parameters will now need to be set to ''K''. ReadFileEx is one example of this. For purposes of my question, let''s assume ReadFileEx has been declared like so: API.new(''ReadFileEx'', ''LPLPK'',

Hi all, I was just working on the FILE_FLAG_NO_BUFFERING stuff again. I''m a little confused about determining the cluster size. According to the MSDN docs, using GetDiskFreeSpace() on disks over 2GB may return incorrect values. Some threads on comp.os.ms-windows.* seem to support this as well. I did come across this, however:

Further research indicates that GetDiskFreeSpace() is still ok for getting sector size, regardless of actual disk size. In any case, I''m going to default to 512 in the unlikely event that the call fails, rather than raise an error. Dan

Hello, Well, I have a brain-dead user (using Thunderbird 2.0.0.14) who just won't listen when I tell them not to try to move 5000+ messages at one time (or if deleting, bypass the Trash), and they managed to royally screw up their maildirs... I have two problems... 1. The /tmp directory has 9+GB in it... can I just rm tmp/* on that directory without making this problem worse? and 2.

Hello I have Debian Linux 2.6.32-5-xen-amd64 Xen 4.0.1, 2 SAS drives in RAID 1, 16GB ram. I have virtualized Windows 2003R2 32bit where you install the latest version 0.11.0.295 gplpv After reading and reading forums and post testing, I noticed that the hard disk performance drops significantly when I assign the windows domU 9GB ram. (below I leave the config files) If I run the

> -----Original Message----- > From: dlibrik at wolfram.com [mailto:dlibrik at wolfram.com] > Sent: Monday, August 18, 2008 12:26 AM > To: Berger, Daniel > Subject: Re: [Win32utils-devel] Playing with NtQueryInformationFile > > Hello Daniel, > > I apologize for writing to you out of nowhere, but you posted > on the Ruby Win32utils-devel list a while back and I

Hi, I'm having a similar problem, I get "The cluster size in this system is not supported." I get this when running wine InstMsiA.exe (using the version from microsoft.com). It comes up in a windows message box. I'm running wine from yesterday's cvs. I tried running Rein's test program from this old email and I get the following output: % wine fds 'c:\'

common/mlutils: Unix_utils.StatVFS.statvfs: This commit implements a full-featured binding for the statvfs(3) function. We then use this to reimplement the daemon statvfs API in OCaml. Note that the Gnulib fallback is fixed in this commit. It previously referenced non-existent field names in the fs_usage struct. --- common/mlutils/unix_utils-c.c | 138 ++++++++++++++++++++++++++++---

1. I have a 4x18GB drive setup as RAIDZ. Now when thinking about it in terms of RAID5 I would expect to get (4-1)x18 worth of drive space, but DF -h shows 4x18. Is this a bug or do I not understand? 2. Once again thinking in RAID5 terms if I have 4X18GB and 12X9GB drives and I want to make a RAIDZ of all of them I would expect the 18GB to be treated at 9GB so the RAIDZ would be 16X9GB. Is

On 1/9/23 01:37, Simon Matter wrote: >> Just starting and trying to boot off the SPP firmware update ISO image >> on a USB stick. >> >> I made the stick with: >> >> # mkfs.vfat /dev/sdb > ^^^^^^^^^^^^^^^^^^^^ > Why create an MS-DOS filesystem on the stick which gets immediately > overwritten in the next step? I think the idea is to get that first

On Mon, Apr 11, 2016 at 7:05 PM, Kevin Korb <kmk at sanitarium.net> wrote: > You didn't say if you were networking or what features of rsync you > are using but if you aren't networking and aren't doing anything fancy > you are probably better off with cp -au which is essentially the same > as rsync -au except faster. I was curious if "cp -au" was indeed as

Dear all, I have a few binary files like 9Gb or even of 50Gb. I would like to ask you what are the known limits of the R for the data processing part, I have a system with a lot of RAM (500Gb) but I am not sure about the "internal" limitations of the R. How long for example a vector can be? Could you please inform me for these internal R limitations? I would like to thank you in

> Just starting and trying to boot off the SPP firmware update ISO image > on a USB stick. > > I made the stick with: > > # mkfs.vfat /dev/sdb ^^^^^^^^^^^^^^^^^^^^ Why create an MS-DOS filesystem on the stick which gets immediately overwritten in the next step? > # dd bs=4M > if=P52581_001_gen10spp-2022.09.01.00-SPP2022090100.2022_0930.1.iso > of=/dev/sdb

On 16/07/13 6:31 PM, Martijn van Beurden wrote: > On 16-07-13 09:07, Leigh Dyer wrote: >> Hi, >> >> On a particular input file, FLAC (testing with current git) greatly >> inflates its output if I encode at level 7, which enables >> --exhaustive-model-search. The source is a 24-bit WAV file of about >> 60MB; flac -6 encodes this to a 43MB FLAC file, but flac