Panther Pre Release

[danbalsh]

What's the advantage of enabling journaling? Is that a factor in the new super fast searchs? I knew it was available before in one of the 10.2.x releases via a terminal command but that's it :blush:

Yeah i'd like to know that too, is it worth turning on?

[Wickedkitten Veteran]

What's the advantage of enabling journaling? Is that a factor in the new super fast searchs? I knew it was available before in one of the 10.2.x releases via a terminal command but that's it :blush:

i think its just the difference between it being on a pc like a ntfs partition vs fat32. it makes it easier to search for things and makes it easier to recover things if the OS coughs on you

[Dazzla Veteran]

Can't be bad then :D

[danbalsh]

Right ok thanks, will enable it now :)

[Cara Veteran]

i could have sworn i had already said that ta

;)

You know how it is WK, if you don't drill it into their heads a million and one times...

[usr.bin]

Yeah i'd like to know that too, is it worth turning on?

I've found a few links regaurding it. Nothing from Panther, but it's been implimented (as Dazzla said) in Jag, you just have to turn it on from the Terminal.

You can look here for it's intro, here to learn how to turn it on, here to see what the register has to say about it, and the Official Apple PDF is here.

[danbalsh]

Thanks macboi!!! :D

[usr.bin]

Thanks macboi!!! :D

n/p

I always like to try and attempt to outdo Wickedkitten. :laugh:

*Runs away before the ###### reads teh post*

[danbalsh]

n/p

I always like to try and attempt to outdo Wickedkitten.  :laugh:

*Runs away before the ###### reads teh post*

LMAO :laugh:

The Kitten has spy's everywhere....... she WILL find you :doctor:

Edited :blush:

[Cara Veteran]

WickedKitten is quite female danbalsh. ;)

[usr.bin]

n/p

I always like to try and attempt to outdo Wickedkitten.  :laugh:

*Runs away before the ###### reads teh post*

LMAO :laugh:

The Kitten has spy's everywhere....... he WILL find you :doctor:

Oh dear, you should probably edit that post to read "she" before she comes back online :whistle: :D

[danbalsh]

Edit what.... theres nothing to edit here..... come on move along... :p

[Wickedkitten Veteran]

at least you were right about the spies bit lol

[usr.bin]

Edit what.... theres nothing to edit here..... come on move along... :p

Fortunatly, she's having some issues with MSN again and I don't think she's been paying attention. ;)

Back on topic, have you noticed any performance gain after turning on Journaling?

[danbalsh]

darn ;)

hmmmm i'm gussing Cara would be one of them.... :shifty:

[the evn show]

Journaling moves harddisk disk writes to a transaction based method.

On a normal file system (fat32, hfs) when you say "write this to the disk" the harddrive will start writting the data to the platter - overwritting files as it goes (i am intentionally ignoring caching etc). Imagine you were writting an update to a critical part of the system and your system went down: you could lose everything on a disk or damage much data so you have to go and check the entire disk to make sure everything is okay.

On a trasaction based system (ntfs, reiserfs, hfs+) every write is first written as a transaction to a journal and then to the disk. The advantage is that if a disk goes down down while writting the system can reboot and not have to worry about losing everything:it can playback the journal and bring the system to a known state.

It won't stop you from loosing data but it will make the recovery from a disk write failure faster.

It's basicly a way of making your disk more reliable in the event of power outage. The performance hit is typically less than 10% for writting though no penalty for reads should be detectable (some say it makes it faster because the data is stored better on the disk - I don't believe them, but what do I know?)

I have journaling turned on for systems that spend most of their time unplugged because you never know what could go wrong. For systems that don't move I leave it turned off.

[danbalsh]

Fortunatly, she's having some issues with MSN again and I don't think she's been paying attention. ;)

Back on topic, have you noticed any performance gain after turning on Journaling?

Not as yet no, but I'm not doing anything intense yet... I'll give it a whirl in a min to see if anything has improved,

Although according to the links you gave me, it's more of a safety procedure than a performance enhancement.

[Wickedkitten Veteran]

darn ;)

hmmmm i'm gussing Cara would be one of them.... :shifty:

them? what them? you mean Them! like the movie or them what, I'm confused.

Macboi is my number one spy

[usr.bin]

darn ;)

hmmmm i'm gussing Cara would be one of them.... :shifty:

Not Cara, but someone who has participated in this thread recently :whistle:

Not giving out any names... :blush:

[Wickedkitten Veteran]

Journaling moves harddisk disk writes to a transaction based method.

On a normal file system (fat32, hfs) when you say "write this to the disk" the harddrive will start writting the data to the platter - overwritting files as it goes (i am intentionally ignoring caching etc). Imagine you were writting an update to a critical part of the system and your system went down: you could lose everything on a disk or damage much data so you have to go and check the entire disk to make sure everything is okay.

On a trasaction based system (ntfs, reiserfs, hfs+) every write is first written as a transaction to a journal and then to the disk. The advantage is that if a disk goes down down while writting the system can reboot and not have to worry about losing everything:it can playback the journal and bring the system to a known state.

It won't stop you from loosing data but it will make the recovery from a disk write failure faster.

It's basicly a way of making your disk more reliable in the event of power outage. The performance hit is typically less than 10% for writting though no penalty for reads should be detectable (some say it makes it faster because the data is stored better on the disk - I don't believe them, but what do I know?)

I have journaling turned on for systems that spend most of their time unplugged because you never know what could go wrong. For systems that don't move I leave it turned off.

have i mentioned lately I absolutely love your posts. I like the way you are always concise and articulate in your giving of information and leave little room for argument :D

[the evn show]

Tx. Old usenet habbit. I just stopped citing sources about a year ago: I finally realized that I'm not writting papers for classes so if people want to verify data they can hit google or something :)

[usr.bin]

Journaling moves harddisk disk writes to a transaction based method.

On a normal file system (fat32, hfs) when you say "write this to the disk" the harddrive will start writting the data to the platter - overwritting files as it goes (i am intentionally ignoring caching etc).  Imagine you were writting an update to a critical part of the system and your system went down: you could lose everything on a disk or damage much data so you have to go and check the entire disk to make sure everything is okay.

On a trasaction based system (ntfs, reiserfs, hfs+) every write is first written as a transaction to a journal and then to the disk.  The advantage is that if a disk goes down down while writting the system can reboot and not have to worry about losing everything:it can playback the journal and bring the system to a known state.

It won't stop you from loosing data but it will make the recovery from a disk write failure faster.

It's basicly a way of making your disk more reliable in the event of power outage.  The performance hit is typically less than 10% for writting though no penalty for reads should be detectable (some say it makes it faster because the data is stored better on the disk - I don't believe them, but what do I know?)

I have journaling turned on for systems that spend most of their time unplugged because you never know what could go wrong.  For systems that don't move  I leave it turned off.

have i mentioned lately I absolutely love your posts. I like the way you are always concise and articulate in your giving of information and leave little room for argument :D

Wicked just hates the fact that most of her posts inspire arguments. Actually, she probably likes that because she would argue with a wall if it would have it.

That's very informative tho. Nice and easy to understand.

[danbalsh]

Wicked just hates the fact that most of her posts inspire arguments.  Actually, she probably likes that because she would argue with a wall if it would have it.

That's very informative tho.  Nice and easy to understand.

You've so just started using SHE a lot since I messed up :cool:

[Wickedkitten Veteran]

Journaling moves harddisk disk writes to a transaction based method.

On a normal file system (fat32, hfs) when you say "write this to the disk" the harddrive will start writting the data to the platter - overwritting files as it goes (i am intentionally ignoring caching etc).  Imagine you were writting an update to a critical part of the system and your system went down: you could lose everything on a disk or damage much data so you have to go and check the entire disk to make sure everything is okay.

On a trasaction based system (ntfs, reiserfs, hfs+) every write is first written as a transaction to a journal and then to the disk.  The advantage is that if a disk goes down down while writting the system can reboot and not have to worry about losing everything:it can playback the journal and bring the system to a known state.

It won't stop you from loosing data but it will make the recovery from a disk write failure faster.

It's basicly a way of making your disk more reliable in the event of power outage.  The performance hit is typically less than 10% for writting though no penalty for reads should be detectable (some say it makes it faster because the data is stored better on the disk - I don't believe them, but what do I know?)

I have journaling turned on for systems that spend most of their time unplugged because you never know what could go wrong.  For systems that don't move  I leave it turned off.

have i mentioned lately I absolutely love your posts. I like the way you are always concise and articulate in your giving of information and leave little room for argument :D

Wicked just hates the fact that most of her posts inspire arguments. Actually, she probably likes that because she would argue with a wall if it would have it.

That's very informative tho. Nice and easy to understand. https://www.neowin.net/forum/html/emoticons...s/thumbs_up.gif

oi, get back on topic you. Post a screenshot of something.

Is it true that IE doesn't come installed in it at all?

[usr.bin]

Journaling moves harddisk disk writes to a transaction based method.

On a normal file system (fat32, hfs) when you say "write this to the disk" the harddrive will start writting the data to the platter - overwritting files as it goes (i am intentionally ignoring caching etc).? Imagine you were writting an update to a critical part of the system and your system went down: you could lose everything on a disk or damage much data so you have to go and check the entire disk to make sure everything is okay.

On a trasaction based system (ntfs, reiserfs, hfs+) every write is first written as a transaction to a journal and then to the disk.? The advantage is that if a disk goes down down while writting the system can reboot and not have to worry about losing everything:it can playback the journal and bring the system to a known state.

It won't stop you from loosing data but it will make the recovery from a disk write failure faster.

It's basicly a way of making your disk more reliable in the event of power outage.? The performance hit is typically less than 10% for writting though no penalty for reads should be detectable (some say it makes it faster because the data is stored better on the disk - I don't believe them, but what do I know?)

I have journaling turned on for systems that spend most of their time unplugged because you never know what could go wrong.? For systems that don't move? I leave it turned off.

have i mentioned lately I absolutely love your posts. I like the way you are always concise and articulate in your giving of information and leave little room for argum:Dt :D

Wicked just hates the fact that most of her posts inspire arguments. Actually, she probably likes that because she would argue with a wall if it would have it.

That's very informative tho. Nice and easy to understand. https://www.neowin.net/forum/html/emoticons...s/thumbs_up.gif

oi, get back on topic you. Post a screenshot of something.

Is it true that IE doesn't come installed in it at all?

No, because I didn't have that craptastic program on my system, I installed Panther, and there the bloody thing was. So, in the Dev Preview at least, it has I.E. installed.