Subject: RE: Disappearing files.....[long, new case/infos]
From: BWS - Offwhite (brennan@offwhite.net)
Date: Tue Dec 05 2000 - 22:49:06 EST
There is still another route to consider. These machines may have a
security hole which has been compromized. Since nothing else seems to
explain it away this could be the case.
I do not mean to bash Linux because I know at times Linux can be a better
choice than FreeBSD, but I just do not trust Linux. My experiences with
Caldera, SuSE and RedHat were all bad and I gave them all a fair shake. I
actually purchased a copy of each to support the cause, then I reverted
back to FreeBSD and have bought several CD sets already.
FreeBSD may not have the nice tools for setting up a GUI interface and it
may require a bit of learning to start, but I find that in the long run my
sys admin duties are much less time consuming. I also find it performs
much better as a server. (your experiences may be different)
And after 2 years of trying 3 major Linux distros and several versions of
FreeBSD I have to say I would have to recommend using FreeBSD for server
applications. But then again, I have always heard the attitude Debian
developers have tends to be closer to that of the FreeBSD developers. If
you are to stay with Linux, Debian may be a solid choice. They seem to
choose stability over features. The other distros have become feature
happy, which is fine for a workstation.
As a Sys Admin, my most valued feature is stability. And I write this on
a FreeBSD server which has been up for 287 days in a row with Netatalk
running since day 1, no problems.
Brennan Stehling - web developer and sys admin
projects: www.greasydaemon.com | www.onmilwaukee.com | www.sncalumni.com
Choose your OS, but choose wisely.
On Wed, 6 Dec 2000, lists-mail wrote:
> BWS - Offwhite <brennan@offwhite.net> said:
>
> > Also, of the people who have had these problems, what OS is the Netatalk
> > server running on? What filesystem is on that server under Netatalk?
> >
> > I have using Netatalk (netatalk-1.4b2+asun-2.1.3) for over 2 years on top
> > of FreeBSD with the default ufs filesystem from FreeBSD 3.0 to 4.2. I
> > have not had experienced any of these problems.
> >
> > Perhaps there is some bug with a specific platforms which need some
> > attention. If we can isolate the potentially flawed situation the
> > developers could get it fixed.
> >
>
> My Freebsd boxes do not show this problem either, both have FBSD Filesystems
> under the netatalk shares. While they are not very busy, maybe 30 gb a year
> transfered, they also haven't needed a reboot ;^)
>
> Currently I am seeing this problem on two Linux boxes, both Slackware 7.0,
> both running ext2 file system. Kernel 2.2.13 with I believe
> netatalk-1.4b2+asun-2.1.3 (I sent that earlier)
>
> > As for OS9 being a problem, I am not so sure of that. Sure it has really
> > screwed up networking but you would think they would have AppleShare/IP
> > working properly.
> >
>
> Again, I experienced no problems until OS 9. My mileage obviously varies 8^(
>
> > But then again, I keep my Macs and all the Macs in the office updated with
> > the Software Update program which comes with OS9. I have seen updates for
> > the ethernet and various network utilities being updated since the release
> > of OS9.
> >
> > Try running the software update on all Macs on your network and see if
> > this problem with lost files continues. So far I have not read anything
> > about this from Apple, but I have much insentive to look as my Macs
> > seem to working quite well, with the required daily reboot of course.
>
> I am very leary of doing that, I've never trusted the OS companies to _know_
> what is best for me. After going from 9.02 to 9.04 I'd never trust them to
> give me a solid update again. 9.04 was very problematic for us with many
> crashes and lost data. We reverted back to 9.02 and have stayed there.
>
> Thanks, all good points to ponder. Anyone else seeing stable netatalk on BSD
> and losing files on ext2
>
>
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:32:44 EST