On Wednesday, June 6, 2012 8:36:04 PM UTC-5, Mark Felder wrote:
Hi guys I'm excitedly posting this from my phone. Good news for you guys, bad
news for us -- we were building HA storage on vmware for a client and can now
replicate the crash on demand. I'll be posting details when I get home to
On Mon, 01 Oct 2012 15:00:40 -0500, guy.hel...@gmail.com wrote:
Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): WRITE(10). CDB: 2a 0 5
ee 60 16 0 1 0 0
Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): CAM status: SCSI
Status Error
Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): SCSI
Hi guys I'm excitedly posting this from my phone. Good news for you guys, bad
news for us -- we were building HA storage on vmware for a client and can now
replicate the crash on demand. I'll be posting details when I get home to my PC
tonight, but this hopefully is enough to replicate the
On Wednesday, May 30, 2012 3:56:02 pm Mark Felder wrote:
On Wed, 30 May 2012 12:17:07 -0500, John Baldwin j...@freebsd.org wrote:
Humm, can you test it with 2 CPUs?
We primarily only run with 1 CPU. We have seen it crash on multiple CPU
VMs. Also, Dane Foster appeared to have been
So when this hang happens, there never is a real panic. It just sits in a
state which I describe as like being in a deadlock. How would I go about
getting a crashdump if it never panics? Is it possible to do the dump over
a network or something because I don't believe it can write through
On Thursday, May 31, 2012 11:11:11 am Mark Felder wrote:
So when this hang happens, there never is a real panic. It just sits in a
state which I describe as like being in a deadlock. How would I go about
getting a crashdump if it never panics? Is it possible to do the dump over
a network
On Thursday, May 24, 2012 9:47:46 am Mark Felder wrote:
On Wed, 23 May 2012 17:30:40 -0500, Adrian Chadd adr...@freebsd.org
wrote:
Hi,
can you please, -please- file a PR? And place all of the above
information in it so we don't lose it?
I'd be glad to post a PR and assist in
On Wed, 30 May 2012 10:06:13 -0500, John Baldwin j...@freebsd.org wrote:
Do you only have one CPU in this VM? If not, do you know which threads
the other CPUs were running (e.g. do you have ps7.png, etc.)?
correct, only one CPU in the VM
___
On Wed, 30 May 2012 12:17:07 -0500, John Baldwin j...@freebsd.org wrote:
Humm, can you test it with 2 CPUs?
We primarily only run with 1 CPU. We have seen it crash on multiple CPU
VMs. Also, Dane Foster appeared to have been using multiple CPUs in his
video transcoding VMs.
On Wed, 23 May 2012 17:30:40 -0500, Adrian Chadd adr...@freebsd.org
wrote:
Hi,
can you please, -please- file a PR? And place all of the above
information in it so we don't lose it?
I'd be glad to post a PR and assist in helping to get it permanently
fixed. I certainly don't want this
Hey all,
On 25/05/2012, at 1:47 AM, Mark Felder wrote:
On Wed, 23 May 2012 17:30:40 -0500, Adrian Chadd adr...@freebsd.org wrote:
Hi,
can you please, -please- file a PR? And place all of the above
information in it so we don't lose it?
I'd be glad to post a PR and assist in helping
On 24. May 2012, at 13:47 , Mark Felder wrote:
On Wed, 23 May 2012 17:30:40 -0500, Adrian Chadd adr...@freebsd.org wrote:
Hi,
can you please, -please- file a PR? And place all of the above
information in it so we don't lose it?
I'd be glad to post a PR and assist in helping to get
Hi,
You guys now absolutely, positively have enough information for a PR.
It's still not clear whether it's a device/interrupt layer issue in
FreeBSD, or whether vmware is doing something wrong with how it
implements shared interrupts, or a bit of both..
Adrian
On 24 May 2012 13:54, dane
Hi,
can you please, -please- file a PR? And place all of the above
information in it so we don't lose it?
If this is indeed the problem then I really think we should root cause
why the driver and/or interrupt handling code is getting angry with
the shared interrupt.
I'd also appreciate it if
OK guys I've been talking with another user who can recreate this crash
and the last bit of information we've learned seems to be leaning towards
interrupts/IRQ issues like someone (bz@ perhaps?) suggested.
I'm still trying to test this myself, but the other user was able to
recreate my
On May 21, 2012, at 12:41 PM, Mark Felder wrote:
OK guys I've been talking with another user who can recreate this crash and
the last bit of information we've learned seems to be leaning towards
interrupts/IRQ issues like someone (bz@ perhaps?) suggested.
I'm still trying to test this
On Mon, 21 May 2012 12:01:19 -0500, Andrew Boyer abo...@averesystems.com
wrote:
You could try switching mpt to MSI. MSI interrupts are never shared.
Add this to /boot/device.hints:
hint.mpt.0.msi_enable=1
Currently implementing this on the known crashy servers. I've been looking
Mark Felder wrote:
OK guys I've been talking with another user who can recreate this crash
and the last bit of information we've learned seems to be leaning towards
interrupts/IRQ issues like someone (bz@ perhaps?) suggested.
I'm still trying to test this myself, but the other user was able
On Mon, 21 May 2012 13:47:45 -0500, Michael Powell
nightre...@hotmail.com wrote:
Very curious how 'irq 22 at device 22.0' and 'dev.mpt.0.%location:
slot=22'
all match with a '22'.
Strangely here in ESXi that doesn't work the same. Emulated BIOS must be
considerably different... :/
$
Quick update:
I have received word last night that this crash has been consistently
happening to someone on FreeBSD 9 and they're looking for more ideas. I
changed the following 41 days ago:
- Video memory to auto if it wasn't already
- SCSI controller changed from LSI Logic Parallel to
Guys,
The crash on my machine with debugging has evaded me for a few days. I'm
still looking for further suggestions of things I should grab from the DDB
when it happens again.
Thanks for the help everyone!
___
freebsd-questions@freebsd.org
On 4/2/2012 3:59 PM, Joe Greco wrote:
On 4/2/2012 11:43 AM, Joe Greco wrote:
As a user, you can't win. If you don't report
a problem, you get criticized. If you report a problem but can't figure
out how to reproduce it, you get criticized. If you can reproduce it
but you don't submit a
On 03/30/2012 07:41, Joe Greco wrote:
On 3/29/2012 7:01 AM, Joe Greco wrote:
On 3/28/2012 1:59 PM, Mark Felder wrote:
FreeBSD 8-STABLE, 8.3, and 9.0 are untested
As much as I'm sensitive to your production requirements, realistically
it's not likely that you'll get a helpful result without
On 03/30/2012 07:41, Joe Greco wrote:
On 3/29/2012 7:01 AM, Joe Greco wrote:
On 3/28/2012 1:59 PM, Mark Felder wrote:
FreeBSD 8-STABLE, 8.3, and 9.0 are untested
As much as I'm sensitive to your production requirements, realistically
it's not likely that you'll get a helpful result
On 4/2/2012 11:43 AM, Joe Greco wrote:
As a user, you can't win. If you don't report
a problem, you get criticized. If you report a problem but can't figure
out how to reproduce it, you get criticized. If you can reproduce it
but you don't submit a workaround, you get criticized. If you
On 4/2/2012 11:43 AM, Joe Greco wrote:
As a user, you can't win. If you don't report
a problem, you get criticized. If you report a problem but can't figure
out how to reproduce it, you get criticized. If you can reproduce it
but you don't submit a workaround, you get criticized. If
On 3/29/2012 7:01 AM, Joe Greco wrote:
On 3/28/2012 1:59 PM, Mark Felder wrote:
FreeBSD 8-STABLE, 8.3, and 9.0 are untested
As much as I'm sensitive to your production requirements, realistically
it's not likely that you'll get a helpful result without testing a newer
version. 8.2
On Thu, 29 Mar 2012 19:27:31 -0500, Joe Greco jgr...@ns.sol.net wrote:
It also doesn't explain the experience here, where one VM basically
crapped out but only after a migration - and then stayed crapped out.
It would be interesting to hear about your datastore, how busy it is,
what
On 3/28/2012 1:59 PM, Mark Felder wrote:
FreeBSD 8-STABLE, 8.3, and 9.0 are untested
As much as I'm sensitive to your production requirements, realistically
it's not likely that you'll get a helpful result without testing a newer
version. 8.2 came out over a year ago, many many things have
Mark Felder wrote:
Alright guys, I'm at the end of my rope here. For those that haven't seen
my previous emails here's the (not so) quick breakdown:
Overview:
FreeBSD ?? - 7.4 never crash
FreeBSD 8.0 - 8.2 crashes
FreeBSD 8-STABLE, 8.3, and 9.0 are untested (Sorry, not possible in our
On Wed, 28 Mar 2012 18:31:38 -0500, Adrian Chadd adr...@freebsd.org
wrote:
* have you filed a PR?
No
* is the crash easily reproducable?
Unfortunately not. It's totally random. Some servers will get the bug
and crash daily, some will crash weekly, some might seem to be fine but 3
On Thu, 29 Mar 2012 02:36:49 -0500, Doug Barton do...@freebsd.org wrote:
As much as I'm sensitive to your production requirements, realistically
it's not likely that you'll get a helpful result without testing a newer
version. 8.2 came out over a year ago, many many things have changed
since
Thank you for the suggestion. We'll put it in our toolbox and see if it
helps!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
Alright, new data. It happened to crash about 10 minutes after I came in
this morning and I ran some stuff in the DDB. I have no idea what
information is useful, but perhaps someone will see something out of the
ordinary?
http://feld.me/freebsd/esx_crash/
Thanks...
Hi,
* have you filed a PR?
* is the crash easily reproducable?
* are you able to boot some ramdisk-only FreeBSD-8.2 images (eg create
a ramdisk image using nanobsd?) and do some stress testing inside
that?
It sounds like you've established it's a storage issue, or at least
interrupt
On Thursday 29 March 2012 15:42:42 Joe Greco wrote:
Hi,
Do both 32- and 64-bit versions of FreeBSD crash?
--HPS
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail
On 3/28/2012 1:59 PM, Mark Felder wrote:
FreeBSD 8-STABLE, 8.3, and 9.0 are untested
As much as I'm sensitive to your production requirements, realistically
it's not likely that you'll get a helpful result without testing a newer
version. 8.2 came out over a year ago, many many things have
On Thu, 29 Mar 2012 09:58:16 -0500, Hans Petter Selasky hsela...@c2i.net
wrote:
Do both 32- and 64-bit versions of FreeBSD crash?
Correct, we see both i386 and amd64 flavors crash in the same way.
___
freebsd-questions@freebsd.org mailing list
At 16:03 29/03/2012, you wrote:
Alright, new data. It happened to crash about 10 minutes after I came in
this morning and I ran some stuff in the DDB. I have no idea what
information is useful, but perhaps someone will see something out of the
ordinary?
http://feld.me/freebsd/esx_crash/
On Thursday 29 March 2012 15:42:42 Joe Greco wrote:
Hi,
Do both 32- and 64-bit versions of FreeBSD crash?
We've only seen it happen on one virtual machine. That was a 32-bit
version. And it's not so much a crash as it is a disk I/O hang.
The fact that it was happening regularly to that
On Thursday 29 March 2012 17:49:30 Joe Greco wrote:
On Thursday 29 March 2012 15:42:42 Joe Greco wrote:
Hi,
Do both 32- and 64-bit versions of FreeBSD crash?
We've only seen it happen on one virtual machine. That was a 32-bit
version. And it's not so much a crash as it is a disk
On Thu, 29 Mar 2012 10:31:24 -0500, Eduardo Morras nec...@retena.com
wrote:
Don't know about ESXi but on others VM Managers i can change the chipset
emulation from ICH10 to ICH4. Can you change it to an older chipset too?
Unfortunately there's no setting in the GUI for that but I'll keep
On Thu, 29 Mar 2012 10:55:36 -0500, Hans Petter Selasky hsela...@c2i.net
wrote:
It almost sounds like the lost interrupt issue I've seen with USB EHCI
devices, though disk I/O should have a retry timeout?
What does wmstat -i output?
--HPS
Here's a server that has a week uptime and is due
On Thu, 29 Mar 2012 10:49:30 -0500, Joe Greco jgr...@ns.sol.net wrote:
I explained it at the time to one of my VMware friends:
This is 100% identical to what we see, Joe! And we're so unlucky that we
have this happen on probably a dozen servers, but a handful are the really
bad ones.
This sounds just like a race condition that happens under Windows 7 on
this laptop. The race condition, as far as I can tell involves heavy
disk access and heavy network access, and usually leaves the drive light
on, while all activity monitors (alldisk, allcpu, allnetwork) are still
active,
On Thu, Mar 29, 2012 at 11:27 AM, Mark Felder f...@feld.me wrote:
On Thu, 29 Mar 2012 10:55:36 -0500, Hans Petter Selasky hsela...@c2i.net
wrote:
It almost sounds like the lost interrupt issue I've seen with USB EHCI
devices, though disk I/O should have a retry timeout?
What does wmstat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/29/2012 07:03, Mark Felder wrote:
Alright, new data. It happened to crash about 10 minutes after I
came in this morning and I ran some stuff in the DDB. I have no
idea what information is useful, but perhaps someone will see
something out of
On Thu, 29 Mar 2012 11:43:45 -0500
Jim Bryant articulated:
Mark Felder wrote:
Alright guys, I'm at the end of my rope here. For those that
haven't seen my previous emails here's the (not so) quick breakdown:
Overview:
FreeBSD ?? - 7.4 never crash
FreeBSD 8.0 - 8.2 crashes
FreeBSD
On Thu, 29 Mar 2012 12:05:30 -0500, Mark Atkinson atkin...@gmail.com
wrote:
If this is an interrupt problem with disk i/o, then you might want to
look into (DDB(4))
show intr
show intrcount
maybe
show allrman
Thank you! I really don't know what things we should be running in DDB to
On Thu, 29 Mar 2012 12:24:30 -0500, je...@seibercom.net wrote:
I just started reading this tread, but I am wondering if I missed
something here. What does this have to do with Windows 7?
I emailed him off-list but I'm guessing he thought this was on VMWare
Workstation or another product
On Thu, 29 Mar 2012 11:53:02 -0500, Alan Cox alan.l@gmail.com wrote:
Not so long ago, VMware implemented a clever scheme for reducing the
overhead of virtualized interrupts that must be delivered by at least
some
(if not all) of their emulated storage controllers:
On Thursday 29 March 2012 17:49:30 Joe Greco wrote:
On Thursday 29 March 2012 15:42:42 Joe Greco wrote:
Hi,
Do both 32- and 64-bit versions of FreeBSD crash?
We've only seen it happen on one virtual machine. That was a 32-bit
version. And it's not so much a crash as it is
On Thu, Mar 29, 2012 at 1:22 PM, Mark Felder f...@feld.me wrote:
If we assume mpt is the culprit
Doesn't VMWare offer different types of emulated disk controllers? If so,
that might be the easiest way to narrow the field. Another thing maybe to
try would be to backport the mpt
Also, it's
On Thu, 29 Mar 2012 15:53:52 -0500, Adam Vande More
amvandem...@gmail.com wrote:
Doesn't VMWare offer different types of emulated disk controllers? If
so,
that might be the easiest way to narrow the field. Another thing maybe
to
try would be to backport the mpt
Yes, they offer
On 3/29/2012 7:01 AM, Joe Greco wrote:
On 3/28/2012 1:59 PM, Mark Felder wrote:
FreeBSD 8-STABLE, 8.3, and 9.0 are untested
As much as I'm sensitive to your production requirements, realistically
it's not likely that you'll get a helpful result without testing a newer
version. 8.2 came out
And then there is this one with similar symptoms and a workaround:
http://forums.freebsd.org/showthread.php?t=3D27899
I'm now investigating those loader.conf options. I have my crashy machine
set to use them on next boot so we'll see if it crashes now that I'm using
LSI SAS emulated
On Thu, 29 Mar 2012 19:27:31 -0500, Joe Greco jgr...@ns.sol.net wrote:
It also doesn't explain the experience here, where one VM basically
crapped out but only after a migration - and then stayed crapped out.
It would be interesting to hear about your datastore, how busy it is,
what technology,
On 28/03/2012 22:59, Mark Felder wrote:
Alright guys, I'm at the end of my rope here. For those that haven't
seen my previous emails here's the (not so) quick breakdown:
Overview:
FreeBSD ?? - 7.4 never crash
FreeBSD 8.0 - 8.2 crashes
FreeBSD 8-STABLE, 8.3, and 9.0 are untested (Sorry, not
Again, it's starting to sound like an interrupt handling issue which
may or may not be limited to the storage device.
You'll have to engage someone who knows those device drivers and
likely have them add some debugging to the driver which can be easily
flipped on (via binaries in a ramdisk - very
Hi,
* have you filed a PR?
* is the crash easily reproducable?
* are you able to boot some ramdisk-only FreeBSD-8.2 images (eg create
a ramdisk image using nanobsd?) and do some stress testing inside
that?
It sounds like you've established it's a storage issue, or at least
interrupt handling for
On Wed, Jan 20, 2010 at 01:10:48PM +0630, komyo gyi wrote:
hi,
yesterday i have modify squid.conf file.i have use vi editior.but i
cannot delete in text message. following error ^? appear.How to do it?.
please help me.
Looks like you're hitting the Delete key. That's not a valid vi
Dan Nelson wrote:
Junior Hacker Project: add an instantaneous-CPU value (calculated by
subtracting successive ki_runtime values) to the list of things top
calculates and toggle it and weighted-CPU when pressing C. The toggling
code is already there; it just toggles between two different
2009/11/3 Chris Stankevitz cstankev...@toyon.com:
Dan Nelson wrote:
Junior Hacker Project: add an instantaneous-CPU value (calculated by
subtracting successive ki_runtime values) to the list of things top
calculates and toggle it and weighted-CPU when pressing C. The toggling
code is
In the last episode (Nov 02), Chris Stankevitz said:
I recently performed a CPU intensive task with Xorg. When I completed the
task and Xorg no longer was using the CPU, I got this result from top:
===
last pid: 1201; load averages: 0.24, 0.10, 0.09up 0+00:29:42
63 processes: 1
Am Mittwoch, den 19.08.2009, 07:59 + schrieb
freebsd-questions-requ...@freebsd.org:
On Tue, Aug 18, 2009 at 01:45:27PM -0400, Karl Vogel wrote:
On Mon, 17 Aug 2009 17:23:29 -0700,
Walt Pawley w...@wump.org said:
W As speculation on my part, perhaps the six character limitation
On Wed, 19 Aug 2009 12:22:11 +0200, Heiner Strauß heiner...@yahoo.de wrote:
Didn't need lower case at this time. REAL PROGRAMMERS USED FORTRAN
http://www.pbm.com/~lindahl/real.programmers.html
When you're there, don't miss The story about Mel. By the
way... we have a Mel on our mailing
On Mon, 17 Aug 2009 17:23:29 -0700 Walt Pawley w...@wump.org
At 4:44 PM +0200 8/17/09, Heiner Strauß wrote:
[..]
Putting the symbol names in one word helped the linker / loader a lot.
Live was so easy.
Heiner
C(one word = 32 bit) .NOT. (some word processor software)
As
On Mon, 17 Aug 2009 17:23:29 -0700,
Walt Pawley w...@wump.org said:
W As speculation on my part, perhaps the six character limitation is less
W a software issue than an early architecture issue - DEC's PDP-6/10
W design used 36-bit words and packed six characters (clearly from a
W limited
On Tue, Aug 18, 2009 at 01:45:27PM -0400, Karl Vogel wrote:
On Mon, 17 Aug 2009 17:23:29 -0700,
Walt Pawley w...@wump.org said:
W As speculation on my part, perhaps the six character limitation is less
W a software issue than an early architecture issue - DEC's PDP-6/10
W design used
On Sun, 16 Aug 2009 10:28:01 -0700, George Davidovich free...@optimis.net
wrote:
Sorry, but while I agree the MICROS~1 pejorative can be a bit juvenile
and uncalled for, your assertion that 8.3 filenames are a thing of the
past is incorrect.
Furthermore, I think it wasn't a gain of comfort
Hi,
On 17 August 2009 pm 16:25:29 Polytropon wrote:
On Sun, 16 Aug 2009 10:28:01 -0700, George Davidovich
free...@optimis.net wrote:
Sorry, but while I agree the MICROS~1 pejorative can be a bit
juvenile and uncalled for, your assertion that 8.3 filenames
are a thing of the past is
On Mon, Aug 17, 2009 at 10:25:29AM +0200, Polytropon wrote:
By the way, where did I read that #define macro names have to
be unique within the first 6 (six) letters? :-)
The 6 letters limit was actually a restriction of earlier linkers and
it affected all identifiers of linkable objects like
Hi,
On 17 August 2009 pm 18:09:06 cpghost wrote:
On Mon, Aug 17, 2009 at 10:25:29AM +0200, Polytropon wrote:
By the way, where did I read that #define macro names have to
be unique within the first 6 (six) letters? :-)
The 6 letters limit was actually a restriction of earlier
linkers and
On Mon, Aug 17, 2009 at 06:18:45PM +0800, Erich Dollansky wrote:
On 17 August 2009 pm 18:09:06 cpghost wrote:
On Mon, Aug 17, 2009 at 10:25:29AM +0200, Polytropon wrote:
By the way, where did I read that #define macro names have to
be unique within the first 6 (six) letters? :-)
The 6
On Mon, Aug 17, 2009 at 06:18:45PM +0800, Erich Dollansky wrote:
On 17 August 2009 pm 18:09:06 cpghost wrote:
On Mon, Aug 17, 2009 at 10:25:29AM +0200, Polytropon wrote:
By the way, where did I read that #define macro names have to
be unique within the first 6 (six) letters? :-)
At 4:44 PM +0200 8/17/09, Heiner Strauß wrote:
On Mon, Aug 17, 2009 at 06:18:45PM +0800, Erich Dollansky wrote:
On 17 August 2009 pm 18:09:06 cpghost wrote:
On Mon, Aug 17, 2009 at 10:25:29AM +0200, Polytropon wrote:
By the way, where did I read that #define macro names have to
be
The average Windows user does not read what's on the screen anyway, so
he will always next. :-)
I get the humor, but based on this and your previous remarks regarding
Windows, you're not an authority on Windows or its users - average or
otherwise.
It does FreeBSD a disservice when its
On Sun, 16 Aug 2009 11:54:41 -0400, Charles Oppermann chuc...@gmail.com
wrote:
I get the humor, but based on this and your previous remarks regarding
Windows, you're not an authority on Windows or its users - average or
otherwise.
I may apologize for that not being the case, sadly, at least
On Sun, Aug 16, 2009 at 11:54:41AM -0400, Charles Oppermann wrote:
I assume your use of MICROS~1 is some sort of clever dig at
Microsoft, but this is 2009 - not 1995
Sorry, but while I agree the MICROS~1 pejorative can be a bit juvenile
and uncalled for, your assertion that 8.3 filenames are
It does FreeBSD a disservice when its supporters slam other platforms and
implicitly (and explicitly on occasion) denigrate users of such.
I agree only insofar as nobody is ever benefited by
insulting/denigrating other users. But that's not what Polytropon was
doing, I don't think. Seems to me
On Mon, Aug 10, 2009 at 01:00:31PM -0700, Raisa Brokhshtut typed:
Hello,
?
My old desktop has FreeBSD that I have never used. One of the friends of my
son installed it long ago, but no one used that PC since then. Now I want to
get rid of this program and to install Windows.?Every time when
Hi,
Am Montag, 10. Aug 2009, 13:00:31 -0700 schrieb Raisa Brokhshtut:
My old desktop has FreeBSD that I have never used. [...] Now I
want to get rid of this program and to install Windows.
Anyway, I would greatly appreciate if you would guide me how to
uninstall that program. [...] So I
Bertram Scharpf wrote:
Hi,
Am Montag, 10. Aug 2009, 13:00:31 -0700 schrieb Raisa Brokhshtut:
My old desktop has FreeBSD that I have never used. [...] Now I
want to get rid of this program and to install Windows.
Anyway, I would greatly appreciate if you would guide me how to
uninstall
Are you suggesting that continuous reinstalling of a program numerous
times until it works is a Windows-only tactic?
Bad software exists on every platform, in proportion to the platform's
installed base.
To the Original Poster: The easiest way to remove FreeBSD and get back
to a Windows
On Wed, 12 Aug 2009 10:32:20 -0400, Charles Oppermann chuc...@gmail.com
wrote:
Correct, and counter to another posters statement that Windows attempts to
wipe entire disks when installing. Yes, that's the default choice, which is
perfectly reasonable, but no Windows Setup will erase entire
Raisa Brokhshtut wrote:
My old desktop has FreeBSD that I have never used. One of the friends of my son
installed it long ago, but no one used that PC since then. Now I want to get
rid of this program and to install Windows. Every time when I boot this PC it
prompts for a user login which I
On Mon, Aug 10, 2009 at 3:00 PM, Raisa Brokhshtutqap...@yahoo.com wrote:
Hello,
My old desktop has FreeBSD that I have never used. One of the friends of my
son installed it long ago, but no one used that PC since then. Now I want to
get rid of this program and to install Windows. Every time
Raisa Brokhshtut wrote:
Hello,
My old desktop has FreeBSD that I have never used. One of the friends of my son installed it long ago, but no one used that PC since then. Now I want to get rid of this program and to install Windows. Every time when I boot this PC it prompts for a user login
On Mon, 10 Aug 2009 13:00:31 -0700 (PDT), Raisa Brokhshtut qap...@yahoo.com
wrote:
Anyway, I would greatly appreciate if you would guide me how to uninstall
that program.
FreeBSD is not a program, it's an operating system.
I don't have windows reskue cd.
You don't need it, but you need
My old desktop has FreeBSD that I have never used. One of the friends of my
son installed it long ago, but no one used that PC since then. Now I want to
get rid of this program and to install Windows. Every time when I boot this
PC it prompts for a user login which I don't know. This guy
On Mon, Feb 16, 2009 at 08:15:41AM +0330, Ali Reza wrote:
Hi i am Install FreeBsd 7.1 in to Detacetad Server
where Are Support Cpanel Whm .. ?
Please Answer Me ...
cPanel and WHM are commercial products:
http://www.cpanel.net/products/cpwhm/cpanel11/index.html
Apparently, they also
2008/3/7, Preston Hagar [EMAIL PROTECTED]:
It looks like you already have your problem solved. One utility you
might want to look at is pftop. With it, you can see pretty much in
real time what is going through pf and what is being blocked. This
has helped me a lot to find out which rule
On Thu, Mar 6, 2008 at 12:02 PM, Alaor Barroso de Carvalho Neto
[EMAIL PROTECTED] wrote:
2008/3/6, Erik Norgaard [EMAIL PROTECTED]:
I know my config is far away from a good config but it's the first time I
configure an firewall, and I have only basic english knowledge, I'm not
totally sure
Alaor Barroso de Carvalho Neto wrote:
nat on $ext_if from $internal_nets to any - ($ext_if)
nat on $cefet_if from $adm_net to any - ($cefet_if)
rdr on $all_if proto tcp from any to any port $proxy_ports \
- 127.0.0.1 port 3128
OK, so do these nat rules actually take effect? Which one?
2008/3/6, Erik Norgaard [EMAIL PROTECTED]:
You can add log statements to your nat rules to see which is applied.
pass quick proto icmp from any to any keep state
pass quick from $adm_net to $cefet_servers keep state
pass quick from $cefet_servers to $adm_net keep state
It appears that
On Thursday 07 February 2008 15:29:29 Mel wrote:
On Tuesday 05 February 2008 04:14:39 Andrew Falanga wrote:
I know it's probably near impossible to know exactly how much longer this
drive has, but how serious are these errors? As I mentioned, the
unreadable sectors on the hard drive are
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Mel
Sent: Thursday, February 07, 2008 2:29 PM
To: freebsd-questions@freebsd.org
Cc: Andrew Falanga
Subject: Re: Please help in diagnosing these smartmon messages
Since it's a church disk, you might
On Thu, Feb 07, 2008 at 11:29:29PM +0100, Mel wrote:
On Tuesday 05 February 2008 04:14:39 Andrew Falanga wrote:
I know it's probably near impossible to know exactly how much longer this
drive has, but how serious are these errors? As I mentioned, the
unreadable sectors on the hard drive
On Feb 7, 2008 3:38 PM, Jerry McAllister [EMAIL PROTECTED] wrote:
On Thu, Feb 07, 2008 at 11:29:29PM +0100, Mel wrote:
On Tuesday 05 February 2008 04:14:39 Andrew Falanga wrote:
I know it's probably near impossible to know exactly how much longer
this
drive has, but how serious are
On Tuesday 05 February 2008 04:14:39 Andrew Falanga wrote:
I know it's probably near impossible to know exactly how much longer this
drive has, but how serious are these errors? As I mentioned, the
unreadable sectors on the hard drive are repeated many times in the log (
100 times).
If
1 - 100 of 237 matches
Mail list logo
