So my question to the Slashdot masses: is this common? In my admittedly limited networking experience, it's been drilled into my head fairly well that not running a firewall is lazy (if not simply negligent), and to open the appropriate ports and call it a day. However, I've seen forum posts here and there with people admitting they run their clients without firewalls, believing that the firewall on their incoming internet connection is good enough, and that their client security will pick up the pieces. I'm curious how many real professionals do this, or if the forum posts I'm seeing (along with the vendor in question) are just a bunch of clowns.
Now, I realize Palm OS 4 software can be run on Palm OS 5, but I'm looking to use some of the 'newer' APIs. Also, I have the Wi-fi add-on card so I wanted to create something that uses it. I thought what I needed was PODS (Palm OS Development Suite) but not only I can't find it anywhere but also it seems it was deprecated during Palm OS's lifetime. It really doesn't help the fact that I'm a beginner, but I really want to give this platform some life. Any general tip, book, working link or even anecdotes related to all this will be greatly appreciated.
I'm curious what Slashdot readers would do if they were in a similar situation. Is there anything productive that could be done with these resources? Obviously something revenue generating is great, but even if there is something novel that could be done with these servers we would be interested in putting them to good use.
I have a maintenance window at about 5AM tomorrow. It's fairly simple — upgrade CentOS, remove a package, install a package, reboot. Downtime shouldn't be more than 5 minutes. While I don't think it would be wise to automate this window, I think with sufficient testing we might be able to automate future maintenance windows so I or someone else can sleep in. Aside from the benefit of getting a bit more sleep, automating this kind of thing means that it can be written, reviewed and tested well in advance. Of course, if something goes horribly wrong having a live body keeping watch is probably helpful. That said, we do have people on call 24/7 and they could probably respond capably in an emergency. Have any of you tried to do something like this? What's your experience been like?
Please post your editor and language of choice in the comments."
I've got more of other stuff lying around, including the manuals to run it. Loki Softs Tribes 2, Kohan, Rune, and the original Unreal Tournament for Linux have me itching too. :-)
I was wondering if it would be possible to do an old 2001ish setup of a Linux workstation on some modern super cheap, super small PC (Raspberry Pi? Mini USB PC?), install all the stuff and give it a spin. What problems should I expect? VESA and Soundblaster drivers I'd expect to work, but what's with the IDE HDD drivers? How well does vintage Linux software from 2003 play with todays cheap system-on-board MicroPCs? What's with the USB stuff? Wouldn't the install expect the IO devices hooked on legacy ports? Have you tried running 10-15 year old Linux setups on devices like these and what are your experiences? What do you recommend?
Then, last Saturday, our lives changed. Probably forever. In the hospital, where she was admitted earlier that week to keep an eye on the baby, the tumor ruptured a small vessel and started leaking blood into the tumor, which swelled up to twice its size. Then she, effectively, had a stroke from the excess blood in the brain stem. In a hurry, the baby was born through C-section (30 weeks and it's a boy — he's doing fine). Saturday night she had complex brain surgery, which lasted nine hours. They removed the blood and tumor that was pressing on the brain.
Last Sunday/Monday they slowly tried to wake her up. The CT scan shows all higher brain functions to work, but a small part of the brain stem shows no activity. She is locked-in, which is a terrible thing to witness since she has virtually no control of any part of her body. She can't breathe on her own, and the only things she can move, ever so slightly, are her lips, eyelids and eyes. And even that's not very steady. Blinking her eyes to answer questions tires her out enormously, as she seems to have to work hard to control those. The crowd on Slashdot is a group of people who have in-depth knowledge of a wide range of topics. I'm certainly not asking for pity here, but maybe you can help me with the following questions: Does anyone have any ideas on how to communicate better with her? Is there technology that could help? Like brain-wave readers or something? Does anyone have any ideas I haven't thought of regarding communication with her, or maybe even experience with it?"
What is the best way to construct a compelling story for upper management so they'll appreciate the hard work that an IT department does? They don't seem particularly impressed with functioning systems, because they expect functioning systems. The extensive effort to design and implement reliable systems has also made IT boring and dull. What types of summaries can you provide upper management to help them appreciate IT infrastructure and the money they spend on the services it provides?"
Unfortunately, while still theoretically possible, installing an alternative init system means doing without a number of useful, even essential system programs. By design, systemd appears to be a full-blown everything-including-the-kitchen-sink solution to the relatively simple problem of starting up a Unix-like system. Systemd, for example, is a hard-coded dependency for installing Network Manager, probably the most user-friendly way for a desktop Linux system to connect to a wireless or wired network. Just this week, I woke up to find out that systemd had become a dependency for running PolicyKit, the suite of programs responsible for user privileges and permissions in a typical Linux desktop.
I was able to replace Network Manager with connman, a lightweight program originally developed for mobile devices. But with systemd infecting even the PolicyKit framework, I find myself faced with a dilemma. Should I just let systemd take over my entire system, or should I retreat to my old terminal-based computing in the hope that the horde of the systemDead don't take over the Linux kernel itself?
What are your plans for working with or working around systemd? Are there any mainstream GNU/Linux distros that haven't adopted and have no plans of migrating to systemd? Or is migrating to one of the bigger BSD systems the better and more future-proof solution?"