how i can run exist-db from cd-rom for distribution?
I've googled for resource but anything found.
Any suggestions will be appreciated.
eXist-db requires a filesystem to write data into, think of storing uploaded data, logfiles, transaction logs. SO you need to have a Harddrive or network drive anyway.
In the old days (...) it was actually possible to run eXist-db from a CD or DVD, but I am pretty sure this does not work any more (cause: we don't test it; it would require some config changes anyway)
eXist-DB is a database management system. You would need something to run it on such as XAMPP. So no, you won't be able to run it straight from the DVD.
Related
I accidentally moved some files from /home/name/Pictures/ directory from my opensuse 11.4 machine to flash drive. Is there a way to recover the data? I lost the data from my flash drive.
Probably no.
Many (most?) Linux desktops have a "wastebasket". If you delete files using the GUI, you should be able to recover them from the wastebasket GUI:
There are also tools like TestDisk or ExtUndelete that might be able to help you:
http://www.linux.org/threads/undelete-files-on-linux-systems.4316/
http://extundelete.sourceforge.net/
Finally, here are some other links that might (might!) help:
http://www.linux.org/threads/undelete-files-on-linux-systems.4316/
https://superuser.com/questions/150027/how-to-recover-a-removed-file-under-linux
https://help.ubuntu.com/community/DataRecovery
http://www.smashingapps.com/2011/08/11/5-must-have-file-recovery-tools-for-linux-users.html
But frankly, your best choices for Linux are the same as for Windows: keep backups of anything you really care about!
I Formatted My D: dard drive partition and I installed Windows on it by mistake. I would have to Install window to C: drive and that was my mistake.
Is there anyway to get my old data of that was stored in D: drive before format.
Please Help me to do this..
Not without having a second hard disk, or a second computer to mount it to.
Also you would need to have data recovery software to do a complete recovery on something like this.
Basic instructions.
shutdown the computer, secure the drive.
Install another hard disk, format, install windows.
Lately I've been recommending getdataback by runtime.org, it's about $99. You most likely need the ntfs version. Install that, (You can test it without purchasing it but you cannot complete the recovery without installing a license)
shutdown the computer.
slave the old hard disk
change the bios settings, if the drive is not identified.
boot into windows run, get data back for ntfs.
choose formatted media
let it run for a few hours.
select the data you want back, save the recovery, install the license, complete the recovery.
it's as easy as that.
More importantly, stop using the computer as any download or use could destroy the data still sitting on the drive by overwriting the data.
I was wondering if there was a way to make a *.dll that mounts archives in Windows without the need for installing drivers. I've tried mounting *.isos (and was successful), but I needed to install drivers, which was not something my intended audience wants to do (or can do). The other relevant alternatives were for Linux (fuse-zip) or dead projects (zipios++).
Something along the lines of this...http://mountziplibrary.codeplex.com/
Oh, and it'd be great if the solution was GPL v3'd or at least open source.
Thanks.
Have you looked at Dokan? It looks like a Windows equivalent to Fuse.
What you're describing is called an Installable File System (IFS). It theory you don't need a driver: implement a SMB server in application space, and let the existing kernel network client talk to that. It's just TCP/IP at that level.
The proper solution is indeed an IFS driver. Fundamentally, drives are objects in the kernel namespace. As such, the code for them should be part of the kernel, and an application never is.
There was a hobbyist project called WinFUSE once, which worked as an SMB server and redirected FS requests to your .NET code. But it's gone, as far as I know. Proper way is to use a driver-based approach. The driver can be installed and removed on-the-fly if the user has admin rights, and if he doesn't, installation of the application requires admin rights anyway. In Unix/Linux it's the same - you can't mount a disk (not saying about the driver now) if you are not an admin. Could I not mention that Callback File System is the only professional supported solution that lets you accomplish the task?
I've decided to Google around for some answers.
One of particular interest was zziplib. It's for C and transparently accesses archives, just like Windows does, treating it as an actual folder.
Of course, the other implementations given by users work too. This one just fit the bill for me.
Maybe this one helps you: ZLib
I'm working on a windows platform and want to be able to auto sync my files one way 'on change' to my virtual windows or linux web server - also need to be able to filter file types. i can connect to the remote machine via network drives.
i'm ideally looking for a free, easy to set up solution - a commercial product that does what I need is called ViceVersa but its a little overkill and costs :)
Thanks
Josh
I'd use rsync - simple, easy to setup, and provides the filters you need. Also very low on bandwidth after the first pass.
Here is a link explaining how to get it working in Windows
Whilst rsync doesn't allow 'on-change' auto-syncing, it is very fast when it scans a sync'ed directory (even very large ones), so you could schedule a frequent sync to overcome this.
Edit: You could combine it with a program like this, to trigger an rsync on folder contents change. Cheaper than viceversa
For other users, its worth mentioning lsyncd, it will auto sync on changes between two machines (by default deferring to rsync). Will only work on Linux though, but if thats not a problem it works great.
It also seems that Sparkleshare has finally released some working code (Dropbox clone). Havent tried it myself but does cross-platform synching and you can setup your own server.
One of my customers has seen $Secure:$SDS:$DATA show up on their drive and it keeps growing while my app is running. I don't (knowingly) write to this file, and don't use any type of Windows secure storage (which might be related). Kind of stumped...
Any thoughts on what this might be?
From what I gather it's a metafile for NTFS. Does your app handle anything related to user access or NTFS permissions on files?