Default File system Authorization

Dear all
I have a question regarding the file systems Authorization
By default File system are created with authorization as follow :
                 - Everyone RX (this folder only)
                 - Users (3 sets of permissions)
                 - CREATOR OWNER F - subfolder and files only
                 - SYSTEM F (all files and folders)
                 - Adminsitrators F (all files and folders)
In fact what I do not like about this is that in the "user group" of the machine is populated "Authenticated Users"
So my collegues non IT, create share on these machines leaving the inheritance and then the whole company have access to thoses files.
Iwas wondering what would be the impact of removing the entries for users, creator owner, everyone and system
would that lead for issues for application to run?
Why keeping such wide permission on sever by default instead of closing the permission and granting access to people that need it ?
Thanks for your help
Bruno

Hi Bruno,
I understand your concern. However, the default permission set is the result after balancing security and usability. If user groups like authenticated users are removed by default, it would break things for sure.
Regarding critical servers like Domain Controllers and file servers, we should keep them in a secure environment and only grant physical access to qualified administrators.
Here are a few threads for your references:
Why is "Authenticated Users" in the local Users group by default?
http://social.technet.microsoft.com/Forums/windowsserver/en-US/bb74fa7c-89bd-476d-88bf-e88cd66618e6/why-is-authenticated-users-in-the-local-users-group-by-default?forum=winserversecurity
Risk of removing NT authority\authenticated users (S-1-5-11) from group "USERS"
http://social.technet.microsoft.com/Forums/en-US/681831a3-7fdc-493c-9cd8-378806733889/risk-of-removing-nt-authorityauthenticated-users-s1511-from-group-users
What is the best method to remove the Authenticated users group from all windows 7 workstations?
http://social.technet.microsoft.com/Forums/windows/en-US/b6794a96-fa6d-43df-8708-92aa4ccb3d8f/what-is-the-best-method-to-remove-the-authenticated-users-group-from-all-windows-7-workstations?forum=w7itprosecurity
Errors after removing Authenticated User in C drive
http://social.technet.microsoft.com/Forums/en-US/e47896d7-21dd-4924-b96c-0aa70b99bcf5/errors-after-removing-authenticated-user-in-c-drive?forum=w8itprosecurity
Best Regards,
Amy

Similar Messages

Btrfs May Be The Default File-System For Fedora 16

Having a somewhat odd interest in different types of filesystems, I'd thought I'd share this snippet I wondered across.
Brought up on the Fedora development list are the plans for Btrfs in Fedora, which provides a target of Fedora 16 when EXT4 will be replaced by Btrfs as the default Linux file-system on new installations.
Fedora was one of the first distributions to deploy support for installing the Linux distribution to a Btrfs root file-system, while the Moblin/MeeGo camp has already turned to it as the default file-system, and now Fedora may finally have everything ready and are comfortable with the state of this Oracle-sponsored file-system.
With the intended Fedora deployment of Btrfs, they will also switch from using LVM as the disk's volume manager to instead relying upon the volume management abilities built into Fedora itself. Fedora / Red Hat developers have previously already worked on taking advantage of other Btrfs features, like snapshots, to provide system roll-back support by creating a copy-on-write snapshot prior to each yum/RPM package transaction.
In order to meet the Fedora 16 Btrfs target, Btrfs support needs to be merged into Fedora's GRUB package (or a separate non-Btrfs /boot file-system must be used), Red Hat's Anaconda must be hooked in to properly utilize Btrfs and its volume management features, and the Fedora LiveCD must be re-worked a bit to handle Btrfs. Additionally, the fsck support for Btrfs must be completed. Oracle's Chris Mason is nearly (circa 90%) complete with this task.
Before Fedora 16 arrives we still have Fedora 15 to worry about, which will continue to offer Btrfs as a file-system option while EXT4 remains the default.
Canonical is also evaluating when to switch to the Btrfs file-system and we may see that move similarly happen for Ubuntu 11.10.
This would seem to imply that fedora is giving btrfs the big thumbs up! They currently release twice a year, and fedora 15 is (I believe) Due out this May, so it wouldnt be too wrong to surmise that come Christmas btrfs would be the standard install option. However, I have always thought of fedora as being a little bit of a testing bed for red hat enterprise, so reading between the lines, I am thinking they want to release btrfs to the wild, and get the bugs sqwished so it can be incorporated into red hat, which is a good thing all round, for all concerned.
Quote blatantly ripped from phoronix.
wikipedia btrfs
kernel.org btrfs

There are, as I understand it, three big issues keeping Btrfs from hitting its final "stable" release:
1) No true fsck (as of November, a fix is due "any time now")
2) The logic used for subvolumes (a sort of "virtual LVM" setup) in Btrfs is wholly different from that used in Ext*, JFS, NTFS, HFS, etc; because of this, there isn't yet a single script/program that will accurately display space consumption. Instead, the user needs to run a couple different commands and extrapolate. A little annoying, but it doesn't affect stability.
3) A bug in the COW aspect of the defrag command which, if run with an incorrect flag, can cause a doubling in the amount of metadata on the filesystem (and thus the amount of space it consumes). Again, it won't wreck anything, but would make management tedious if one needs to restore a snapshot to get rid of extra cruft.
These are all mentioned in the FAQ's on the Btrfs wiki, though the wiki doesn't give priority to any of them. I'm guessing that, if Fedora 16 will be using this later in the year, the Oracle folks have told the Red Hat folks that they're planning on plowing through these issues very soon.
Last edited by ANOKNUSA (2011-03-01 14:55:46)

WebDAV file system authorization box

This box appears on my screen requesting login information: username and password. But it doesn't recognize either one that I input. I cancel the box (twice). Five minutes later, it's back, like a fly buzzing around. Two more cancels buys five more minutes. I don't even know what WebDAV is: so much for having a friend touch my Apple. Help!

WebDAV has nothing to do with synchronization - it's a technology for posting or 'publishing' content publicly on the internet. With Mac OS X, it is most often associated with selectively publishing iCal calendars as an alternative to doing so with .Mac. You are likely sharing selected files and directories on your computer with potentially everyone on the internet, and—if you do not know that you are doing so or why you are doing so—that's a big problem.
I suggest that you have a conversation with your friend about why your platform has anything at all to do with WebDAV. Keep in mind that it is intended to allow users to collaboratively edit and manage files on remote web servers. You might ask yourself, or your friend, if you are being managed remotely.
Incidentally, it is not a good idea to offer someone you do not absolutely trust sufficient access to enable such technologies on your computer. Maybe, there is an innocent explanation for this behavior - likely, there is not. The mere fact that you are not aware of what is going on should be sufficient cause for concern on your part.
Here is some background on the technology:
http://www.webdav.org/other/faq.html

What was the last windows operating system to use FAT as its default file system?

I just wanted to test peoples knowledge of windows and its limitations. I thought this was the perfect place to do so.
I think it is windows me. Anyone have any other opinions?
Note: Question I was asking is in title.
Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering
- Yoda. Blog - http://www.computerprofessions.co.nr

 menu --> About this Mac:
What does "About this mac" say your processor is?

Solaris 10 - File System Size / Layout

Hello, I�m very new to Solaris OS � UNIX world and have a question around the file system.
I have SUN System with a single 36GB of Hard Disk, and eventually I want to install Oracle 10g on it as a development server for myself.
My question is around the file system size and layout
I have installed Solaris 10 and accepted the default file system, which is as below:
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t1d0s0 5.0G 3.4G 1.6G 69% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 1.5G 1.1M 1.5G 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
/platform/sun4u-us3/lib/libc_psr/libc_psr_hwcap1.so.1 5.0G 3.4G 1.6G 69% /platform/sun4u-us3/lib/libc_psr.so.1
/platform/sun4u-us3/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1 5.0G 3.4G 1.6G 69% /platform/sun4u-us3/lib/sparcv9/libc_psr.so.1
fd 0K 0K 0K 0% /dev/fd
swap 1.5G 136K 1.5G 1% /tmp
swap 1.5G 88K 1.5G 1% /var/run
/dev/dsk/c1t1d0s7 28G 28M 28G 1% /export/home
What I don�t understand is when I eventually install Oracle, where will the directory go for it?
The /home/export folder is aprrox: 28GB which is now taking up most of the space, and I understand that this is for users, therefore my question is:
1.Should I have allocated a more space to the root file system for oracle during the OS install?
2. If so what should I do? (its not a production system and I know it will have to go somewhere on the single drive, I�m happy to rebuild as I�m still learning the OS).
Any suggestions?
Rgds
D

Thanks, I do have this but needed info on the file system layout... but I have the info now...
If you select the auto file system layout on Solaris 10 then it gives the remaining space to the home/export . I have since re-installed, customised the file system layout and have space for the database.
D

Please REFS as the new file system

it's about time for ntfs to be retired REFS is the file system everybody should have should be included in windows 10 as the default file system when upgrading should slowly migrate to the new file system just a thought i hate defragging

you might be right, but ReFS does not support booting to windows yet.

Corrupt DMG file - "No Mountable File Systems"

Hello, I have an important backup DMG file that I can't mount. When I try, I get this error..."No Mountable File Systems".
I have tried the following with no success...
- repairing the DMG in Disk Utility.
- converting the DMG in Disk Utility to a R/W image.
- Repair in Data Rescue 3
- Repair in Disk Warrior
- Repair in File Salvage (this actually recovered a single mp3 file, so this makes me think the data is still there)
- Repair in Stellar Phoenix
- Repair in Disk Drill
I have read on one of these forums (I can't seem to find it anymore) that someone had a similar issue and someone helped them through a lot of digging around in the broken file (something to do with headers?)...and in the end they managed to repair the broken DMG file. I would really like to repair this file, so just in case someone who knows how to fix this sort of thing, I've shared the file here...
files.me.com/jeffvandyck/x4qv9c
I have a few other files like this and would really like to recover those as well. I'm relatively technical, and once I understand what I'm looking for I can try to fix the others.
Thanks in advance for any help!
Cheers,
Jeff

Output of hdid -nomount -verbose -debug
Jeffs-MacBook-Pro:~ Jeff$ hdid /Users/Jeff/Jeff\ Projects.dmg -nomount -verbose -debug
calling DIHLDiskImageAttach with
agent: hdid
mount-required: false
debug: true
quiet: false
image-options:
drive-options:
main-url: /Users/Jeff/Jeff Projects.dmg
verbose: true
mount-attempted: false
2011-10-10 13:30:57.030 hdiutil[438:60f] DIHLDiskImageAttach: creating DIHelperProxy
2011-10-10 13:30:57.032 hdiutil[438:60f] [DIHelperProxy alloc]
2011-10-10 13:30:57.032 hdiutil[438:60f] [DIHelperProxy alloc] returning self 0x100500a20, retainCount 1
2011-10-10 13:30:57.033 hdiutil[438:60f] DIHLDiskImageAttach: running DIHelperProxy
2011-10-10 13:30:57.033 hdiutil[438:60f] [DIHelperProxy performOperationReturning] entry
2011-10-10 13:30:57.034 hdiutil[438:60f] [DIHelperProxy performOperationReturning] detaching thread
2011-10-10 13:30:57.034 hdiutil[438:2603] [DIHelperProxy workerThread] entry
2011-10-10 13:30:57.034 hdiutil[438:2603] [DIHelperProxy workerThread] setting up server
2011-10-10 13:30:57.035 hdiutil[438:2603] [DIHelperProxy threadSetupServer] entry
2011-10-10 13:30:57.035 hdiutil[438:2603] [DIHelperProxy threadSetupServer] setting up _headerConnection
2011-10-10 13:30:57.035 hdiutil[438:2603] [DIHelperProxy threadSetupServer] setting up _headerConnection rootObject
2011-10-10 13:30:57.036 hdiutil[438:2603] [DIHelperProxy threadSetupServer] adding NSConnectionDidInitializeNotification notification
2011-10-10 13:30:57.036 hdiutil[438:2603] [DIHelperProxy threadSetupServer] exiting
2011-10-10 13:30:57.036 hdiutil[438:2603] [DIHelperProxy workerThread] launching
2011-10-10 13:30:57.037 hdiutil[438:2603] [DIHelperProxy threadLaunchToolAuthenticated] entry
2011-10-10 13:30:57.038 hdiutil[438:2603] launching helper tool at "/System/Library/PrivateFrameworks/DiskImages.framework/Resources/diskimages-he lper".
2011-10-10 13:30:57.038 hdiutil[438:2603] [DIHelperProxy threadLaunchToolAuthenticated] adding NSTaskDidTerminateNotification notification
2011-10-10 13:30:57.038 hdiutil[438:2603] [DIHelperProxy thread LaunchToolAuthenticated] launching
2011-10-10 13:30:57.039 hdiutil[438:2603] [DIHelperProxy threadLaunchToolAuthenticated] exiting
2011-10-10 13:30:57.040 hdiutil[438:2603] [DIHelperProxy workerThread] running runloop
2011-10-10 13:30:57.040 hdiutil[438:2603] DIHelperProxy threadRunRunLoop] entry, retainCount 3
2011-10-10 13:30:57.049 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] entry
2011-10-10 13:30:57.049 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] adding new NSConnectionDidDieNotification notification
2011-10-10 13:30:57.049 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] removing old NSConnectionDidDieNotification notification
2011-10-10 13:30:57.050 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] removing old connection rootObject
2011-10-10 13:30:57.050 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] invalidating old connection
2011-10-10 13:30:57.050 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] releasing old connection
2011-10-10 13:30:57.051 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] and replacing with new connection
2011-10-10 13:30:57.051 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] exit
2011-10-10 13:30:57.052 hdiutil[438:2603] [DIHelperProxy connectToFramework] entry, helper 0x10011d350
2011-10-10 13:30:57.052 hdiutil[438:2603] [DIHelperProxy connectToFramework] exit
2011-10-10 13:30:57.152 hdiutil[438:2603] [DIHelperProxy sendOperationToHelper] entry
2011-10-10 13:30:57.153 hdiutil[438:2603] [DIHelperProxy sendOperationToHelper] starting operation with helper
2011-10-10 13:30:57.155 hdiutil[438:2603] [DIHelperProxy sendOperationToHelper] exit
2011-10-10 13:30:57.159 hdiutil[438:2603] [DIHelperProxy frameworkCallbackWithDictionary] entry
status proc called: initialize
myStatusProc: returning 0
2011-10-10 13:30:57.159 hdiutil[438:2603] [DIHelperProxy frameworkCallbackWithDictionary] exit
2011-10-10 13:30:57.160 diskimages-helper[440:2003] _imageOptions: {
    "enable-keychain" = 1;
2011-10-10 13:30:57.162 diskimages-helper[440:2003] _driveOptions: {
    autodiskmount = 0;
    "unmount-timeout" = 0;
2011-10-10 13:30:57.162 diskimages-helper[440:2003] DIHelperAttach: performOperation: initializing framework
2011-10-10 13:30:57.163 diskimages-helper[440:2003] {
    agent = hdid;
    "auto-fsck-failure-override-type" = callback;
    "auto-open-ro-root" = 0;
    "auto-open-rw-root" = 0;
    "auto-stretch" = 0;
    "bundlebs-checkpointing" = 0;
    "bundlebs-localcloseonflush" = 0;
    "bundlebs-localcloseonidle" = 0;
    "bundlebs-localcloseonsleep" = 0;
    "bundlebs-localfdcount" = 6;
    "bundlebs-remotecloseonflush" = 0;
    "bundlebs-remotecloseonidle" = 0;
    "bundlebs-remotecloseonsleep" = 0;
    "bundlebs-remotefdcount" = 3;
    "burn-apple-supported-devices-only" = 0;
    "burn-no-underrun-protection" = 0;
    "burn-synthesize-content" = 1;
    "bzip2-level" = 0;
    "callback-with-sla" = 1;
    debug = 1;
    "disable-encrypted-images" = 0;
    "disable-kernel-mounting" = 1;
    "disable-owners" = 0;
    "drive-options" = <62706c69 73743030 d0080000 00000000 01010000 00000000 00010000 00000000 00000000 00000000 0009>;
    "enable-owners" = 0;
    "filevault-default-case-sensitive-file-system" = "Case-sensitive Journaled HFS+";
    "filevault-default-encryption-type" = "AES-128";
    "filevault-default-file-system" = "Journaled HFS+";
    "filevault-default-image-type" = SPARSEBUNDLE;
    "filevault-default-partition-type" = SPUD;
    "filevault-default-volume-name" = FileVault;
    "force-idme" = 0;
    "hfsplus-stretch-parameters" =     {
        "hfsplus-stretch-allocation-block-size" = 4096;
        "hfsplus-stretch-allocation-file-size" = 8388608;
        "hfsplus-stretch-threshold" = 524288;
    "idle-timeout" = 15;
    "ifd-format" = UDZO;
    "ifd-ignore-io-errors" = 1;
    "ifd-segment-size" = 0;
    "iff-format" = UDZO;
    "iff-fs" = "HFS+";
    "iff-layout" = SPUD;
    "iff-source-owners" = auto;
    "iff-spotlight-indexing" = 0;
    "iff-temp-sparse-band-size" = 20480;
    "iff-temp-use-rw-if-possible" = 1;
    "iff-usehelper" = 1;
    "ignore-bad-checksums" = 0;
    "image-options" = <62706c69 73743030 d0080000 00000000 01010000 00000000 00010000 00000000 00000000 00000000 0009>;
    "main-url" = "file://localhost/Users/Jeff/Jeff%20Projects.dmg";
    "mount-attempted" = 0;
    "mount-point" = "/Volumes/";
    "mount-private" = 0;
    "mount-required" = 0;
    "mount-type" = in;
    "nbi-spotlight-indexing" = 0;
    operation = DIHelperAttach;
    "progress-delay" = 5;
    "pthread-reader-cap" = 4;
    quiet = 0;
    "reauthenticate-upon-wake" = 1;
    "skip-auto-fsck-for-system-images" = 1;
    "skip-idme" = 1;
    "skip-idme-reveal" = 0;
    "skip-idme-trash" = 0;
    "skip-previously-verified" = 1;
    "skip-sla" = 0;
    "skip-verify" = 1;
    "skip-verify-locked" = 0;
    "skip-verify-remote" = 1;
    "sparsebundle-compactonidle" = 0;
    "suppress-uiagent" = 1;
    "unmount-timeout" = 0;
    "use-compressed-xml" = 0;
    "use-keychain" = 1;
    verbose = 1;
    "zlib-level" = 1;
DILoadDriver: checking for disk image driver
DILoadDriver: DI_kextExists() returned 0x00000000 (0)
DIIsInitialized: returning NO
2011-10-10 13:30:57.169 diskimages-helper[440:2003] -checkForPreviouslyAttachedImage: entry
2011-10-10 13:30:57.169 diskimages-helper[440:2003]
file://localhost/Users/Jeff/Jeff%20Projects.dmg - (null) ((null), (null)). perm=0
DIIsInitialized: returning YES
DIBackingStoreNewWithCFURL: entry with
file://localhost/Users/Jeff/Jeff%20Projects.dmg
skip-permissions-check: true
DIBackingStoreInstantiatorProbe: entry
file://localhost/Users/Jeff/Jeff%20Projects.dmg
skip-permissions-check: true
DIBackingStoreInstantiatorProbe: probing interface 0 CBSDBackingStore
CBSDBackingStore::newProbe score 100 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 0, score      100, CBSDBackingStore
DIBackingStoreInstantiatorProbe: probing interface 1 CBundleBackingStore
CBundleBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 1, score    -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: probing interface 2 CRAMBackingStore
CRAMBackingStore::probe: scheme "file": not ram: or ramdisk: scheme.
CRAMBackingStore::probe: score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 2, score    -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: probing interface 3 CCarbonBackingStore
CCarbonBackingStore::newProbe: setting initial rval to +100
CCarbonBackingStore::newProbe score 100 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 3, score      100, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: probing interface 4 CDevBackingStore
CDevBackingStore::newProbe: not /dev/disk or /dev/rdisk (/Users/Jeff/Jeff Projects.dmg).CDevBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 4, score    -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: probing interface 5 CCURLBackingStore
CCURLBackingStore::probe: scheme is: file
CCURLBackingStore::probe: not recognized URL scheme.
CCURLBackingStore::probe: score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 5, score    -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: probing interface 6 CVectoredBackingStore
CVectoredBackingStore::newProbe not "vectored" scheme.
CVectoredBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 6, score    -1000, CVectoredBackingStore
DIBackingStoreInstantiatorProbe: selecting CBSDBackingStore
DIBackingStoreNewWithCFURL: CBSDBackingStore
CBSDBackingStore::setNoFollow: setting _noFollow to 0
DIBackingStoreNewWithCFURL: instantiator returned 0
DIBackingStoreNewWithCFURL: returning 0x00000000
2011-10-10 13:30:57.170 diskimages-helper[440:2003] -checkForPreviouslyAttachedImage: resolving file://localhost/Users/Jeff/Jeff%20Projects.dmg returned 0
2011-10-10 13:30:57.170 diskimages-helper[440:2003] -checkForPreviouslyAttachedImage: imageUID (
    "d234881026:i2592177"
) shadowUID (null)
***** testing:
0: d234881026:i939052
(null)
(null)
***** testing:
0: d234881026:i939052
(null)
(null)
***** testing:
0: d234881026:i939052
(null)
(null)
2011-10-10 13:30:57.173 diskimages-helper[440:2003] DIHelperAttach: performOperation: resolving disk image
DIIsInitialized: returning YES
DIIsInitialized: returning YES
DIBackingStoreNewWithCFURL: entry with
file://localhost/Users/Jeff/Jeff%20Projects.dmg
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIBackingStoreInstantiatorProbe: entry
file://localhost/Users/Jeff/Jeff%20Projects.dmg
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIBackingStoreInstantiatorProbe: probing interface 0 CBSDBackingStore
CBSDBackingStore::newProbe score 100 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 0, score      100, CBSDBackingStore
DIBackingStoreInstantiatorProbe: probing interface 1 CBundleBackingStore
CBundleBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 1, score    -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: probing interface 2 CRAMBackingStore
CRAMBackingStore::probe: scheme "file": not ram: or ramdisk: scheme.
CRAMBackingStore::probe: score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 2, score    -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: probing interface 3 CCarbonBackingStore
CCarbonBackingStore::newProbe: setting initial rval to +100
CCarbonBackingStore::newProbe score 100 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 3, score      100, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: probing interface 4 CDevBackingStore
CDevBackingStore::newProbe: not /dev/disk or /dev/rdisk (/Users/Jeff/Jeff Projects.dmg).CDevBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 4, score    -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: probing interface 5 CCURLBackingStore
CCURLBackingStore::probe: scheme is: file
CCURLBackingStore::probe: not recognized URL scheme.
CCURLBackingStore::probe: score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 5, score    -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: probing interface 6 CVectoredBackingStore
CVectoredBackingStore::newProbe not "vectored" scheme.
CVectoredBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 6, score    -1000, CVectoredBackingStore
DIBackingStoreInstantiatorProbe: selecting CBSDBackingStore
DIBackingStoreNewWithCFURL: CBSDBackingStore
CBSDBackingStore::setPermission: opening /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::setPermission: kDI_PERM_READWRITE granted.
CBSDBackingStore::setNoFollow: setting _noFollow to 0
DIBackingStoreNewWithCFURL: instantiator returned 0
DIBackingStoreNewWithCFURL: returning 0x00000000
DIResolveURLToBackingStore: processing level 1 encodings.
DIFileEncodingNewWithBackingStore: entry for encoding level 1
DIFileEncodingInstantiatorProbe: entry for level 1
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIFileEncodingInstantiatorProbe: probing level 1 interface 0 CMacBinaryEncoding
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::openDataFork: returning 0
CBSDBackingStore::closeDataFork fSIZE = 868220928
00000000: 7801 edd0 3101 0000 00c2 a0f5 4fed 6d07   | x...1.......O.m. |
00000010: 8840 61c0 8001 0306 0c18 3060 c080 0103   | [email protected]`.... |
00000020: 060c 1830 60c0 8001 0306 0c18 3060 c080   | ...0`.......0`.. |
00000030: 0103 060c 1830 60c0 8001 0306 0c18 3060   | .....0`.......0` |
00000040: c080 0103 060c 1830 60c0 8001 0306 0c18   | .......0`....... |
00000050: 3060 c080 0103 060c 1830 60c0 8001 0306   | 0`.......0`..... |
00000060: 0c18 3060 c080 0103 060c 1830 60c0 8001   | ..0`.......0`... |
00000070: 0306 0c18 3060 c080 0103 060c 1830 60c0   | ....0`.......0`. |
diskimages-helper: fileNameLength          $00000001
diskimages-helper: resourceForkLength      $0C183060
diskimages-helper: dataForkLength          $80010306
diskimages-helper: commentLength           $000060C0
diskimages-helper: MacBinary III signature   \001\003\006\f (0x0103060C)
diskimages-helper: header CRC              $00001830
diskimages-helper: minimum decoder version $0000000C
diskimages-helper: encoder version         $00000006
no MacBinary III signature - checking for MacBinary I or IIDIFileEncodingInstantiatorProbe: interface 0, score    -1000, CMacBinaryEncoding
DIFileEncodingInstantiatorProbe: probing level 1 interface 1 CAppleSingleEncoding
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::openDataFork: returning 0
00000000: d0ed 0178 0000 0131 00c2 a0f5 4fed 6d07   | ...x...1....O.m. |
00000010: 8840 61c0 8001 0306 180c 3060 c080 0103   | [email protected]`.... |
00000020: 060c 1830 60c0 .... .... .... .... ....   | ...0`........... |
CBSDBackingStore::closeDataFork fSIZE = 868220928
CAppleSingleEncoding::isAppleSingleFile loadAppleSingleHeader failed with error 22
DIFileEncodingInstantiatorProbe: interface 1, score    -1000, CAppleSingleEncoding
DIFileEncodingInstantiatorProbe: probing level 1 interface 2 CEncryptedEncoding
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::openDataFork: returning 0
CEncryptedEncoding::copyHeaderInformation: inBackingStore->openDataFork returned 0
CEncryptedEncoding::copyHeaderInformation: inBackingStore->getDataForkLength (stub header) returned 0
CEncryptedEncoding::copyHeaderInformation: backingStore data fork length is 868220928
CEncryptedEncoding::copyHeaderInformation: reading V1 header from offset 868219652
CEncryptedEncoding::copyHeaderInformation: inBackingStore->readDataFork (stub header) returned 0
CEncryptedEncoding::copyHeaderInformation: not recognized as v1 header
CEncryptedEncoding::copyHeaderInformation: reading V2 header from offset 0
CEncryptedEncoding::copyHeaderInformation: inBackingStore->readDataFork (stub header) returned 0
CEncryptedEncoding::copyHeaderInformation: not recognized as v2 header
CBSDBackingStore::closeDataFork fSIZE = 868220928
(null)
DIFileEncodingInstantiatorProbe: interface 2, score    -1000, CEncryptedEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
DIFileEncodingNewWithBackingStore: returning 0x0000006B
DIResolveURLToBackingStore: level 1 encoding match failed. 107.
(continuing)
DIResolveURLToBackingStore: processing level 2 encodings.
DIFileEncodingNewWithBackingStore: entry for encoding level 2
DIFileEncodingInstantiatorProbe: entry for level 2
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIFileEncodingInstantiatorProbe: probing level 2 interface 0 CUDIFEncoding
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::openDataFork: returning 0
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: returning 0
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: returning 0
CBSDBackingStore::closeDataFork fSIZE = 868220928
CUDIFEncoding::newProbe: failing because backing store is not UDIF file
DIFileEncodingInstantiatorProbe: interface 0, score    -1000, CUDIFEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
DIFileEncodingNewWithBackingStore: returning 0x0000006B
DIResolveURLToBackingStore: level 2 encoding match failed. 107.
(continuing)
DIResolveURLToBackingStore: processing level 3 encodings.
DIFileEncodingNewWithBackingStore: entry for encoding level 3
DIFileEncodingInstantiatorProbe: entry for level 3
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIFileEncodingInstantiatorProbe: probing level 3 interface 0 CSegmentedNDIFEncoding
checkTypeCreator:     /
checkTypeCreator: returning     , score 0
CSegmentedNDIFEncoding::isSegmentedNDIFFile checkTypeCreator failed
DIFileEncodingInstantiatorProbe: interface 0, score    -1000, CSegmentedNDIFEncoding
DIFileEncodingInstantiatorProbe: probing level 3 interface 1 CSegmentedUDIFEncoding
CSegmentedUDIFEncoding::isSegmentedUDIFFile backing store is not of type CUDIFEncoding
DIFileEncodingInstantiatorProbe: interface 1, score    -1000, CSegmentedUDIFEncoding
DIFileEncodingInstantiatorProbe: probing level 3 interface 2 CSegmentedUDIFRawEncoding
CSegmentedUDIFRawEncoding::isSegmentedUDIFRawFile looking for segment 2 "file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart"
DIIsInitialized: returning YES
DIBackingStoreNewWithCFURL: entry with
file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIBackingStoreInstantiatorProbe: entry
file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIBackingStoreInstantiatorProbe: probing interface 0 CBSDBackingStore
CBSDBackingStore::newProbe stat() failed. No such file or directory.
CBSDBackingStore::newProbe score 1 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 0, score        1, CBSDBackingStore
DIBackingStoreInstantiatorProbe: probing interface 1 CBundleBackingStore
CBundleBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 1, score    -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: probing interface 2 CRAMBackingStore
CRAMBackingStore::probe: scheme "file": not ram: or ramdisk: scheme.
CRAMBackingStore::probe: score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 2, score    -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: probing interface 3 CCarbonBackingStore
CCarbonBackingStore::newProbe stat() failed. No such file or directory.
CCarbonBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 3, score    -1000, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: probing interface 4 CDevBackingStore
CDevBackingStore::newProbe: not /dev/disk or /dev/rdisk (/Users/Jeff/Jeff Projects.002.dmgpart).CDevBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 4, score    -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: probing interface 5 CCURLBackingStore
CCURLBackingStore::probe: scheme is: file
CCURLBackingStore::probe: not recognized URL scheme.
CCURLBackingStore::probe: score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 5, score    -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: probing interface 6 CVectoredBackingStore
CVectoredBackingStore::newProbe not "vectored" scheme.
CVectoredBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 6, score    -1000, CVectoredBackingStore
DIBackingStoreInstantiatorProbe: selecting CBSDBackingStore
DIBackingStoreNewWithCFURL: CBSDBackingStore
DIBackingStoreNewWithCFURL: instantiator returned 2
DIBackingStoreNewWithCFURL: returning 0x00000002
DIResolveURLToBackingStore: unable to resolve to any backing store class. 2.
CSegmentedUDIFRawEncoding::isSegmentedUDIFRawFile failed because could not find second segment.
DIFileEncodingInstantiatorProbe: interface 2, score    -1000, CSegmentedUDIFRawEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
DIFileEncodingNewWithBackingStore: returning 0x0000006B
DIResolveURLToBackingStore: level 3 encoding match failed. 107.
(continuing)
DIIsInitialized: returning YES
DIDiskImageNewWithBackingStore: entry with
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIDiskImageInstantiatorProbe: entry
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIDiskImageInstantiatorProbe: probing interface 0 CDARTDiskImage
DIDiskImageInstantiatorProbe: interface 0, score        0, CDARTDiskImage
DIDiskImageInstantiatorProbe: probing interface 1 CDiskCopy42DiskImage
DIDiskImageInstantiatorProbe: interface 1, score        0, CDiskCopy42DiskImage
DIDiskImageInstantiatorProbe: probing interface 2 CNDIFDiskImage
checkTypeCreator:     /
checkTypeCreator: returning     , score 0
CNDIFDiskImage::checkExtension: dmg
CNDIFDiskImage::newProbe: checkExtension gives score -1000.
DIDiskImageInstantiatorProbe: interface 2, score    -1000, CNDIFDiskImage
DIDiskImageInstantiatorProbe: probing interface 3 CUDIFDiskImage
CUDIFDiskImage::checkBackingStoreType: backing store is wrong type
DIDiskImageInstantiatorProbe: interface 3, score    -1000, CUDIFDiskImage
DIDiskImageInstantiatorProbe: probing interface 5 CRawDiskImage
checkBackingStoreType returned score 0 type
checkTypeCreator returned score 0 type
CRawDiskImage::checkExtension: dmg
checkExtension returned score 100 type WRDU
CBSDBackingStore::setPermission: opening /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000000 -> 0x00000014 (locks are MANDATORY)
(RO lock acquired)
CBSDBackingStore::setPermission: kDI_PERM_READONLY granted
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000000 -> 0x00000014 (locks are MANDATORY)
(RO lock acquired)
CBSDBackingStore::openDataFork: returning 0
===== iso scan =====
(null)
(null)
===============================
none
0:
          partition-name: whole disk
          partition-start: 0
          partition-synthesized: true
          partition-length: 1695744
          partition-hint: unknown partition
block-size: 512
burnable: false
appendable: false
CBSDBackingStore::closeDataFork fSIZE = 868220928
CRawDiskImage::checkExtension: dmg
CRawDiskImage: checkExtension returns score 100
DIDiskImageInstantiatorProbe: interface 5, score      100, CRawDiskImage
DIDiskImageInstantiatorProbe: probing interface 6 CShadowedDiskImage
DIDiskImageInstantiatorProbe: interface 6, score     -100, CShadowedDiskImage
DIDiskImageInstantiatorProbe: probing interface 7 CSparseDiskImage
CSparseDiskImage::checkExtension: dmg
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000000 -> 0x00000014 (locks are MANDATORY)
(RO lock acquired)
CBSDBackingStore::openDataFork: returning 0
CBSDBackingStore::closeDataFork fSIZE = 868220928
DIDiskImageInstantiatorProbe: interface 7, score        0, CSparseDiskImage
DIDiskImageInstantiatorProbe: probing interface 8 CSparseBundleDiskImage
CSparseBundleDiskImage::checkExtension: dmg
CSparseBundleDiskImage::newProbe: returning 0
DIDiskImageInstantiatorProbe: interface 8, score        0, CSparseBundleDiskImage
DIDiskImageInstantiatorProbe: probing interface 9 CCFPlugInDiskImage
DIDiskImageInstantiatorProbe: interface 9, score    -1000, CCFPlugInDiskImage
DIDiskImageInstantiatorProbe: probing interface 10 CWrappedDiskImage
DIDiskImageInstantiatorProbe: interface 10, score     -100, CWrappedDiskImage
DIDiskImageInstantiatorProbe: selecting CRawDiskImage
DIDiskImageNewWithBackingStore: CRawDiskImage
checkBackingStoreType returned score 0 type
checkTypeCreator returned score 0 type
CRawDiskImage::checkExtension: dmg
checkExtension returned score 100 type WRDU
CBSDBackingStore::setPermission: opening /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::setPermission: kDI_PERM_READWRITE granted.
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::openDataFork: returning 0
DIDiskImageNewWithBackingStore: instantiator returned 0
DIDiskImageNewWithBackingStore: returning 0x00000000
2011-10-10 13:30:57.258 diskimages-helper[440:2003] DIHelperAttach: performOperation: resolving shadow/section options
2011-10-10 13:30:57.258 diskimages-helper[440:2003] resolveShadowAndSectionOptions: returned 0
2011-10-10 13:30:57.258 diskimages-helper[440:2003] DIHelperAttach: performOperation: checking in-use (1)
DIBackingStore::inUse: this->_fUniqueID
0: d234881026:i2592177
DI_kextCreateDiskImageIdentifierArray: exiting
0:
          writeable-components:

Restrict or disable file system export to force usage of CTS+

Is there any way to restrict or disable direct file system export in a portal environment (for example by authorizations or customizing) to force usage of CTS+?
Thanks in advance for any kind of input!
Cheers,
Andy

Hi Lokendra,
I know that already. Basically I need to know if it's somehow possible to limit the selection on CTS+ only when trying to export any kind of objects out of a Portal environment - meaning the option file export is not availbale at all. If not - is it somehow possible to distinguish between File Export and CTS+ by authorization (not file system authorizations)? As far as I've seen it, the authorizations for both functions are based on the same objects and need the same parameters at least for export. Doesn't seem like a way to solve this issue.
Cheers,
Andy

How to set the system default file character encoding to UTF-8?

Hi all. This is driving me nuts, on both my Windows box and Snow Leopard; I figure much more chance of finding the answer for OS X.
My language and locale are set to Australian English. $LANG=en_AU.UTF-8
However, as I believe is expected, OS X (and Windows for that matter) will create files by default with character encoding of Cp1252 (Latin-1). That is, the FILE encoding in the file metadata - the Byte Order Mark I believe. The file itself, not the characters written to it.
This, in a word, bites. I don't want to be restricted to only ASCII by default, and it is causing me problems with certain software (a Firefox plugin) that creates text files, passing in UTF-8 encoded content, which is then mangled because the file encoding itself is still Cp1252. (I know, I've tested this by changing the file encoding manually and having it overwritten again by the plugin: works correctly.)
As a simple example, just `touch somefile` from terminal creates a file in Cp1252 -- I'm obtaining that info by opening in jEdit by the way (anyone know of something better?).
In other locales that are not English-based, I believe the default file encoding is UTF-8. But surely this can be controlled independently? There must be a system configuration value somewhere that specifies file encoding default. Can someone please tell me what it is?
Thanks!

However, as I believe is expected, OS X (and Windows for that matter) will create files by default with character encoding of Cp1252 (Latin-1). That is, the FILE encoding in the file metadata - the Byte Order Mark I believe. The file itself, not the characters written to it.
Apps like TextEdit and Mail have settings that let you determine the encoding of text produced. The default would normally depend on the character content of the file, ranging from ASCII for basic English to Windows Latin-1 (Win 1252) or ISO Latin -1 (ISO 8859-1) to UTF-8 for other content.
Win 1252 is not ASCII, but has twice the number of characters in the latter.
Byte Order Mark is something totally different --it's a particular character used to signal certain encodings.
http://en.wikipedia.org/wiki/Byteordermark
As a simple example, just `touch somefile` from terminal creates a file in Cp1252 -- I'm obtaining that info by opening in jEdit by the way (anyone know of something better?).
For what Terminal does and how to change it, it might best to post in the Unix forum:
http://discussions.apple.com/forum.jspa?forumID=735
For problems with a FireFox plugin, it might be good to ask on their own forums as well.

Can we change the default file format 'BIN' of system to 'ASC' using table

can we change the default file format u2018BINu2019 of system to u2018ASCu2019 using table TSOPE
if possible:will it affect any system performance

Hello Vincent,
BIN(Binary) is default selection.and so we have to select ascii.to make myself more clear my queries is like:
first for setting ascii what we need to enter in text box that is against ASCII.and
secondly if we select ASCII will it affect system performance in anyways.

Help! what is the default location for shared file system?

Help! i came in this morning and for some bizarre reason the shard file system information had disappeared and podcast producer wouldn't work i thought it was in library/quicktimestreaming/movies so i set it to there but when i try and submit a video i just get question-marks in the post where the video should be its obviously not finding it. So i found where most of the previous videos were which is a folder called Podcast Producer which seems to be a link to my external drive but when i set the shared file system to this folder it creates a new folder called podcasts and sticks them in there so i get the same question-mark scenario. Its bizarre i can't figure out why it would losse the information in server admin the only thing i can think of is that i did a repair permissions and wondered if it might have set some permission on the shared filesystem folder differently and made it somehow inaccessible does anybody know what permissions should be set on the folder? Also regarding quicktime streaming does this location have to be the same as the shared file system folder?
Message was edited by: purplemonkey1

Thanks - The folder was hidden, so once I changed my options to see hidden files, I was able to find it exactly where the link told me it would be.
Much appreciated!

How do I use a NAS file system attached to my router to store iTunes purchases?

We have four Windows devices networked in our house. They all run iTunes with the same Apple ID so when any one of them has iTunes running, we can see that computer on our Apple TV. Two run Windows XP, one runs Vista Business, and the newest runs Windows 7. Upgrading all to the same Windows software is out of the question. Our NAS is hung on an "off warranty" Linksys E3000 router which communicates via USB with a 1TB NTFS formatted Western Digital hard drive. Our plan when we set up this little network, not cheaply, in our 1939 baloon construction tank of a house, was to build our library of digital images, music, and video primarily on that device. It supports a variant of Windows streaming support, but poorly. The best streaming support for our environment seems to be our ethernet connected Apple TV which is hung off the big TV in our family room, and has access to the surround sound "Home Theater" in that room. We've incrementally built up collections of photos, digitized music, and most recently educational materialsd, podcasts, etc. which threaten storage limits on a couple of default C: drives on these windows systems. iTunes, before the latest upgrades, gave us some feedback on the file system connections it established without going to the properties of the individual files, but the latest one has yet to be figured out. MP3's and photos behave fairly well, including the recently available connection between Adobe software and iTunes which magically appeared, allowing JPEG files indexed by Adobe Photoshop Elements running on the two fastest computers to show up under control on the Apple TV attached 56' Samsung screen!
Problems arose when we started trying to set things up so that purchases downloaded from the iTunes store ended up directly on the NAS, and when things downloaded to a specific iTunes library on one of the Windows boxes caused storage "issues" on that box. A bigger problem looming in the immediate future is the "housecleaning" effort which is part of my set of "new years resolutions." How do I get control of all of my collections and merge them on the NAS without duplicate files, or when, for example, we have .ACC and .MP3 versions, only the required "best" option for the specific piece of music becomes a candidate for streaming?
I envission this consolidation effort as a "once in a lifetime" effort. I'm 70, my wife is 68 and not as "technical" as I am, so documented procedures will be required.
I plan to keep this thread updated with progress and questions as this project proceeds. Links to "how to" experiences which are well documented, etc. may be appreciated by those who follow it. I plan to post progress reports and detailed issues going forward. Please help?

Step 1 - by trial and error...
So far, I have been able to create physical files containing MP3 and JPG on the NAS using the Windows XP systems to copy from shared locations on the Vista and Win7 boxes. This process has been aided by the use of a 600 GB SATA 2 capable hard drive enclosure. I first attach to Win 7 or Win Vista and reboot to see the local drive spaces formatted on the portable device. Then I copy files from the user's private directories to the public drive space. When the portable drive is wired to an XP box, I can use Windows to move the files from the portable device to the NAS without any of the more advanced file attributes being copied to the NAS. Once the files are on the NAS, I can add the new folder(s) to iTunes on any of the computers and voila, the data becomes sharable via iTunes. So far, this works for anything that I have completely purchased, or for MP3's I made from the AIC files created when I purchased alblums via iTunes.
I have three huge boxes full of vynl records I've accumulated. The ones that I've successfully digitized via a turntable attached to the sound card on one of my computers and third party software, have found their way to the NAS after being imported into iTunes and using it to bring down available album art work. In general I've been reasonably well pleased with the sound quality of digital MP3 files created this way, but the software I've been using sometimes has serious problems automatically separating individual songs from the album tracks and re-converting "one at a time" isn't very efficient.

ACS 5.3 cannot create default network access authorization rule

Hi, when I click 'Create...' under Access Policies > Default Network Access > Authorization, and then press the 'OK' button, it says 'Please configure at least 1 condition.' However I have no way to configure conditions as the 'Conditions' text is just bold text and not a link or any sort of configurable area. If I go to 'Customize' on the bottom right and add conditions to the right list box, I still have no options when I press Create. Also, the 'green light' next to Default Network Access is grey with a line through it. This is the most cryptic system I have ever used.. anyone have an idea? Thank you!

Looks like you are using chrome amd it's not a supported browser.
Supported Web Client/Browsers
You can access ACS 5.3 administrative user interface using the following Web Client/Browsers:
•Windows 7 32 bit
•Windows XP Professional (Service Pack 2 and 3)
•Windows Vista
•Internet Explorer version 7.x
•Internet Explorer version 8.x
•Internet Explorer version 9.x
•Mozilla Firefox version 3.x
•Mozilla Firefox version 4.x
http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.3/release/notes/acs_53_rn.html#wp222016
Jatin Katyal
- Do rate helpful posts -

Crystal Report failed scheduling onto the File System

Hi,
We have set up a Crystal report file for scheduling via file system. This report has been running fine with regards to generation all through last few months, but has started failing to generate the report at the scheduled time onto the file system from the last few days. When I checked the logs of the Instance Manager, it shows an error like this 'Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: 1017 ]'.
Please note, I was able to run the report from InfoView without any issue, so I don't believe there is any issue with stored procedure/report/database connection but something else.
Can someone please provide some insights on this.
Thanks.

Hello Satish,
Is this issue specific to FileSystem location? What about default enterprise location?
When you view the reprt in InfoView, click on Refresh button to get current data. If the repot was published with Saved Data option, then you would see data in the report but it would be old one.
Above step would confirm that there is no issues with database user credentials specified with the report.
Also, open the report in Crystal Reports 2011, refresh it and publish without saved data in BI 4 repository and schedule it.
Regards,
Mahesh

File system error: The record ID is incorrect. Physical file: . Logical file:

Hi,
I face this error message when I try to 'process update' a dimention, sometime it works but sometime it failed with the error below:
Description: File system error: The record ID is incorrect. Physical file: . Logical file: .
My environment: Window Server 2008 R2+SQL Server 2008 R2.
Note: this issue can be resolved by full cube process, but I can't to that every time if it failed, just want to know what happen at backend of SSAS, It block me neary 2 week without any finding, really appreciate that someone can help on this.
I have do some research with google, I think the root cause here is not TopCount function(It may be a problem with SQL Server2005), also not the size limitation of 4GB size of .astore file.(I check the size of my cube under 'Data\XXX.db\' folder, which only
have few MB size).
Thanks,
Tom

Hi Tom,
Here is a microsoft fix
FIX: "File system error" occurs when you try to run a process update operation on a dimension in Microsoft SQL Server 2008 Analysis Services and in Microsoft SQL Server 2008 R2 Analysis Services
In your acenario, in order to fix this issue, please apply the latest Cumulative update and Service Pack according to your SQL Server version. Besides, there are two workarounds in that fix, plese try it and check if it works or not.
http://support.microsoft.com/default.aspx?scid=kb;en-US;2276495
Regards,
Charlie Liao
TechNet Community Support

Default File system Authorization

Similar Messages

Maybe you are looking for