fsck and filesystem errors

[Derick Centeno]

Hi Paul:

Part of what makes this list so accessible is that we each have a turn 
at experiencing a ... duh ... moment.  Many who participate here report 
what worked and what didn't, and more.  Although other sites may have 
more copious information, here a sort of communal drive towards mastery 
appears to exist.  This is rather interesting as most efforts in 
education are individual requiring individual development.  There 
appears to be an element within the community comprising this list to do 
things differently, such that it appears that the community rises or 
progresses together with the individuals who are learning and who are 
learned.  This is something very special and unique to this community.

Regarding OS X and ext3:  One interesting difference between OX 3 and 
Linux is that journaling can be turned off and on as often as one 
pleases.  This is not the case, as far as I know with ext3.  I think 
that the interdependent relationships for the ext3 structure is more 
involved.  As I intimated earlier you may be ahead of me; I'll also have 
to refer to the Linux Documentation Project link I provided earlier for 
more information.

Good Luck and I look forward to learning more of your progress!

Derick.
------------------------------------------------------------------------

Paul Higgins wrote:
> Thanks for your help on this; I'll report back to the list on how things went 
> with the disk repairs.  The info that I got from the automatic fsck done at 
> boot time suggested a problem with only one file, so hopefully not much else 
> is wrong.  I obviously wasn't thinking too clearly when I sent that message 
> re: repairing a boot drive without booting from the CD...duh.
>
> Re: OS X vs. ext3 and journaling filesystems, I know that since OS 10.3, X has 
> used a journaling filesystem similar to ext3.  You're right about the amount 
> of hand-holding that goes on in OS X; while going with FreeBSD is the best 
> decision Apple ever made, there are some things about it that really drive me 
> crazy.  I find Linux to be a much more powerful OS, though there are one or 
> two things about it that drive me crazy as well (e.g. not being able to 
> automount flash drives).  YDL running the KDE desktop to me seems like the 
> best compromise between the two.  (I like Gnome as well, but I find it a bit 
> too rigid in the way it makes me work; KDE seems a lot more like OS X to me).
>
> -PRH
>
> P.S.  It was estimated somewhere that about 90% of OS X is GPL/BSD code, but 
> as far as I'm aware, Apple's software falls under several licenses.  Most of 
> the Unix stuff is BSD-licensed and can be downloaded free from Apple.  Of 
> course, things like their window manager are closed-source.
>
> On Saturday 16 September 2006 05:23, Derick Centeno wrote:
>   
>> Hi Paul:
>>
>> I don't use that version of YDL however, the instructions are pretty
>> clear.  You can try to see if it works using the 1st install CD of YDL
>> 4.0 and proceed from there.
>>
>> The whole point of using a repair tool like fsck is to use it on the
>> drive you want repaired, not on the same drive the tool is running
>> from.  Think about it.  This also holds true for any OS whether it be
>> Windows, Macs or something else.  Just to extend the discussion a tiny
>> bit, this is why Micromat developed the eDrive concept which is
>> essentially a tiny partition with the requisite software so that the
>> partition with OS X can be safely repaired from this eDrive -- a rather
>> nice trick.  However with YDL also on the same drive that means I've got
>> three different partitions OS X, the eDrive, and YDL; it took a lot of
>> thinking to figure out the proper partition structures allowing them to
>> share one drive.
>> There is no manual for that I'm afraid.
>>
>> Anyway don't get confused regarding what OS X can do with journaling and
>> ext3.  Referring to details of the formatting theory behind these
>> concepts is a bit of a challenge and definitely not light reading but as
>> you've gotten this far you might as well go farther and do the
>> research.  I'm right behind ya buddy, and should review the same
>> material myself!  I just don't intend to do that kind of reading right now!
>>
>> Linux, or any other OS, has tools which need to be mastered by
>> independent minded persons -- like ourselves -- who want to do things
>> our own way.  You can't get much more your own way, than open source.
>> Sadly, as attractive as OS X is; it is too seductive in that nearly
>> anyone can become too comfortable in being supported by the OS and
>> forgetting that it is in fact a tool in the same way that the keyboard
>> is a tool.  And like any tool one should be familiar with it's guts so
>> that one builds what one wants!  Of course, Apple's design is
>> intentionally structured to make you forget that ... the computer is
>> your buddy, your friend, and for some people ... well, you get the idea.
>>
>> YDL is a tool for you.  Yours.  Mine.  Completely.  YDL is completely
>> open and available for minute study, research and review.  OS X is only
>> somewhat open even though officially it's license is defined as
>> equivalent to the GPL (this is still a point of argument for some).
>> Apple can remove the source of OS X and make it unavailable at any
>> time.  I believe YDL is a special, high quality Linux; it shares with
>> all other Linux that ALL it's source is available -- all the time.  No
>> need to ask permission to see it!  So let's take advantage of that fact
>> and dig in!
>> Take charge --- own it!
>>
>> I believe Picard (a character of the Enterprise universe) would
>> encourage and challenge us if he was our instructor with the phrase,
>> "dare to make it so!"
>>
>> Good Luck...
>>     
>
> _______________________________________________
> yellowdog-newbie mailing list
> yellowdog-newbie at lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie
>
>