date:20081006

On Mon, Oct 06, 2008 at 06:07:17AM +, dhaneshk k wrote:
 People ;
 I installed freebsd-7.0  in a p4 machine , after installation when I reboot 
 the machine , I am getting the message 
 acpi_tz0: _TMP value is absurd ignored (-269.7C)   in every 3 seconds ..
 intel p4 3.0 GHz 
 Intel 82915G  (915G GMCH )
  
 How can i get rid off this ... can someone shed some light on this regard ..

You posted this mail 3 days ago; I'm not sure why you're re-posting it.

This question should go to the freebsd-acpi list, not freebsd-questions,
as the problem is ACPI-related.  (I am not subscribed to freebsd-acpi).

A BIOS upgrade might fix the problem.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: How to generate password hashes for vipw and chpass

2008-10-06 Thread Ivan Rambius Ivanov

Hello Adam,

On Mon, Oct 6, 2008 at 8:40 AM, Adam Zaleski [EMAIL PROTECTED] wrote:
 Ivan Rambius Ivanov pisze:

 # /sbin/md5 -s newpassword
 and then I passed the output to chpass. I tried to use the new
 password for the next login but it failed - so I believe this is
 wrong.
 Can you please show me how to generate the password hashes?

 You can add new account with one command like this:

 echo user_password |pw user add new_user -h0

 Also if you only want to generate valid password hash
 you can use 'openssl passwd -1 new_password'
Thank you, this is the command I was looking for.

Regards
Ivan

-- 
Tangra Mega Rock: http://www.radiotangra.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

USB mouse problems

I have one Razer Lachesis USB mouse attached to the rear usb ports of my
pc. This mouse has never worked, however when I plug in another USB
mouse in the front of my pc it works?! I wonder; how do I get the Razer
Lachesis working without plugging it in the front?

Furthermore I wondered if there is a way to use both the mouse in a
terminal (gpm) and in xorg?


-- 
Regards,

Aniruddha




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: pf vs. RST attack question

2008-10-06 Thread Matthew Seaman


Jeremy Chadwick wrote:

On Sun, Oct 05, 2008 at 12:53:03PM -0500, Scott Bennett wrote:

 I'm getting a lot of messages like this:

Oct  4 14:30:00 hellas kernel: Limiting closed port RST response from 250 to 
200 packets/sec

Is there some rule I can insert into /etc/pf.conf to reject these apparently
invalid RST packets before they can bother TCP?  At the same time, I do not
want to reject legitimate RST packets.


They're outbound RST packets coming from your box as a result of
incoming packets someone is sending you (possibly an attack).

Proper firewalling rules should help defeat this, but there is no magic
rule you can place into pf.conf that will stop this.

If you want a magic solution, see blackhole(4).



block drop all

looks fairly magical to me.  Stick that at the top of your ruleset as
your default policy, add more specific rules beneath it to allow
the traffic you do want to pass, and Robert is your Mother's Brother.
No more floods of RST packets.

(Actually, I'd recommend always adding a 'log' clause to any rules that
drop packets like so: 'block log drop all'.  Makes running 'tcpdump -i pflog0'
an invaluable debugging aid.)

Cheers,

Matthew

--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: pf vs. RST attack question

On Mon, Oct 06, 2008 at 08:19:09AM +0100, Matthew Seaman wrote:
 Jeremy Chadwick wrote:
 On Sun, Oct 05, 2008 at 12:53:03PM -0500, Scott Bennett wrote:
  I'm getting a lot of messages like this:

 Oct  4 14:30:00 hellas kernel: Limiting closed port RST response from 250 
 to 200 packets/sec

 Is there some rule I can insert into /etc/pf.conf to reject these apparently
 invalid RST packets before they can bother TCP?  At the same time, I do not
 want to reject legitimate RST packets.

 They're outbound RST packets coming from your box as a result of
 incoming packets someone is sending you (possibly an attack).

 Proper firewalling rules should help defeat this, but there is no magic
 rule you can place into pf.conf that will stop this.

 If you want a magic solution, see blackhole(4).


 block drop all

 looks fairly magical to me.  Stick that at the top of your ruleset as
 your default policy, add more specific rules beneath it to allow
 the traffic you do want to pass, and Robert is your Mother's Brother.
 No more floods of RST packets.

This is incredibly draconian.  :-)  I was trying my best to remain
realistic.

 (Actually, I'd recommend always adding a 'log' clause to any rules that
 drop packets like so: 'block log drop all'.  Makes running 'tcpdump -i pflog0'
 an invaluable debugging aid.)

I cannot advocate use of log on such vague rules, and my attitude is
based on experience:

We had log set on some of our deny rules, specifically on an entry
which blocked any traffic to an IP to any ports other than 53 (DNS).
Someone initiated an attack against that IP, to a destination port of
something other than 53, which caused pflog to go crazy with logging.

What inadvertently resulted was a local system DoS -- the system began
sporting a load average between 40 and 50, and was sluggish.

The root cause?  /var/log/pflog was growing at such a tremendous rate
that newsyslog (trying to rotate and compress the logs) could not keep
up.  When I got to it, I found 8 or 9 gzip/newsyslog processes running
trying to deal with the chaos.

Bottom line: be very, very cautious what rules you use log on, and be
sure to remove it once the system is in production.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: pf vs. RST attack question

2008-10-06 Thread Matthew Seaman


Jeremy Chadwick wrote:

On Mon, Oct 06, 2008 at 08:19:09AM +0100, Matthew Seaman wrote:

Jeremy Chadwick wrote:




If you want a magic solution, see blackhole(4).


block drop all

looks fairly magical to me.  Stick that at the top of your ruleset as
your default policy, add more specific rules beneath it to allow
the traffic you do want to pass, and Robert is your Mother's Brother.
No more floods of RST packets.


This is incredibly draconian.  :-)  I was trying my best to remain
realistic.


It's no such thing.  This is the recommended standard practice when designing
firewalls: always start from the premise that all traffic will be dropped by
default and add specific exceptions to allow the traffic you want.  Trying to
work the other way round is a recipe for disaster: 'allow everything, but block
what is then shown to be deleterious' means that you're always playing catch-up
as changes on your servers expose new attack vectors and as attackers discover
and try to exploit those holes.  Not recommended, unless you actually /like/
being paged in the wee small hours.


(Actually, I'd recommend always adding a 'log' clause to any rules that
drop packets like so: 'block log drop all'.  Makes running 'tcpdump -i pflog0'
an invaluable debugging aid.)


I cannot advocate use of log on such vague rules, and my attitude is
based on experience:

We had log set on some of our deny rules, specifically on an entry
which blocked any traffic to an IP to any ports other than 53 (DNS).
Someone initiated an attack against that IP, to a destination port of
something other than 53, which caused pflog to go crazy with logging.

What inadvertently resulted was a local system DoS -- the system began
sporting a load average between 40 and 50, and was sluggish.

The root cause?  /var/log/pflog was growing at such a tremendous rate
that newsyslog (trying to rotate and compress the logs) could not keep
up.  When I got to it, I found 8 or 9 gzip/newsyslog processes running
trying to deal with the chaos.

Bottom line: be very, very cautious what rules you use log on, and be
sure to remove it once the system is in production.



You have a point here, I will certainly admit that.  In my experience, I've not
yet run into that scenario.  I've tended to see systems more easily DoSed by
running out of pf states due to excessive DoS traffic to allowed ports than to
any extra load from pflogd and newsyslog from logging denied traffic.  The
machines in question already log so much legitimate traffic from Squid and 
Apache
that pflog is trivial by comparison.  Of course, now I've said 'it never 
happens'
I'm expecting half our firewalls to explode any minute now...

Cheers,

Matthew

--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: Touch screen ETT on Clevo tn120r

2008-10-06 Thread Da Rock


On Sun, 2008-10-05 at 14:59 -0300, Sdävtaker wrote:
 Hello,
 I installed FreeBSD 7.0r in a Clevo tablet.
 I works great, but i am missing the touchscreen.
 Did someone make it work or got any idea where can i start to try?
 I got the pciconf -lv and scanpci -v info:
 Thanks in advance for any help you can give me.

Check your usb connections- copy the info here as with the pci stuff you
sent. Most of these types of features are connected via usb.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

The disc in your drive looks more like an Audio CD than a FreeBSD release

2008-10-06 Thread kiffin.gish

Hi there.

I tried to install 7.1-BETA from the CD I burned from 7.1-BETA-i386-disc1.iso, 
but after I created all the partitions etc and then selected to install, I get 
the following error message:

The disc in your drive looks more like an Audio CD than a FreeBSD release

Any idea what's wrong?

-- 
Kiffin Gish [EMAIL PROTECTED] 
Gouda, The Netherlands

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: pf vs. RST attack question

On Mon, 6 Oct 2008 02:07:04 -0700, Jeremy Chadwick [EMAIL PROTECTED] wrote:
 This is incredibly draconian.  :-)  I was trying my best to remain
 realistic.

 It's no such thing.  This is the recommended standard practice when
 designing firewalls: always start from the premise that all traffic
 will be dropped by default and add specific exceptions to allow the
 traffic you want.  [...]

 What I mean by 'draconian': block drop all includes both incoming
 *and* outgoing traffic.

 I have absolutely no qualms with block in all, but block out all
 is too unrealistic, depending greatly on what the purpose of the
 machine is.  Any outbound sockets are going to be allocated
 dynamically (e.g.  non-static port number), so there's no effective
 way to add pass rules for outbound traffic.  Using uid/gid is not
 sufficient.

 I often advocate using block in all, pass out all, and then adding
 specific pass rules for incoming traffic (e.g. an Internet request
 wishing to speak to BIND on port 53, Apache on 80/443, etc.).

Ah! :)

I was a bit confused in my last post then.  I thought you were talking
about `block in all' too.

 Good discussion!  (And I hope the OP is learning something :-) )

:-)

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: pf vs. RST attack question

On Mon, 6 Oct 2008 04:51:01 -0700, Jeremy Chadwick [EMAIL PROTECTED] wrote:
 I run my laptop with a `pf.conf' that (putting most of the comments and
 other disabled rules for one-off tests aside) looks pretty much like:

   set block-policy drop
   set require-order yes
   set skip on lo0
   scrub   in  all
   block   in  all
   block   out all
   passin  quick proto icmp all
   passout quick proto icmp all
   passout proto { tcp, udp } all keep state

 A couple things to point out here:

 First, ICMP rules coming first (especially with quick) might not be
 ideal; ICMP is often considered a last resort protocol, meaning TCP
 and UDP packets should have priority over it.  It all depends on what
 you want, but this is often the industry norm.

That's nice.

 Second, and much more importantly, if you're on RELENG_7, keep state
 serves no purpose here; flags S/SA is implicit on TCP rules, and
 keep state is implicit in TCP, UDP, and ICMP rules.

8.0-CURRENT so `flags S/SA' is indeed implicit.

I updated the rules to include `flags S/SA' too.  Both this part and
`keep state' are implicit now, but I like being slightly less verbose
because I tend to forget what is `default' and what is not, at the
expense of being slightly more verbose :)

 Happy firewalling!  :-)

Thanks :)

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

stupid xfce clock question

2008-10-06 Thread Aryeh M. Friedman

I work remotely with a company that is across the international date 
line from me and I can do the math in my head but want to know if it is 
possible to add a clock to my xfce panel that shows the time their (and 
keep the one that has my time on it)

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: pf vs. RST attack question

On Mon, Oct 06, 2008 at 02:33:38PM +0300, Giorgos Keramidas wrote:
 On Mon, 6 Oct 2008 00:26:11 -0700, Jeremy Chadwick [EMAIL PROTECTED] wrote:
  On Mon, Oct 06, 2008 at 08:19:09AM +0100, Matthew Seaman wrote:
  block drop all
 
  looks fairly magical to me.  Stick that at the top of your ruleset as
  your default policy, add more specific rules beneath it to allow the
  traffic you do want to pass, and Robert is your Mother's Brother.  No
  more floods of RST packets.
 
  This is incredibly draconian.  :-)  I was trying my best to remain
  realistic.
 
 Yes this is a bit draconian, but it is also pretty ``realistic'', as in
 ``it works fine if all you need is a very basic, but strict firewall''.
 
 I run my laptop with a `pf.conf' that (putting most of the comments and
 other disabled rules for one-off tests aside) looks pretty much like:
 
   set  block-policy drop
   set  require-order yes
   set  skip on lo0
   scrubin  all
   blockin  all
   blockout all
   pass in  quick proto icmp all
   pass out quick proto icmp all
   pass out proto { tcp, udp } all keep state

A couple things to point out here:

First, ICMP rules coming first (especially with quick) might not be
ideal; ICMP is often considered a last resort protocol, meaning TCP
and UDP packets should have priority over it.  It all depends on what
you want, but this is often the industry norm.

Second, and much more importantly, if you're on RELENG_7, keep state
serves no purpose here; flags S/SA is implicit on TCP rules, and keep
state is implicit in TCP, UDP, and ICMP rules.

If you're using RELENG_6, then your above rules have a serious problem:
you're tracking state for all outbound packets regardless of flags, and
not just initial setup (SYN).  This is Very Bad(tm).  In that case, you
should use these rules instead:

  pass out proto tcp all flags S/SA keep state
  pass out proto udp all keep state
  pass out proto icmp all keep state

I've never gotten a definite answer as to what happens if you use flags
S/SA on a rule that is for UDP, since UDP is a non-negotiated protocol.
That's why I split them up per protocol on RELENG_6 boxes.

Happy firewalling!  :-)

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

update.FreeBSD.org / No mirrors remaining, giving up

2008-10-06 Thread Zbigniew Szalbot

Hello,

I am not sure why but whenever I do:

$ freebsd-update fetch
Fetching metadata signature for 7.0-RELEASE from update.FreeBSD.org... failed.
No mirrors remaining, giving up.

but if type:
$ portsnap fetch
Fetching snapshot tag from portsnap.FreeBSD.org... done.

Many thanks for any hint as to what may be wrong with
update.FreeBSD.org on this machine!

-- 
Zbigniew Szalbot
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: USB mouse problems

2008-10-06 Thread Patrick Lamaizière

Le Mon, 06 Oct 2008 08:41:59 +0200,
Aniruddha [EMAIL PROTECTED] a écrit :

 I have one Razer Lachesis USB mouse attached to the rear usb ports of
 my pc. This mouse has never worked, however when I plug in another USB
 mouse in the front of my pc it works?! I wonder; how do I get the
 Razer Lachesis working without plugging it in the front?

I don't know.

 Furthermore I wondered if there is a way to use both the mouse in a
 terminal (gpm) and in xorg?
 
Yes, see moused(8) and vidcontrol(1). 

Regards.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Setting up skype

2008-10-06 Thread Aryeh M. Friedman

I am running the most recent version of net/skype (not -devel) and do 
not have a mic or camera and want to know what people recommend.   
Ideally I would like a all in one phone type head set for the audio.  
bTW I am usinf xfce on 8-CURRENT (i386)

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: pf vs. RST attack question

2008-10-06 Thread Matthew Seaman

Jeremy Chadwick wrote:

On Mon, Oct 06, 2008 at 09:34:46AM +0100, Matthew Seaman wrote:

Jeremy Chadwick wrote:

On Mon, Oct 06, 2008 at 08:19:09AM +0100, Matthew Seaman wrote:

Jeremy Chadwick wrote:

If you want a magic solution, see blackhole(4).

block drop all

looks fairly magical to me. Stick that at the top of your ruleset as
your default policy, add more specific rules beneath it to allow
the traffic you do want to pass, and Robert is your Mother's Brother.
No more floods of RST packets.

This is incredibly draconian. :-) I was trying my best to remain
realistic.

It's no such thing. This is the recommended standard practice when designing
firewalls: always start from the premise that all traffic will be dropped by
default and add specific exceptions to allow the traffic you want. Trying to
work the other way round is a recipe for disaster: 'allow everything, but block
what is then shown to be deleterious' means that you're always playing catch-up
as changes on your servers expose new attack vectors and as attackers discover
and try to exploit those holes. Not recommended, unless you actually /like/
being paged in the wee small hours.

What I mean by 'draconian': block drop all includes both incoming
*and* outgoing traffic.

Well, yeah. But 'block drop in all' is pretty much just an optimised
variant of

block drop all
pass out all

even if you never write it out that way. You're just starting two
steps into the process I was talking about.

I have absolutely no qualms with block in all, but block out all is
too unrealistic, depending greatly on what the purpose of the machine
is. Any outbound sockets are going to be allocated dynamically (e.g.
non-static port number), so there's no effective way to add pass rules
for outbound traffic. Using uid/gid is not sufficient.

I often advocate using block in all, pass out all, and then adding
specific pass rules for incoming traffic (e.g. an Internet request
wishing to speak to BIND on port 53, Apache on 80/443, etc.).

Like I said: I'm being realistic.

One man's realism is another's open proxy or information disclosure
and having to deal with abuse complaints. Yes, in practice for some
of the firewalls we manage the policy is 'all outgoing is allowed',
but by no means the majority. Most of the time we do permit outgoing for some or all of these protocols: FTP(passive), SSH, SMTP, DNS,
HTTP, NTP, HTTPS, RSYNC, CVSUP and frequently that's allowing
outgoing to any unless there's a requirement to restrict things
further.

We aren't concerned with writing filter rules that operate on the
local port numbers here, but with the port numbers on the remote sites
we're connecting to. As you say, local port numbers are unpredictable,
but stateful firewall rules handle all that sort of thing easily,
even for stateless (UDP) protocols like DNS. Not only that, but looking up a packet in the state table is generally quite a bit faster
than having to traverse the whole rule set. At least, it is when using
pf.

Cheers,

Matthew

--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW

signature.asc
Description: OpenPGP digital signature

Re: continuous backup solution for freebsd?

On Mon, Oct 06, 2008 at 12:58:30PM +0300, Evren Yurtesen wrote:
 Hello,

 Is there a known continuous backup solution similar to r1soft backup for  
 FreeBSD? I googled a lot but couldnt find anything.

 R1soft says they need help to develop FreeBSD support in their product. 
 Do you know anybody who can help r1soft on this issue?

 Please see: http://forum.r1soft.com/showpost.php?p=3414postcount=9

Would the GEOM gate class handle this?  See ggatec(8) and ggated(8).

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: pf vs. RST attack question

On Mon, Oct 06, 2008 at 09:34:46AM +0100, Matthew Seaman wrote:
 Jeremy Chadwick wrote:
 On Mon, Oct 06, 2008 at 08:19:09AM +0100, Matthew Seaman wrote:
 Jeremy Chadwick wrote:


 If you want a magic solution, see blackhole(4).

 block drop all

 looks fairly magical to me.  Stick that at the top of your ruleset as
 your default policy, add more specific rules beneath it to allow
 the traffic you do want to pass, and Robert is your Mother's Brother.
 No more floods of RST packets.

 This is incredibly draconian.  :-)  I was trying my best to remain
 realistic.

 It's no such thing.  This is the recommended standard practice when designing
 firewalls: always start from the premise that all traffic will be dropped by
 default and add specific exceptions to allow the traffic you want.  Trying to
 work the other way round is a recipe for disaster: 'allow everything, but 
 block
 what is then shown to be deleterious' means that you're always playing 
 catch-up
 as changes on your servers expose new attack vectors and as attackers discover
 and try to exploit those holes.  Not recommended, unless you actually /like/
 being paged in the wee small hours.

What I mean by 'draconian': block drop all includes both incoming
*and* outgoing traffic.

I have absolutely no qualms with block in all, but block out all is
too unrealistic, depending greatly on what the purpose of the machine
is.  Any outbound sockets are going to be allocated dynamically (e.g.
non-static port number), so there's no effective way to add pass rules
for outbound traffic.  Using uid/gid is not sufficient.

I often advocate using block in all, pass out all, and then adding
specific pass rules for incoming traffic (e.g. an Internet request
wishing to speak to BIND on port 53, Apache on 80/443, etc.).

Like I said: I'm being realistic.

 (Actually, I'd recommend always adding a 'log' clause to any rules that
 drop packets like so: 'block log drop all'.  Makes running 'tcpdump -i 
 pflog0'
 an invaluable debugging aid.)

 I cannot advocate use of log on such vague rules, and my attitude is
 based on experience:

 We had log set on some of our deny rules, specifically on an entry
 which blocked any traffic to an IP to any ports other than 53 (DNS).
 Someone initiated an attack against that IP, to a destination port of
 something other than 53, which caused pflog to go crazy with logging.

 What inadvertently resulted was a local system DoS -- the system began
 sporting a load average between 40 and 50, and was sluggish.

 The root cause?  /var/log/pflog was growing at such a tremendous rate
 that newsyslog (trying to rotate and compress the logs) could not keep
 up.  When I got to it, I found 8 or 9 gzip/newsyslog processes running
 trying to deal with the chaos.

 Bottom line: be very, very cautious what rules you use log on, and be
 sure to remove it once the system is in production.

 You have a point here, I will certainly admit that.  In my experience, I've 
 not
 yet run into that scenario.  I've tended to see systems more easily DoSed by
 running out of pf states due to excessive DoS traffic to allowed ports than to
 any extra load from pflogd and newsyslog from logging denied traffic.  The
 machines in question already log so much legitimate traffic from Squid and 
 Apache
 that pflog is trivial by comparison.  Of course, now I've said 'it never 
 happens'
 I'm expecting half our firewalls to explode any minute now...

:-)  I sure hope not!  The situation we experienced came as a great
surprise, and it wasn't something I even remotely considered when
setting up the rules in question.

Since then, log has been removed from all of our rules, but I keep
pflog running in the case that something starts happening and I need
to temporary add log to rules + /etc/rc.d/pf reload to see what's
going on.  Of course, tcpdump also works wonders here.

Good discussion!  (And I hope the OP is learning something :-) )

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

continuous backup solution for freebsd?


Hello,

Is there a known continuous backup solution similar to r1soft backup for 
FreeBSD? I googled a lot but couldnt find anything.


R1soft says they need help to develop FreeBSD support in their product. Do you 
know anybody who can help r1soft on this issue?


Please see: http://forum.r1soft.com/showpost.php?p=3414postcount=9

Thanks,
Evren
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: stupid xfce clock question

On Mon, 06 Oct 2008 04:39:20 -0400, Aryeh M. Friedman [EMAIL PROTECTED] 
wrote:
 I work remotely with a company that is across the international date
 line from me and I can do the math in my head but want to know if it
 is possible to add a clock to my xfce panel that shows the time their
 (and keep the one that has my time on it)

If you are using XFCE4 then you are reaping all the benefits of the
freely available work of others.  This style of subject is offensive to
their efforts to provide a light-weight, beautiful, functional and fast
performing desktop environment in a multitude of UNIX platforms.

Please consider using a less confrontational style for posting questions
in the future.

Now, regarding the timezone question: You can use the `Orage Clock'.  It
is bundled with the current XFCE4 in the FreeBSD Ports, and its startup
options include one that sets the clock timezone.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: USB mouse problems

2008-10-06 Thread Andrew D


Patrick Lamaizière wrote:

Le Mon, 06 Oct 2008 08:41:59 +0200,
Aniruddha [EMAIL PROTECTED] a écrit :


I have one Razer Lachesis USB mouse attached to the rear usb ports of
my pc. This mouse has never worked, however when I plug in another USB
mouse in the front of my pc it works?! I wonder; how do I get the
Razer Lachesis working without plugging it in the front?


I don't know.


Some motherboards have a jumper (or BIOS option) to that has to be set, 
so that the front connectors work at the expense of other ports.





Furthermore I wondered if there is a way to use both the mouse in a
terminal (gpm) and in xorg?
 
Yes, see moused(8) and vidcontrol(1). 


Regards.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: pf vs. RST attack question

On Mon, 6 Oct 2008 00:26:11 -0700, Jeremy Chadwick [EMAIL PROTECTED] wrote:
 On Mon, Oct 06, 2008 at 08:19:09AM +0100, Matthew Seaman wrote:
 block drop all

 looks fairly magical to me.  Stick that at the top of your ruleset as
 your default policy, add more specific rules beneath it to allow the
 traffic you do want to pass, and Robert is your Mother's Brother.  No
 more floods of RST packets.

 This is incredibly draconian.  :-)  I was trying my best to remain
 realistic.

Yes this is a bit draconian, but it is also pretty ``realistic'', as in
``it works fine if all you need is a very basic, but strict firewall''.

I run my laptop with a `pf.conf' that (putting most of the comments and
other disabled rules for one-off tests aside) looks pretty much like:

  setblock-policy drop
  setrequire-order yes
  setskip on lo0
  scrub  in  all
  block  in  all
  block  out all
  pass   in  quick proto icmp all
  pass   out quick proto icmp all
  pass   out proto { tcp, udp } all keep state

Depending on the network I am connected to, I may leave DHCP replies
open too, i.e.:

  pass   in  quick proto udp from 192.168.1.1/24 to 255.255.255.255 port = 68

This seems to have worked pretty well so far, but this is, as I wrote,
merely a laptop.  For production servers, there are probably going to be
quite a few other rules to allow incoming connections.

 I cannot advocate use of log on such vague rules, and my attitude
 is based on experience:

 We had log set on some of our deny rules, specifically on an entry
 which blocked any traffic to an IP to any ports other than 53 (DNS).
 Someone initiated an attack against that IP, to a destination port of
 something other than 53, which caused pflog to go crazy with logging.

Heh, that's indeed a possibility.   Hence the lack of 'log' in my
default ruleset shown above.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: stupid xfce clock question

On Mon, Oct 06, 2008 at 02:45:21PM +0300, Giorgos Keramidas wrote:
 On Mon, 06 Oct 2008 04:39:20 -0400, Aryeh M. Friedman [EMAIL PROTECTED] 
 wrote:
  I work remotely with a company that is across the international date
  line from me and I can do the math in my head but want to know if it
  is possible to add a clock to my xfce panel that shows the time their
  (and keep the one that has my time on it)
 
 If you are using XFCE4 then you are reaping all the benefits of the
 freely available work of others.  This style of subject is offensive to
 their efforts to provide a light-weight, beautiful, functional and fast
 performing desktop environment in a multitude of UNIX platforms.
 
 Please consider using a less confrontational style for posting questions
 in the future.

It depends on how you read it.  I read the Subject line to mean I'm
asking a stupid question, not xfce is stupid.  I'm pretty sure Aryeh
meant the lesser, not the latter.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

VNC server embedded into Xorg server

2008-10-06 Thread Laszlo Nagy



 Hi All,

There was a port called net/vnc that contained a vnc.so file. That file 
could be loaded into the Xorg server and then I was able to monitor the 
X desktop with VNC.


Now I'm using gnome, and gnome2-fifth-toe installs tightvnc. It 
conflicts with net/vnc. So I cannot install net/vnc. What other options 
I have to run an X server?


The only extra wish is that the X server must be able to start 
automatically, e.g. without logging into gnome. I need this because the 
X server will be located at a distant location and I have to be able to 
use it after a system restart.


Thanks,

  Laszlo

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: stupid xfce clock question

2008-10-06 Thread Aryeh M. Friedman


Jeremy Chadwick wrote:

On Mon, Oct 06, 2008 at 02:45:21PM +0300, Giorgos Keramidas wrote:
  

On Mon, 06 Oct 2008 04:39:20 -0400, Aryeh M. Friedman [EMAIL PROTECTED] 
wrote:


I work remotely with a company that is across the international date
line from me and I can do the math in my head but want to know if it
is possible to add a clock to my xfce panel that shows the time their
(and keep the one that has my time on it)
  

If you are using XFCE4 then you are reaping all the benefits of the
freely available work of others.  This style of subject is offensive to
their efforts to provide a light-weight, beautiful, functional and fast
performing desktop environment in a multitude of UNIX platforms.

Please consider using a less confrontational style for posting questions
in the future.



It depends on how you read it.  I read the Subject line to mean I'm
asking a stupid question, not xfce is stupid.  I'm pretty sure Aryeh
meant the lesser, not the latter.

  
Just for clarity thats what I meant... I use it specifically because it 
is the best desktop out there and has not made the same mistakes gnome 
and/or kde did (the only complaint I have is it your be nice if the 
desktop would updat7e it self as you change the contents of ~/Desktop)

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

multihomed fbsd7 router with nat

2008-10-06 Thread Andrew D


G'Day all,

Got a network that has 2 DSL connections.
The 1st has cheap data and the 2nd is a more reliable provider.
Basically all data goes out the first provider except some IPs which
will use the second provider (just a ipfw fwd rule).
If the cheap one goes offline data has to route out via the 2nd ISP,
likewise if the 2nd does happen to go off then the fwd rule needs to be
dropped.

I have already solved this with an attached script (for
suggestions and maybe to help others who may face this problem in the
future).

Anyway I plan to put the 2 modems into bridge mode use the ppp that
comes with fbsd to do the auth side of things.

My question is what should I use for NAT.  Use the inbuilt NAT that 
comes with PPP or firewall based?


TIA

Cheers
cya
Andrew
#!/usr/local/bin/bash


FWRUL=1

# put main connection first
# the names must match the config names in /etc/ppp/ppp.conf
# Must also have a /etc/namedb/named.conf.ISP_NAME for each 
# ISP so that named's forward lookups points to the right name server


PISP='isp1'
BISP='isp2'

FWBLOCK='192.168.1.209/28'
LAN='192.168.1.0/24'

#  Functions


function getgwip {
  PID=$1
  GW=''
  for i in 0 1 2 3 4 5 6 7 8 9; do 
STR=`ifconfig tun$i 2/dev/null |grep PID $pid `
if [ -n $STR ]; then
   GW=`ifconfig tun$i |grep inet |tail -n 1|awk '{print $2   $4}'`
fi
  done
  echo $GW
}

function ch_route {
  X=Changing routing for all data to: $2\nOld default gateway: $3
  GW=`getgwip $1 |awk '{print $2}'`
  if [ $GW == $3 ]; then
exit;
  fi
  echo $X
  /sbin/route delete default 
  /sbin/route add default $GW 
  echo New default gateway: $GW
  cp /etc/named/named.conf.$ROUTO /etc/namedb/named.conf
  /etc/rc.d/named reload
  exit
}

function ch_firewall {
  if [ $1 != $PISP ]; then
/sbin/ipfw -q delete $FWRUL /dev/null 21
  else
F=`ipfw show $FWRUL 2/dev/null|| echo FAIL`
if [ $F == FAIL ]; then
  /sbin/ipfw -q add $FWRUL fwd $2 ip from $FWBLOCK to not $LAN 
fi
  fi
}

PPPCOM='/usr/sbin/ppp -quiet -ddial -nat '
PID1=`ps ax | grep ppp | grep -v grep |grep $PISP |awk '{print $1}'`
PID2=`ps ax | grep ppp | grep -v grep |grep $BISP |awk '{print $1}'`

ROUTO=''
if [ -z $PID1 ] then
 $PPPCOM $PISP /dev/null 21 
 ROUTO=$BISP
 RPID=$PID2
fi

if [ -z $PID2 ] then
 $PPPCOM $BISP /dev/null 21 
 ROUTO=$PISP
 RPID=$PID1
fi

CGW=`netstat -rn | grep ^default | awk '{print $2}'`

if [ -n $ROUTO ]; then
  echo restarting $ROUTO
  ch_firewall clear
  ch_route $RPID $ROUTO $CGW 
fi


TMP=`getgwip $PISP`
PGW=`echo $TMP | awk '{print $2}'`
PIP=`echo $TMP | awk '{print $1}'`
TMP=`getgwip $BISP`
BGW=`echo $TMP | awk '{print $2}'`
BIP=`echo $TMP | awk '{print $1}'`

OUT=Current default gateway: $CGW

if [ -z $PIP -a -z $BIP ]; then
  logg BOTH $PISP and $BISP are DOWN!!
  exit
fi

if [ -z $PIP ]; then
  if [ $CGW != $BGW ]; then
logg $PISP currently down
ch_firewall clear
ch_route $PID2 $BISP $CGW 
  fi
  exit
fi

if [ -z $BIP ]; then
  if [ $CGW != $PGW ]; then
logg $BISP currently down
ch_firewall clear
ch_route $PID1 $PISP $CGW 
  fi
  exit
fi


PISPING=`ping -n -s 1 -o -c 5 -S $PIP -W 5000 -t 6 $PGW /dev/null 21 || echo 
FAIL`  
BISPING=`ping -n -s 1 -o -c 5 -S $BIP -W 5000 -t 6 $BGW /dev/null 21 || echo 
FAIL`

if [ $PISPING == FAIL ]; then
  if [ $CGW != $BGW ]; then
logg $PISP currently down
ch_firewall clear
ch_route $PID2 $BISP $CGW 
  fi
  exit
fi
if [ $BISPING == FAIL ]; then
  if [ $CGW != $PGW ]; then
logg $BISP currently down
ch_firewall clear
ch_route $PID1 $PISP $CGW 
  fi
  exit
fi


FWCHECK=`ipfw show $FWRUL 2/dev/null || echo FAIL`
if [ $FWCHECK != FAIL ];
logg Added policy routing for $FWBLOCK
ch_firewall $PISP
fi

if [ $CGW != $PGW ]; then
logg Changed routing back to $PISP
ch_route $PID1 $PISP $CGW 
fi




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: pf vs. RST attack question

2008-10-06 Thread James Seward

On Mon, Oct 6, 2008 at 12:51 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
 I've never gotten a definite answer as to what happens if you use flags
 S/SA on a rule that is for UDP, since UDP is a non-negotiated protocol.
 That's why I split them up per protocol on RELENG_6 boxes.

It intelligently ignores it:
 % pfctl -vn -f-
pass out proto { tcp udp } all flags S/SA keep state

Output:
pass out proto tcp all flags S/SA keep state
pass out proto udp all keep state

/JMS
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: continuous backup solution for freebsd?

2008-10-06 Thread Julien Cigar

Bacula ? http://www.bacula.org
I use it at work to backup linux and freebsd boxes and it works like a
charm.

On Mon, 2008-10-06 at 04:20 -0700, Jeremy Chadwick wrote:
 On Mon, Oct 06, 2008 at 12:58:30PM +0300, Evren Yurtesen wrote:
  Hello,
 
  Is there a known continuous backup solution similar to r1soft backup for  
  FreeBSD? I googled a lot but couldnt find anything.
 
  R1soft says they need help to develop FreeBSD support in their product. 
  Do you know anybody who can help r1soft on this issue?
 
  Please see: http://forum.r1soft.com/showpost.php?p=3414postcount=9
 
 Would the GEOM gate class handle this?  See ggatec(8) and ggated(8).
 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: stupid xfce clock question

On Mon, 06 Oct 2008 09:28:12 -0400, Aryeh M. Friedman [EMAIL PROTECTED] 
wrote:
 If you are using XFCE4 then you are reaping all the benefits of the
 freely available work of others.  This style of subject is offensive
 to their efforts to provide a light-weight, beautiful, functional
 and fast performing desktop environment in a multitude of UNIX
 platforms.

 Please consider using a less confrontational style for posting
 questions in the future.

 It depends on how you read it.  I read the Subject line to mean I'm
 asking a stupid question, not xfce is stupid.  I'm pretty sure
 Aryeh meant the lesser, not the latter.

 Just for clarity thats what I meant... I use it specifically because it
 is the best desktop out there and has not made the same mistakes gnome
 and/or kde did (the only complaint I have is it your be nice if the
 desktop would updat7e it self as you change the contents of ~/Desktop)

Ok, an apology from me is in order then.  My non-native English failed
to parse the subject correctly, sorry about that :-/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: pf vs. RST attack question

On Mon, 6 Oct 2008 14:44:54 +0100, James Seward [EMAIL PROTECTED] wrote:
 On Mon, Oct 6, 2008 at 12:51 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
 I've never gotten a definite answer as to what happens if you use flags
 S/SA on a rule that is for UDP, since UDP is a non-negotiated protocol.
 That's why I split them up per protocol on RELENG_6 boxes.

 It intelligently ignores it:
  % pfctl -vn -f-
 pass out proto { tcp udp } all flags S/SA keep state

 Output:
 pass out proto tcp all flags S/SA keep state
 pass out proto udp all keep state

The ruleset optimizer displays something similar too:

 pfctl -sr -o basic

shows the same pair of rules :)

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: continuous backup solution for freebsd?


Jeremy Chadwick wrote:

On Mon, Oct 06, 2008 at 12:58:30PM +0300, Evren Yurtesen wrote:

Hello,

Is there a known continuous backup solution similar to r1soft backup for  
FreeBSD? I googled a lot but couldnt find anything.


R1soft says they need help to develop FreeBSD support in their product. 
Do you know anybody who can help r1soft on this issue?


Please see: http://forum.r1soft.com/showpost.php?p=3414postcount=9


Would the GEOM gate class handle this?  See ggatec(8) and ggated(8).



I am not saying it is impossible. They just need somebody to put them to 
right track I guess. I personally cant do that. It would be nice if 
somebody who has knowledge in this area contacts r1soft. At the very 
least r1soft seems to be willing to communicate on this issue.


Continuous backups as well as bare-metal-restore seem to be a key 
feature for many hosters. FreeBSD is loosing users because of this issue.


Thanks,
Evren
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Coretemp seems to be off quite a bit

2008-10-06 Thread Kirk Strauser

I have a Gigabyte motherboard with an Intel ICH-9 chipset, and a  
3.0GHz Core 2 Duo (E8400).  The coretemp sysctls seem to always show  
50C as the baseline temperature:


$ sysctl dev.cpu | grep temp
dev.cpu.0.temperature: 50
dev.cpu.1.temperature: 50

This is with a big PSU fan, a good CPU fan, a clean heatsink, and two  
case fans aimed the right direction (front fan pulling cool air in,  
rear fan pushing warm air out).  If I reboot and go into the BIOS, I  
get numbers around 42-43C.  I know it's kind of hard to compare  
directly, but the coretemp numbers are from a totally idle system with  
powerd scaling it back to 373MHz, so it should be as cool as when  
sitting idle in the BIOS screens.  When I work the system hard, like  
running make -j4 buildworld, I see temperatures up around 63-64C,  
and I'm almost positive that's not right.


Any ideas why coretemp and the BIOS would show such different numbers?
--
Kirk Strauser

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: continuous backup solution for freebsd?


Julien Cigar wrote:

Bacula ? http://www.bacula.org
I use it at work to backup linux and freebsd boxes and it works like a
charm.

On Mon, 2008-10-06 at 04:20 -0700, Jeremy Chadwick wrote:

On Mon, Oct 06, 2008 at 12:58:30PM +0300, Evren Yurtesen wrote:

Hello,

Is there a known continuous backup solution similar to r1soft backup for  
FreeBSD? I googled a lot but couldnt find anything.


R1soft says they need help to develop FreeBSD support in their product. 
Do you know anybody who can help r1soft on this issue?


Please see: http://forum.r1soft.com/showpost.php?p=3414postcount=9

Would the GEOM gate class handle this?  See ggatec(8) and ggated(8).






Bacula does not support continuous backups as far as I know. It has to 
scan all the files to find new/changed files to backup. The r1soft agent 
monitors file system writes and backs up changed parts immediately. This 
does allow r1soft backup to restore the system to its latest state 
(10-15minutes ago state, thus continuous backup is achieved) as it 
continually updates the backups. Also has much less stress on the 
systems where the writes are not so much since it doesnt have to check 
every file at each backup cycle. Also r1soft cdp has support for MySQL 
where you can easily restore mysql data in table level if required. It 
is as well supported by a wide variety of web hosting automation systems 
for example H-Sphere ( http://www.parallels.com/hsphere/ ) etc. through 
plugins.


Please see the info about continuous data protection:
http://en.wikipedia.org/wiki/Continuous_Data_Protection

Otherwise I am currently using BackupPC (which is pretty good in my 
opinion and easier to use compared to Bacula) to take nightly backups of 
the servers.


Thanks,
Evren
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

RE: Can't add new 1TB disk in FreeBSD 6.1

 I just swapped out an old 500G disk with a 1TB one and I'm trying to 
 label it and mount it...
 
 If I run bsdlabel -w ad4, I get:
 
 bsdlabel: Geom not found
 
 If I run sysinstall, it tells me that it can't write to the disk.
 
 I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that 
 didn't help.
 
 Can anyone help me get this new disk installed without having to boot 
 off a recovery CD? The server is 500 miles away from me and I don't 
 have direct console access.
 Can you provide output from dmesg, as well as geom disk list?

OK... I tried:

# dd if=/dev/zero of=/dev/ad4 bs=512 count=1000
dd: /dev/ad4: Operation not permitted

# fdisk /dev/ad4
*** Working on device /dev/ad4 ***
parameters extracted from in-core disklabel are:
cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)

fdisk: invalid fdisk partition table found
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 1953525105 (953869 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 612/ head 15/ sector 63
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED

Geometry output:

Geom name: ad4
Providers:
1. Name: ad4
   Mediasize: 1000204886016 (932G)
   Sectorsize: 512
   Mode: r0w0e0
   fwsectors: 63
   fwheads: 16

Nothing exciting coming from dmesg.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: stupid xfce clock question

2008-10-06 Thread Jason C. Wells


Aryeh M. Friedman wrote:
I work remotely with a company that is across the international date 
line from me and I can do the math in my head but want to know if it 
is possible to add a clock to my xfce panel that shows the time their 
(and keep the one that has my time on it)

___
You can run two instances of orage.  I think they read the same config 
file.  I think you would have little trouble hacking up a TZ1, TZ2 
variable for seperate instances to read.


Later,
Jason
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: acpi_tz0: _TMP value is absurd ignored (-269.7C) Message in every 3 seconds .

2008-10-06 Thread John Nielsen

On Monday 06 October 2008 02:07:17 am dhaneshk k wrote:
 I installed freebsd-7.0  in a p4 machine , after installation when I
 reboot the machine , I am getting the message

 acpi_tz0: _TMP value is absurd ignored (-269.7C)   in every 3 seconds

I have a machine that does this as well. I haven't done any research into 
the cause or an actual fix, but a workaround is to add
hw.acpi.thermal.polling_rate=0
to /etc/sysctl.conf.

JN

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Freebsd-update with a custom kernel and jails

2008-10-06 Thread FreeBSD


FreeBSD a écrit :

FreeBSD a écrit :

matt donovan a écrit :
On Sun, Oct 5, 2008 at 12:58 PM, FreeBSD [EMAIL PROTECTED] 
wrote:


 

There is my situation:
I want to be able to use freebsd-update to update a FreeBSD 7.0-Release
installation to the latest security patches (I want an update and 
not an
upgrade if I understand correctly). Where this gets more complicated 
is that

I need a custom kernel (for ULE, pf and ALTQ while also disabling some
devices I'll never need) and I want to use jails to isolate every 
services

(Apache and MySQL by now).

So, I read at some places that you can't use freebsd-update with a 
custom

kernel, but I'm not sure if this apply only in the case of an upgrade
between release or if I'll need to manually recompile the kernel 
with every

use of freebsd-update.

I also read that it's possible to update the jails from the host system
with the -b flag. In this case, I supposed that I need to update the 
host
system before the jail, but is the procedure going to be exactly the 
same?


yes all you need to do is freebsd-update fetch install your kernel 
won't be

updated but your userland will


So it is right to say that the custom kernel problem applies only 
when upgrading to a newer release?


All I have to do is 'freebsd-update fetch install' to update the base 
system then 'freebsd-update -b /usr/jail/jail_name fetch install' to 
update the jails?


I hope so because it would be very impressing :)

Martin
Another question just came to my head: May I update the src before 
compiling my custom kernel or should I keep the original src that 
shipped with the release to be able to use freebsd-update?


Thank you very much for your help!

Martin



I just tried it (freebsd-update fetch install) and after a reboot uname 
-a still shows FreeBSD 7.0-RELEASE #0 while freebsd-update told me I was 
going to update to 7.0-RELEASE-p5. But, I noticed that the files that 
needed to be updated were updated.


I'm a little confused...can someone explain this behaviour to me?

Thanks,

Martin

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Can't add new 1TB disk in FreeBSD 6.1

On Mon, Oct 06, 2008 at 08:03:46AM -0700, Don O'Neil wrote:
  I just swapped out an old 500G disk with a 1TB one and I'm trying to 
  label it and mount it...
  
  If I run bsdlabel -w ad4, I get:
  
  bsdlabel: Geom not found
  
  If I run sysinstall, it tells me that it can't write to the disk.
  
  I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that 
  didn't help.
  
  Can anyone help me get this new disk installed without having to boot 
  off a recovery CD? The server is 500 miles away from me and I don't 
  have direct console access.
  Can you provide output from dmesg, as well as geom disk list?
 
 OK... I tried:
 
 # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000
 dd: /dev/ad4: Operation not permitted

Did you sysctl kern.geom.debugflags=16 before doing this?

What's happening here is that GEOM isn't letting you overwrite the MBR
on the disk.  Setting kern.geom.debugflags=16 should permit that to
happen.

 # fdisk /dev/ad4
 *** Working on device /dev/ad4 ***
 parameters extracted from in-core disklabel are:
 cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)
 
 Figures below won't work with BIOS for partitions not in cyl 1
 parameters to be used for BIOS calculations are:
 cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)
 
 fdisk: invalid fdisk partition table found

This line right here looks very bad.  I would recommend running sade(8)
and properly configuring this disk.

 Media sector size is 512
 Warning: BIOS sector numbering starts with sector 1
 Information from DOS bootblock is:
 The data for partition 1 is:
 sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
 start 63, size 1953525105 (953869 Meg), flag 80 (active)
 beg: cyl 0/ head 1/ sector 1;
 end: cyl 612/ head 15/ sector 63

This portion looks okay, although I guess the addressing mode chosen is
different on your system.  Most of my systems show the end CHS as
1023/254/63.

 Geometry output:
 
 Geom name: ad4
 Providers:
 1. Name: ad4
Mediasize: 1000204886016 (932G)
Sectorsize: 512
Mode: r0w0e0
fwsectors: 63
fwheads: 16

This looks okay.

 Nothing exciting coming from dmesg.

Thanks for providing the output like I requested.  :-)

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Problem with Passive FTP through PF

2008-10-06 Thread Michael K. Smith - Adhost

Hello All:

We are running the following:
- FreeBSD 6.3 Release #1
- PF
- pftpx for our ftp proxy

We have several ftp servers of different flavors behind the PF firewalls and we 
are getting a lot of the following when users are trying to connect using 
passive mode.

Server sent passive reply with unroutable address

We're running pftpx as a daemon with no specific flags.  From a ps:

proxy 4845  0.0  0.0  1452  1100  ??  Is   27Sep08   0:02.13 
/usr/local/sbin/pftpx

Here is a sample of the rules we are using to allow traffic and to proxy.  The 
server macros are defined and working correctly.  Any help would be greatly 
appreciated.

nat-anchor pftpx/*
rdr-anchor pftpx/*
rdr on ! $vlan10_if proto { udp tcp } from any to $f1_cps01_ext0 port { 80 443 
2087 2083 ftp 49152:65535 } - $f1_cps01_int0 sticky-address
rdr on ! $vlan10_if proto { udp tcp } from any to $f1_cps01_ext1 port { 80 443  
ftp 49152:65535 } - $f1_cps01_int1 sticky-address


--
Michael K. Smith - CISSP, GISP
Chief Technical Officer - Adhost Internet LLC
[EMAIL PROTECTED]
w: +1 (206) 404-9500 f: +1 (206) 404-9050
PGP: B49A DDF5 8611 27F3  08B9 84BB E61E 38C0 (Key ID: 0x9A96777D)




PGP.sig
Description: PGP signature

Re: continuous backup solution for freebsd?

On Mon, Oct 06, 2008 at 05:36:32PM +0300, Evren Yurtesen wrote:
 Jeremy Chadwick wrote:
 On Mon, Oct 06, 2008 at 12:58:30PM +0300, Evren Yurtesen wrote:
 Hello,

 Is there a known continuous backup solution similar to r1soft backup 
 for  FreeBSD? I googled a lot but couldnt find anything.

 R1soft says they need help to develop FreeBSD support in their 
 product. Do you know anybody who can help r1soft on this issue?

 Please see: http://forum.r1soft.com/showpost.php?p=3414postcount=9

 Would the GEOM gate class handle this?  See ggatec(8) and ggated(8).


 I am not saying it is impossible. They just need somebody to put them to  
 right track I guess. I personally cant do that. It would be nice if  
 somebody who has knowledge in this area contacts r1soft. At the very  
 least r1soft seems to be willing to communicate on this issue.

First and foremost, the URL you gave is terse and out of context.  Let
people read the entire thread:

http://forum.r1soft.com/showthread.php?p=3414

So let me throw around some ideas.

First and foremost, David appears to be saying We'll take FreeBSD
seriously if we can get proper documentation, and it needs to be
thorough, that explains how to interface with devices on a block level
so we can perform block-level backups and write our software
appropriately.  AFAIK we don't have any documentation that outlines
that in a clear, concise manner.

With regards to providing protocol documentation and letting the
open-source community write the software, R1Soft is generally right.
Time and resources are the biggest problem with open-source; do not
think for a moment that just because millions of users can look at
source code means they understand it, or even know how to write it, or
will even *want* to.  The majority do/will not.

That said, I'd like to know exactly how low-level R1Soft's software
truly is.  dump(8), AFAIK, is block-level -- and that's a userland
program.  Does R1Soft's software *truly* require kernel-land?  I have
more to say on that issue (not against R1Soft, but speaking with regards
to the current state of FreeBSD's developer count) if it truly does.

I'm somewhat surprised that their software focuses on Linux and Windows
and not Solaris and Linux, especially given that they're interested in
dedicated server markets.  Solaris is always the first OS that comes
to my mind when talking about hardcore server operating systems.

 Continuous backups as well as bare-metal-restore seem to be a key  
 feature for many hosters.

Regarding continuous backups: the GEOM gate class could be used for
this.  Meaning, I think it could be used as an alternate to R1Soft's
software.

Regarding bare-metal restoration I'm not aware of how to do that under
FreeBSD, Linux, or even Solaris with ease.  In most cases, companies
develop their own PXE-booting environments which wipe the disks and
reinstall + restore data as they see fit.  There is no standard.

 FreeBSD is loosing users because of this issue.

Why does the number of FreeBSD users matter?  Quantity does not
necessarily represent quality.

I'm sorry for sounding anti-FreeBSD, but the reality is that people
should use whatever solutions work best for them -- if that's using
Windows, Solaris, or Linux, great!  Remember that open-source is about
choice: and choice means supporting the possibility that someone chooses
something else.  Blind one-sided advocacy is very damaging to the
open-source model and concept.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: gmirror prerequisite question SOLVED

2008-10-06 Thread Dino Vliet

 I've bought a secondary HDD to attach to my server running freebsd 7.0.
 I want to enable gmirror on it (will reinstall everything from scratch),

you don't have to.

but I want to know if my hardware is setup correctly as a prerequisite for 
doing this operation.

 The command

 dmesg | grep Seagate

 Yields:

 ad4: 76319MB Seagate ST380815AS 3.AAC at ata2-master UDMA33
 ad6: 76319MB Seagate ST380815AS 3.AAC at ata3-master UDMA33

yes it is.
 
*
Thanks for all your help! I managed to install it on my working system and it 
was a fairly simple procedure. Now I need to restructure my system because I've 
installed it as a desktop system, but want to use the system more like a server 
(database  ruby  weka ). So I will need to deinstall all installed packages 
like KDE4.1, Xorg, Firefox etc etc.
Will still need to figure that out (assuming a pkg_delete -a is what I need)
Brgds
Dino



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Can't add new 1TB disk in FreeBSD 6.1

On Mon, Oct 06, 2008 at 08:03:46AM -0700, Don O'Neil wrote:

  I just swapped out an old 500G disk with a 1TB one and I'm trying to 
  label it and mount it...
  
  If I run bsdlabel -w ad4, I get:
  
  bsdlabel: Geom not found
  
  If I run sysinstall, it tells me that it can't write to the disk.
  
  I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that 
  didn't help.
  
  Can anyone help me get this new disk installed without having to boot 
  off a recovery CD? The server is 500 miles away from me and I don't 
  have direct console access.
  Can you provide output from dmesg, as well as geom disk list?
 
 OK... I tried:
 
 # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000
 dd: /dev/ad4: Operation not permitted
 
 # fdisk /dev/ad4
 *** Working on device /dev/ad4 ***
 parameters extracted from in-core disklabel are:
 cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)
 
 Figures below won't work with BIOS for partitions not in cyl 1
 parameters to be used for BIOS calculations are:
 cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)
 
 fdisk: invalid fdisk partition table found
 Media sector size is 512
 Warning: BIOS sector numbering starts with sector 1
 Information from DOS bootblock is:
 The data for partition 1 is:
 sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
 start 63, size 1953525105 (953869 Meg), flag 80 (active)
 beg: cyl 0/ head 1/ sector 1;
 end: cyl 612/ head 15/ sector 63
 The data for partition 2 is:
 UNUSED
 The data for partition 3 is:
 UNUSED
 The data for partition 4 is:
 UNUSED


OK.   That looks pretty normal.

Did you try doing an: fdisk -I ad4   or  maybe  fdisk -BI ad4

It takes that to get fdisk to initialize the disk.
(the -B puts the master boot block there.

Just doing anfdisk ad4   only had fdisk read out stuff
and there isn't anything there yet to read - so of course
it is invalid.

jerry



 
 Geometry output:
 
 Geom name: ad4
 Providers:
 1. Name: ad4
Mediasize: 1000204886016 (932G)
Sectorsize: 512
Mode: r0w0e0
fwsectors: 63
fwheads: 16
 
 Nothing exciting coming from dmesg.
 
 
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Can't add new 1TB disk in FreeBSD 6.1

On Mon, Oct 06, 2008 at 12:07:08PM -0400, Jerry McAllister wrote:

 On Mon, Oct 06, 2008 at 08:03:46AM -0700, Don O'Neil wrote:
 
   I just swapped out an old 500G disk with a 1TB one and I'm trying to 
   label it and mount it...
   
   If I run bsdlabel -w ad4, I get:
   
   bsdlabel: Geom not found
   
   If I run sysinstall, it tells me that it can't write to the disk.
   
   I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but that 
   didn't help.
   
   Can anyone help me get this new disk installed without having to boot 
   off a recovery CD? The server is 500 miles away from me and I don't 
   have direct console access.
   Can you provide output from dmesg, as well as geom disk list?
  
  OK... I tried:
  
  # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000
  dd: /dev/ad4: Operation not permitted
  
  # fdisk /dev/ad4
  *** Working on device /dev/ad4 ***
  parameters extracted from in-core disklabel are:
  cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)
  
  Figures below won't work with BIOS for partitions not in cyl 1
  parameters to be used for BIOS calculations are:
  cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)
  
  fdisk: invalid fdisk partition table found
  Media sector size is 512
  Warning: BIOS sector numbering starts with sector 1
  Information from DOS bootblock is:
  The data for partition 1 is:
  sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
  start 63, size 1953525105 (953869 Meg), flag 80 (active)
  beg: cyl 0/ head 1/ sector 1;
  end: cyl 612/ head 15/ sector 63
  The data for partition 2 is:
  UNUSED
  The data for partition 3 is:
  UNUSED
  The data for partition 4 is:
  UNUSED
 
 
 OK.   That looks pretty normal.

Well, except for not allowing the dd to the disk.  
I haven't had that happen on a disk.  (I used to see that
a lot on DAT tapes)

So, maybe, as someone else suggested, you also need:

  OK... I tried:
  
  # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000
  dd: /dev/ad4: Operation not permitted
  
 Did you sysctl kern.geom.debugflags=16 before doing this?
  
 What's happening here is that GEOM isn't letting you overwrite the MBR
 on the disk.  Setting kern.geom.debugflags=16 should permit that to
 happen.
 

But, do the following too.  

 
 Did you try doing an: fdisk -I ad4   or  maybe  fdisk -BI ad4
 
 It takes that to get fdisk to initialize the disk.
 (the -B puts the master boot block there.
 
 Just doing anfdisk ad4   only had fdisk read out stuff
 and there isn't anything there yet to read - so of course
 it is invalid.
 
 jerry
 
 
 
  
  Geometry output:
  
  Geom name: ad4
  Providers:
  1. Name: ad4
 Mediasize: 1000204886016 (932G)
 Sectorsize: 512
 Mode: r0w0e0
 fwsectors: 63
 fwheads: 16
  
  Nothing exciting coming from dmesg.
  
  
  ___
  freebsd-questions@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to [EMAIL PROTECTED]
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

RE: Can't add new 1TB disk in FreeBSD 6.1


 On Mon, Oct 06, 2008 at 08:03:46AM -0700, Don O'Neil wrote:
 
   I just swapped out an old 500G disk with a 1TB one and I'm trying 
   to label it and mount it...
   
   If I run bsdlabel -w ad4, I get:
   
   bsdlabel: Geom not found
   
   If I run sysinstall, it tells me that it can't write to the disk.
   
   I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but 
   that didn't help.
   
   Can anyone help me get this new disk installed without having to 
   boot off a recovery CD? The server is 500 miles away from me and I 
   don't have direct console access.
   Can you provide output from dmesg, as well as geom disk list?
  
  OK... I tried:
  
  # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000
  dd: /dev/ad4: Operation not permitted
  
  # fdisk /dev/ad4
  *** Working on device /dev/ad4 *** parameters extracted from 
  in-core disklabel are:
  cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)
  
  Figures below won't work with BIOS for partitions not in cyl 1 
  parameters to be used for BIOS calculations are:
  cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)
  
  fdisk: invalid fdisk partition table found Media sector size is 512
  Warning: BIOS sector numbering starts with sector 1 Information from 
  DOS bootblock is:
  The data for partition 1 is:
  sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
  start 63, size 1953525105 (953869 Meg), flag 80 (active)
  beg: cyl 0/ head 1/ sector 1;
  end: cyl 612/ head 15/ sector 63 The data for partition 2 
  is:
  UNUSED
  The data for partition 3 is:
  UNUSED
  The data for partition 4 is:
  UNUSED
 
 
 OK.   That looks pretty normal.

 Well, except for not allowing the dd to the disk.  
 I haven't had that happen on a disk.  (I used to see that a lot on DAT
tapes)

 So, maybe, as someone else suggested, you also need:

  OK... I tried:
  
  # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000
  dd: /dev/ad4: Operation not permitted
  
 Did you sysctl kern.geom.debugflags=16 before doing this?
  
 What's happening here is that GEOM isn't letting you overwrite the MBR 
 on the disk.  Setting kern.geom.debugflags=16 should permit that to 
 happen.
 

 But, do the following too.  

 
 Did you try doing an: fdisk -I ad4   or  maybe  fdisk -BI ad4
 
 It takes that to get fdisk to initialize the disk.
 (the -B puts the master boot block there.
 
 Just doing anfdisk ad4   only had fdisk read out stuff
 and there isn't anything there yet to read - so of course it is 
 invalid.
 
 
  
  Geometry output:
  
  Geom name: ad4
  Providers:
  1. Name: ad4
 Mediasize: 1000204886016 (932G)
 Sectorsize: 512
 Mode: r0w0e0
 fwsectors: 63
 fwheads: 16
  
  Nothing exciting coming from dmesg.

I tried kern.geom.debugflags=16 originally, still doesn't help.

Someone else recommended running sade(8) and properly configuring this disk.
What is sade(8)? I don't have such an application on 6.1, and there is
nothing in the ports. I think that sade is a 7.0+ tool.

Any other ideas?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Can't add new 1TB disk in FreeBSD 6.1

On Mon, Oct 06, 2008 at 09:36:19AM -0700, Don O'Neil wrote:
 
  On Mon, Oct 06, 2008 at 08:03:46AM -0700, Don O'Neil wrote:
  
I just swapped out an old 500G disk with a 1TB one and I'm trying 
to label it and mount it...

If I run bsdlabel -w ad4, I get:

bsdlabel: Geom not found

If I run sysinstall, it tells me that it can't write to the disk.

I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but 
that didn't help.

Can anyone help me get this new disk installed without having to 
boot off a recovery CD? The server is 500 miles away from me and I 
don't have direct console access.
Can you provide output from dmesg, as well as geom disk list?
   
   OK... I tried:
   
   # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000
   dd: /dev/ad4: Operation not permitted
   
   # fdisk /dev/ad4
   *** Working on device /dev/ad4 *** parameters extracted from 
   in-core disklabel are:
   cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)
   
   Figures below won't work with BIOS for partitions not in cyl 1 
   parameters to be used for BIOS calculations are:
   cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)
   
   fdisk: invalid fdisk partition table found Media sector size is 512
   Warning: BIOS sector numbering starts with sector 1 Information from 
   DOS bootblock is:
   The data for partition 1 is:
   sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
   start 63, size 1953525105 (953869 Meg), flag 80 (active)
   beg: cyl 0/ head 1/ sector 1;
   end: cyl 612/ head 15/ sector 63 The data for partition 2 
   is:
   UNUSED
   The data for partition 3 is:
   UNUSED
   The data for partition 4 is:
   UNUSED
  
  
  OK.   That looks pretty normal.
 
  Well, except for not allowing the dd to the disk.  
  I haven't had that happen on a disk.  (I used to see that a lot on DAT
 tapes)
 
  So, maybe, as someone else suggested, you also need:
 
   OK... I tried:
   
   # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000
   dd: /dev/ad4: Operation not permitted
   
  Did you sysctl kern.geom.debugflags=16 before doing this?
   
  What's happening here is that GEOM isn't letting you overwrite the MBR 
  on the disk.  Setting kern.geom.debugflags=16 should permit that to 
  happen.
  
 
  But, do the following too.  
 
  
  Did you try doing an: fdisk -I ad4   or  maybe  fdisk -BI ad4
  
  It takes that to get fdisk to initialize the disk.
  (the -B puts the master boot block there.
  
  Just doing anfdisk ad4   only had fdisk read out stuff
  and there isn't anything there yet to read - so of course it is 
  invalid.
  
  
   
   Geometry output:
   
   Geom name: ad4
   Providers:
   1. Name: ad4
  Mediasize: 1000204886016 (932G)
  Sectorsize: 512
  Mode: r0w0e0
  fwsectors: 63
  fwheads: 16
   
   Nothing exciting coming from dmesg.
 
 I tried kern.geom.debugflags=16 originally, still doesn't help.

Can you please do it and then attempt the exact dd you ran above?

The reason I'm hounding: you're not providing a lot of detail between
whatever it is you're doing.  Just a lot of one-liner responses No
didn't work, next.  It's very difficult to discern what exactly you're
doing; for example, you could've run the sysctl and then attempted an
install, rather than re-execute the dd.

I can refer you to historic data that shows people have gotten the exact
error you're seeing when attempting to write to block 0 (MBR), stopped
by GEOM, which is why I'm a little wary.

 Someone else recommended running sade(8) and properly configuring this disk.
 What is sade(8)? I don't have such an application on 6.1, and there is
 nothing in the ports. I think that sade is a 7.0+ tool.

6.1?  Why?  This is a new install, right?  Is there some reason you're
installing 6.1 and not 6.3, or better yet, 7.0?  That's a separate
question, but it does make me wonder if something was fixed between 6.1
and 6.3/7.0 which might address this problem.

There is one thing about later FreeBSDs which I am aware of: 48-bit LBA
addressing.  I'm left wondering if what you're running into is a bug or
a problem with older FreeBSD (6.1) not supporting this.  I would have to
go back through CVS commit lots for ata(4) to find out when 48-bit LBA
was added.  I think 48-bit LBA support is required for disks 500GB.

sade(8) is the famous console UI for disk partitioning and labelling
inside of sysinstall.  It's a separate application, and was introduced
in FreeBSD 6.3.  You can get the exact same functionality out of
sysinstall on earlier FreeBSDs.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list

Re: USB mouse problems

On Mon, 2008-10-06 at 13:09 +0200, Patrick Lamaizière wrote:
 Le Mon, 06 Oct 2008 08:41:59 +0200,
 Aniruddha [EMAIL PROTECTED] a écrit :
 
  I have one Razer Lachesis USB mouse attached to the rear usb ports of
  my pc. This mouse has never worked, however when I plug in another USB
  mouse in the front of my pc it works?! I wonder; how do I get the
  Razer Lachesis working without plugging it in the front?
 
 I don't know.
 
  Furthermore I wondered if there is a way to use both the mouse in a
  terminal (gpm) and in xorg?
  
 Yes, see moused(8) and vidcontrol(1). 
 
 Regards.
 ___

Thanks for your help! I'll look into moused and vidcontrol. 


-- 
Regards,

Aniruddha




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: USB mouse problems

On Mon, 2008-10-06 at 22:10 +1030, Andrew D wrote:
 Patrick Lamaizière wrote:
  Le Mon, 06 Oct 2008 08:41:59 +0200,
  Aniruddha [EMAIL PROTECTED] a écrit :
  
  I have one Razer Lachesis USB mouse attached to the rear usb ports of
  my pc. This mouse has never worked, however when I plug in another USB
  mouse in the front of my pc it works?! I wonder; how do I get the
  Razer Lachesis working without plugging it in the front?
  
  I don't know.
 
 Some motherboards have a jumper (or BIOS option) to that has to be set, 
 so that the front connectors work at the expense of other ports.

I don't think this has something  to with a bios setting/jumper. My
other USB ports are working fine ( I also have an USB keyboard plugged
in).

Furthermore in Linux nor Vista I've encountered this problem. Therefor I
suspect it must have something to do with FreeBSD. Maybe it's an bug? If
someone has an solution that would be great!


-- 
Regards,

Aniruddha




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Can't add new 1TB disk in FreeBSD 6.1

On Mon, Oct 06, 2008 at 09:45:52AM -0700, Jeremy Chadwick wrote:
 There is one thing about later FreeBSDs which I am aware of: 48-bit LBA
 addressing.  I'm left wondering if what you're running into is a bug or
 a problem with older FreeBSD (6.1) not supporting this.  I would have to
 go back through CVS commit lots for ata(4) to find out when 48-bit LBA
 was added.  I think 48-bit LBA support is required for disks 500GB.

The issue I'm referring to has been touched on many times.

First and foremost, 6.1-RELEASE was released in May 2006.  Keep that
date in mind when reading the below.

The first incident, according to CVS commit logs, was adding 48-bit
LBA support, supporting disks 137GB.  That would've been in
RELENG_4, dated 2002/01/05.  FreeBSD 6.1 should have this.

Next, we have a commit dated 2003/01/19, affecting 48-bit LBA support
on Promise 66/100 controllers.  FreeBSD 6.1 should have this.

Next, 2004/12/09, talking about disk firmware bugs affecting 48-bit LBA
addressing, which was affecting a significant number of users.  That was
applied to HEAD and RELENG_5, so FreeBSD 6.1 (HEAD at that time)
should have this.

Next, 2005/04/14, something about read back the real taskfile
register values when in 48-bit mode.  Committed to HEAD, which would've
been during days shortly before RELENG_6 was tagged (6.0).

Next, 2005/08/17, support for working around controllers that can't
do DMA in 48-bit LBA mode, forcing the disk to use PIO mode allowing
the disk to address 137GB.  This was added to HEAD and RELENG_6, so
this should also exist in 6.1.

Next, 2007/12/13, also fix 48-bit LBA addressing issues, apparently
newe chips need 16-bit writes and not the usual FIFO thing.  This
was committed to HEAD first, RELENG_7 on 2008/01/09, and RELENG_6
on 2008/01/09.

This is one which FreeBSD 6.1 *would not* have fixes for.

I do not know if this is the problem -- I'm just speculating.

Because dmesg output was not provided (nothing interesting), we can't
tell what sort of controller your disks are hooked to, yadda yadda.
This is explicitly why I asked for that information.

If you could please try 7.0-STABLE or 7.1-PRERELEASE, that would be
highly recommended.  It would at least allow us to determine if you're
being affected by a bug in older FreeBSD, or if this is something that
is unique to your environment or applies to present-day FreeBSD.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

RE: Can't add new 1TB disk in FreeBSD 6.1

 
I just swapped out an old 500G disk with a 1TB one and I'm 
trying to label it and mount it...

If I run bsdlabel -w ad4, I get:

bsdlabel: Geom not found

If I run sysinstall, it tells me that it can't write to the disk.

I've tried an old 'bypass': sysctl kern.geom.debugflags=16, but 
that didn't help.

Can anyone help me get this new disk installed without having to 
boot off a recovery CD? The server is 500 miles away from me and 
I don't have direct console access.
Can you provide output from dmesg, as well as geom disk list?
   
   OK... I tried:
   
   # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000
   dd: /dev/ad4: Operation not permitted
   
   # fdisk /dev/ad4
   *** Working on device /dev/ad4 *** parameters extracted 
   from in-core disklabel are:
   cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)
   
   Figures below won't work with BIOS for partitions not in cyl 1 
   parameters to be used for BIOS calculations are:
   cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)
   
   fdisk: invalid fdisk partition table found Media sector size is 
   512
   Warning: BIOS sector numbering starts with sector 1 Information 
   from DOS bootblock is:
   The data for partition 1 is:
   sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
   start 63, size 1953525105 (953869 Meg), flag 80 (active)
   beg: cyl 0/ head 1/ sector 1;
   end: cyl 612/ head 15/ sector 63 The data for partition 2
   is:
   UNUSED
   The data for partition 3 is:
   UNUSED
   The data for partition 4 is:
   UNUSED
  
  
  OK.   That looks pretty normal.
 
  Well, except for not allowing the dd to the disk.  
  I haven't had that happen on a disk.  (I used to see that a lot on 
  DAT
 tapes)
 
  So, maybe, as someone else suggested, you also need:
 
   OK... I tried:
   
   # dd if=/dev/zero of=/dev/ad4 bs=512 count=1000
   dd: /dev/ad4: Operation not permitted
   
  Did you sysctl kern.geom.debugflags=16 before doing this?
   
  What's happening here is that GEOM isn't letting you overwrite the 
  MBR on the disk.  Setting kern.geom.debugflags=16 should permit that 
  to happen.
  
 
  But, do the following too.  
 
  
  Did you try doing an: fdisk -I ad4   or  maybe  fdisk -BI ad4
  
  It takes that to get fdisk to initialize the disk.
  (the -B puts the master boot block there.
  
  Just doing anfdisk ad4   only had fdisk read out stuff
  and there isn't anything there yet to read - so of course it is 
  invalid.
  
  
   
   Geometry output:
   
   Geom name: ad4
   Providers:
   1. Name: ad4
  Mediasize: 1000204886016 (932G)
  Sectorsize: 512
  Mode: r0w0e0
  fwsectors: 63
  fwheads: 16
   
   Nothing exciting coming from dmesg.
 
 I tried kern.geom.debugflags=16 originally, still doesn't help.

 Can you please do it and then attempt the exact dd you ran above?

# sysctl kern.geom.debugflags=16
kern.geom.debugflags: 16 - 16

# dd if=/dev/zero of=/dev/ad4 bs=512 count=1000
dd: /dev/ad4: Operation not permitted

The reason I'm hounding: you're not providing a lot of detail between
whatever it is you're doing.  Just a lot of one-liner responses No didn't
work, next.  It's very difficult to discern what exactly you're doing; for
example, you could've run the sysctl and then attempted an install, rather
than re-execute the dd.

I did exactly as you suggested, and I've posed all my results here... I'm
scratching my head on this one as much as you are.

I can refer you to historic data that shows people have gotten the exact
error you're seeing when attempting to write to block 0 (MBR), stopped by
GEOM, which is why I'm a little wary.

 Someone else recommended running sade(8) and properly configuring this
disk.
 What is sade(8)? I don't have such an application on 6.1, and there is 
 nothing in the ports. I think that sade is a 7.0+ tool.

6.1?  Why?  This is a new install, right?  Is there some reason you're
installing 6.1 and not 6.3, or better yet, 7.0?  That's a separate
question, but it does make me wonder if something was fixed between 6.1 and
6.3/7.0 which might address this problem.

No, it's not a new install, I'm just trying to add a new disk on an older
server. I REALLY don't want to do an OS upgrade at this point on a
production box that is running fine. We do that 1x a year, and I'm not in
the mood to do it just to add a bigger disk.

There is one thing about later FreeBSDs which I am aware of: 48-bit LBA
addressing.  I'm left wondering if what you're running into is a bug or a
problem with older FreeBSD (6.1) not supporting this.  I would have to go
back through CVS commit lots for ata(4) to find out when 48-bit LBA was
added.  I think 48-bit LBA support is required for disks 500GB.

Thart's a good point...  I'll have to look into that to see when the 48 bit
LBA was added. HOWEVER, I believe 48 bit LBA was needed for anything 248
GB, and I had a 500 G drive in there before. I had this EXACT

Re: USB mouse problems

On Mon, Oct 06, 2008 at 06:52:22PM +0200, Aniruddha wrote:
 On Mon, 2008-10-06 at 22:10 +1030, Andrew D wrote:
  Patrick Lamaizière wrote:
   Le Mon, 06 Oct 2008 08:41:59 +0200,
   Aniruddha [EMAIL PROTECTED] a écrit :
   
   I have one Razer Lachesis USB mouse attached to the rear usb ports of
   my pc. This mouse has never worked, however when I plug in another USB
   mouse in the front of my pc it works?! I wonder; how do I get the
   Razer Lachesis working without plugging it in the front?
   
   I don't know.
  
  Some motherboards have a jumper (or BIOS option) to that has to be set, 
  so that the front connectors work at the expense of other ports.
 
 I don't think this has something  to with a bios setting/jumper. My
 other USB ports are working fine ( I also have an USB keyboard plugged
 in).
 
 Furthermore in Linux nor Vista I've encountered this problem. Therefor I
 suspect it must have something to do with FreeBSD. Maybe it's an bug? If
 someone has an solution that would be great!

FreeBSD's existing USB stack is known to be... shall we say, flaky.
It's well-established at this point.  The possibility of it being
related to FreeBSD's USB stack is very likely.

A new USB stack is available for CURRENT, but requires manual patching.
If you're willing to try this, you should get in contact with Alfred
Perlstein [EMAIL PROTECTED] to discuss/get the patch.  Keep in mind
that this patch, as I stated, only applies to CURRENT, and not to
FreeBSD 7 or earlier.

You can download a CURRENT ISO here:

ftp://ftp4.freebsd.org/pub/FreeBSD/snapshots/200809/

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

analyzing freebsd core dumps

2008-10-06 Thread Mister Olli

hi list...

I have a freebsd maschine running for more 6 months without any
problems.
the machine's only service is to be an openvpn gateway for a hand of
users.

2 weeks ago the first problems started. the openvpn exited with signal
11 and 4 and core dumps were written.

the same happend yesterday with the postfix/cleanup process, and the
suddenly the machine rebooted without any further log messages.

what is the best way to troubleshoot the cause of this problem?

greetz
olli

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: continuous backup solution for freebsd?

First of all, I am not an r1soft advocate, but they seem to be making a 
software which is popular and affordable and interested in giving 
FreeBSD support... r1soft is not the issue here, the problem is that 
there is no way to do near continuous backups on FreeBSD servers.


Jeremy Chadwick wrote:


That said, I'd like to know exactly how low-level R1Soft's software
truly is.  dump(8), AFAIK, is block-level -- and that's a userland
program.  Does R1Soft's software *truly* require kernel-land?  I have
more to say on that issue (not against R1Soft, but speaking with regards
to the current state of FreeBSD's developer count) if it truly does.


I think you might not have understood the concept of near continuous 
backups. The R1Soft backup monitors the filesystem operations and backs 
up written blocks. So it has to know what is written and when to be able 
to back it up. The dump command simply reads/writes the blocks. It cant 
only read changed blocks. It has to read the whole thing (inefficient).


Continuous backups as well as bare-metal-restore seem to be a key  
feature for many hosters.


Regarding continuous backups: the GEOM gate class could be used for
this.  Meaning, I think it could be used as an alternate to R1Soft's
software.


The GEOM gate allows mirroring to a remote machine, am I not right? That 
would be more or less same as same as using RAID. The continuous backup 
(or near continuous) means that you can restore the filesystem to a 
point like 15 minutes ago, or 1 hour ago. Besides, I hear geom might 
have network delay problems and it is much more complicated setup to 
build two machines in mirror configuration just for backup purposes as 
well as you cant restore to a point in the past.



Regarding bare-metal restoration I'm not aware of how to do that under
FreeBSD, Linux, or even Solaris with ease.  In most cases, companies
develop their own PXE-booting environments which wipe the disks and
reinstall + restore data as they see fit.  There is no standard.


OK. Actually there is more than one solution which can do 
bare-metal-restores for FreeBSD also. However those solutions at best 
rely on nightly backups of the filesystems. With R1Soft, you can restore 
the system to only few minutes before the total meltdown.


Unrelated to bare metal restore, with normal backups you are not taking 
backups of files which are created/deleted often. For example this can 
be customer mails or if a hacker hacks the box and removes his trails. 
Even sometimes customers upload some file and remove from their computer 
the same they and then accidentally remove from the server. With R1Soft 
backup the data would go into the backup server right away and you an 
restore every single file independent of when it was put or removed.



FreeBSD is loosing users because of this issue.


Why does the number of FreeBSD users matter?  Quantity does not
necessarily represent quality.


Thats a perfectly fine statement. But a quality product would be nothing 
without users. As well as this problem effects the quality. Consider a 
system which has sensitive data which shouldnt get lost, with continuous 
data protecton you can restore such failed system to only few minutes 
before the failure point. Doing this is currently impossible with 
FreeBSD. Best we can do is to return to previous snapshot taken (which 
might be a day old). This is an important design criteria since 
restoring the lost data might be time consuming and expensive. Thge 
issue is not even r1soft, they are just the most popular company giving 
such solution, only if there was at least one backup solution which 
could provide near continuous data protection...


In addition to this, near continuous backups create less load on boxes 
with a lot of reads but little writes. Standart backups have to scan all 
the files to detect which files were changed.



I'm sorry for sounding anti-FreeBSD, but the reality is that people
should use whatever solutions work best for them -- if that's using
Windows, Solaris, or Linux, great!  Remember that open-source is about
choice: and choice means supporting the possibility that someone chooses
something else.  Blind one-sided advocacy is very damaging to the
open-source model and concept.


I agree, and please dont shoot the messenger :) I just have a bunch of 
customers who would use FreeBSD but not using only because of this 
problem. In addition to that I myself would like to use near continuous 
backups as well.


I was just trying to inform the FreeBSD community here so if somebody 
can have some time to divert to giving the right advices to r1soft then 
we all could benefit from it. It doesnt even have to be free even, with 
a reasonable price they can probably hire somebody to work for building 
the basics of this feature.


So the real question is, is there anybody who is willing and have the 
experience to help on this issue?


Thanks,
Evren
___

carp no working after upgrade

2008-10-06 Thread Gábri Máté

Dear List,
i have a FreeBSD 7-release cluster firewall using carp for the public IP
addresses. Last evening i've upgraded one of the firewalls to 7-release-p5
and after that carp stopped working. The two nodes can't understang each
others cap packets so both of them are in master state. Does p5 differs from
the original release so that the carp packets are different two?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: analyzing freebsd core dumps

On Mon, Oct 06, 2008 at 08:04:07AM +0200, Mister Olli wrote:
 hi list...
 
 I have a freebsd maschine running for more 6 months without any
 problems.
 the machine's only service is to be an openvpn gateway for a hand of
 users.
 
 2 weeks ago the first problems started. the openvpn exited with signal
 11 and 4 and core dumps were written.
 
 the same happend yesterday with the postfix/cleanup process, and the
 suddenly the machine rebooted without any further log messages.
 
 what is the best way to troubleshoot the cause of this problem?

Signal 11 happening out of no where on machines which have been
running fine, most of the time, is a sign of hardware failure (usually
RAM, but sometimes motherboard or PSU).  The fact you got a reboot is
also further evidence of this.

http://www.freebsd.org/doc/en/books/faq/troubleshoot.html#SIGNAL11

I would recommend taking the machine offline and running something like
memtest86+ on it for 6-7 hours.  Any errors seen are a pretty good sign
that you should replace the memory or the motherboard.  You can
download an ISO or floppy disk images here:

http://www.memtest.org/

Bottom line is that this is probably a hardware issue.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: USB mouse problems

On Mon, 2008-10-06 at 10:05 -0700, Jeremy Chadwick wrote:
  I don't think this has something  to with a bios setting/jumper. My
  other USB ports are working fine ( I also have an USB keyboard plugged
  in).
  
  Furthermore in Linux nor Vista I've encountered this problem. Therefor I
  suspect it must have something to do with FreeBSD. Maybe it's an bug? If
  someone has an solution that would be great!
 
 FreeBSD's existing USB stack is known to be... shall we say, flaky.
 It's well-established at this point.  The possibility of it being
 related to FreeBSD's USB stack is very likely.
 
 A new USB stack is available for CURRENT, but requires manual patching.
 If you're willing to try this, you should get in contact with Alfred
 Perlstein [EMAIL PROTECTED] to discuss/get the patch.  Keep in mind
 that this patch, as I stated, only applies to CURRENT, and not to
 FreeBSD 7 or earlier.
 
 You can download a CURRENT ISO here:
 
 ftp://ftp4.freebsd.org/pub/FreeBSD/snapshots/200809/
 

Lol, during my search for a solution I did see numerous problems with
mice. Out of curiosity; is CURRENT the same as FreeBSD 7.1-BETA?


-- 
Regards,

Aniruddha




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: continuous backup solution for freebsd?

2008-10-06 Thread Roland Smith

On Mon, Oct 06, 2008 at 12:58:30PM +0300, Evren Yurtesen wrote:
 Hello,
 
 Is there a known continuous backup solution similar to r1soft backup for 
 FreeBSD? I googled a lot but couldnt find anything.

I don't think so. The closest thing I know of is rsnapshot
(http://www.rsnapshot.org/). 

My solution is to run rsync in a cron job. In my situation this takes
about 5 minutes for approximately 100GB of data. The time it takes will
obviously depend on the rate of change in the data.

You could also use local snapshots with mksnap_ffs(8), to solve the oh
shit I deleted my files situation.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpy2oCjkIRDg.pgp
Description: PGP signature

Re: analyzing freebsd core dumps

On Mon, Oct 06, 2008 at 10:18:09AM -0700, Jeremy Chadwick wrote:

 On Mon, Oct 06, 2008 at 08:04:07AM +0200, Mister Olli wrote:
  hi list...
  
  I have a freebsd maschine running for more 6 months without any
  problems.
  the machine's only service is to be an openvpn gateway for a hand of
  users.
  
  2 weeks ago the first problems started. the openvpn exited with signal
  11 and 4 and core dumps were written.
  
  the same happend yesterday with the postfix/cleanup process, and the
  suddenly the machine rebooted without any further log messages.
  
  what is the best way to troubleshoot the cause of this problem?
 
 Signal 11 happening out of no where on machines which have been
 running fine, most of the time, is a sign of hardware failure (usually
 RAM, but sometimes motherboard or PSU).  The fact you got a reboot is
 also further evidence of this.
 
 http://www.freebsd.org/doc/en/books/faq/troubleshoot.html#SIGNAL11
 
 I would recommend taking the machine offline and running something like
 memtest86+ on it for 6-7 hours.  Any errors seen are a pretty good sign
 that you should replace the memory or the motherboard.  You can
 download an ISO or floppy disk images here:
 
 http://www.memtest.org/
 
 Bottom line is that this is probably a hardware issue.

Could also be a contacts if it is not the actual memory or board.
A marginal contact where something is plugged in can over time
build up deposits that make it fail.   Of course, this is still
a hardware problem, but can often be cured by reseating everything.
If it is bad enough, it could also be exacerbated by reseating 
everything.

jerry

 
 -- 
 | Jeremy Chadwickjdc at parodius.com |
 | Parodius Networking   http://www.parodius.com/ |
 | UNIX Systems Administrator  Mountain View, CA, USA |
 | Making life hard for others since 1977.  PGP: 4BD6C0CB |
 
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: continuous backup solution for freebsd?

On Mon, Oct 06, 2008 at 08:07:30PM +0300, Evren Yurtesen wrote:
 First of all, I am not an r1soft advocate, but they seem to be making a  
 software which is popular and affordable and interested in giving  
 FreeBSD support... r1soft is not the issue here, the problem is that  
 there is no way to do near continuous backups on FreeBSD servers.

 Jeremy Chadwick wrote:

 That said, I'd like to know exactly how low-level R1Soft's software
 truly is.  dump(8), AFAIK, is block-level -- and that's a userland
 program.  Does R1Soft's software *truly* require kernel-land?  I have
 more to say on that issue (not against R1Soft, but speaking with regards
 to the current state of FreeBSD's developer count) if it truly does.

 I think you might not have understood the concept of near continuous  
 backups. The R1Soft backup monitors the filesystem operations and backs  
 up written blocks. So it has to know what is written and when to be able  
 to back it up. The dump command simply reads/writes the blocks. It cant  
 only read changed blocks. It has to read the whole thing (inefficient).

It depends on how it's implemented, but in general, yes, I guess this
would advocate reliance on GEOM, which would be kernel.  The thing is,
the GEOM gate class could be extended to handle this situation -- it's
a class intended for filesystem replication in real-time, over a
network.

That said, I shall unleash with the comments I had originally planned on
including, but removed them since I felt it might be too hasty of me.

The sad reality with FreeBSD is that we do not have enough clueful folks
who are familiar with the kernel innards.  Those who are clueful are
very busy (with other things, and with real life), and often do not have
the time to give direct/constant focus on a single item for long periods
of time.  I have a mental list of those who are absolutely incredible
FreeBSD developers (and I will name one of them: pjd@, who should be
given tens of thousands of dollars, IMHO, for his work on bringing ZFS
to FreeBSD), but the list is small compared to how many *users* we have.

The learning curve for getting familiar with pieces of the FreeBSD
kernel is astoundingly large.  I myself have tried it on a couple of
occasions, but lack of concise and up-to-date documentation makes it
very difficult to accomplish.  (I'm familiar with very old operating
systems, such as MS-DOS, ProDOS, and GS/OS on the Apple IIGS -- FreeBSD
is far from those).  Books are also not of much help, as I've been told
that the existing book which covers FreeBSD engineering models is long
outdated and that many pieces now are completely different.  A
complete and total moral killer right there.  The book is for FreeBSD
5.2, by the way.

We cannot rely on the FreeBSD Documentation folks to write the necessary
docs either, because they do not have the knowledge of the kernel to
write such.  As someone who's written software, I can assure you that
the only way to get good documentation for low-level pieces is to write
the documentation in parallel to the code; otherwise, you end up with
lots of after-the-fact reverse engineering efforts, which takes tons
of time, and requires a lot of communication between the code author(s)
and the documenters.  We're talking thousands of hours here.

Requiring the user/developer to reverse-engineer hundreds of thousands
of lines of C code is not reasonable/plausible; hardly anyone is
willing to do that for free.

This is why Linux often has the upper hand: they have multiple eyes and
individuals fully familiar with different pieces of the kernel.  If one
or two people go on hiatus or disappear (death, life, whatever), the
existing kernel piece does not sit in limbo for years -- there are other
people to pick up the responsibilities.  Much of the FreeBSD kernel and
device layer does not have this degree of freedom; much is
single-person, single-maintainer, single-point-of-failure.

Then there's commercial company support -- by that I mean, actual
hardware vendors that support the OS.  FreeBSD has some of this, but
most are very small companies (few employees), with limited funds,
or have very *very* limited/specific focus; there are a couple big
ones, but they are few and far between.  Linux has hundreds, and many
of the vendors are *very* large.  In fact, the support is so large
that freelance Linux developers are able to get things like development
PCI boards for new NICs from the vendors directly; FreeBSD?  Rare.  What
this means is that the commercial world takes Linux seriously, while
FreeBSD not so.  Sorry, but that's reality.

It amazes me how easy someone can pick up programming something in
kernel-land for Linux, while for FreeBSD it just doesn't happen on a
regular basis.  When I see it happen, it's bizarre -- suddenly out of no
where comes this one fellow (we'll call him Bob), appearing on a mailing
list with a bunch of patches.  Heard of him before?  Nope, but here he
is, and somehow he engineered all of

Re: continuous backup solution for freebsd?

2008-10-06 Thread Mel

On Monday 06 October 2008 19:07:30 Evren Yurtesen wrote:
 First of all, I am not an r1soft advocate, but they seem to be making a
 software which is popular and affordable and interested in giving
 FreeBSD support... r1soft is not the issue here, the problem is that
 there is no way to do near continuous backups on FreeBSD servers.

 Jeremy Chadwick wrote:
  That said, I'd like to know exactly how low-level R1Soft's software
  truly is.  dump(8), AFAIK, is block-level -- and that's a userland
  program.  Does R1Soft's software *truly* require kernel-land?  I have
  more to say on that issue (not against R1Soft, but speaking with regards
  to the current state of FreeBSD's developer count) if it truly does.

 I think you might not have understood the concept of near continuous
 backups. The R1Soft backup monitors the filesystem operations

So does ggate. But read on.

 So it has to know what is written and when to be able 
 to back it up. The dump command simply reads/writes the blocks. It cant
 only read changed blocks. It has to read the whole thing (inefficient).

But Jeremy's point being, dump(8) does not need /dev/special_device to 
read/write at block level.

  Continuous backups as well as bare-metal-restore seem to be a key
  feature for many hosters.
 
  Regarding continuous backups: the GEOM gate class could be used for
  this.  Meaning, I think it could be used as an alternate to R1Soft's
  software.

 The GEOM gate allows mirroring to a remote machine, am I not right? That
 would be more or less same as same as using RAID. The continuous backup
 (or near continuous) means that you can restore the filesystem to a
 point like 15 minutes ago, or 1 hour ago. Besides, I hear geom might
 have network delay problems and it is much more complicated setup to
 build two machines in mirror configuration just for backup purposes as
 well as you cant restore to a point in the past.

I think once you and R1soft step out of the I need a block level device 
paradigm, you will see that modifying ggate with a copy and fall through 
mode, as well as a mechanism to block writes to the local provider, when the 
remote provider wants to write is the best solution all around and your best 
bet to get support for it.
Right now, ggate does intercept and redirect, but the concept of copy and 
fall through is not that far away. Bringing the R1soft devs in contact with 
the FreeBSD geom list and having them browse the sys/geom/ggate sources to 
see how trivial it is to hook into filesystem operations would be the course 
of action I'd recommend.

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: USB mouse problems

On Mon, Oct 06, 2008 at 07:23:00PM +0200, Aniruddha wrote:
 On Mon, 2008-10-06 at 10:05 -0700, Jeremy Chadwick wrote:
   I don't think this has something  to with a bios setting/jumper. My
   other USB ports are working fine ( I also have an USB keyboard plugged
   in).
   
   Furthermore in Linux nor Vista I've encountered this problem. Therefor I
   suspect it must have something to do with FreeBSD. Maybe it's an bug? If
   someone has an solution that would be great!
  
  FreeBSD's existing USB stack is known to be... shall we say, flaky.
  It's well-established at this point.  The possibility of it being
  related to FreeBSD's USB stack is very likely.
  
  A new USB stack is available for CURRENT, but requires manual patching.
  If you're willing to try this, you should get in contact with Alfred
  Perlstein [EMAIL PROTECTED] to discuss/get the patch.  Keep in mind
  that this patch, as I stated, only applies to CURRENT, and not to
  FreeBSD 7 or earlier.
  
  You can download a CURRENT ISO here:
  
  ftp://ftp4.freebsd.org/pub/FreeBSD/snapshots/200809/
  
 
 Lol, during my search for a solution I did see numerous problems with
 mice. Out of curiosity; is CURRENT the same as FreeBSD 7.1-BETA?

No -- significantly different.  CURRENT is super alpha it's probably
going to break, while 7.1-BETA is simply the upcoming release of 7.1
which is slated to become -STABLE after a few months.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Coretemp seems to be off quite a bit

On Mon, Oct 06, 2008 at 09:39:40AM -0500, Kirk Strauser wrote:
 I have a Gigabyte motherboard with an Intel ICH-9 chipset, and a 3.0GHz 
 Core 2 Duo (E8400).  The coretemp sysctls seem to always show 50C as the 
 baseline temperature:

 $ sysctl dev.cpu | grep temp
 dev.cpu.0.temperature: 50
 dev.cpu.1.temperature: 50

 This is with a big PSU fan, a good CPU fan, a clean heatsink, and two  
 case fans aimed the right direction (front fan pulling cool air in, rear 
 fan pushing warm air out).  If I reboot and go into the BIOS, I get 
 numbers around 42-43C.

First and foremost: there is always the possibility of a bug in
coretemp(4).  I'm not dissuading that possibility, but let's talk about
the other aspects first.

There is a common misconception that what the BIOS reports is the on-die
CPU temperature.  This is often not the case.  In 90% of the
motherboards out there, the temperatures shown in the BIOS are taken
from external sensors: that is to say, a thermistor on the motherboard
intended for monitoring system temperature.  This is very different from
the on-die processor core temperatures that coretemp(4) shows.

You didn't state what exact model of Gigabyte motherboard you're using,
nor did you state what BIOS version, so I can't help here.  But all
of these boards come with 1) the ability to monitor voltages, 2) the
ability to monitor fan RPMs, and 2) the ability to monitor temperatures.
All of these requires an external H/W monitoring IC, which *is not*
the same thing coretemp(4) reports.

Secondly, if the BIOS does in fact report on-die core temperatures,
then there is a certain amount of differential which should be allowed.
That's often 4-5C, believe it or not.  The BIOS has a tendency to run
hotter, because it does not do things such as execute HLT instructions
on idle processors and so on, like FreeBSD, Linux, and Windows do.

Thirdly, there is a known issue with on-die temperature reporting.  On
my E6550, the Windows program called RMClock reports my cores at
something like 56C each, yet CoreTemp (which uses the same data) reports
them at 36C.  While on my Q9550, all cores are reported properly in both
CoreTemp and RMClock (about 30-36C per core; the variance between cores
is normal).

The 20C difference seen on my E6550 between RMClock and CoreTemp has to
do with something called TJunction, or at least that's what I'm told
by the RMClock author.  You can Google for that term and see exactly
what I'm talking about.  Different software authors implement the
calculation formula differently.

http://www.alcpu.com/CoreTemp/howitworks.html

Finally, there's also something called TjunctionMax, which is the
temperature point where if any of the cores reach, will result in the
processor literally shutting off.  CoreTemp also shows this.  I believe
it's set to 85C on my E6550, while 100C on my Q9550.  God forbid the
temperatures ever reach that.

 I know it's kind of hard to compare directly, but the coretemp numbers
 are from a totally idle system with powerd scaling it back to 373MHz,
 so it should be as cool as when sitting idle in the BIOS screens.
 When I work the system hard, like running make -j4 buildworld, I see
 temperatures up around 63-64C, and I'm almost positive that's not
 right.

If at all possible, boot Windows and run CoreTemp.  If the numbers shown
there are identical to what FreeBSD shows (give or take a couple
degrees), then they are correct.  If Windows is not an option, surely
Linux has something that can show core temperatures.

Be aware that the stock retail heatsink/fan on Intel CPUs is known to be
*horrible* at cooling, and after a few months of use will become noisy
as hell.

If you're using your own heatsink/fan, I highly recommend you consider
removing it and reseating it.  The temperatures you're reporting, in or
out of the BIOS, are what I consider high.  I used to see ~36-37C
on my E6550 per core when idling, and ~43-44C under load.  On my Q9550 I
see ~30-36C on idle, and 40-42C on load.

 Any ideas why coretemp and the BIOS would show such different numbers?

See above.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

RE: Can't add new 1TB disk in FreeBSD 6.1

 On Mon, Oct 06, 2008 at 09:45:52AM -0700, Jeremy Chadwick wrote:
  There is one thing about later FreeBSDs which I am aware of: 48-bit 
  LBA addressing.  I'm left wondering if what you're running 
 into is a 
  bug or a problem with older FreeBSD (6.1) not supporting this.  I 
  would have to go back through CVS commit lots for ata(4) to 
 find out 
  when 48-bit LBA was added.  I think 48-bit LBA support is 
 required for disks 500GB.
 
 The issue I'm referring to has been touched on many times.
 
 First and foremost, 6.1-RELEASE was released in May 2006.  
 Keep that date in mind when reading the below.
 
 The first incident, according to CVS commit logs, was adding 
 48-bit LBA support, supporting disks 137GB.  That would've 
 been in RELENG_4, dated 2002/01/05.  FreeBSD 6.1 should have this.
 
 Next, we have a commit dated 2003/01/19, affecting 48-bit LBA 
 support on Promise 66/100 controllers.  FreeBSD 6.1 should have this.
 
 Next, 2004/12/09, talking about disk firmware bugs affecting 
 48-bit LBA addressing, which was affecting a significant 
 number of users.  That was applied to HEAD and RELENG_5, so 
 FreeBSD 6.1 (HEAD at that time) should have this.
 
 Next, 2005/04/14, something about read back the real 
 taskfile register values when in 48-bit mode.  Committed to 
 HEAD, which would've been during days shortly before RELENG_6 
 was tagged (6.0).
 
 Next, 2005/08/17, support for working around controllers 
 that can't do DMA in 48-bit LBA mode, forcing the disk to 
 use PIO mode allowing the disk to address 137GB.  This was 
 added to HEAD and RELENG_6, so this should also exist in 6.1.
 
 Next, 2007/12/13, also fix 48-bit LBA addressing issues, 
 apparently newe chips need 16-bit writes and not the usual 
 FIFO thing.  This was committed to HEAD first, RELENG_7 on 
 2008/01/09, and RELENG_6 on 2008/01/09.
 
 This is one which FreeBSD 6.1 *would not* have fixes for.
 
 I do not know if this is the problem -- I'm just speculating.
 
 Because dmesg output was not provided (nothing 
 interesting), we can't tell what sort of controller your 
 disks are hooked to, yadda yadda.
 This is explicitly why I asked for that information.
 
 If you could please try 7.0-STABLE or 7.1-PRERELEASE, that 
 would be highly recommended.  It would at least allow us to 
 determine if you're being affected by a bug in older FreeBSD, 
 or if this is something that is unique to your environment or 
 applies to present-day FreeBSD.

The hardware I have is the built in SATA controller on the motherboard,
which is GIGABYTE GA-M61P-S3. With the NVIDIA GeForce 6100 / nForce 430 and
Super I/O chip: ITE IT8716.  

Dmesg had no output pertaining to the partition/format/dd, etc... Just
messages from my ftp daemon. If you're wanting to see the boot messages,
this is from the last time I rebooted when I installed the disk:

Oct  4 04:07:30 kermit kernel: Copyright (c) 1992-2006 The FreeBSD Project.
Oct  4 04:07:30 kermit kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988,
1989, 1991, 1992, 1993, 1994
Oct  4 04:07:30 kermit kernel: The Regents of the University of California.
All rights reserved.
Oct  4 04:07:30 kermit kernel: FreeBSD 6.1-STABLE-200608 #0: Mon Mar 19
22:52:31 PDT 2007
Oct  4 04:07:30 kermit kernel:
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/KERMIT
Oct  4 04:07:30 kermit kernel: ACPI APIC Table: GBTNVDAACPI
Oct  4 04:07:30 kermit kernel: Timecounter i8254 frequency 1193182 Hz
quality 0
Oct  4 04:07:30 kermit kernel: CPU: AMD Athlon(tm) 64 X2 Dual Core Processor
5200+ (2611.90-MHz 686-class CPU)
Oct  4 04:07:30 kermit kernel: Origin = AuthenticAMD  Id = 0x40f32
Stepping = 2
Oct  4 04:07:30 kermit kernel:
Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA
,CMOV,PAT,PSE36,CLFLUSH,MMX,F
XSR,SSE,SSE2,HTT
Oct  4 04:07:30 kermit kernel: Features2=0x2001SSE3,CX16
Oct  4 04:07:30 kermit kernel: AMD
Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow+,3DNow
Oct  4 04:07:30 kermit kernel: AMD Features2=0x1fLAHF,CMP,b2,b3,CR8
Oct  4 04:07:30 kermit kernel: Cores per package: 2
Oct  4 04:07:30 kermit kernel: real memory  = 3724476416 (3551 MB)
Oct  4 04:07:30 kermit kernel: avail memory = 3647496192 (3478 MB)
Oct  4 04:07:30 kermit kernel: FreeBSD/SMP: Multiprocessor System Detected:
2 CPUs
Oct  4 04:07:30 kermit kernel: cpu0 (BSP): APIC ID:  0
Oct  4 04:07:30 kermit kernel: cpu1 (AP): APIC ID:  1
Oct  4 04:07:30 kermit kernel: ioapic0: Changing APIC ID to 2
Oct  4 04:07:30 kermit kernel: ioapic0 Version 1.1 irqs 0-23 on
motherboard
Oct  4 04:07:30 kermit kernel: kbd1 at kbdmux0
Oct  4 04:07:30 kermit kernel: acpi0: GBT NVDAACPI on motherboard
Oct  4 04:07:30 kermit kernel: acpi_bus_number: can't get _ADR
Oct  4 04:07:30 kermit kernel: acpi_bus_number: can't get _ADR
Oct  4 04:07:30 kermit kernel: acpi0: Power Button (fixed)
Oct  4 04:07:30 kermit kernel: acpi_bus_number: can't get _ADR
Oct  4 04:07:30 kermit kernel: acpi_bus_number: can't get _ADR
Oct  4 04:07:30 kermit kernel:

Re: continuous backup solution for freebsd?

2008-10-06 Thread Julien Cigar

Sorry for once more but: you can make incremental backups every x
minutes with Bacula too .. it only takes one or two minutes on my box to
scan for changed files for ~150GB (even faster if you tweak it a bit).
It's not really a true continuous backup solution, but it's perfectly
possible to restore directories/files for changes which occurred x
minutes ago, and with retention periods of x days/months/years.

On Mon, 2008-10-06 at 19:38 +0200, Roland Smith wrote:
 On Mon, Oct 06, 2008 at 12:58:30PM +0300, Evren Yurtesen wrote:
  Hello,
  
  Is there a known continuous backup solution similar to r1soft backup for 
  FreeBSD? I googled a lot but couldnt find anything.
 
 I don't think so. The closest thing I know of is rsnapshot
 (http://www.rsnapshot.org/). 
 
 My solution is to run rsync in a cron job. In my situation this takes
 about 5 minutes for approximately 100GB of data. The time it takes will
 obviously depend on the rate of change in the data.
 
 You could also use local snapshots with mksnap_ffs(8), to solve the oh
 shit I deleted my files situation.
 
 Roland

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Can't add new 1TB disk in FreeBSD 6.1

On Mon, Oct 06, 2008 at 11:08:34AM -0700, Don O'Neil wrote:
 The hardware I have is the built in SATA controller on the motherboard,
 which is GIGABYTE GA-M61P-S3. With the NVIDIA GeForce 6100 / nForce 430 and
 Super I/O chip: ITE IT8716.  

 Oct  4 04:07:30 kermit kernel: atapci0: GENERIC ATA controller port 
 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0
 Oct  4 04:07:30 kermit kernel: ata0: ATA channel 0 on atapci0
 Oct  4 04:07:30 kermit kernel: ata1: ATA channel 1 on atapci0
 Oct  4 04:07:30 kermit kernel: pci0: bridge at device 7.0 (no driver 
 attached)
 Oct  4 04:07:30 kermit kernel: atapci1: GENERIC ATA controller port 
 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd000-0xd00f mem 
 0xf7004000-0xf7004fff irq 20 at device 8.0 on pci0
 Oct  4 04:07:30 kermit kernel: ata2: ATA channel 0 on atapci1
 Oct  4 04:07:30 kermit kernel: ata3: ATA channel 1 on atapci1
 Oct  4 04:07:30 kermit kernel: atapci2: GENERIC ATA controller port 
 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xe400-0xe40f mem 
 0xf700-0xf7000fff irq 21 at device 8.1 on pci0
 Oct  4 04:07:30 kermit kernel: ata4: ATA channel 0 on atapci2
 Oct  4 04:07:30 kermit kernel: ata5: ATA channel 1 on atapci2
 Oct  4 04:07:30 kermit kernel: ad0: 76293MB Maxtor 6L080P0 BAH41G10 at 
 ata0-master UDMA33
 Oct  4 04:07:30 kermit kernel: ad4: 953869MB Seagate ST31000340AS SD15 at 
 ata2-master UDMA33

This motherboard uses the nForce 430, but the SATA portion is actually a
subset chip called the MCP61.  I've confirmed this by looking at PRs
116880 and 108830.

I can see two things from the dmesg:

1) FreeBSD has no idea what this controller is, or any quirks
surrounding the controller (meaning it's possible that disk or block
addressing is being done incorrectly),

2) The disks are seen as classic PATA disks and not SATA.  This could be
a result of there being no nForce 430 support in 6.1, but it could also
be due to a BIOS setting on that motherboard.

I'm looking at the User Manual for this motherboard, but I can't find
the BIOS option that I'm used to seeing on other nForce-based boards,
and Intel ICH-based boards:

A feature where you can change the way the OS sees the underlying SATA
controller; it's called Emulated or Emulation mode.  The controller
is able to interface with SATA disks, but the OS sees the controller
as a classic PATA/IDE controller.  This is often used for OSes which
lack SATA support or native SATA drivers, such as MS-DOS.

The only thing in the User Manual I see which sets off red flags is the
Serial-ATA RAID Config item under the Integrated Peripherals menu.  I
really hope the NV SATA Raid Function is set to Disabled on your box.

Looking at CVS commit logs for src/sys/dev/ata/ata-chipset.c, I can see
that MCP61 support was officially added to HEAD on on 2007/06/26.  I'm
having a difficult time determining what HEAD meant at that date.  I
can't figure out for the life of me if it was referring to RELENG_6
or RELENG_7.

Either way, point is, FreeBSD 6.1 flat out does not have support for
that chip, even a 6.1 dated August 2006.  I can't help but wonder if
that's what's causing the odd problem.

I also found another LBA48-related issue, dated 2007/10/04, labelled
fix the LBA28/LBA48 crossover bug.  I'm still not sure what that is.

And I haven't even begun to look at GEOM changes/bugfixes, which might
be a more likely place.

 This is actually a FreeBSD-Stable install... From 08/2006 I realize it's
 probably time to do an OS upgrade, but this is the ONLY issue I've run into
 running this code base. Some of the software I'm running hasn't been tested
 with 7.X, so I'm not comfortable going there yet.

What this means is that it's a 6.1-RELEASE install which follows the
RELENG_6 tag, and has been cvsup'd at least up until August 2006.

I understand you're not comfortable upgrading to FreeBSD 7, but it would
be worthwhile if you could download FreeBSD 7.1-PRERELEASE (specifically
disc 1 or a live CD), and see if that reports the same problem as 6.1.

I still can't explain why booting the 6.1 installer and using a fixit
image lets you work around the problem.  That is just flat out bizarre.

You have to understand: there's been a lot of evolution/bugfixes applied
between 6.1 and 7.1.  There's almost too much for me to try and track
down.  I'm trying very hard, but it's difficult.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Problem with Passive FTP through PF

On Mon, Oct 06, 2008 at 08:00:11AM -0700, Michael K. Smith - Adhost wrote:
 Hello All:
 
 We are running the following:
 - FreeBSD 6.3 Release #1
 - PF
 - pftpx for our ftp proxy
 
 We have several ftp servers of different flavors behind the PF firewalls and 
 we are getting a lot of the following when users are trying to connect using 
 passive mode.
 
 Server sent passive reply with unroutable address
 
 We're running pftpx as a daemon with no specific flags.  From a ps:
 
 proxy 4845  0.0  0.0  1452  1100  ??  Is   27Sep08   0:02.13 
 /usr/local/sbin/pftpx
 
 Here is a sample of the rules we are using to allow traffic and to proxy.  
 The server macros are defined and working correctly.  Any help would be 
 greatly appreciated.
 
 nat-anchor pftpx/*
 rdr-anchor pftpx/*
 rdr on ! $vlan10_if proto { udp tcp } from any to $f1_cps01_ext0 port { 80 
 443 2087 2083 ftp 49152:65535 } - $f1_cps01_int0 sticky-address
 rdr on ! $vlan10_if proto { udp tcp } from any to $f1_cps01_ext1 port { 80 
 443  ftp 49152:65535 } - $f1_cps01_int1 sticky-address

I can't help you with regards to the rdr rules, as I'm still fairly
unfamiliar with redirecting packets around, but with regards to actual
firewall rules, these are what we use on our RELENG_6 boxes.  (On
RELENG_7, you can use the same thing, but remove the flags S/SA keep
state portion -- it's implicit).


# Punch holes for FTP.  The rule looks complex, so here it is explained:
# - Make sure pass rule only applies to the X IP (ftp.server.com)
# - Permit incoming connections to port 21 (main FTP service)
# - Permit incoming connections to ports 49152-65535 (FTP passive mode)
# - TCP port 20 is actually for **outbound** connections in FTP active mode,
#   and since we allow all outbound traffic, we don't need a rule for it.
# - TCP ports 49152-65535 come from ftpd(8) and ip(4) manpages; there are
#   sysctl(8) knobs for theses, but we shouldn't mess with those.
#
pass in quick on $ext_if proto tcp from any to X port { ftp, 49152:65535 } 
flags S/SA keep state


Hope this helps, particularly the comments in our pf.conf.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

has anyone actually received a bsdmag ?

2008-10-06 Thread Craig Butler

Hi Guys

I have been subscribed to BSD Magazine since the start of September, I
was hoping to get the first issue sent to me I am still waiting.

Looking on their website they have the second issue published again
I am waiting to receive it.

I have tried emailing them but have not had any replies.

Has anybody else received their copy ? 

Cheers

Craig B

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: USB mouse problems

On Mon, 2008-10-06 at 11:00 -0700, Jeremy Chadwick wrote:
 On Mon, Oct 06, 2008 at 07:23:00PM +0200, Aniruddha wrote:
  On Mon, 2008-10-06 at 10:05 -0700, Jeremy Chadwick wrote:
I don't think this has something  to with a bios setting/jumper. My
other USB ports are working fine ( I also have an USB keyboard plugged
in).

Furthermore in Linux nor Vista I've encountered this problem. Therefor I
suspect it must have something to do with FreeBSD. Maybe it's an bug? If
someone has an solution that would be great!
   
   FreeBSD's existing USB stack is known to be... shall we say, flaky.
   It's well-established at this point.  The possibility of it being
   related to FreeBSD's USB stack is very likely.

 No -- significantly different.  CURRENT is super alpha it's probably
 going to break, while 7.1-BETA is simply the upcoming release of 7.1
 which is slated to become -STABLE after a few months.

Ah I see. Unfortunately I think I have found the problem. My Razer
Lachesis doesn't work with FreeBSD. It doesn't matter which USB port I
use. I found  this patch though:
http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/118670

What does 3-20-2008: Fix merged to RELENG_7 mean? Is this fix
available in the FreeBSD 7 (stable) release I'm running? Thanks in
advance!


-- 
Regards,

Aniruddha




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: USB mouse problems

On Mon, Oct 06, 2008 at 08:53:30PM +0200, Aniruddha wrote:
 On Mon, 2008-10-06 at 11:00 -0700, Jeremy Chadwick wrote:
  On Mon, Oct 06, 2008 at 07:23:00PM +0200, Aniruddha wrote:
   On Mon, 2008-10-06 at 10:05 -0700, Jeremy Chadwick wrote:
 I don't think this has something  to with a bios setting/jumper. My
 other USB ports are working fine ( I also have an USB keyboard plugged
 in).
 
 Furthermore in Linux nor Vista I've encountered this problem. 
 Therefor I
 suspect it must have something to do with FreeBSD. Maybe it's an bug? 
 If
 someone has an solution that would be great!

FreeBSD's existing USB stack is known to be... shall we say, flaky.
It's well-established at this point.  The possibility of it being
related to FreeBSD's USB stack is very likely.
 
  No -- significantly different.  CURRENT is super alpha it's probably
  going to break, while 7.1-BETA is simply the upcoming release of 7.1
  which is slated to become -STABLE after a few months.
 
 Ah I see. Unfortunately I think I have found the problem. My Razer
 Lachesis doesn't work with FreeBSD. It doesn't matter which USB port I
 use. I found  this patch though:
 http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/118670
 
 What does 3-20-2008: Fix merged to RELENG_7 mean? Is this fix
 available in the FreeBSD 7 (stable) release I'm running? Thanks in
 advance!

It means the original fix was applied to CURRENT (what is also known as
HEAD), and then backported to RELENG_7 (what you would call FreeBSD
7.x-STABLE) on 2008/03/20.  MFC stands for Merge From CURRENT.

You can confirm this by looking at cvsweb for the file in question:

http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/ums.c

The change for HEAD/CURRENT was made in Revision 1.98 (date = Mar 12)
The MFC to RELENG_7 was made in Revision 1.96.2.1 (date = Mar 20)

If you csup your src tree (use /usr/share/examples/cvsup/stable-supfile)
the patched code will be downloaded and used.  You'll have to rebuild
world to get the changes, of course.  See the FreeBSD Handbook for doing
a csup as well as for rebuilding world.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

what are the top few mp3[4] Podcast helpers-apps for firefox-3.03?


Guys,

Even tho firefox3 doesn't do all that (I think) it should, my main use
for the web is listening to audio streams.  So: what should I select to
be my default mp3/postcast player?

thanks,

gary


-- 
 Gary Kline  [EMAIL PROTECTED]  http://www.thought.org  Public Service Unix
http://jottings.thought.org   http://transfinite.thought.org


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: has anyone actually received a bsdmag ?

2008-10-06 Thread Gonzalo Nemmi

On Monday 06 October 2008 4:24:47 pm Craig Butler wrote:
 Hi Guys

 I have been subscribed to BSD Magazine since the start of September, I
 was hoping to get the first issue sent to me I am still waiting.

 Looking on their website they have the second issue published again
 I am waiting to receive it.

 I have tried emailing them but have not had any replies.

 Has anybody else received their copy ?

 Cheers

 Craig B

 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]

Good to know that ...

I bought the first issue on .pdf format back when it was release and I was 
seconds away from subscribing for a full year (printed version) until I read 
your mail ...

So .. I guess I'll put my subscription on hold until I know for sure that they 
do send the mag to your door and that they do it on time ...

Please, let me know how things end up for you.

Regards
-- 
Blessings
Gonzalo Nemmi
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

widescreen: np, :-)


[np (in the Subject:line) does not refer to a category of algorithm.
it means: No Problem]

Some time back I  was determined to get rid of that battle-ship anchor
19 CRT and upgrade to at least a 20 LCD, preferably widescreen.  An 
older, even nerdier friend *was* not only to heft it to my office floor,
but carry it out to the garage and install my new 20.1 LCD and it 
worked
for my Ubuntu system.  --I only needed to do an 

# X -configure

then test it and move xorg.conf.new to /etc/X11.

I just have KDE4 up (hopefully) and am about to find out what is broken.
O/wise, the new display works here on my home FBSD computer.  

IOW, those who said it should/world work were right.  Thanks to all of 
you
who encouraged the switch.  :-) , :-D , [!!!]

-- 
 Gary Kline  [EMAIL PROTECTED]  http://www.thought.org  Public Service Unix
http://jottings.thought.org   http://transfinite.thought.org


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Can't add new 1TB disk in FreeBSD 6.1

On Mon, Oct 06, 2008 at 11:08:34AM -0700, Don O'Neil wrote:

  On Mon, Oct 06, 2008 at 09:45:52AM -0700, Jeremy Chadwick wrote:
   There is one thing about later FreeBSDs which I am aware of: 48-bit 
   LBA addressing.  I'm left wondering if what you're running 
  into is a 
   bug or a problem with older FreeBSD (6.1) not supporting this.  I 
   would have to go back through CVS commit lots for ata(4) to 
  find out 
   when 48-bit LBA was added.  I think 48-bit LBA support is 
  required for disks 500GB.
  
  The issue I'm referring to has been touched on many times.
  
  First and foremost, 6.1-RELEASE was released in May 2006.  
  Keep that date in mind when reading the below.
  
  The first incident, according to CVS commit logs, was adding 
  48-bit LBA support, supporting disks 137GB.  That would've 
  been in RELENG_4, dated 2002/01/05.  FreeBSD 6.1 should have this.
  
  Next, we have a commit dated 2003/01/19, affecting 48-bit LBA 
  support on Promise 66/100 controllers.  FreeBSD 6.1 should have this.
  
  Next, 2004/12/09, talking about disk firmware bugs affecting 
  48-bit LBA addressing, which was affecting a significant 
  number of users.  That was applied to HEAD and RELENG_5, so 
  FreeBSD 6.1 (HEAD at that time) should have this.
  
  Next, 2005/04/14, something about read back the real 
  taskfile register values when in 48-bit mode.  Committed to 
  HEAD, which would've been during days shortly before RELENG_6 
  was tagged (6.0).
  
  Next, 2005/08/17, support for working around controllers 
  that can't do DMA in 48-bit LBA mode, forcing the disk to 
  use PIO mode allowing the disk to address 137GB.  This was 
  added to HEAD and RELENG_6, so this should also exist in 6.1.
  
  Next, 2007/12/13, also fix 48-bit LBA addressing issues, 
  apparently newe chips need 16-bit writes and not the usual 
  FIFO thing.  This was committed to HEAD first, RELENG_7 on 
  2008/01/09, and RELENG_6 on 2008/01/09.
  
  This is one which FreeBSD 6.1 *would not* have fixes for.
  
  I do not know if this is the problem -- I'm just speculating.
  
  Because dmesg output was not provided (nothing 
  interesting), we can't tell what sort of controller your 
  disks are hooked to, yadda yadda.
  This is explicitly why I asked for that information.
  
  If you could please try 7.0-STABLE or 7.1-PRERELEASE, that 
  would be highly recommended.  It would at least allow us to 
  determine if you're being affected by a bug in older FreeBSD, 
  or if this is something that is unique to your environment or 
  applies to present-day FreeBSD.
 
 The hardware I have is the built in SATA controller on the motherboard,
 which is GIGABYTE GA-M61P-S3. With the NVIDIA GeForce 6100 / nForce 430 and
 Super I/O chip: ITE IT8716.  
 
 Dmesg had no output pertaining to the partition/format/dd, etc... Just
 messages from my ftp daemon. If you're wanting to see the boot messages,
 this is from the last time I rebooted when I installed the disk:

Dmesg never has anything pertaining to the slicing/partitioning/newfsing
a disk.   But, it should have information about the physical drive
and the controller and such.Do you see the drive even show up
in dmesg?   Also, what does the controller look like in dmesg?

Namely, your drives seem to be:

 Oct  4 04:07:30 kermit kernel: ad0: 76293MB Maxtor 6L080P0 BAH41G10 at
 ata0-master UDMA33
 Oct  4 04:07:30 kermit kernel: ad4: 953869MB Seagate ST31000340AS SD15 at
 ata2-master UDMA33

etc.

jerry


 
 Oct  4 04:07:30 kermit kernel: Copyright (c) 1992-2006 The FreeBSD Project.
 Oct  4 04:07:30 kermit kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988,
 1989, 1991, 1992, 1993, 1994
 Oct  4 04:07:30 kermit kernel: The Regents of the University of California.
 All rights reserved.
 Oct  4 04:07:30 kermit kernel: FreeBSD 6.1-STABLE-200608 #0: Mon Mar 19
 22:52:31 PDT 2007
 Oct  4 04:07:30 kermit kernel:
 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/KERMIT
 Oct  4 04:07:30 kermit kernel: ACPI APIC Table: GBTNVDAACPI
 Oct  4 04:07:30 kermit kernel: Timecounter i8254 frequency 1193182 Hz
 quality 0
 Oct  4 04:07:30 kermit kernel: CPU: AMD Athlon(tm) 64 X2 Dual Core Processor
 5200+ (2611.90-MHz 686-class CPU)
 Oct  4 04:07:30 kermit kernel: Origin = AuthenticAMD  Id = 0x40f32
 Stepping = 2
 Oct  4 04:07:30 kermit kernel:
 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA
 ,CMOV,PAT,PSE36,CLFLUSH,MMX,F
 XSR,SSE,SSE2,HTT
 Oct  4 04:07:30 kermit kernel: Features2=0x2001SSE3,CX16
 Oct  4 04:07:30 kermit kernel: AMD
 Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow+,3DNow
 Oct  4 04:07:30 kermit kernel: AMD Features2=0x1fLAHF,CMP,b2,b3,CR8
 Oct  4 04:07:30 kermit kernel: Cores per package: 2
 Oct  4 04:07:30 kermit kernel: real memory  = 3724476416 (3551 MB)
 Oct  4 04:07:30 kermit kernel: avail memory = 3647496192 (3478 MB)
 Oct  4 04:07:30 kermit kernel: FreeBSD/SMP: Multiprocessor System Detected:
 2 CPUs
 Oct  4 04:07:30 kermit kernel: cpu0 (BSP):

Re: what are the top few mp3[4] Podcast helpers-apps for firefox-3.03?

2008-10-06 Thread Andreas Rudisch

On Mon, 6 Oct 2008 12:05:15 -0700
Gary Kline [EMAIL PROTECTED] wrote:

 what should I select to be my default mp3/postcast player?

mplayer?

Andreas
--
GnuPG key  : 0x2A573565|http://www.gnupg.org/howtos/de/
Fingerprint: 925D 2089 0BF9 8DE5 9166  33BB F0FD CD37 2A57 3565


pgpmDv7tKzDgJ.pgp
Description: PGP signature

Re: USB mouse problems

On Mon, 2008-10-06 at 12:03 -0700, Jeremy Chadwick wrote:
 It means the original fix was applied to CURRENT (what is also known as
 HEAD), and then backported to RELENG_7 (what you would call FreeBSD
 7.x-STABLE) on 2008/03/20.  MFC stands for Merge From CURRENT.
 
 You can confirm this by looking at cvsweb for the file in question:
 
 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/ums.c
 
 The change for HEAD/CURRENT was made in Revision 1.98 (date = Mar 12)
 The MFC to RELENG_7 was made in Revision 1.96.2.1 (date = Mar 20)
 
 If you csup your src tree (use /usr/share/examples/cvsup/stable-supfile)
 the patched code will be downloaded and used.  You'll have to rebuild
 world to get the changes, of course.  See the FreeBSD Handbook for doing
 a csup as well as for rebuilding world.
 

Thanks for your help and patience. If I'm not mistaken I can also
install 7.1 Beta. It would be logical to assume it contains the fix
right?


-- 
Regards,

Aniruddha




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Installing multiple ports quietly and efficiently

2008-10-06 Thread Kelly Jones

Here's one way to install multiple FreeBSD ports unattended on a
machine:

cd /usr/port/foo/prog1; make install; cd/usr/ports/foo/prog2; make install

and so on (perhaps even in a shell script). Two problems:

 % It's ugly. I'd prefer cd /usr/ports; make foo/prog1 foo/prog2 ...

 % make install often pops up windows asking me to choose
 configuration options, and hangs until I do so.

I want to install 50 apps on a new server, but not have to watch it
constantly. I want to tell ports: just use the default options for
now: if I'm unhappy w/ them, I'll come back, do a 'make rmconfig' and
rebuild.

How can I do this?

-- 
We're just a Bunch Of Regular Guys, a collective group that's trying
to understand and assimilate technology. We feel that resistance to
new ideas and technology is unwise and ultimately futile.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

RE: Can't add new 1TB disk in FreeBSD 6.1

  The hardware I have is the built in SATA controller on the 
  motherboard, which is GIGABYTE GA-M61P-S3. With the NVIDIA GeForce 
  6100 / nForce 430 and Super I/O chip: ITE IT8716.
 
  Oct  4 04:07:30 kermit kernel: atapci0: GENERIC ATA 
 controller port 
  0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on 
  pci0 Oct  4 04:07:30 kermit kernel: ata0: ATA channel 0 
 on atapci0 
  Oct  4 04:07:30 kermit kernel: ata1: ATA channel 1 on 
 atapci0 Oct  4 
  04:07:30 kermit kernel: pci0: bridge at device 7.0 (no driver 
  attached) Oct  4 04:07:30 kermit kernel: atapci1: GENERIC ATA 
  controller port 
  0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd000-0xd00f mem 
  0xf7004000-0xf7004fff irq 20 at device 8.0 on pci0 Oct  4 04:07:30 
  kermit kernel: ata2: ATA channel 0 on atapci1 Oct  4 
 04:07:30 kermit 
  kernel: ata3: ATA channel 1 on atapci1 Oct  4 04:07:30 kermit 
  kernel: atapci2: GENERIC ATA controller port 
  0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xe400-0xe40f mem 
  0xf700-0xf7000fff irq 21 at device 8.1 on pci0 Oct  4 04:07:30 
  kermit kernel: ata4: ATA channel 0 on atapci2 Oct  4 
 04:07:30 kermit 
  kernel: ata5: ATA channel 1 on atapci2 Oct  4 04:07:30 kermit 
  kernel: ad0: 76293MB Maxtor 6L080P0 BAH41G10 at 
 ata0-master UDMA33 
  Oct  4 04:07:30 kermit kernel: ad4: 953869MB Seagate ST31000340AS 
  SD15 at ata2-master UDMA33
 
 This motherboard uses the nForce 430, but the SATA portion is 
 actually a subset chip called the MCP61.  I've confirmed this 
 by looking at PRs 116880 and 108830.
 
 I can see two things from the dmesg:
 
 1) FreeBSD has no idea what this controller is, or any quirks
 surrounding the controller (meaning it's possible that disk 
 or block addressing is being done incorrectly),
 
 2) The disks are seen as classic PATA disks and not SATA.  
 This could be a result of there being no nForce 430 support 
 in 6.1, but it could also be due to a BIOS setting on that 
 motherboard.
 
 I'm looking at the User Manual for this motherboard, but I 
 can't find the BIOS option that I'm used to seeing on other 
 nForce-based boards, and Intel ICH-based boards:
 
 A feature where you can change the way the OS sees the 
 underlying SATA controller; it's called Emulated or 
 Emulation mode.  The controller is able to interface with 
 SATA disks, but the OS sees the controller as a classic 
 PATA/IDE controller.  This is often used for OSes which lack 
 SATA support or native SATA drivers, such as MS-DOS.
 
 The only thing in the User Manual I see which sets off red 
 flags is the Serial-ATA RAID Config item under the 
 Integrated Peripherals menu.  I really hope the NV SATA Raid 
 Function is set to Disabled on your box.
 
 Looking at CVS commit logs for src/sys/dev/ata/ata-chipset.c, 
 I can see that MCP61 support was officially added to HEAD on 
 on 2007/06/26.  I'm having a difficult time determining what 
 HEAD meant at that date.  I can't figure out for the life of 
 me if it was referring to RELENG_6 or RELENG_7.
 
 Either way, point is, FreeBSD 6.1 flat out does not have 
 support for that chip, even a 6.1 dated August 2006.  I can't 
 help but wonder if that's what's causing the odd problem.
 
 I also found another LBA48-related issue, dated 2007/10/04, 
 labelled fix the LBA28/LBA48 crossover bug.  I'm still not 
 sure what that is.
 
 And I haven't even begun to look at GEOM changes/bugfixes, 
 which might be a more likely place.
 
  This is actually a FreeBSD-Stable install... From 08/2006 I 
  realize it's probably time to do an OS upgrade, but this is 
 the ONLY 
  issue I've run into running this code base. Some of the 
 software I'm 
  running hasn't been tested with 7.X, so I'm not comfortable 
 going there yet.
 
 What this means is that it's a 6.1-RELEASE install which follows the
 RELENG_6 tag, and has been cvsup'd at least up until August 2006.
 
 I understand you're not comfortable upgrading to FreeBSD 7, 
 but it would be worthwhile if you could download FreeBSD 
 7.1-PRERELEASE (specifically disc 1 or a live CD), and see if 
 that reports the same problem as 6.1.
 
 I still can't explain why booting the 6.1 installer and using 
 a fixit image lets you work around the problem.  That is just 
 flat out bizarre.
 
 You have to understand: there's been a lot of 
 evolution/bugfixes applied between 6.1 and 7.1.  There's 
 almost too much for me to try and track down.  I'm trying 
 very hard, but it's difficult.

Thanks for all the clarifications, I didn't realize there have been that
many changes since 6.1. I suppose its time to upgrade. What I need to do is
build an identical server to that one and test it all out locally. Since the
drive is currently 500 miles away it will take me some time, but I'll see
what I can do.

I'll also check my BIOS settings to make sure the RAID is disabled. I'm
almost positive it is, but who knows. Jerry pointed out that the boot
process is seeing it as a regular ATA device, so it may be running

Re: kde4 question

2008-10-06 Thread Pollywog

On Sunday 05 October 2008 19:42:36 Gary Kline wrote:
   Over the past four days I've managed to get my FreeBSD server running 
 KDE
   up by installing kde4.  Now, for some reason, konqueror fails to 
 conntect
   anywhere.

   How can I free up my old kde3 files and get konqueror working again?

Have you tried running Konqueror from konsole in order to see the errors?
You might also check the proxy settings and make sure your other browsers are 
working properly (Firefox for example).

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Installing multiple ports quietly and efficiently

2008-10-06 Thread Vincent Hoffman

Kelly Jones wrote:
 Here's one way to install multiple FreeBSD ports unattended on a
 machine:

 cd /usr/port/foo/prog1; make install; cd/usr/ports/foo/prog2; make install

 and so on (perhaps even in a shell script). Two problems:

  % It's ugly. I'd prefer cd /usr/ports; make foo/prog1 foo/prog2 ...
   
I'd suggest using portupgrade then just
portinstall prog1 prog2 prog3

  % make install often pops up windows asking me to choose
  configuration options, and hangs until I do so.

   
 I want to install 50 apps on a new server, but not have to watch it
 constantly. I want to tell ports: just use the default options for
 now: if I'm unhappy w/ them, I'll come back, do a 'make rmconfig' and
 rebuild.

 How can I do this?

   
add
BATCH=yes
to /etc/make.conf


Vince
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

TRUE realtime priority

2008-10-06 Thread Wojciech Puchar


is it possible on FreeBSD

i run asterisk with realtime priority. it works perfectly no matter how 
much CPU is loaded by other non-telephony tasks.


but with lots of VM pressure it starts to so... like like tha..that...

what causes it to behave like that and how to fix it.

for example when lots of spam comes to server and lots of resource hungry 
spamassassin processes are spawned our calls starts to be crappy.


CPU load for asterisk rarely exceed few percent!

i think having separate computer just for this is stupid, i would do this 
having no other choice, but can it be done without this.


realtime priority is realtime priority anyway - it should work.


i understand that asterisk may stall requesting memory when VM pressure is 
high, but asterisk's thread that processes already set-up call - just 
moving voicepackets in and out - it doesn't need to allocate more memory 
so why it's stalled?



any network problems are eliminated, the effect happens even with 2 local 
phones.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: USB mouse problems (SOLVED)

On Mon, 2008-10-06 at 21:58 +0200, Aniruddha wrote:
 On Mon, 2008-10-06 at 12:03 -0700, Jeremy Chadwick wrote:
  It means the original fix was applied to CURRENT (what is also known as
  HEAD), and then backported to RELENG_7 (what you would call FreeBSD
  7.x-STABLE) on 2008/03/20.  MFC stands for Merge From CURRENT.
  
  You can confirm this by looking at cvsweb for the file in question:
  
  http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/ums.c
  
  The change for HEAD/CURRENT was made in Revision 1.98 (date = Mar 12)
  The MFC to RELENG_7 was made in Revision 1.96.2.1 (date = Mar 20)
  
  If you csup your src tree (use /usr/share/examples/cvsup/stable-supfile)
  the patched code will be downloaded and used.  You'll have to rebuild
  world to get the changes, of course.  See the FreeBSD Handbook for doing
  a csup as well as for rebuilding world.
  
 
 Thanks for your help and patience. If I'm not mistaken I can also
 install 7.1 Beta. It would be logical to assume it contains the fix
 right?

I just installed 7.1 Beta and now my Razer Lachesis  works :D



-- 
Regards,

Aniruddha




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Installing multiple ports quietly and efficiently

2008-10-06 Thread Robert Huff


Vincent Hoffman writes:

   I want to install 50 apps on a new server, but not have to watch it
   constantly. I want to tell ports: just use the default options for
   now: if I'm unhappy w/ them, I'll come back, do a 'make rmconfig' and
   rebuild.
  
   How can I do this?

  add
  BATCH=yes
  to /etc/make.conf

Only if you remember to take it out (or comment it out) again
when you're done.
Personally, I'd run a new shell, set the variable, do the
builds, then kill the shell. Next: edit make.conf and put it in
comented out and with additional comments.


Robert Huff

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: has anyone actually received a bsdmag ?

2008-10-06 Thread matt donovan

On Mon, Oct 6, 2008 at 2:14 PM, Gonzalo Nemmi [EMAIL PROTECTED] wrote:

 On Monday 06 October 2008 4:24:47 pm Craig Butler wrote:
  Hi Guys
 
  I have been subscribed to BSD Magazine since the start of September, I
  was hoping to get the first issue sent to me I am still waiting.
 
  Looking on their website they have the second issue published again
  I am waiting to receive it.
 
  I have tried emailing them but have not had any replies.
 
  Has anybody else received their copy ?
 
  Cheers
 
  Craig B
 
  ___
  freebsd-questions@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to
  [EMAIL PROTECTED]

 Good to know that ...

 I bought the first issue on .pdf format back when it was release and I was
 seconds away from subscribing for a full year (printed version) until I
 read
 your mail ...

 So .. I guess I'll put my subscription on hold until I know for sure that
 they
 do send the mag to your door and that they do it on time ...

 Please, let me know how things end up for you.

 Regards
 --
 Blessings
 Gonzalo Nemmi
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to 
 [EMAIL PROTECTED]


BSDmagazine is not the same as Linux Magazine they don't follow teh same
release dates I believe BSDmag is like every 4 months or something you'll
get one
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Installing multiple ports quietly and efficiently

2008-10-06 Thread Mel

On Monday 06 October 2008 21:28:25 Kelly Jones wrote:
 Here's one way to install multiple FreeBSD ports unattended on a
 machine:

 cd /usr/port/foo/prog1; make install; cd/usr/ports/foo/prog2; make install

 and so on (perhaps even in a shell script). Two problems:

  % It's ugly. I'd prefer cd /usr/ports; make foo/prog1 foo/prog2 ...

  % make install often pops up windows asking me to choose
  configuration options, and hangs until I do so.

As others said, BATCH turns off config target. But don't 
clutter /etc/make.conf with stuff like that, cause you will forget you put it 
there. make -DBATCH is short enough to type.
It is however useful to inspect pkg-install files and set variables in 
either /etc/make.conf or /etc/(profile|login.conf). For example 
POSTFIX_DEFAULT_MTA will replace /etc/mail/mailer.conf when -DBATCH is set. 
Over time you'll pick up quite a few of these that save you doing the same 
thing all over.

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

compat/linux program claims no write access to ~

2008-10-06 Thread Steve Franks

Sounds like a bogus error to me.  I just downgraded amd64 to i386,
reinstalled a linux program and it claims it can't write to ~ now.
I'm running it, and I have no reason to think it wouldn't run as me.
~ is 775 anyway.  Also, running the linux program as su or sudo gives
the same error.  Any ideas just where this might be coming from?  I'm
on 7-STABLE, i386, linux-base-fc4.

Best,
Steve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: has anyone actually received a bsdmag ?

2008-10-06 Thread Craig Butler

On Mon, 2008-10-06 at 17:48 -0400, matt donovan wrote:
 On Mon, Oct 6, 2008 at 2:14 PM, Gonzalo Nemmi [EMAIL PROTECTED] wrote:
 
  On Monday 06 October 2008 4:24:47 pm Craig Butler wrote:
   Hi Guys
  
   I have been subscribed to BSD Magazine since the start of September, I
   was hoping to get the first issue sent to me I am still waiting.
  
   Looking on their website they have the second issue published again
   I am waiting to receive it.
  
   I have tried emailing them but have not had any replies.
  
   Has anybody else received their copy ?
  
   Cheers
  
   Craig B
  
   ___
   freebsd-questions@freebsd.org mailing list
   http://lists.freebsd.org/mailman/listinfo/freebsd-questions
   To unsubscribe, send any mail to
   [EMAIL PROTECTED]
 
  Good to know that ...
 
  I bought the first issue on .pdf format back when it was release and I was
  seconds away from subscribing for a full year (printed version) until I
  read
  your mail ...
 
  So .. I guess I'll put my subscription on hold until I know for sure that
  they
  do send the mag to your door and that they do it on time ...
 
  Please, let me know how things end up for you.
 
  Regards
  --
  Blessings
  Gonzalo Nemmi
  ___
  freebsd-questions@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to 
  [EMAIL PROTECTED]
 
 
 BSDmagazine is not the same as Linux Magazine they don't follow teh same
 release dates I believe BSDmag is like every 4 months or something you'll
 get one
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]

Yep that correct

Its meant to be quarterly (every 3 months) 

However I am still waiting for the first issue let alone the second..

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: TRUE realtime priority

2008-10-06 Thread Roland Smith

On Mon, Oct 06, 2008 at 10:21:01PM +0200, Wojciech Puchar wrote:
 is it possible on FreeBSD

No, I think.
 
 i run asterisk with realtime priority. it works perfectly no matter how 
 much CPU is loaded by other non-telephony tasks.
 
 but with lots of VM pressure it starts to so... like like tha..that...
 
 what causes it to behave like that and how to fix it.

Well, basically you are the only one who can answer that. And that's not
a paradox or an attempt at humor. You should investigate. Maybe
interrupts aren't processed fast enough (hardware sharing an
interrupt?), or memory or kernel resources are low.

 for example when lots of spam comes to server and lots of resource hungry 
 spamassassin processes are spawned our calls starts to be crappy.
 
 CPU load for asterisk rarely exceed few percent!

Yes, but FreeBSD isn't a _hard_ real-time OS (see below).
 
 i think having separate computer just for this is stupid, i would do this 
 having no other choice, but can it be done without this.
 
 realtime priority is realtime priority anyway - it should work.

It does depend what you mean by real-time. Usually real-time systems are
devided into the soft and hard categories. See the Wikipedia article
on real-time computing [http://en.wikipedia.org/wiki/Real-time_computing]
and operating systems [http://en.wikipedia.org/wiki/Real-time_operating_system].

Most hard real-time systems are embedded systems with a specific
function (say, ECU, FADEC, ABS, digital music player). I don't think
there are general use OS's which would classify as hard real-time
(AFAIK, RTLinux runs Linux as a low-priority task on a real-time
core). Most of them support soft real-time, as in we'll try to get
these tasks done before a specific deadline, but no promises.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpznmhwkzvAp.pgp
Description: PGP signature

Cant remove /var, in relocating /var to a symbolic link

2008-10-06 Thread jaymax


I am attempting to relocate /var to avoid files system full issues. 
Using a -
mkdir /usr/var
cd /var
tar cf - . | (cd /usr/var; tar xf - )
cd /
rm -rf /var
ln -s /usr/var /var
approach

at the 
rm -rf /var step, the following was received
rm: /var/empty: Operation not permitted
rm: /var/named/dev: Device busy
rm: /var/named: Directory not empty
rm: /var: Device busy

Te contents of /var at this site was
ls /var
./  ../ empty/  named/
and
ls /var/empty/
./  ../

ls -l /var/empty/
total 4
dr-xr-xr-x  2 root  wheel  512 Nov  3  2005 ./
drwxr-xr-x  4 root  wheel  512 Oct  6 14:02 ../

Can't change permissons either
chmod 755 /var/empty/
chmod: /var/empty/: Operation not permitted

while 
ls /var/named/
./  ../ dev/
ls -l /var/named/
total 5
drwxr-xr-x  3 root  wheel  512 Oct  4 19:46 ./
drwxr-xr-x  5 root  wheel  512 Oct  6 14:16 ../
dr-xr-xr-x  4 root  wheel  512 Jan  1  2002 dev/

ls -l /var/named/dev
total 0
Could chmod755 but still cant remove, dev, dir empty but = Device busy

How can I remove these two directories so that I can create a link from
/usr/var to /var
-- 
View this message in context: 
http://www.nabble.com/Cant-remove--var%2C-in-relocating--var-to-a-symbolic-link-tp19847627p19847627.html
Sent from the freebsd-questions mailing list archive at Nabble.com.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: has anyone actually received a bsdmag ?

2008-10-06 Thread kenneth hatteland

Bought printed copy quite a while before the first release and have 
gotten both released issues delivered flawlessly here in Norway.
I am very pleased with the magazine and recommend everyone to  
subscribe. They were a bit slow to reply on emails but always comes 
around at a later timethat is my experience so far.


Kenneth Hatteland
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Cant remove /var, in relocating /var to a symbolic link

On Mon, Oct 06, 2008 at 03:31:42PM -0700, jaymax wrote:

 
 I am attempting to relocate /var to avoid files system full issues. 
 Using a -
   mkdir /usr/var
   cd /var
   tar cf - . | (cd /usr/var; tar xf - )
   cd /
   rm -rf /var
   ln -s /usr/var /var
 approach
 
 at the 
 rm -rf /var step, the following was received
   rm: /var/empty: Operation not permitted
   rm: /var/named/dev: Device busy
   rm: /var/named: Directory not empty
   rm: /var: Device busy
 
 Te contents of /var at this site was
   ls /var
   ./  ../ empty/  named/
 and
   ls /var/empty/
   ./  ../
   
   ls -l /var/empty/
   total 4
   dr-xr-xr-x  2 root  wheel  512 Nov  3  2005 ./
   drwxr-xr-x  4 root  wheel  512 Oct  6 14:02 ../
 
 Can't change permissons either
   chmod 755 /var/empty/
   chmod: /var/empty/: Operation not permitted
 
 while 
   ls /var/named/
   ./  ../ dev/
   ls -l /var/named/
   total 5
   drwxr-xr-x  3 root  wheel  512 Oct  4 19:46 ./
   drwxr-xr-x  5 root  wheel  512 Oct  6 14:16 ../
   dr-xr-xr-x  4 root  wheel  512 Jan  1  2002 dev/
 
   ls -l /var/named/dev
   total 0
 Could chmod755 but still cant remove, dev, dir empty but = Device busy
 
 How can I remove these two directories so that I can create a link from
 /usr/var to /var

The best way is to boot the 'fixit' image and do it from that.
On a running system, the var directory is likely to always be busy.
You might also be able to do it just from a boot to single user mode
if the /var directory is not mounted.   

But, I would suggest actually not moving the whole /var filesystem.
Rather, move some of the move heavily used directories such
as /var/log and /var/mail, maybe even /var/db and /var/spool.  Copy 
them over to the larger space and make sym links in /var to the new
ones.   Careful of your naming so you don't get confused on a 
sleepy morning.I tend to name the new alternates something
like  var.log and var.mail, etc which helps keep them straight
in my mind.

jerry  

 -- 
 View this message in context: 
 http://www.nabble.com/Cant-remove--var%2C-in-relocating--var-to-a-symbolic-link-tp19847627p19847627.html
 Sent from the freebsd-questions mailing list archive at Nabble.com.
 
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Cant remove /var, in relocating /var to a symbolic link

2008-10-06 Thread Roland Smith

On Mon, Oct 06, 2008 at 03:31:42PM -0700, jaymax wrote:
 
 I am attempting to relocate /var to avoid files system full issues. 
 Using a -
   mkdir /usr/var
   cd /var
   tar cf - . | (cd /usr/var; tar xf - )
   cd /
   rm -rf /var
   ln -s /usr/var /var
 approach
 
 at the 
 rm -rf /var step, the following was received
   rm: /var/empty: Operation not permitted

/var/empty has the system immutable flag set :-)

slackbox:~ ls -lod /var/empty
dr-xr-xr-x  2 root  wheel  schg 512 Oct  9  2005 /var/empty/


   rm: /var/named/dev: Device busy

If you have named(8) running with named_chrootdir set to /var/named in
/etc/rc.conf, a devfs(5) filesystem will be mounted on
/var/named/dev. That's what keeping the device busy.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpReFDhBKGAC.pgp
Description: PGP signature

Re: continuous backup solution for freebsd?


Roland Smith wrote:

On Mon, Oct 06, 2008 at 12:58:30PM +0300, Evren Yurtesen wrote:

Hello,

Is there a known continuous backup solution similar to r1soft backup for 
FreeBSD? I googled a lot but couldnt find anything.


I don't think so. The closest thing I know of is rsnapshot
(http://www.rsnapshot.org/). 


My solution is to run rsync in a cron job. In my situation this takes
about 5 minutes for approximately 100GB of data. The time it takes will
obviously depend on the rate of change in the data.

You could also use local snapshots with mksnap_ffs(8), to solve the oh
shit I deleted my files situation.




Thanks I am using BackupPC for such task already. Although it takes more than 5 
minutes to traverse millions of files using rsync independent of if they were 
changed or not (since rsync has to scan all the files to detect what is changed 
or not even if it only checks modification times, this takes time for so many 
files).


I just was curious about if anybody could contact r1soft and ask for a pile of 
money to implement a driver for FreeBSD, since I couldnt do it even if I wanted 
to :)


Thanks,
Evren
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

kgdb debugging

2008-10-06 Thread alan yang

hi, there,

wonder people can shed some lights on remote debugging.  i have
freebsd7 configured with option DDB / KDB / GDB but after entering the
db on the target system the command gdb gives the remote GDB backend
could not be selected.

i browsed through the mailing list, and do find 1 similar post but
without answer.

thanks in advance  apology if i overlooked things ...

cheers,
alan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: kgdb debugging

2008-10-06 Thread Pietro Cerutti


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

alan yang wrote:
| hi, there,
|
| wonder people can shed some lights on remote debugging.  i have
| freebsd7 configured with option DDB / KDB / GDB but after entering the
| db on the target system the command gdb gives the remote GDB backend
| could not be selected.
|
| i browsed through the mailing list, and do find 1 similar post but
| without answer.
|
| thanks in advance  apology if i overlooked things ...

I suggest the following tutorial:
http://www.lemis.com/grog/Papers/Debug-tutorial/tutorial.pdf

Have fun :)

|
| cheers,
| alan
| ___
| [EMAIL PROTECTED] mailing list
| http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
| To unsubscribe, send any mail to [EMAIL PROTECTED]


- --
Pietro Cerutti
[EMAIL PROTECTED]

PGP Public Key:
http://gahr.ch/pgp

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iEYEAREKAAYFAkjqnpQACgkQwMJqmJVx945RSwCgoDb0JTr8LSFDB1vpAbGUjb76
ZH0An19HpFVJJTUB5/XnyZc0pIDzgxc3
=6Pdm
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: what are the top few mp3[4] Podcast helpers-apps for firefox-3.03?

On Mon, Oct 06, 2008 at 09:40:23PM +0200, Andreas Rudisch wrote:
 On Mon, 6 Oct 2008 12:05:15 -0700
 Gary Kline [EMAIL PROTECTED] wrote:
 
  what should I select to be my default mp3/postcast player?
 
 mplayer?
 
 Andreas



Well, I tried Kmplayer; it works for some sites and hangs on kuow.org;
so you somebody confirm this.  Maybe it's the radio station and their 
mp3
feed is broken.

(It says:

   Connecting... 

and hangs.

BTW, I tried every other audio driver that kmplayer talks to.  No 
diff.
 --
 GnuPG key  : 0x2A573565|http://www.gnupg.org/howtos/de/
 Fingerprint: 925D 2089 0BF9 8DE5 9166  33BB F0FD CD37 2A57 3565



-- 
 Gary Kline  [EMAIL PROTECTED]  http://www.thought.org  Public Service Unix
http://jottings.thought.org   http://transfinite.thought.org


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: has anyone actually received a bsdmag ?

2008-10-06 Thread Pollywog

On Monday 06 October 2008 21:48:12 matt donovan wrote:
 On Mon, Oct 6, 2008 at 2:14 PM, Gonzalo Nemmi [EMAIL PROTECTED] wrote:
  On Monday 06 October 2008 4:24:47 pm Craig Butler wrote:
   Hi Guys
  
   I have been subscribed to BSD Magazine since the start of September, I
   was hoping to get the first issue sent to me I am still waiting.
  
   Looking on their website they have the second issue published again
   I am waiting to receive it.
  
   I have tried emailing them but have not had any replies.
  
   Has anybody else received their copy ?
  
   Cheers
  
   Craig B
  
   ___
   freebsd-questions@freebsd.org mailing list
   http://lists.freebsd.org/mailman/listinfo/freebsd-questions
   To unsubscribe, send any mail to
   [EMAIL PROTECTED]
 
  Good to know that ...
 
  I bought the first issue on .pdf format back when it was release and I
  was seconds away from subscribing for a full year (printed version) until
  I read
  your mail ...
 
  So .. I guess I'll put my subscription on hold until I know for sure that
  they
  do send the mag to your door and that they do it on time ...
 
  Please, let me know how things end up for you.
 
  Regards
  --
  Blessings
  Gonzalo Nemmi
  ___
  freebsd-questions@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to 
  [EMAIL PROTECTED]

 BSDmagazine is not the same as Linux Magazine they don't follow teh same
 release dates I believe BSDmag is like every 4 months or something you'll
 get one

I bought the most recent issue (it is only the second issue of the magazine) 
at Borders approximately two weeks ago.  The second issue is an issue about 
OpenBSD.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: continuous backup solution for freebsd?


Jeremy Chadwick wrote:


What I'm saying is that Linux has the upper hand here.  More eyes, more
people, more developers, larger community, larger vendor support, and
much **much** faster turn-around time on fixes/bugs.  We can sit here
and argue about those facts all we want (it's the equivalent of doing
burn-outs in an AMC Pacer in a parking lot -- wasted time, zero gain),
but nothing changes the facts.


Sorry, I had to remove the whole bunch of text that you wrote :) but I get the 
point.


I think it is a funny historical fact that BSD was commercially licensed way too 
long to allow Linux to be developed at first place. If BSD was not commercial at 
that times, Linus Torvalds probably wouldnt have started writing the Linux 
kernel. Thus we wouldnt be having this sort of conversation now and it might as 
well be that Microsoft wouldnt have become so huge. If we look at this from that 
point of view then eventually all BSD and Linux etc. are bound to disappear in 
time and Microsoft will stand all alone.


But things can change one step at a time. I prefer(or try) to look at this 
positively. I thought it wouldnt hurt to ask for help if somebody could contact 
r1soft and perhaps ask a pile of money to develop a driver. It would have been a 
win-win situation eh?



Right.  We're definitely talking about snapshots, at least in concept.

The fact that you're able to restore data within *minutes* is pretty
impressive.  I'm curious what sort of disk requirements are needed
though (I guess it depends on how often changes happen on the
filesystem).


Well it is not so fine grained (5 to 10 minutes intervals as mentioned).
http://www.r1soft.com/CDP.html
(there is more information in the link above, with links to outside sources on 
the concept such as wikipedia articles etc.)


I know some large hosters who use this technology with Linux servers. As a 
matter of fact the only reason they went with Linux instead of FreeBSD is 
because they cant get CDP with FreeBSD. I can ask how much space it is using and 
return back to you.


But if you think about it for a second, a traditional backup program would copy 
the whole file even if there was 1 byte changed in it. Lets say 10mbyte file and 
1 byte is changed. R1soft copies only 1 byte. Sure enough the tables can turn 
around if the filesystem was modified really a lot. But it looks like this type 
of solution is mostly effective (at least I didnt see anywhere that anybody is 
complaining that it is using too much disk space yet).


The best is, all it would take for FreeBSD users to be able to utilize this 
technology is a driver to interface with r1soft agent and buy a license. Now I 
am not expecting anybody to write this for free or nobody is obligated to help. 
I just dont know anybody who can help so I thought I would drop in a line here so...



I for one have never correlated snapshots and backup restorations
(bare-metal recovery).  I consider them completely separate things, and
handled *very* differently.  I have a feeling that no one's done this on
FreeBSD because the amount of effort required is quite large.  Someone
did mention HAMMER on DragonflyBSD, but I have no knowledge of it or
what it provides -- that said, Matt (Dillon)'s stuff is usually very,
very good.


I also dont know much about HAMMER either. But it doesnt look like it will make 
mainstream usage anytime soon on FreeBSD if it ever does. Actually I found a 
nice document here:

http://www.dragonflybsd.org/hammer/hammer.pdf
http://www.dragonflybsd.org/hammer/index.shtml


It depends on how the filesystem is done.  For example, with UFS2+SU
snapshots, snapshot generation can take literally hours: completely
unreasonable.  While with ZFS, snapshot generation usually takes 2-3
seconds -- even on massive changes (e.g. take a snapshot, then rm a
600MB ISO image, then compare present vs. snapshot -- the diff is
something like 40KBytes).


Yes, but r1soft backup can restore a single file at a consistent state without 
restoring the whole filesystem from a graphical user interface and can restore 
mysql databases at a table level. While I agree that there might be different 
solutions that I dont know about, it just takes a driver to get this 
functionality on current FreeBSD systems without everybody to change to ZFS or 
HAMMER. One has to think, would people change their filesystems or install a 
driver? :) I would rather pay license fee to a backup program and use the 
driver. The price of the software is very well justified if I can return back to 
5min before in my backups. The data I might loose is much more expensive.



I'm sorry for sounding anti-FreeBSD, but the reality is that people
should use whatever solutions work best for them -- if that's using
Windows, Solaris, or Linux, great!  Remember that open-source is about
choice: and choice means supporting the possibility that someone chooses
something else.  Blind one-sided advocacy is very damaging to the
open-source model and

Re: kde4 question

On Mon, Oct 06, 2008 at 07:37:27PM +, Pollywog wrote:
 On Sunday 05 October 2008 19:42:36 Gary Kline wrote:
  Over the past four days I've managed to get my FreeBSD server running 
  KDE
  up by installing kde4.  Now, for some reason, konqueror fails to 
  conntect
  anywhere.
 
  How can I free up my old kde3 files and get konqueror working again?
 
 Have you tried running Konqueror from konsole in order to see the errors?
 You might also check the proxy settings and make sure your other browsers are 
 working properly (Firefox for example).
 


firefox-3.03 is the only other one I use regularly; it works, more/less.
But nothing is printed to stdout or stderr by exec'ing konq by the
commandline.  --I have, FWIW, pkg_deleted the whole bunch of kde3
binaries.
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]

-- 
 Gary Kline  [EMAIL PROTECTED]  http://www.thought.org  Public Service Unix
http://jottings.thought.org   http://transfinite.thought.org


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: kde4 question