HFS and case sensitive file systems

I recently received a pre-installed Macbook. The file system is HFS+ (Apple_HFS according to 'diskutil list').
This file system is not case sensitive but I would like it to be. Is there a way to deactivate the HFS wrapper responsible for that without formatting the disk and re-installing the OS from scratch ?

I got issues synchronizing my linux account with my macosx account
If it's home directory contents that's the issue, you might consider simply partitioning your drive and creating a separate home directory partition that is case sensitive, separate from the boot partition tht is not.
Assuming you're on an Intel-based machine, you can resize the existing partition to make room, then create a new case-sensitive partition and move your home directory there.
Now your account synchronization shouldn't have an issue and you didn't have to re-install the entire OS.

Similar Messages

  • CS4 and Case Sensitive File Systems

    Does anyone know if CS4 will support case sensitive file systems?

    While I do wish all software companies including Apple completely
    supported the case-sensitive file system. Many don't. I cannot pull up
    an article, but I remember reading that Apple only recommended the use
    of the case-sensitive file system for OS X server and if memory serves
    even for that it only recommended it for the attached hard drives.
    We can lament the lack of support but if you really want to change the
    status quo for Adobe products then the only useful way to do so is:
    ...Mike

  • What is HFS case sensitive file system

    What is HFS case sensitive file system?

    FlowerChick,
    a HFS case-sensitive filesystem would allow you to have files that differ only by case in the same folder; for example, you could have different files named “FlowerChick” and “flowerchick” in the same folder. On a case-insensitive filesystem, that wouldn’t be allowed.

  • CS5.5 Master Collection on Case-Sensitive File System

    Hello,
    The first thing I'll say is that I already know it's not possible to install on a case-sensitive file system.
    So, on to my question.  I have been tasked to find out a way to get this installed on our 30-35 Macs with case-sensitive file systems (required for other courses/tasks, so not an option to format.)  I was trying to think of a work-around that would let me install and use the CS5.5 Master Collection, but have not been successful yet.  Please note, I am not looking for a hack or extensive renaming of a bunch of files or other half-solutions I've found.
    Basically, what I was wondering is, if I go into Disk Utility and create a 35GB "Disk Image", mount that, and then try to install, why doesn't that work?  I mean, I am technically trying to install to a case-insensitive file system at that point, but CS5.5 still pops up with an error.  Has anyone gotten this type of solution to work, or any other for that matter?  Luckily my college hasn't bought the licenses for all these systems yet, but when a solution is found, they're jumping on it right away.  The main reason I don't want a "hacky" solution is that being deployed on 30-35 systems, this has to be a simple solution, not something that takes hours per system.
    Any insight is greatly appreciated.
    Jeffrey Simmons

    Thank you for the information, I had a hunch it was installing stuff elsewhere too, but wasn't 100% sure.  As for the problem, I ended up just converting to a case-insensitive boot partition.  To others who may want to do this, I used iPartition without a problem.  The only catch is, you can't just run it from the OS drive, you either have to burn a iPartition Boot DVD (requires you have your OS dvd as well), or do what I did and just install OSX to an external drive, install iPartition, then convert the file system on the regular OS drive.  A bit of a hassle, but you don't have to format your system. 
    CS5.5 Master Collection then installed fine, with no problems.  Unfortunately, Photoshop keeps repeatedly crashing.  It's fine for hours, then crashes 4+ times within an hour.  Repeats this over and over unfortunately.  Adobe support hasn't been helpful at all, so I'm just going to return this software and continue using Gimp.  It has always done everything I wanted, but I wanted the "name brand" software.  In the end, it's not worth the hassle, and definitely not worth losing my work over and over, so back to the store it goes.  Thanks again for taking the time to help out though.
    Jeffrey Simmons

  • Case-Sensitive File System?

    I downloaded the trial for Flash CS4 pro and it won't install on my computer.
    It says:
    System Requirements Error
    This software cannot be installed because the file system of the OS volume is not supported. The OS volume should be local , writable and should have non case-sensitive file system
    Anything I can do to get it to work? I have a MBP running Leopard on an intel processor.
    Message was edited by: guynjoan

    guynjoan wrote:
    The hard drive is internal. And Adobe tech doesn't work on the weekends. I checked the "get info" on my hd and it said it is case-sensitive,
    that's your problem. Lots of apps have problems with case sensitive drives so you should never use case sensitive file system unless you have a compelling reason to do so. Your only recourse now is to move your data to a non case sensitive drive. Clone your hard drive to an external drive, boot from the leopard install DVD, reformat the drive non case sensitive and install leopard on it. then use migration assistant to migrate your data from the external.

  • ColdFusion Builder with case sensitive file system on Mac?

    Hi there,
    I tried to install CF Builder on my MacBook Pro (Intel), OS-X 10.5.7 with case sensitive file system. Installation went smoothly, but, when I try to launch CF Builder, I get an error saying that the "architecture is not supported". Is it just nor possible to have CF Builder on a case sensitive fs?
    Thank you
    Chris

    I am having the same issue and logged in here to see what the deal is.
    After I installed cfbuilder my flex builder crapped out as well.
    The cfbuilder logs (which were conveniently scattered throughout my system for no reason) report that I am running:
    java.vm.version               == 1.5.0_19-137
    But if I run "java -version" in terminal I get:
    daves-macbook-pro-2:~ Dave$ java -version
    java version "1.6.0_13"
    Java(TM) SE Runtime Environment (build 1.6.0_13-b03-211)
    Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02-83, mixed mode)
    "Is JDK 1.5 available in the system"
    Definale "available"...
    Does it exist? yes
    Is it set to default? no

  • CS5 install on case-sensitive file system - can't choose different drive (Mac OS)

    I just upgraded my macbook pro to a new drive and 10.6, and chose 'case sensitive' HFSX, 'cause I'm a heavy command line user and wanted the maximum BASH experience.
    I'm trying to install the CS5 demo to try some web design tools, and the installer immediately says "Installation to case-sensitive drives is not supported. Please choose a different drive location to install." So case-sensitive drives aren't supported; crappy but fair enough.
    The error message leads me to think that I can just choose a non-case-sensitive drive to install to, but I never get a chance to pick one - I click on the installer and it goes straight to the error message.
    So - how do I pick a different drive to install to? Am I just an idoit, is there no way to select a different drive, or will it not install on a system that even BOOTS from a c.s. drive, regardless of the format of the drive that CS5 is installed to?
    I called the support number, and the poor fellow on the other end suggested I re-download the demo, and if the new download fails call Apple support to report my 'drive error'.
    I'm hoping to avoid an entire backup-reformat-restore and lose CLI compatibility just to try some demo software.
    ch

    That is part of why I would prefer case sensitive by default.   I know some server packages do the folding for you, same as some web servers do not differentiate between 'htm' and 'html' when people type in requests, but most of the time the backend server is going to be case sensitive and it is not safe to assume (or hope) that the service will fix things.  Compensating for mistakes is fine, but allowing such silent corruption is not a terribly laudable things and it encourage people be careless.
    Every once in a while I do encounter someone submitting some work where their configuration values and file names do not match, and 'well my laptop silently fixes it for me since it does not care' is a poor excuse.  And if I sent broken filenames upstream or even worse commit them to be used on a server, that is a pretty significant professional failure.
    Back to Adobe specifically, I have been trying the suggestion on poster mentioned in where one installs the Adobe applications to a case insensitive drive then copy over the installed files.  This does not quite work out of the box, but for reasons I would be hard pressed to believe are Apple's fault.
    For instance the first error I encounter is the inability of Bridge to load:
    "@executable_path/../Frameworks/WRServices.framework/Versions/A/WRServices"
    When I go look inside the app directories I can see that in Bridge the file has been named 'awrservices', but in Illustrator it is correctly named AWRServices.   So it looks more like a problem in whatever version control they are using.  The only way I can picture (which my adminitialy limited knowledge of what I am sure is a large and complex project with all sorts of legacy issues) that the installer toolchain factors in as a problem is if they have mismatches in their own scripts/packaging and have been depending on HFS's bad behavior to hide the problem.  I can understand not wanting to invest the time to pay down the technical debt on such an issue, but having such errors in your configuration causes long term headaches.
    And I say this as someone who worked on just such a project, moving a software suite that had legacy code stretching back longer than Adobe has existed as a company.  This conversion included moving from a case insenstive filesystem to a case sensitive one and yeah, there were lots of problems that the old FAT32 system hid from us, but it really paid off over the long run to fix them rather than try to twist the code to compensate.
    Having said that, if the problem is really that they do not want to go update their filenames (in version control or config files), then you can always add folding to your loaders.  I have had to do that a few times due to upstream people developing on case insensitive systems and sending data files with incorrect file names.  This is an old class of problem, and while I can empathize with the struggles project managers have trying to get approval for paying down technical debt, the problem never gets better on its own and usually gets worse.
    Which is why I responded with so much grump to the 'I never needed it' argument since that is exactly the type of customer comment that marketing tends to point to in order to push such things off the schedule.  This is the type of thing where the customer does not really know what they want because they are already accustomed to broken behavior and most of the problems are hidden from their immediate view.  It is easy to cover up the limitations since modern UI (and their search capabilities) can handle this. 
    It is not just arcane developers stuff, and it is the same transition that people have made with things like spaces, quotes, and parentheses, where years ago users believed they had no need for them since they were not using them, but they were only not using them because they did not work.   Today try to tell a modern user they can not put (, ", ) or even ' ' in their filenames and they would rightly question why this piece of obvious functionality is not working since today they are used to it working and no longer automatically compensate for it.
    I also find it ironic that by default OSX hides a number of file extensions, so from the user's perspective you can have multiple files with the exact same name displayed to them, so you can get display issues where 'foo' is the same as 'foO' if both have .txt, but 'foo' and 'foO' are not the same if one has .txt while the other is .pdf.  Add to this confusion cases like 'foo.txt' and 'foo.pdf" both being shortened to 'foo'.

  • Print dialog options in case sensitive file system

    Since changing the file system running Lion and Mountain Lion from Mac OS Extended (Journaled) to Mac OS Extended (Case-sensitive, Journaled), certain features in print dialogs have disappeared.
    Particularly the option to print notes with slides in Microsoft Powerpoint are gone. Also, when choosing to print only 1 (or more, but not all) of multiple pages in Microsoft Word, the printer will nevertheless print all pages.
    This problem occurs on printers of different brands, i.e. HP, Lexmark, Brother.
    I was able to determine this problem by reproducing the issue on a cleanly installed Macbook Pro with OS X 10.8 formatted as Mac OS Extended (Case-sensitive, Journaled) vs a cleanly installed Macbook Pro with OS X 10.8 formatted as Mac OS Extended (Journaled), not Case-sensitive.
    Has anyone else had the same problem and maybe a solution?

    I just fixed this on my Mac. It is a bug in Microsoft Office... the Printer Dialog Extension (PDE) for Powerpoint is located in a directory named "Plugins", but PowerPoint is looking for it in "PlugIns". This obviously does not work in a case-sensitive filesystem.
    Here are the steps to fix the issue:
    http://apple.stackexchange.com/a/119974/69562

  • FileVault in Snow Leopard and case-sensitive filesystem?

    Does FileVault in Snow Leopard support case-sensitive filesystems?
    I know it doesn't in Leopard but was wondering if the situation had changed with Snow Leopard.

    V.K. wrote:
    I don't know the answer to that but why are you using a case sensitive file system?
    it's generally a bad idea not only because of filevault but also because many apps will not work well with it and some like many Adobe apps won't run on it at all.
    I find it amusing how Apple tout the virtues of their operating system being Unix-based when they allow MSDOS-style bastardisations like this.
    I've been using OS X for five years in case sensitive mode because I write software for (proper) Unix systems for a living. I need to be able to connect to a Unix-hosted version control system and know that my Mac isn't going to throw a wobbler just because there are two different files which would have the same name under a case-insensitive file system.
    It's a shame that I am therefore denied access to Filevault but, from what I hear, Filevault causes all sorts of problems with Time Machine backups anyway, so perhaps it's for the best.
    I have to say, in five years I haven't encountered a single piece of software that has a problem with case-sensitivity although, admittedly, I've never voluntarily used any Adobe software (does Adobe Air count)?

  • Crashes and read-only file systems

    Notice: I apolgize for the long post, I've tried to be as thorough as possible.  I have searched everywhere for possible solutions, but things I've found end up being temporary workarounds or don't apply to my situation.  Any help, even as simple as, "have you checked out XYZ log, it's hidden here", would be greatly appreciated.  Thanks
    I'm not sure what exactly caused the issues below, but they did start to happen within a day of running pacman -Syu.  I hadn't run that since I first installed Arch on December 2nd of this year.
    Setup:
    Thinkpad 2436CTO
    UEFI/GPT
    SSD drive
    Partitions: UEFISYS, Boot, LVM
    The LVM is encrypted and is broken up as: /root, /var, /usr, /tmp, /home
    All LVM file systems are EXT4 (used to have /var and /tmp as ReiserFS)
    The first sign that something was wrong was gnome freezing.  Gnome would then crash and I'd get booted back to the shell with all filesystems mounted as read-only.  I started having the same issues as this OP:
    https://bbs.archlinux.org/viewtopic.php?id=150704
    At the time, I had /var and /tmp as ReiserFS, and would also get reiserfs_read_locked_inode errors.
    When shutting down (even during non-crashed sessions) I would notice this during shutdown:
    Failed unmounting /var
    Failed unmounting /usr
    Followed by a ton of these:
    device-mapper: remove ioctl on <my LVM group> failed: Device or resource busy
    Nother of these errors had ever appeared before.
    After hours of looking for solutions (and not finding any that worked) I was convinced (without any proof) that my Reiser file systems were corrupt and so I reformatted my entire SSD and started anew - not the Arch way, I know   I set all logical volumes as EXT4.
    After started anew, I noticed
    device-mapper: remove ioctl on LVM_SysGroup failed: Device or resource busy
    was still showing up, even with just a stock Arch setup (maybe even when powering off via Arch install ISO, don't remember).  After a lot of searching, I found that most people judged it a harmless error, so I ignored it and continued setting up Arch.
    I set up Gnome and a basic LAMP server, and everything seemed to work for a couple of hours.  Soon after, I got the same old issues back.  The System-journald issue came back and per the workaround on https://bbs.archlinux.org/viewtopic.php?id=150704 and a couple other places, I rotated the journals and stopped journald from saving to storage.  That seemed to stop THOSE errors from at least overwhelming the shell, but I would still get screen freezes, crashes, and read-only file systems.
    I had to force the laptop to power off, since poweroff/reboot/halt commands weren't working (would get errors regarding the filesystems mounted as read-only).
    I utilized all disk checking functions possible.  From running the tests (SMART test included) that came as part of my laptop's BIOS to full blown fsck.  All tests showed the drive was working fine, and Fsck would show everything was either clean, or
    Clearing orphaned inode ## (uid=89, gid=89, mode=0100600, size=###
    Free blocks count wrong (###, counted=###)
    Which I would opt to fix.  Nothing serious, though.
    I could safely boot back into Arch and use the system fine until the system decides to freeze/crash and do the above all over again.
    The sure way of recreating this for me is to run a cron job on a local site I'm developing. After a brief screen freeze (mouse still moveable but everything is otherwise unreponsive) I'll systemctl status mysqld.service and notice that mysqld went down.
    It seems that it's at this point my file systems are mounted as read only, as trying to do virtually anything results in:
    unable to open /var/db/sudo/...: Read-only file system
    After some time, X/Gnome crashes and I get sent back to shell with
    ERROR: file_stream_metrics.cc(37)
    RecordFileError() err = 30 source = 1 record = 0
    Server terminated successfully (0)
    Closing log file.or_delegate.h(30)] sqlite erro1, errno 0: SQL logic error or missing database[1157:1179
    rm: cannot remove '/tmp/serverauth.teuroEBhtl': Read-only file system
    Before all this happened, I was using Arch just fine for a few weeks.  I wiped the drives and started anew, and this still happens with just the minimal number of packages installed.
    I've searched for solutions to each individual problem, but come across a hack that doesn't solve anything (like turning off storing logs for journal), or the solution doesn't apply to my case.
    At this point, I'm so overwhelmed I'm not even sure where exactly to pick up figuring this issue out.
    Thanks in advance for any help

    Did this occur when you booted from the live/install media?
    What is your current set up? That is, partitions, filesystems etc. I take it you have not yet reinstalled X but are in the default CLI following installation?
    If turning off log storage didn't help, reenable it so that you may at least stand a chance of finding something useful.
    What services, if any, are you running? What non-default daemons etc.?
    Does it happen if you keep the machine off line?
    Have you done pacman -Syu since installation and dealt with any *.pacnew files?
    Last edited by cfr (2012-12-26 22:17:57)

  • Mac OS X, User Folder and Case-sensitivity (plus a Partitioning Question)

    Hello everybody.
    Today, I'd like to start a new thread regarding the configuration of OS X and the formatting of the drive with a HFS+ (case-sensitive, journaled) file system.
    There is a problem that has been tormenting me for quite some time now, and so far I haven't been able to find a losution yet.
    Here is the issue. When I bought my MacBook Pro (early 2011), I changed the main dirve to an hybrid SSD destinating the original 750GB to a Time Machine backup disk. As a consequence I had to make a fresh install of OS X. When it came the time of formatting I've opted for:
    Creating two partitions: 1 for the OS and 1 for the user folder (I have only one admin-user). Back then, I was coming from a Win enviroment and having two partitions seemed to be the best option for me. (Less chanche of user-data corruption in case something goes wrong in the OS partition).
    Chose a HFS+ (case-sensitive, journaled) file system. It seemed to be the more complete alternative.
    Everything was absolutely for a couple of months then I encountered the first issue: Adobe products don't work on a case-sensitive fs.
    I managed to get Photoshop to work eventually (manually correcing folders name) and didn't care too much about the rest.
    In the meantime over a year has passed and I kept the mentioned configuration, uptdating to Lion and ML. Recently another couple of isses have appeared: AutoCAD presents the same problem as Adobe and there is an issue in the keyboard balcklight control (from forums seems that ML is not able to store any information in System Preferences regarding the backlight).
    Despite the fact that case-sensitive fs seems to be the future solution chosen by Apple, it is still premature to have it as OS fs unless you are an hard-core developer that don't care about tons of programs that would eventually miss from your application folder.
    Being decided to move back to a case-insesntive fs, I need wish I could calrify a couple of doubts before proceding:
    (Not relatete to fs) Is it a good practice to keep user folder on a separate volume? Does it generates any issue on the base of your experience?
    Is it possible to have the OS on case-insensitive fs and the user folder on a case-sensitive one? Does the OS have an issue with that?
    The second point is the most critical as my data are now on a case-sensitive volume. They mostly consists in documents, images and music which should be migrated on a case-insensitive volume seamlessy, however, I'm not 100% sure about what happened during the last year (i.e. if there has been the generation of not-unique names).
    Furhtermore, I wish I could keep a case-sens volume as I plan to be dealing with a Linux enviroment soon. If that could be the user volume, this would be amazing.
    I'd also like to ask personal opinion on advantages of having case-sens fs.
    I understand I asked lots of questions in a single post. I hope, however, that this thread could be a base to collect some of the quite dispersive topics related to case-sensitivity present on the web.
    Best Regards,
    Alexander

    alexanderxc wrote:
    Linc, in the provious post you said there might be issues having user data on a separte partition.
    Which kind of issues are you tihnking of? Have you ever encountered such problems?
    The biggest risk is that poorly written software will assume your home directory is at /Users/you and will fail (or worse) if it doesn't like what it finds there.
    I really appreciated if you could be more specific and don't worry about being too technical.
    There are two ways you can go about it.
    1) Set everything up normally as if you only had one partition. Create your user on that one parition. Then, copy all the real user data to the 2nd partition. Using your admin account, make sure that all the permission on the user folder on the 2nd partition are the same as on the original partition. The, use System Preferences > Users & Groups > your account > right/control click > Advanced > Home directory and change it to the home directory on the 2nd partition. Log in to that new account. Make sure everything works. Then delete the user directory at /Users.
    2) A even more robust, old-school option is to create an /etc/fstab file and have your 2nd partition mounted at /Users. Then, everything will function normally and your user home directories will all be at /Users. /Users will, however, be on a different volume.

  • Portable Home Directories, FileSyncAgent, and Case-sensitive drives

    I have a 10.5.3 Server machine that is serving (via NFS) home directories to a mixed group of Leopard (10.5.3) and Linux clients. The drive containing user home directories is formatted to be case-sensitive. I also use Portable Home Directories and mobile accounts on all the Leopard clients. Many of the client machines have case-insensitive drives.
    FileSyncAgent is dying on the client machines with a lot of "Reverification failed" messasges in ~/Library/Logs/FileSyncAgent.log. The files being verified often have mixed case file names, while the error messages show lower case file names.
    Anyone else seeing FileSyncAgent dying on every home sync?

    Hi Guys, So far I have found what seems to be a fix for this issue. I was also having the issue happen to me around some iphoto file but that seems to be coincidental. I will detail what I did below but please first backup the mobile account on the local machine as you will need to recreate it.
    Backup the local mobile home folder
    Log into a admin account and delete the mobile account under the Accounts Pane in System Prefs
    Log into the users Network account on the notebook
    Delete all the following items
    ~/Library/Application Support/SyncServices
    ~/Library/Mirrors
    ~/Library/Preferences/ByHost/com.apple.syncservices.*
    ~/Library/Preferences/com.apple.filesync.plist
    ~/Library/Preferences/com.apple.homesync.plist
    ~/Library/Preferences/com.apple.LaunchServices.plist
    ~/Library/Preferences/com.apple.syndication.plist
    ~/Library/Preferences/Syndication
    Logout of the Network account and then back in
    Recreate the Mobile Account
    From this point on I have not seen any issues with the FileSyncAgent crashing. Omit any of the files listed above that do not exist. I generally have the notebooks sync on login and logout and I forced a sync while logged in to make sure everything was okay and so far so good. Hope this helps.

  • Renaming filenames and case-sensitivity: a race condition in the OS?

    There appears to be a curious set of circumstances where the OS doesn't allow you to rename a file where the only changes are case-sensitive. For example, "foo.JPG" to "foo.jpg". You can see an example using the command-shell "tcsh". Start this shell (type "tcsh" at any command prompt), and then type:
    % touch foo.JPG
    % mv foo.JPG foo.jpg
    overwrite foo.jpg? (y/n [n])
    Now, you may think it's no problem because few people use tcsh, but the problem is more systemic that should be addressed because I'm finding the problem at a programming level as well. The simplistic tcsh example illustrates the problem: the internals of tcsh call the OS-layer library function rename(2) to move or rename a file. However, something in the OS that reports back that the new filename exists (even though it doesn't) Because it sees foo.JPG, and it doesn't differentiate letter case, it thinks foo.jpg exists, so it returns an error to the calling program. In this case, it's tcsh, which is what prompts the user to overwrite. It doesn't matter what you answer, the result is the same. If you say yesthe OS doesn't see them as different, so it doesn't do anything.
    If you're a programmer, you can see this happen for yourself by writing a small program that does the same thing:
    #!/usr/bin/perl
    if (!rename "foo.JPG", "foo.jpg") {
    print "Error: $!\n";
    This simple perl script just calls the rename(2) library call, which is part of the OS.
    What I don't understand is why this error happens, when, and how to get around it. Obviously, other programs that rename files don't have this problem. The default shell, bash, doesn't have a problem either--even though tcsh (also a similar command-line shell) does. In fact, most programs don't have this problem. But as a programmer, I'm not sure what I should be doing. This exact same perl script (and correlating C programs) work perfectly well on all other unix platforms I've tried.
    G5 Mac OS X (10.4.5)

    It's not at the os layer, it's at the filesystem
    layer. The filesystem you have is not case sensitive.
    well, the filesystem is part of the operating system, although it's clearly only one component of it. In fact, one of the primary defining characteristics of unix is how the filesystem works, albeit there are variations of implementation. But this is a nit=picking point.
    As to the issue of whether the filesystem truly is case-insensitive, that isn't so clear. I can rename a file from foo.JPG to foo.jpg easily in the Finder (just click and edit a file to change it's name from upper to lower, or mixed), and the new name you give it DOES change. similarly, I can do this with virtually any other app that has a file-finder style dialog box. Why I can't do it with the shell (or at an API level) is the real mystery, and there is no doc on the subject that I'm aware of. Clearly, the OS is preserving the change somewhere, somehow. the question is, who's doing it? (and if it's not part of the filesystem, why?)
    It could be that some other layer is sitting on top of the filesystem that is overseeing such actions, and is preserving the case of the filenames, but this is such a huge waste of time and work, all for a "feature" whose value is still as yet unclear to me.
    If it is, as you say, that "my version" of the filesystem happens to be case-insensitive, I'd love to know where that came from, and what the rationale was behind it. And, of course, how to get some version of the filesystem that doesn't have this feature. I've been working with unix systems at every layer since 1983, and have never run into such a thing before.
    dan

  • CAS Sharepoint/File System Question

    If CAS is used to index Sharepoint or a file system with the appropriate adapter, can it be configured to know what changed or does it have to crawl the entire repository every night to index? If it crawls the entire system, does it re-index everything?

    The answer is different between SharePoint and File Systems.
    For File Systems, the crawler will go out and "touch" each file checking a variety of properties (Filename, size, date modified, owner, etc.) and if it recognizes a change in any of those properties, it will crawl that particular file and extract the content. If no change in those properties is detected, it will skip that file.
    For SharePoint, I believe that it re-crawls the entire repository but the documentation is a little sparse in this area. Regardless, the record store is smart enough to keep the generations distinct and allow you to pull incremental updates between the two versions, even if they were both the result of a full crawl.
    Patrick

  • Ho to reformat to a non  case sensitive file

    How to reformat to a non  case sensitive file

    If you want quotes around all the fields, and you currently
    have quotes around
    none of the fields, you could probably do this using
    find-and-replace in a word processor.
    Open up the CSV file with 'word' or a similar word processor.
    The important thing is that the word processor must be able to do a
    find and replace on 'special' characters, like 'return'.
    Use find and replace to:
    Replace all 'comma' characters with the sequence: quote comma
    quote
    Replace all 'return' characters with the sequence: quote
    return quote
    You should then find that your CSV text has quotes around
    every record, but you'll have an extra quote character at the very
    start and very end of the file (on separate lines), which you'll
    need to delete by hand.
    Of course, make a backup of your data first - and this won't
    work if some of your columns already have quotes, or if some of
    your fields actually use the 'comma' character inside the field
    data.
    - Ben

Maybe you are looking for