what's more, said firewall is turned off by default, even if it was turned on in your migrated tigger install. Block All Incoming Connections would be the simple choice for a single user, but then things rapidly go south. as i understand, apple is using an indeterminate black box rather than ipfw, so it doesn't configure by ipfw rules.
after a month plus of daily use with 12-15 open applications, i find spaces no more productive, and the zooming around tiring. when an unassigned application reverts to the space in which it was opened, it is a non-productive inconvenience. asking mac users to configure a time machine lan in terminal is heresy, i think apple will fix that soon. i have time machine up for the experiment, but it certainly eats disk. 1.4G a day here setting on a 500G disk which might last a year and i'm a lightweight. my raid is still intact, but were i on a single disk machine, or generated large amounts of input files, i would consider other solutions. better than nothing and remembering it took more than a year to get 10.4 straight. best...jf On Dec 8, 2007, at 7:17 PM, Lee Larson wrote: > While the article was certainly written as flame-bait, I do think > the Leopard was given its freedom a little early. I'm using it on > three different machines and it's not crashed on any of them, but > there are some rough edges. > > ? The firewall, as it installs right out of the box, is a joke. It > took me a couple of weeks to get back the security I had with Tiger > because the IPFW interface apparently doesn't work the way IPFW is > supposed to work and the controls in System Preferences are both > confusing and anemic. > > ? Spaces is the right idea, but they should have looked more closely > at other virtual desktops. I've been using Desktop Manager under > Tiger forever and the virtual desktops built into Gnome and KDE in > Linux for many years. None of them have the annoying interface > rigidness of Spaces. I never find myself suddenly whisked over to > another desktop in Linux or with Desktop Manager just because I > changed programs. In Spaces, it happens all the time, and no matter > how I jigger the settings, it keeps happening. The desktops should > be more tied to windows than applications. > > ? Why can't Time Machine be easily made to work over a local network? > > ? Apple's desktop sharing seems a lot more finicky than other VNC > implementations. It took me forever to connect to my office Mac from > home because I had to tweak routers and firewalls. Making a VNC > connection to the Linux machine in my office from my Mac at home was > easy.
