3dinfluence's questions

I've always found it confusing on where to mount permanent non-standard filesystems in Linux. Such as a filesystem that contains company files which is shared out via Samba or NFS.

It's not something that the Filesystem Hierarchy Standard has really tackled that I have found. The latest version of the spec 2.3 adds /srv but at this point it doesn't look like many distro's have started defaulting to using this directory for services data. Traditionally most distro's have defaulted to /var for this so I'm not sure administrators will adopt that convention.

Out of habit I tend to mount these non-standard filesystems under /mnt but FHS states that this should be used for temporary mount points. But I've also seen administrators put additional mount points in /, in /home, in /var, and in /usr/local.

So I'm curious to what the consensus is here on where these filesystems should be mounted.

• What have you found has worked for you and your organization?
• Are there any published best-practices that cover this subject?

Anyone know if an equivalent of lspci exists for Windows?

lspci is a really nice Linux command to list all the device info on the pci bus. This tells you exactly what chipsets are present in video, network, and audio devices. Since companies like Dell allow you to choose from a couple of different network and video options it would really help when trying to figure out how the system you're working on is configured when the system is missing drivers.

We are looking at ways to help cut our costs and our T1 contract is up. We have run across a local company that offers a 2mbit WiFi Max solution that is considerably cheaper than a T1. They have a pretty standard SLA and references are all positive. But I can't help but think that the references are all hand selected for the positive comments.

• Are wireless options worth considering over traditional T1 services?
• Anyone have any good or bad experiences with them?
• Any compelling arguments in favor or against these type of services?

We currently run our email, web, and ftp sites locally via our T1.