FUSE looks really good. I am going to investigate it.
TIA
On Thu, Aug 21, 2008 at 10:49 AM, Shachar Or <[EMAIL PROTECTED]> wrote:
> On Thursday 21 August 2008 16:18, Tzafrir Cohen wrote:
>> On Thu, Aug 21, 2008 at 06:29:00AM -0400, Mag Gam wrote:
>> > Sharchar:
>> >
>> > Can I do that with autof
On Thursday 21 August 2008 16:18, Tzafrir Cohen wrote:
> On Thu, Aug 21, 2008 at 06:29:00AM -0400, Mag Gam wrote:
> > Sharchar:
> >
> > Can I do that with autofs? Lets say I have a directory called
> > /home/$userid/image_files; can I have autofs to look for
> > /home/$userid/& and automatically mo
On Thu, Aug 21, 2008 at 06:29:00AM -0400, Mag Gam wrote:
> Sharchar:
>
> Can I do that with autofs? Lets say I have a directory called
> /home/$userid/image_files; can I have autofs to look for
> /home/$userid/& and automatically mount and unmount these fs images?
> Lets say I keep the fs images i
Le Thursday 21 August 2008 vers 03:58, Mag Gam("Mag Gam"
<[EMAIL PROTECTED]>) a écrit:
Hello,
> I am very interested in the fuse AND the fs image solution. Is it
> possible to integrate that into auto mounter or autofs type
> solution?
Afuse seems do this sort things. Have a look at
http://afu
On Thursday 21 August 2008 14:44, Owen Townend wrote:
> fuse allows users with filesystem access to an image to mount it
> within one of their own directories.
> There are fuse drivers for iso (fuseiso), ext (fuseext2), tar
> (archivemount, avfs), tar, gzip, bzip2, rar (avfs), network (fusesmb).
>
2008/8/21 Mag Gam <[EMAIL PROTECTED]>:
> Sharchar:
>
> Can I do that with autofs? Lets say I have a directory called
> /home/$userid/image_files; can I have autofs to look for
> /home/$userid/& and automatically mount and unmount these fs images?
> Lets say I keep the fs images in /home/$user/.isos
Sharchar:
Can I do that with autofs? Lets say I have a directory called
/home/$userid/image_files; can I have autofs to look for
/home/$userid/& and automatically mount and unmount these fs images?
Lets say I keep the fs images in /home/$user/.isos
ANy thoughts about this?
Either way, thanks for
On Wednesday 20 August 2008 13:50, Mag Gam wrote:
> David:
>
> Do you have some sort of script to manage this? I am a little hesitate
> to give professors mkfs and mount sudo access. Is there a way around
> this?
You can specify the 'user' option in fstab so that usres can mount the
relevant fil
Thank you all.
I am very interested in the fuse AND the fs image solution. Is it
possible to integrate that into auto mounter or autofs type solution?
I don't want too many open mounts. If the /tmp/mountpoint it not open,
I would like to automatically disregard the mount point.
On Wed, Aug 20,
Le Wednesday 20 August 2008 vers 02:40, Mag Gam("Mag Gam"
<[EMAIL PROTECTED]>) a écrit:
Hello,
> I would like to tar them
> per day into one tar file. I would then like an interface similar
> to zsh/ksh to "cd tar.file" and use it as a typeical shell.
Try fuse[1]. It has a driver for tar(Archi
I've been a DBA for 10 (11?) years, but I know that they aren't good
for everything. 30,000file/hr * 6 hrs/day * 6 days = 1.08*10^6
files. *Many* more, if the simulations run for weeks.
Hierarchical structures are much better at storing such data than
RDBMSs. (I don't know how MySQL stor
On Wed, Aug 20, 2008 at 02:34:59PM +0300, Shachar Or wrote:
> After solving the problem in the immediate consider telling the developer of
> that simulation software to use a database!
Err... I guess you meant:
"tell the developer of the application to use a zip archive, as it
allows random acce
I'm not sure what you're saying here.
It seems more appropriate to use a database instead of files in this case.
On Wednesday 20 August 2008 15:05, Ron Johnson wrote:
> Databases aren't filesystems, and they shouldn't be treated as such.
> Especially if the text BLOBs need to be analyzed, summa
Databases aren't filesystems, and they shouldn't be treated as such.
Especially if the text BLOBs need to be analyzed, summarized, etc.
On 08/20/08 06:34, Shachar Or wrote:
After solving the problem in the immediate consider telling the developer of
that simulation software to use a database
After solving the problem in the immediate consider telling the developer of
that simulation software to use a database!
On Wednesday 20 August 2008 03:40, Mag Gam wrote:
> At my university we run fluid dynamic simulations. These simulations
> create many small files (30,000) per hour. Their size
On 08/20/08 05:50, Mag Gam wrote:
David:
Do you have some sort of script to manage this? I am a little hesitate
to give professors mkfs and mount sudo access. Is there a way around
this?
In that case, go back to Owen Townend's suggestion.
On Wed, Aug 20, 2008 at 12:13 AM, Mag Gam <[EMAIL PR
David:
Do you have some sort of script to manage this? I am a little hesitate
to give professors mkfs and mount sudo access. Is there a way around
this?
On Wed, Aug 20, 2008 at 12:13 AM, Mag Gam <[EMAIL PROTECTED]> wrote:
> WOW!
>
> Very nice ideas.
>
> I like the dd idea. What command would I u
WOW!
Very nice ideas.
I like the dd idea. What command would I use for that? Also, the files
are coming from NFS; how can I help this? Any ideas for this?
On Tue, Aug 19, 2008 at 10:24 PM, David Fox <[EMAIL PROTECTED]> wrote:
> On Tue, Aug 19, 2008 at 5:40 PM, Mag Gam <[EMAIL PROTECTED]> wrot
On Tue, Aug 19, 2008 at 5:40 PM, Mag Gam <[EMAIL PROTECTED]> wrote:
> At my university we run fluid dynamic simulations. These simulations
> create many small files (30,000) per hour. Their size is very small
> (20k to 200k). Instead of having this on the filesystem since it take
My approach:
mak
You can browse tar archives with Midnight Commander (mc).
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
2008/8/20 Mag Gam <[EMAIL PROTECTED]>:
> At my university we run fluid dynamic simulations. These simulations
> create many small files (30,000) per hour. Their size is very small
> (20k to 200k). Instead of having this on the filesystem since it take
> up inode space, I would like to tar them per
At my university we run fluid dynamic simulations. These simulations
create many small files (30,000) per hour. Their size is very small
(20k to 200k). Instead of having this on the filesystem since it take
up inode space, I would like to tar them per day into one tar file. I
would then like an int
22 matches
Mail list logo
