Looking at Longhorn
ShinyPlasticBag writes "Paul Thurrott has an excellent preview of Longhorn milestone five over at his Supersite for Windows. It looks like this may be Microsoft's equivalent to OS X -- the next version of Windows will have a 3D accelerated desktop and other graphical goodies. In addition to this, it will include a journaling file system, so us mere mortals can enjoy what Linux Geeks have had for years."
git with the program dude.
Here is a mirror.
I Didn't get a chance to fix the links to the images, so Here is the directory with a dump of them.
(And where is the Coward option?)
--sig fault--
Microsoft's equivalent to OS X...will include a journaling file system, so us mere mortals can enjoy what Linux Geeks have had for years."
And OS X users have had for months...
W
-------------------
This is my SIG. There are many like it, but this one is mine.
No journaling file system guarantees that any unsaved data will be preserved in the event of a system crash. Data that's in RAM in the disk write cache is lost in the event of a crash. That has nothing to do with the file system.
Journaling file systems are transaction based. If a transaction fails partway through (IE the system crashes) the state of the disk is the same as if the transaction had never started, and is thus always consistent.
You would have to be doing something extra weird to risk corrupting an entire ext2 volume in the event of a crash. Also the article doesn't mention that ext3 IS ext2 with a journal added, it's not a totally different file system. In fact an ext3 file system that is cleanly unmounted can be mounted as an ext2 file system, FYI.
-73, de n1ywb
www.n1ywb.com
NTFS was a journaling filesystem from the start; even before NT4 came out. It was a journaling filesystem before Reiserfs or EXT3 even had a single line of code written. You can set it up to fully journal the filesystem data as well (it only does metadata by default). It did change with NT 5, but the journaling capabilities still existed in prior versions. More documentation can be found here
The wheel is turning, but the hamster is dead.
Winmodems are designed to use M$ Windows system calls to offload processing power from the hardware to the CPU. Same with Winprinters. This is why they have "Win" in the name. Why the hell should there be a law against this? I can still buy any REAL modem and it will work flawlessly with Linux. If your hardware doesn't work with Linux, get hardware that does. Start checking the HCL before you go to Best Buy.
Everyone is entitled to their own opinion. It's just that yours is stupid.
The new big feature of the filesystem is not that it's journalling.
They are integrating the filesystem with their SQL engine so that files are easily searchable with the multiple GB hard drives everyone will have by the time 2005 rolls around. The big feature is that it's a database filesystem called WinFS.
I guess the submitters of the article don't even read the articles anymore! Gotta love the quip at the end of the summary--makes him look even more moronic. NTFS has been a journalling file system since its inception. Many years before ext3 reared its ugly head.
"Sufferin' succotash."
"3D accelerated desktop" is too easy to misinterpret. What's really going is that a lot of graphics tasks (compositing, mostly) are offloaded to the GPU. The real advantage to having the entire screen as a GL context means that tricks that used to be very processor-intensive are now ready for everyday use. OS X's use of transparency was a bit much for a 400Mhz G3, but a modern graphics card barely notices the load. The Terminal could use transparent windows since day 1, but with a significant performance hit; with QE that hit is gone and some people leave their windows transparent all the time. The genie effect used to take up 100% of pretty much every Mac's CPU, with the GPU handling the grunt work of the bitmap distortion there's enough power left over that DVDs actually keep playing while they are being genied. The full-screen zoom tool (for the visually impaired) uses bilinear filtering, and again with virtually zero performance hit - I use it to watch postage-stamp streaming movies embedded in web pages at full screen.
A 3D-accelerated desktop is just the logical next step after blitting acceleration from a 2D card.
if you peek around /etc/security/time.conf, PAM (which redhat uses at least) will manage access control for you that way.
Any application that uses PAM will automatically time-locked accordingly.
Why aren't you encrypting your e-mail?
Control Panel - Administrative Tools - Disk Management
Select the partition, right click on 'Change Drice Letter and Paths' , select 'Change' and you'll be presented with two option. One is to mount the drive as a traditional letter, the other as a directory.
That's just wrong on several levels.
First of all, the file system is not consistent after a crash: journaling file systems need to replay the journal in order to make it consistent. This is no different in principle from non-journaling file systems (which, traditionally, also have incorporated various features to permit recovery), it just happens to be faster.
Second, I/O APIs usually do not define a notion of "transaction" at the file system level, and even if they do, there aren't a whole lot of guarantees you can make that are particularly useful. In fact, journaling file systems and transaction-based file systems really are very different things. A journaling file system can be used to implement a transaction-based file system, but it can also be used just to implement fast recovery.
Third, for performance reasons, very few journaling file systems journal file content; they only worry about meta-data. And NTFS falls back a step further by making particularly weak guarantees. For example, if I create files "a", "b", and "c" in that sequence, with three separate programs, after a crash, any combination of those files may be present, and their content may be arbitrarily messed up.
So does ramfs. The difference between tmpfs and ramfs is that tmpfs is swappable, whereas ramfs is pinned in RAM. tmpfs is definititely the preferred choice for /tmp.
NTFS is a journaling file system, and Longhorn has a more advanced journaling file system that Linux can't not match. The new file system will classify files for you, from word document to mp3 files. You only need to type in keywords like "Picture taken in Feburary by John" it will show up a list of picture taken in Feburary by the name John. It is too powerful that Linux is still way behind.
Huh? Where did you get this?
As far as I know, Microsoft has NO plans on removing compatibility with older applications. I'm running Windows Server 2003, and I can still run Win16 apps as well as most DOS apps.
The parent is nothing but a troll. Yes, DRM in the OS is not a good thing. No, it will not have the profound impact that you think it will have. No one will stop you from running Linux on your computer.
DRM in the OS means very little. Application developers know that the adoption of a new OS is slow, and they will not do anything that would reduce their userbase.
kdm. Easy to configure, many useful options. You can even configure it to log you in automatically. Switch on your machine, go make coffee, come back, you're logged in and ready to start work, your previous session restored.
kuser can do this for you. Linux distributors often provide their own tools for this, for example SuSE, whose admin tools are handily integrated into the KDE Control Centre.
Play around with kicker, the KDE panel. It does most of the stuff that Longhorn thing does, plus lots more stuff which they haven't done.
I expect Gnome does some or all of these things too; I picked KDE because it's what I know.
Rik
Look here for one of several knowledgeable accounts of the history behind Microsoft's TCP/IP stack that are floating around the web.
Please be more careful before you declare that something has been proven.
I got it from here:
o rn
http://www.aaxnet.com/editor/edit029.html#longh
"Current Windows based software will not be compatible with the Longhorn filesystem".