Date: Sun, 10 Oct 1999 02:30:01 +0200 From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: Joss Roots <osiris2002@yahoo.com> Cc: Steve Doty <sdoty@jaxx.net>, freebsd-questions@freebsd.org Subject: Re: Internet Connection Speed - Followup Message-ID: <19991010023000.D38786@daemon.ninth-circle.org> In-Reply-To: <19991009162252.14822.rocketmail@web118.yahoomail.com> References: <19991009162252.14822.rocketmail@web118.yahoomail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On [19991009 20:00], Joss Roots (osiris2002@yahoo.com) wrote: >--- Steve Doty <sdoty@jaxx.net> wrote: >> > FreeBSD-4.0 Current >> Hmm I have not installed the 4.0 yet, still >> working with 3.2. You might be >> right and there is something up with this new >> version. >> Dunno. Don't install. FreeBSD-CURRENT is developer's material. >Well, I have tried this pathway before, and >decided not to go there anymore, the only logical >answer I'll get if I complain about the version, >everyone wil say ok, don't run 4.0-current its >for developers, and I really want to be -current, >if you know what I mean, although got hit No, I don't know what you mean. I can only guess you are influenced by either Microsoft or Linux that you actually think newer is better. This is your wake-up call. FreeBSD does NOT work like that. In fact I know people who used FreeBSD from its early days who still run 2.0.x machines for mission critical systems, patched and secured for any security holes discovered later, and whom are quite happy with it. >SEVERLY, some 4 months back, and ALL the hard >disks got fucked up because of some problems Messed up. >during saving into the filesystems, I did not >complain to anyone, I swallowed my mysery, forgot You swallowed your mysery? Good thing. You probably caused this upon yourself by a lack of knowledge since you insisted on running CURRENT. Do not do that. Stick with user friendly releases. CURRENT has been a breeze this year, but it has been known to be rough on those using it if they have little clue what to do in special cases when things go bad. >about TONS of software that were lost after very >long downloads, and reformatted about 15 Gigs, >patiently, quit using FreeBSD for few months, >then reinstalled version 3.1 -RELEASE, and at >that momnet there was a very stupid thing, the >machine swore NOT to connect AT ALL to the net, >always giving me very CRAZY error "All received >bytes had 7th bit unset" so I figured the system You probably misconfigured something. And if that was not the case you would have been wise to check out STABLE and see if there were any bugs present in 3.1-RELEASE after its release. >really is angry, so I decided to put up BACK my The system really is angry? I really don't know what you mean here. Computers do not live. They operate according to software. So either something internal in the OS must have been flakey or your configuration must have been. >Free BSD 4.0 -current, same one suspected to have >caused Major loss of data, Oh I forgot very Which have most likely been your own fault. I run one box here on CURRENT since 2.2.6 last year and have had only hardware problems due to a messed up SCSI termination. I now run a second CURRENT box on which I do most of my development. Neither one have lost data due to the system, except by my own stupidity. So I don't buy your line that you `suspected to have caused major loss of data' is due to the system. >important thing to say, that FreeBSD have some >problems with writing "or burning" (according to >your personal aggressiveness) on HP 8100 CD >writer, so I could not save my data really, and I >was hit real hard, but you know we always like to >keep fighting in this life aint we. FreeBSD provides the basic layers on which third/external party's applications can run which can thus use the underlying layer to accomplish certain tasks. cdrecord from the ports is such a tool, which will ``burn'' CD's by making using of the CAM sublayer. This project is based on volunteerwork. Instead of making this side remark, you could also try to ask around what it takes to get this drive to get fully recognised in the system so that you, and your peers can use it in new releases. You can do this, most of the time, by acquiring techincal information about the driver from the vendor, specsheets, timing tables and programmer's documentation come to mind, and let the appropriate programmers annex developers know of your driver and the documentation you have. This may all sound harsh or unkind, but I am merely trying to make you see that you obviously should not be using CURRENT. You still have a lot to learn with regard to a lot of things FreeBSD, which is fine, I started there myself and am willing to help people who start `down there' again [that is, the bottom of the ladder of FreeBSD, and related, knowledge, not status or anything associated]. One minor nit: could you please use proper capitalisation and punctuation? Your post was hard to read. Let this be a help, HAND, -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>; Network/Security Specialist BSD: Technical excellence at its best I know you have tried, to Feel... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991010023000.D38786>