Pinky3 asks: "I recently started digitizing my reel-to-reel music tapes. Most are thirty to forty years old (the first was recorded in 1964). How confident are you that the music you are collecting today will still be playable in forty years? What strategies are you adopting to keep your music safe?"

torpor asks: "Has anyone on Slashdot ever stepped off of the grid? I don't just mean long yuppy vacations to pacified islands, but seriously gone from 'tech-dedicated' to 'doing my own thing in the middle of nowhere for a while'. It's that time of year again. I've killed my TV, and I'm finding myself looking for adventure and mayhem in distant quarters. Have any of you ever done this, and returned with interesting stories to tell?"

mr number two asks: "I live in the mountains and have poor GSM reception. I can buy an active repeater to boost signal strength in my home to good levels, but what I'd really like to do is have a private GSM picocell, such that at home I would be connected to my own PBX. Calls to my home phone number would ring through to my cell phone. I wouldn't have to worry about a home cordless phone (and 802.11 interference) and I'd have all my speed dialing / contacts info right there. There are many other benefits. Ignoring FCC licensing issues, is there a base station I can purchase which has a signalling interface that will interface to a small PBX?"

Now that we've seen what's in the pipe for the immediate future IGN is running an article hoping for the games of the future, and talking about novels, tv shows, and other properties that they'd like to see be made into games. From the article: "...while we at IGN are all for original, non-franchise titles--reference Katamari, Psychonauts, God of War, Spore--a lot of us have places in our hearts for certain TV shows, films, and books that made us all fuzzy with joy." What would you like to see be made into a game? Microsoft, if you are listening, I have two words for you: Shadowrun MMOG.

squared99 asks: "I have just delved into some research on a set up for very high traffic websites. I'm particularly interested in how many webservers would be needed at minimum and the type of technology powering them. Slashdot seemed like a good sample site to check out, so I went to Slashdot's technology FAQ to get a starting point. This setup seems to be from 2000, is most likely a bit out of date, and I'm assuming the same number of webservers would not be needed with current server technology. What would experts in the Slashdot community recommend as a required setup to handle Slashdot-like volumes, if they had to do it today using more current hardware? How many webservers could it be reduced to, while maintaining enough redundancy to keep serving pages, even under the heaviest of loads?"

Where's My CreditCard asks: "Recently There has been a large increase in the amount of press relating to identity theft and the related crimes. I have recently been subject to several fraudulent transactions on my credit card and debit card through the internet. It has been over a month and my bank is still stringing me along saying it will take up to 10 weeks to get my money back. What have other on Slashdot done in this type of situation. What is the best way to keep things moving forward?"

Tyrson asks: "I work at a university and we are looking to purchase new A/V carts. At the moment we have the plain and simple shelves-on-wheels and the nicer multimedia display carts. The simple carts are sturdy yet insecure and lack useful features. The display carts are secure and useful yet built from weaker materials that only last a few semesters. We are looking for A/V carts with useful features preferably built from metal or plastics. After googling it and making some phone calls I had found several good carts that were sadly upwards of $1,200 apiece. I don't expect them to be cheap, but $1,200 was a little to steep. Does Slashdot have some suggestions for us?"

bionic-john asks: "We are a relatively small shop running 11 point-to-point T-1's carrying both voice and data. It seems weekly we have an issue, and it takes SBC at least a day from notification to resolution. To my knowledge, they are the only game in Chicago since they control all the copper which resellers just resell. The data bit is easy -- DSL with VPN, but what about the voice and central voice-mail? I have spoken with other vendors offering pseudo-VOIP using a hardware layer between their CO and our voice-switch, but it seems like the technology is still in its infancy, is not fully tested, and it's still SBC copper out the door. The strange thing with all this is, that we have just as many PRI's, and probably 1/20th of our issues involve those. It's always the point-to-point. What am I missing? What can I do?"

miazmatic asks: "I am one of the tech managers for my high school's FM radio station. We have been using Rhythmbox on Debian to play music after hours when no one is broadcasting. However, it took some pretty ugly hacks to get it to transmit the station ID every hour. We are adding a 600GB RAID 0 VG to our PC (P4 2.4/512MB), to which we plan to encode all our CDs losslessly. Along with this upgrade I would also like to find a permanent solution for broadcasting the station ID hourly. Has anyone used Linux to run a radio station before? Can anyone suggest a F/OSS software package or solution? Any help is appreciated."

Bob Bobbinson asks: "I'm currently looking to convert my workplace's CVS repository over to Subversion. The main issue I'm having at the moment before I can commence a roll-out is how we are currently using tags, and sticky tags. The project is a website and we have two tags which are used to put changes from the main trunk live (internally, and externally). All development is committed to the main branch, and when we want a change to go live we move the two 'live' tags to that current version. The live servers are both sticky tagged to these tags, so when we run an update on these servers they will only update to the version that the 'live' tags refer to. Currently I haven't found a satisfactory way to replicate this in Subversion, as moving tags, and updating on separate servers seems to be quite kludgy i.e. need to remove current tagged version from tag, then copy from the main branch over to the tag, then update this on the live server. So I'm trying to look for an alternative way to implement this staggered releasing of code live, and maintaining the ability to see what versions of files constitute what is live. Any ideas?"