Anton Aylward wrote:
Sorry -- its not. a 1TB file still takes 1TB out of the backing store whether it is on disk or memory.
Ah, another fringe case raises its head!
Nope.. another real-life case. But if you only think of yourself, you'll think everyone else is fringe. ---------------------
Or are you being ridiculous just for the sake of the argument?
This is the problem with current openSUSE -- it's being designed for laptops and handhelds. I'm talking about a server. And while 1TB would be large, 300-400GB would not be -- and that would still overwhelm any memory based tmp system. I'll grab snapshots of directories on client machines in windows using star (stores acls and extended attrs). I'll want to copy such a file to or from a server & client and unpack the results locally -- it's a way of quickly transferring / syncing, for example a roaming profile that's gotten too "out of sync" to trust to windows's normal profile sync operations. (happens quite frequently, BTW, so it's not a fringe case for those running servers that serve up user-home dirs via the net. I know I don't want to store the image on the remote machine, so no matter which direction, .. if I create the tar, it goes into tmp, then I can use 'scp xxx-> machine:xxx' -- or more likely cp xxx \\machine\root$\tmp (usually faster as it skips scp's encrption). \tmp is always guaranteed to be there -- and always writable by all users. That guarantee has been there longer than and has been more stable that the secondary /var/tmp. Again -- my "/var/ is on another partition. So when I first boot, or if var doesn't come up, /tmp would be used. If the machine is up, I know /tmp is there -- but /var/tmp -- it's on another partiton. Either way -- applications are told to use /tmp for short-term storage, and /var/tmp for long term. But short-term doesn't mean smaller than memory. Most of the issues -- like separate partitions and booting from the metal -- using custom compiled kernels for your system -- those are common practice in the enterprise model -- not so much in the portable model, where 1 disk is often it. SuSE's changes indicate a much stronger leaning toward portables. Most server admins would think nothing of their system using a custom kernel for their HW -- you want the best performance out of it possible. laptops & handhelds, portability is key -- ease of use -- dumbing down interfaces for non-computer users... and locking down the machines so users can't corrupted them with their own software and binaries -- they'll only be able to use stuff they buy from "the app store"... That's the direction suse's changes are going. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org