Return to Question

I think that over time a large number of questions will be duplicated over superuser.com and serverfault.com.

To cite an example, I'm investigating protocols to mount remote filesystems on linux with full locking capability (to configure NAS for my home network). I've looked at (and had questions on) Samba, NFS, SSHFS etc - server technologies used by power users as much as by network admins.

Is it immediately clear which site these questions should be directed towards ? If not, the same question is bound to be raised on both sites by different users (or even the same user).

Duplicate postings are already an issue on SO, why not nip it in the bud by designing for duplicate/cross-posting for SU and SF rather than trying to manage it later ?

Just as an example, I think this question I asked on SF has near-equal relevance on both sites.

I know a similar question was asked earlier, but I'd like to debate the merits of cross-posting on these two sites only, because of their overlap.

I think that over time a large number of questions will be duplicated over superuser.com and serverfault.com.

To cite an example, I'm investigating protocols to mount remote filesystems on linux with full locking capability (to configure NAS for my home network). I've looked at (and had questions on) Samba, NFS, SSHFS etc - server technologies used by power users as much as by network admins.

Is it immediately clear which site these questions should be directed towards ? If not, the same question is bound to be raised on both sites by different users (or even the same user).

Duplicate postings are already an issue on SO, why not nip it in the bud by designing for duplicate/cross-posting for SU and SF rather than trying to manage it later ?

Just as an example, I think this question I asked on SF has near-equal relevance on both sites.

I know a similar question was asked earlier, but I'd like to debate the merits of cross-posting on these two sites only, because of their overlap.

I think that over time a large number of questions will be duplicated over superuser.com and serverfault.com.

To cite an example, I'm investigating protocols to mount remote filesystems on linux with full locking capability (to configure NAS for my home network). I've looked at (and had questions on) Samba, NFS, SSHFS etc - server technologies used by power users as much as by network admins.

Is it immediately clear which site these questions should be directed towards ? If not, the same question is bound to be raised on both sites by different users (or even the same user).

Duplicate postings are already an issue on SO, why not nip it in the bud by designing for duplicate/cross-posting for SU and SF rather than trying to manage it later ?

Just as an example, I think this question I asked on SF has near-equal relevance on both sites.

I know a similar question was asked earlier, but I'd like to debate the merits of cross-posting on these two sites only, because of their overlap.

I think that over time a large number of questions will be duplicated over superuser.com and serverfault.com.

To cite an example, I'm investigating protocols to mount remote filesystems on linux with full locking capability (to configure NAS for my home network). I've looked at (and had questions on) Samba, NFS, SSHFS etc - server technologies used by power users as much as by network admins.

Is it immediately clear which site these questions should be directed towards ? If not, the same question is bound to be raised on both sites by different users (or even the same user).

Duplicate postings are already an issue on SO, why not nip it in the bud by designing for duplicate/cross-posting for SU and SF rather than trying to manage it later ?

Just as an example, I think this question I asked on SF has near-equal relevance on both sites.

I know a similar question was asked earlier, but I'd like to debate the merits of cross-posting on these two sites only, because of their overlap.

I think that over time a large number of questions will be duplicated over superuser.com and serverfault.com.  

To cite an example, I'm investigating protocols to mount remote filesystems on linux with full locking capability (to configure NAS for my home network). I've looked at (and had questions on) Samba, NFS, SSHFS etc - server technologies used by power users as much as by network admins.  

Is it immediately clear which site these questions should be directed towards ? If not, the same question is bound to be raised on both sites by different users (or even the same user).  

Duplicate postings are already an issue on SO, why not nip it in the bud by designing for duplicate/cross-posting for SU and SF rather than trying to manage it later ?  

Just as an example, I think this question I asked on SF has near-equal relevance on both sites.

I know a similar question was asked earlier, but I'd like to debate the merits of cross-posting on these two sites only, because of their overlap.

I think that over time a large number of questions will be duplicated over superuser.com and serverfault.com.

To cite an example, I'm investigating protocols to mount remote filesystems on linux with full locking capability (to configure NAS for my home network). I've looked at (and had questions on) Samba, NFS, SSHFS etc - server technologies used by power users as much as by network admins.

Is it immediately clear which site these questions should be directed towards ? If not, the same question is bound to be raised on both sites by different users (or even the same user).

Duplicate postings are already an issue on SO, why not nip it in the bud by designing for duplicate/cross-posting for SU and SF rather than trying to manage it later ?

Just as an example, I think this question I asked on SF has near-equal relevance on both sites.

I know a similar question was asked earlier, but I'd like to debate the merits of cross-posting on these two sites only, because of their overlap.