I installed Apache 2.0.52 on my fresh reinstallation of FreeBSD 5.3, but
I can't figure out how the new rc.conf system works. How do I set
things up so I can start Apache in rc.conf? I installed Apache directly
from the downloaded source rather than from the ports, so this wasn't
done automatical
I started setting securelevel=3 at boot, and I notice that healthd
refuses to run, giving the message "InitMBInfo: Operation not permitted"
even from root. I assume this is because of the higher securelevel.
Is there a way to make healthd work with this higher level (assuming
that's the problem)?
Bill Moran writes:
BM>
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-rcng.html
BM>
BM> Unfortunatly, this document doesn't fully explain how /usr/local/etc/rc.d
BM> has changed, but it's a good start nonetheless. More can be gleaned
BM> by following the links to other ma
Joshua Lokken writes:
JL> I have apache2 working fine on FreeBSD 5.2.1-RELEASE-p13.
JL> In /etc/rc.conf I have a line that reads:
JL>
JL> apache2_enable="YES"
JL>
JL> and in /usr/local/etc/rc.d, I have:
JL>
JL> -rwxr-x--x 1 root wheel 183 Dec 28 13:55 000.apache2libs.sh
JL> -rwxr-x--x 1 root
Joshua Lokken writes:
JL> # cat /usr/local/etc/rc.d/000.apache2libs.sh
[...]
Thanks.
I couldn't get that to work, either. After trying several things, I
finally copied the moused script and modified that, and cooked up
something that seems to work. So I guess the problem is solved, even if
it
I'd like to run top on the system console to keep an eye on the system,
but I'd prefer not to have the console logged on to do so. Is there an
elegant way to do this?
I know I can start top and redirect output to /dev/console and detach it
from the current terminal with "top -s 3 >/dev/console &"
> How about creating a user like this with vipw:
> topper::userno:groupno::0:0:Topper Harley:/nonexistent:/usr/bin/top
> and then just logging in on spare console screen as topper?
>
> I'm not sure if there are security implications though, even if the user
> is not member of the wheel group etc.
Tom Vilot writes:
TV> I prefer to use just about any other tool (except, of course, for
TV> JSP/.NET, etc). Python, Perl, ... any other tool will do the jobs I
TV> need done and I can avoid the sluggishness of Java, the licensing
TV> ambiguities, and the dependence on a company that is *not* a
TV>
Reko Turja writes:
RT> Actually not command line options as such, but you can make a login
RT> class for the top user in /etc/login.conf and feed the options via TOP
RT> environment variable from there.
RT>
RT> You cant shell out from top and renicing from non root account is
RT> impossible (exce
Dick Davies writes:
DD> The phrase 'Java is the COBOL of the nineties' springs to mind
At least COBOL served a useful purpose (and still does).
--
Anthony
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/f
I had a very similar problem over the holidays. After a power failure
over a month ago, I noticed some anomalies in FreeBSD, but they were
very insidious and didn't seem like hardware (and the system was on a
UPS plus a surge protector, so I didn't think the PF alone could have
done damage, unless
Is there any kind of problem with syslogd and the -a option? I've tried
all sorts of variations (-a 10.0.0.x, -a 10.0.0.x/24, -a
myrouter.mydomain, -a myrouter.mydomain/24, etc.) and it just doesn't
seem to let anything through. Starting syslogd without any option works
(my router can write to the
Rob writes:
R> On 5.3, I have following in rc.conf:
R> syslogd_flags="-a 192.168.123.0/24 -b 192.168.123.254"
R>
R> on the machine that has IP 192.168.123.254.
R> It serves a cluster of 192.168.123.X with X = 1 to 7
R>
R> /etc/syslog.conf on the 192.168.123.X PCs has:
R>*.* @192.168.123.
Billy Newsom writes:
BN> ...and that's all I ever see. But while this is being printed to the
BN> screen, I get five beeps. I don't remember that many beeps in FreeBSD 4.x.
BN>
BN> BEEP, beep beep beep, BEEP
See http://bioscentral.com for a list of beep codes for many different
BIOS. Most BIOS
Robert Watson writes:
RW> All I know is that the XP bits don't crash every week, they crash every
RW> three weeks. :-) My NT4 box crashed almost continuously.
I have three machines, running FreeBSD, NT, and XP. All of them will
run until I boot them. They don't crash, or at least I can't reme
Mark writes:
M> Ah, this point fascinates me. Running for years? Do you ever have
M> to recompile your kernel? :)
Usually once when I first install the OS, then never again (unless I
change something in the hardware, which I hardly ever do). Windows
often has to be rebooted just to install a new
Robert Watson writes:
RW> The problems I have on the Windows XP platform appear to come from a
RW> lack of robustness in the face of nasty application failure.
A problem with the Windows environment as a whole is that applications
tend to assume that they have the entire machine to themselves, an
What's the safest and most elegant way to copy an entire directory tree
such that only newer files and directories are actually copied?
Essentially I have one directory that contains my test version of my Web
site, and another directory that contains the production version of the
site. Normally t
Giorgos Keramidas writes:
GK> cpio(1) does that by default ...
Looks like that's just what I need--thanks.
--
Anthony
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any
J65nko BSD writes:
JB> Have a look at "rsync" http://rsync.samba.org/ It is in ports ;)
I did look at it, but cpio seems to do what's required and it's already
on the system. Thanks anyway.
--
Anthony
___
freebsd-questions@freebsd.org mailing list
Chris writes:
C> Long uptimes = unsecured+unpatched boxes.
C> Long uptimes? No thanks.
Most vulnerabilities are in daemons or other programs outside the
kernel, so one need not necessarily boot the machine to fix them.
--
Anthony
___
freebsd-questio
Frank J. Laszlo writes:
FJL> Yahoo most likely runs some home-brewed version of FreeBSD. highly
FJL> customized for their needs.
Why do you say that?
--
Anthony
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
Olivier Nicole writes:
ON> Maybe for the same reason you should better not use a non-SMP kernel
ON> if you have 2 CPU in your box.
Is a hyperthreading CPU identical to a second CPU from the software's
standpoint? If not, what are the differences?
--
Anthony
__
Jonathan Chen writes:
JC> Not true on 5.3+ GENERIC systems. If you look at dmesg, you'll see the
JC> second virtual CPU launched as well as the extra column in top(1) if
JC> you enable HTT in the BIOS.
Well, now I'm confusing. I have an Asus P4P800-E Deluxe MB with an
Intel P4 processor mounted
Giorgos Keramidas writes:
GK> You need to enable SMP too, to allow the FreeBSD kernel to use the
GK> second (hyper-threaded) CPU.
I found it, in a file called SMP. Why is the SMP option tucked away in
a separate file?
I stuck this into the config and rebuilt the kernel. Seems to run fine.
I see
Scott Bennett writes:
SB> Well, no, not exactly. The dual-cored CPUs share certain resources
SB> on the chip that are not shared in a multi-CPU situation, and that sharing
SB> means certain operations have to be handled differently. An MP setup has
SB> separate cache and TLB managment in ea
Giorgos Keramidas writes:
GK> The 'separate file' is NOTES. This file is actually the complete
GK> reference of options that the kernel supports, so it's not like the SMP
GK> option is hidden or something.
I must have a magic special version of FreeBSD:
# cd /usr/src/sys/i386/conf
# grep SMP *
Andrea Venturoli writes:
AV> FWIW I tried numerical computations on a P4 with HT enabled: I expected
AV> using 2 threads might give *at least slightly* better results, but I
AV> could come to the conclusion that with 1, 2 or 4 threads the performance
AV> gain (or loss) was exactly zero.
Where the
Scott Bennett writes:
SB> I notice that the 5.2.1 boot messages refer to the second core as an
SB> AP, which I'm guessing stands for "attached processor". If that
SB> guess is correct, then it means that only the first core is able to
SB> perform certain functions, and the AP core has to get the f
Is there someplace where I can find definitions of the process states
that I see in the STATE column of top? RUN and CPU1 are easy enough
to figure out, but most of the rest are mysterious.
--
Anthony
___
freebsd-questions@freebsd.org mailing list
ht
Olivier Nicole writes:
ON> Not always true, I had a P4 1.5 die on me for lack of fan.
I understood that all recent Intel processors will first slow the clock
and then halt completely if the die temperature rises too much, but
there may be exceptions (or perhaps some processors run so hot that the
Subhro writes:
S> This *used* to be true. I am using a AMD64 3000+ and the idle
S> temperature is 28C. The room temp is around 12-14C. After asking this
S> kid to crunch FPs for over 16 hrs, the processor temperature rose to
S> only 38C. I am not using any special cooling gears, just the stock
S>
Andrea Venturoli writes:
AV> Not exactly the same algorithm and on different set of data.
But similar machine instructions, perhaps?
AV> Yes.
Just the contention for the FPU alone might have had the effect of
single-threading the workload. That plus the SMP overhead might give
you a zero or ne
Olivier Nicole writes:
ON> It was dead for good, well it is still dead as a matter of fact :)
The AMD processor on my XP system overheated and stalled a few times, before
I realized that the (brand-new) fan had failed. It still runs okay now,
though, with a reliable fan.
The other AMD processor
Colin J. Raven writes:
CJR> I always understood in FreeBSD that "Free Memory is wasted memory"
In any operating system, free memory is wasted memory. But if you
suddenly need more memory and you don't have it, system performance will
slide right down into the abyss, no matter which OS you are us
Andrea Venturoli writes:
AV> I've come to the same conclusion. Still I can't put this together with
AV> 100% load on both processors. If, as someone said, there is only one
AV> FPU, *how* are these figures coming out???
The operating system tracks a dispatch of a processor into a process
thread.
Boris Spirialitious writes:
BS> Oh, but I do understand! FreeBSD is not good choice for companies
BS> that need support for the latest hardware.
It's not a question of latest, it's a question of which hardware.
FreeBSD, like all operating systems, targets a broad but not universal
user base, and
Ramiro Aceves writes:
RA> So, why do we start always the war? The real war should be against the
RA> Bill Gates OSes, instead of fighting among us.
Professionals and serious amateurs in IT never wage "wars" at all.
--
Anthony
___
freebsd-questions@f
lord grinny writes:
lg> Don't they?? Then what are all the law suits about?
Business.
--
Anthony
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROT
Ramiro Aceves writes:
RA> I do not like to start wars among free OSes, I enjoy fighting the
RA> Bill OSes.
There are plenty of challenging video games on the market if you like to
fight.
RA> For me, making the war against Bill OSes means using Free Software
RA> OSes (Debian, Gentoo, FreeBSD.
[EMAIL PROTECTED] writes:
Fac> The entire point of this extended discussion, for those who have
Fac> paid attention, is that FreeBSD 4.x, which is admittedly the
Fac> fastest version available, DOES NOT work with intel's fastest CPUs
Fac> because it doesnt support the necessary chipsets ...
While
Len Zettel writes:
LZ> Better to expend resources on making 5.3 faster than 4.10 on all
LZ> chipsets or retrofit 4.10 to the new ones?
New OS versions should always provide either better functionality with
the same performance, or better performance with the same functionality.
Ideally they'd pro
John writes:
J> If you are running FreeBSD 5.x, you get the cool "L" option on
J> dump which will automatically snapshot the mounted filesystems.
What exactly is meant by a "snapshot," and how much extra disk space
does it require when dump runs? I've seen the warnings when I run dump
on a runni
Paul Schmehl writes:
PS> Not to pick a nit...well, ok...to pick a nit...developers do not
PS> support systems. Support organizations do. If you're going to be
PS> using FreeBSD in a corporate environment then you need to find a
PS> good *support* company that can backstop your local admins. *Then*
Xian writes:
X> I installed FreeBSD on a machine with an Athlon 3200 that I accident under
X> clocked to 1.4GHz. I didn't notice for quite a while as the performance was
X> amazing any way. It didn't half go some when I put the clock speed up to
X> 2.2GHz.
I think people nowadays forget how fast
Jorn Argelo writes:
JA> Either way, I never want another server OS again. This is great.
If I had to install a dozen more servers today, they would all get
FreeBSD. It makes extremely good use of whatever hardware you care to
give it. Indeed, FreeBSD can turn even junky old PCs into productive
[EMAIL PROTECTED] writes:
Fac> I think the "junky old PC" market is just what the current FreeBSD "team"
Fac> is targeting.
At least someone is thinking of it. There are a lot of PCs out there
that are still in perfect working order, but are too slow to run the
hugely bloated desktop operating s
faisal gillani writes:
fg> hmmm exactly right .. u know i have a 750MHz At halon
fg> with 256MB ram .. & still my processor is 80% idle
fg> most of the time ..
fg> i also have some windows server on my network but
fg> thats a compulsory rather then choice .
I'm gradually migrating legacy aps off
Jay O'Brien writes:
JOB> Thanks, but what I want to know is what risk I have with port 80,
JOB> and only port 80 open.
The risk depends on Apache, since that's the daemon answering the phone
when someone calls in on port 80.
Just make sure you're using the latest version of Apache (1.3.33, if y
Mike Jeays writes:
MJ> I presume you have tried changing the boot order in the BIOS settings?
MJ> You should be able to make the CD or floppy drive come ahead of the hard
MJ> disk in the boot sequence.
Yes, I've tried lots of stuff. It's a HP motherboard and apparently a
HP BIOS. I've tried all
Giorgos Keramidas writes:
GK> I've seen Windows machines "lose" CD-ROM or floppy drives, on perfectly
GK> working systems. You may find that booting the installation CD-ROM of
GK> some FreeBSD version locates the floppy drive just fine.
The problem is external to Windows. The machine won't even
Matthias Buelow writes:
MB> And where do you think would they "find" this "junk PC"?
The first world could send it to them, instead of throwing perfectly
good PCs into a landfill.
MB> Don't you think that's a bit condescending?
No, I think it's pretty realistic. Right now a lot of completely
u
Scott Bennett writes:
SB> The recent discussion in this thread causes me to wonder whether
SB> FreeBSD's performance on older, slower equipment could be a
SB> contributing factor to why hardware vendors like Dell and ATI are
SB> willing to provide only limited support for LINUX and none at all
SB>
Giorgos Keramidas writes:
GK> This is likely too. Floppies have mechanical moving parts that are
GK> more prone to failure than other pieces of hardware.
The eerie part is that the diskette drive worked find right up until the
moment where I tried to boot from it. Now it doesn't seem to work at
Colin J. Raven writes:
CJR> Eh? Surely you don't meant trashed - physically annihilated?
Absolutely. That's the only safe way to protect data. Any disk drive
with platters that are even remotely intact can still be read.
I have yet to throw away any disk drives for this reason (can't find a
co
Colin J. Raven writes:
CJR> I always thought that formatting/fdisk'ing twice completely erased
CJR> *permanently* whatever had been on the disc.
Information can be recovered from disks even after a dozen or more
overwrites. The data is never safe with the platters intact.
--
Anthony
Matthias Buelow writes:
MB> Wake up from your pipe dreams. Shipping decommissioned computers to the
MB> 3rd world is not going to solve any development problem.
It helps solve an environmental problem, though. And they need not be
shipped anywhere. It is sufficient to just continue using them,
Matthew Seaman writes:
MS> If your drive contains or once contained military secrets, then in the
MS> USA and probably anywhere in the West, standard disposal procedure is
MS> that the drive be completely overwritten with specific patterns of
MS> random data several times, and then taken to a secu
Erik Norgaard writes:
EN> Many larger companies have a fixed upgrading schedule, a pc lives 3
EN> years.
One must wonder why. After all, they don't rebuild their offices every
three years (although some seem to replace company cars fairly
quickly--but mostly due to wear and tear, I presume, whic
Pat Maddox writes:
> I forgot to give a bit of info. My local machine has the correct time
> of 10:05PM, and the server has the correct time of 11:05PM. If I send
> an email from a mail account on the server to gmail, it has the
> correct time. If I send an email from gmail back to the server,
John writes:
> I suppose I'm nit-picking here, but you would cron it rather than running it
> by hand.
It's mostly the space that I prefer not to part with.
> How much space have you got to play with?
About 2 GB total remaining on /usr. Just installing X stuff gobbled up
a few hundred megabyte
Dan Nelson writes:
> Try lowering the max tags for that drive: "camcontrol tags da0 -N 32".
Tried it. I still get the same error; it doesn't seem to have
diminished. I get the "queue full" stuff in bursts, then the process
trying to do the I/O stalls, then after 30-40 seconds I get one of those
Pat Maddox writes:
> I've included the headers of messages from both Gmail and Hotmail, to
> show that it's not on Gmail's end. Also, here's the output from date:
> %date
> Sun Feb 27 02:42:21 CET 2005
That can't be right. You sent your message in reply to a message I sent
at 9:34 CET. The tim
Ted Mittelstaedt writes:
> Cisco's online knowledgebase is far superior.
Since Cisco equipment is outside my budget, I've never had any occasion
to look at theirs, but I'll take your word for it. (Then again,
hopefully I wouldn't _need_ the knowledgebase if I had Cisco gear.)
--
Anthony
Pat Maddox writes:
> Alright, I got it all working now. Not sure how to change the time
> zone with config files, so I just used sysinstall to change it to MST
> (time zone is arbitrary, but since this is the zone I live in, it's
> convenient for me).
Well, no, time zone isn't arbitrary, it need
Ramiro Aceves writes:
> If you have 2 GB remaining in /usr, install the ports tree, it will eat
> about 350 MB.
I tried it. The system generates so many SCSI errors that it panics
before the entire tree is installed.
--
Anthony
___
freebsd-question
Leonard Zettel writes:
> My own experiences have given me a definite bias toward using the
> ports system to compile stuff to be added to my system rather than
> going with the binary packages. I get the impression that many
> port maintainers who are fairly careful about keeping their port
> ver
[EMAIL PROTECTED] writes:
> I have a question in regards to file recovery, to be precise, recovering
> an entire directory [with files] that may have been deleted/moved.
Just restore from backup.
--
Anthony
___
freebsd-questions@freebsd.org mailing
I've gotten two messages like the ones below today on my production server
(5.3-RELEASE):
messages:Feb 27 14:48:17 freebie kernel: ad10: TIMEOUT - WRITE_DMA retrying (2
retries left) LBA=4848803
messages:Feb 27 14:48:17 freebie kernel: ad10: FAILURE - WRITE_DMA timed out
What do these messages m
I get an e-mail like the following every eleven minutes on my test
system:
=
From [EMAIL PROTECTED] Sun Feb 27 16:55:00 2005
Date: Sun, 27 Feb 2005 16:55:00 +0100 (CET)
From: [EMAIL PROTECTED] (Cron Daemon)
To: [EMAIL PROTECTED]
Subj
[EMAIL PROTECTED] writes:
> Theoretically, one could use 'fsdb -r' in a scripted manner, to
> generate a mapping of file names to blocks (relative to the partition
> of the file system you are mapping). Once you have the blocks, you'll
> need to do so artithmetics to map those blocks to LBA addres
Roland Smith writes:
> The save-entropy script is being run from cron. See /etc/crontab. The first
> line of this script after the header begins with "# This". It looks like
> the hash mark was removed, and the shell is trying to find the "This"
> command and fails.
I checked both /usr/libexec/sa
David Fleck writes:
> As a wild guess, check to see that line 29 in /usr/libexec/save-entropy
> has a comment mark at the start of it:
>
> # This script is called by cron to store bits of randomness which are
It does. It looks identical to the same file on my production system.
The only differen
Roland Smith writes:
> Could it be that the cron output is mailed to someone else on the
> production machine?
I checked my aliases and stuff and sent some test messages to operator,
and they get through okay. Apparently it's not happening on my
production box, only on the test box.
> It works
David Fleck writes:
> Hmmm. Well, I don't know, but I'd try running the save-entropy script
> manually and see if you can recreate the message that way. If so, add a
> -x to the first line
>
>#!/bin/sh -x
>
> and run it manually again - you should be able to see what command
> precedes the
[EMAIL PROTECTED] writes:
> Actually, it's not that hard. You need three mappings:
>
> 1. (lba address, (filesystem, block #))
> 2. ((filesystem, block #), (filesystem, inode #))
> 3. ((filesystem, inode #), (list of filenames linking to inode #))
Seems like it would be straightforward with adequ
Mike Tancsa writes:
> Could be a bad sector on the drive, or bad cable. Hard to say. Try
> /usr/ports/sysutils/smartmontools/
>
> It can read all sorts of info off the drive and help you narrow down
> what the problem might be.
Wow! That is a very cool tool. There's even a Windows port so I ca
John writes:
> 1. you mentioned that you had the ports tree on another machine. Can you nfs
> mount it?
I pulled all the NFS stuff out of the kernel, alas!
> 2. As others have mentioned, firebird is a fast-moving target. You *need* a
> cvsupped ports in order to keep up with it. So why not insta
Chris Hodgins writes:
> It should be trivial to update your kernel config and rebuild and
> install the new kernel. Remember to reboot when you are done.
It's trivial in principle, but this is a production server. The golden
rule for production servers is never to change anything unless you hav
Chris Hodgins writes:
> Well if you are doing all this you will carry out the updates to your
> test machine first and validate everything works fine. Once you are
> happy build a package from it and add it to your production server. I
> am not sure how you would verify a package as big as firef
John writes:
> well, put it back in then :) You'd only need the client stuff on the
> small-harddrive machine of course. Is it also stripped out of the server?
Yes. I saw it as an unnecessary overhead and a security risk.
> I extended the usable lifetime of a p90 laptop like this. It was short
Chris writes:
> Hmmm, what exactly are Windows Updates?
Unnecessary.
--
Anthony
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Ted Mittelstaedt writes:
> One of the several techs that work for that company has your
> attitude. He's been burned a few times when he's installed patches
> that broke existing software at a customer.
>
> However, the customers that he cares for have the highest percentage
> of broken-into serv
Ted Mittelstaedt writes:
> Rule of thumb on IDE hard drives, if they show more than a few errors
> with a tool like smartmon, they need to be thrown in the garbage.
Seems prudent to me, but right now I don't have the budget to replace
this drive (yes, 40 GB IDE drives are cheap, but I don't have
Garance A Drosihn writes:
> First question: which SATA controller are you using?
The controller is built into the Asus P4P800-E motherboard, and is
based on the Intel ICH5R southbridge chipset. There's also a Promise
20378 RAID controller on board but I do NOT use it (disabled in BIOS).
> And w
Ted Mittelstaedt writes:
> I agree Ramiro, I've setup dozens and dozens of different SCSI setups,
> and I think that his problem is hardware, such as incorrect
> termination, a bad scsi cable, bad connectors on the cable, or an
> incompatible SCSI/disk combination (which is rare, but it does happe
Ramiro Aceves writes:
> Anthony, I understand your frustration. I think you should fix the SCSI
> problems before doing anything.
If I could find out what is causing them, I would. The only thing I
know right now is that it's not hardware.
--
Anthony
_
Ted Mittelstaedt writes:
> One word: ebay
I don't trust used equipment. You never know where it's been.
--
Anthony
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any m
Ruben de Groot writes:
> 1 Secure mode - the system immutable and system append-only flags may
>not be turned off; disks for mounted file systems, /dev/mem,
>/dev/kmem and /dev/io (if your platform has it) may not be opened
>for writing; kernel modules (see kld(4)) may
RacerX writes:
> The hardware has ran for over 8 years - you don't think that after 8 years
> its going to show wear and tear? I do/would.
It's not going to suddenly fail on the very day and hour that I install
FreeBSD.
> We as humans are not perfect - so that means the things we make can't be
>
Chris Hodgins writes:
> Sounds like the perfect time for them to go wrong. They have been doing
> the same thing for 8 years without problem.
They are still doing the same thing today. There is no additional
stress in changing operating systems.
> Suddenly you come along and give them a good o
John writes:
> Have you considered the possibility that windows just didn't
> report the error?
Yes. If that's true, and if no actual data loss is occurring, then I'm
not worried about the error ... although I'd like to know how to remove
the error messages, in that case.
FreeBSD actually stall
Chris writes:
> So - it "could" be it. Never dismiss anything when it comes to hardware.
> Even the littlest thing can cause the greatest catastrophes.
It's illogical to dismiss the extremely high probability of a software
bug or configuration error while embracing the extremely low probability
Robert Marella writes:
> Perhaps you could try a live CD. Knoppix or Freesbie and see if the
> trouble is gone.
This machine won't boot from a CD.
--
Anthony
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fr
Ted Mittelstaedt writes:
> But that was under NT I understand, using NT drivers, right?
Yes.
> I wouldn't put it past the NT driver author of your SCSI card, in an
> effort to avoid problems, to have written the NT driver so that ALL
> transactions on the SCSI bus are asynchronous.
I don't know
Ted Mittelstaedt writes:
> I have an Adaptec AAA-131 Ultra 2 card here that is just jumping up and
> down to prove you wrong.
This is an AIC7880. When you have one of those, let me know.
> However, I CAN tell you how to go about finding out what you need to
> change. Do you want to do this? I
Ted Mittelstaedt writes:
> Do you always buy new cars? New homes?
Yes. And new PCs.
> If you were tasked with going out and buying Windows server hardware
> and you had a maximum of $200 to spend, you would be pretty stupid to
> go down to Fry's and get one of their $199 on-sale computers when
Chris Hodgins writes:
> I might have missed it but I can't find any information about what SCSI
> errors you are receiving. Why don't you post the errors you are seeing
> and/or perhaps your dmesg output as well and maybe someone can help
> you. Without more information noone can do more than gu
Andrea Venturoli writes:
> Hello.
> On a 5.3 machine I'm getting the following log messages. It appears they
> started when I activated smartd from smartmontools. Now I disabled it,
> but I'd like to have some more insight.
> Any info?
I've been getting strange messages of similar character on my
Fafa Diliha Romanova writes:
> i didn't realize all my users had full access to my homedir!
They don't. They have read and execute access by default, but not
write.
I'll agree that it's probably not a good idea to default to this, but it
has been that way on UNIX for a long time.
--
Anthony
1 - 100 of 605 matches
Mail list logo
