Rob wrote:
> The only difference I've found is that in the RocketRAID BIOS, the 3
> 500GB drives are recognized with a Legacy Status, whereas the 1TB is
> recognized as New Status. Not sure what that means or how to
> change it.
Your "problem" is that the old drives you have hooked up to the
On Saturday 22 August 2009 21:11:01 Nerius Landys wrote:
> > I don't remember the original description, but any time I hear
> > about a 30 second "gap" during startup, I think of the well-known DNS
> > reverse look-up issue. Are you sure this is not the case here?
>
> Indeed, I have forgott
> I don't remember the original description, but any time I hear about
> a 30 second "gap" during startup, I think of the well-known DNS reverse
> look-up issue. Are you sure this is not the case here?
Indeed, I have forgotten to have the PTR record set up for my new IP address.
However t
Nerius Landys wrote:
I am still bambuzzled by the network taking 30 seconds to come up.
I don't remember the original description, but any time I hear about a
30 second "gap" during startup, I think of the well-known DNS reverse
look-up issue. Are you sure this is not the case here?
> calcru: runtime went backwards from 37332 usec to 16577
> usec for pid 47 (sh)...
Not to seem like I'm talking to myself, but I fixed this problem:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#CALCRU-NEGATIVE-RUNTIME
(Turn off Intel® Enhanced SpeedStep.)
I am still bam
One last question. I'm getting interesting [kernel?] messages during
bootup. You know, the kind that are highlighted white in the console.
The relevant lines of rc.conf look like this right now:
defaultrouter="64.156.192.1"
hostname="daffy.nerius.com"
ifconfig_em0="inet 64.156.192.169 netmask
Thanks for the script. I found the underlying problem on my system.
My server is at a data center and I don't know what kind of equipment
the server is connected to. It appears that it takes 30 seconds for
the networking to start. I added this script as
/etc/rc.d/waitfornetwork, and enabled it i
I have several jails running on my freebesd machine and lately it started to
crash when it gets a bit loaded. I followed the freebsd kernel debugging
manual, and got some output, but I have no idea what to do with it. The only
thing I think I understand of it that the bit that matters are just the
On Fri, 21 Aug 2009 21:37:09 -0700
Nerius Landys wrote:
> Then why
> can't I do a lookup right after named starts?
Possibly it's a delay in bind being ready or maybe you don't have any
network access - the latter is common with ppp.
> By the way, the underlying issue that I'm trying to address
Hello
Anybody knows how to install iwn-firmware on Freebsd 7.2 Stable?
(I need it for: Intel Wireless WiFi Link 4965AGN)
I do not have /usr/ports/net/iwn-firmware dir since it is only in 8.0.
Is a way to install it and use that firmware? I've searched alot on
Google, but I did not find a howto
Jeffrey Goldberg wrote:
On Aug 21, 2009, at 2:33 PM, John Almberg wrote:
I am currently using rsnapshot to back up these directories on a
FreeBSD 7.2 webserver:
/etc
/usr/home
/usr/local
/var/cron
Here is my exclude list from my rsnapshot.conf
exclude /var/log
exclude
On Sat, 22 Aug 2009, Joe Snikeris wrote:
> On Fri, Aug 21, 2009 at 11:53 PM, Ian Smith wrote:
> > On Fri, 21 Aug 2009, Joe Snikeris wrote:
> > > On Thu, Aug 20, 2009 at 10:58 PM, Ian Smith wrote:
[..]
> > > At any rate, I gave up on ACPI. I've got suspend-to-ram and
> > > suspend-to-disk (
John Francis Lee wrote:
> I got an answer to my question, posted here, from ... but I've been
> instructed not to post to individuals but to the list so I copy the
> Mak's response here :
>
>
> Your CPU is 64-bit from what I can see. From a bit of Googling, others
> have encountered this problem
On Fri, Aug 21, 2009 at 09:37:09PM -0700, Nerius Landys wrote:
> I am trying to figure out why DNS lookups are not possible right after
> the "named" process has been launched (during bootup).
At start, named sends a couple of queries to e.g. root servers. All
this requires the network connection
This question was asked a few weeks ago, but the original poster
must have had their questions amswered. As follow-ups offered
further assistance given more detail, I wonder if I could be so bold
as to provide that detail for my own circumstances.
I have six disks:
ad4 - 500MB
ad5 - 500MB
ad6
On Fri, Aug 21, 2009 at 11:53 PM, Ian Smith wrote:
> On Fri, 21 Aug 2009, Joe Snikeris wrote:
> > On Thu, Aug 20, 2009 at 10:58 PM, Ian Smith wrote:
> > > On Thu, 20 Aug 2009 14:03:29 -0500 Joe Snikeris
> wrote:
> > >
> > > > First off, I apologize if this is not the right forum for this
>
I got an answer to my question, posted here, from ... but I've been
instructed not to post to individuals but to the list so I copy the
Mak's response here :
Your CPU is 64-bit from what I can see. From a bit of Googling, others
have encountered this problem, and it seems to have to do with V
17 matches
Mail list logo