Hammer Hardlinks (permission question)

Hello, all i have encountered a bit unexpected and counter-intuitive behaviour of ln and wonder if it is OK: to require _write_ permission on the _source_ file while creating a hardlink to. here is a shell session: $ ls -l drwxr-xr-x 1 sad sad- 0 Aug 25 14:48 dir1/ drwxrwxr-x 1 sad

Hammer Hardlinks (directory question)

Hello, all I wonder if it is OK for a hammer to make hardlinks on directories? Does it legally support such a pervesion properly? Are there any strings attached? Is it safe for now and later on?

Re: Hammer Hardlinks (directory question)

Karthik Subramanian пишет: Not a hammer expert - but in general directory hardlinks are bad because they can cause cycles in the directory tree. yep. i just discovered that hammer simply prohibits directory hardlinks, throwing a proper error message. i am sorry i asked it before try it

your own filesystem

Hi, all i have tried to create my own nullfs using the original nullfs as a template. and i failed. first of all i rename it (as thorougly as i could) then successfully make it then put myfs.ko to /boot/kernel/ then kldload myfs and got File already exists error it looks like i possibly have

Re: your own filesystem

it looks like i possibly have missed the module identifier somewhere but i can not locate... plese! help. How does the VFS_SET() part look in your *_vfsops.c? Sascha VFS_SET(null_vfsops, null, VFCF_LOOPBACK); MODULE_VERSION(myfs, 1);

Re: your own filesystem

it looks like i possibly have missed the module identifier somewhere but i can not locate... plese! help. How does the VFS_SET() part look in your *_vfsops.c? Sascha VFS_SET(null_vfsops, null, VFCF_LOOPBACK); MODULE_VERSION(myfs, 1); Rename null_vfsops structure

Re: your own filesystem

hi again i have some progress here and the next question arises: is there any detailed manual on nullfs and/or stackable filesystems... with function specifications, flowcharts etc... ...or at least proper keywords for google.

Re: your own filesystem

hi, all (thanx for the links to the books) i have added few handlers to my_vnops.c file (that originally was null_vnops.c of nullfs) and (with intention to involve my handlers into execution flow) i have extended struct vop_ops (last 4 lines): struct vop_ops my_vnode_vops = {

modifying nullfs

hello, all i can not figure out how to extend null_layer with new vop hadlers. it already intercepts several operations, but i wish to intercept some more, say vop_read and vop_write.. how to?

Re: modifying nullfs

Antonio Huete Jimenez пишет: Hi, For what is the filesystem you are trying to develop? Does it try to fill any specific gap other filesystem do not? Or are you doing it just for educational purposes? Educational, for now. And then i sincerely apologize, i must familiarize myself with the

Re: modifying nullfs

Matthew Dillon пишет: :Antonio Huete Jimenez пишет: : Hi, : : For what is the filesystem you are trying to develop? Does it try to : fill any specific gap other filesystem do not? : Or are you doing it just for educational purposes? : :Educational, for now. :And then i sincerely apologize, :i