date:20120401

On Mon, 02 Apr 2012 08:50:42 +1000
Da Rock articulated:

> Given that the other tech in question asked me to help him, and he is
> a Winblows nut like yourself, I think this premise can be dismissed
> out of hand. I won't even bother to qualify the rest, I wouldn't want
> to ruin your delusion.

No delusion here. You have confirmed what I suspected. A classic case
of "The blind leading the blind." If one idiot can screw something up,
just think what two idiots can accomplish?

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access to Time Warner cable network


On 04/02/12 08:41, Jerry wrote:

On Mon, 02 Apr 2012 08:20:02 +1000
Da Rock articulated:


Both networking in FreeBSD _and_ Winblows can be difficult at times.
My point is that Winblows is not some magical fairy that can make
everything better. It doesn't. It quite often gets it wrong, and when
it does its a b**ch to fix- especially now with the newer versions;
it just just gets harder and harder to fix. And (forget your phd)
considering both myself and the other tech have _Microsoft_ certs and
I topped in networking in that same certification thats saying
something, do you think?

A degree != practical knowledge. The only thing you are telling me is
that you are a failure with no practical knowledge of what you are
doing. You display an obvious disdain for the OS, so how can you even
pretend to be objective? That is like me going on a jury with a
predisposed hated of the defendant. Guess how that is going to turn
out. It is like me putting together model planes. I hate model planes
and end up destroying them and conversely blaming the destruction on
the planes. It is exactly what you are doing.

You obviously are a failure at networking in a Microsoft environment,
so go back to whatever it is that you are semi capable of doing, which
will also save your employer monies spent on time wasted. Unless of
course this happens to be your own unit, in which case run down the
block and find a 12 year old and have him/her fix it for you.

Given that the other tech in question asked me to help him, and he is a 
Winblows nut like yourself, I think this premise can be dismissed out of 
hand. I won't even bother to qualify the rest, I wouldn't want to ruin 
your delusion.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Many SATA disks

2012-04-01 Thread Mike Tancsa

On 3/31/2012 6:28 PM, Daniel Feenberg wrote:
> 
> We would like to build a FreeBSD machine ourselves with many (~15) SATA
> drives, but NOT use a RAID controller. We want to be able to remove any
> drive and connect it to an ordinary motherboard SATA port and mount the
> filesystem using only the OS provided drivers and tools. I have built
> many FreeBSD systems, but never used port multipliers and don't know
> which controllers advertised as RAID controllers will support a plain
> pass-thru mode. Would anyone like to make a suggestion from actual
> experience?
> 
> The system will be used solely for archiving, so performance is not
> critical, but portability of the partitions to other systems is necessary.


We use this controller
http://www.addonics.com/products/adsa3gpx8-4e.php
connected to 3 external drive cages.  It works via the siis driver


# camcontrol devlist | egrep "ada|ulti"
   at scbus0 target 0 lun 0 (ada0,pass0)
   at scbus0 target 1 lun 0 (ada1,pass1)
   at scbus0 target 2 lun 0 (ada2,pass2)
   at scbus0 target 3 lun 0 (ada3,pass3)
at scbus0 target 15 lun 0 (pass4,pmp2)
   at scbus2 target 0 lun 0 (ada4,pass5)
   at scbus2 target 1 lun 0 (ada5,pass6)
   at scbus2 target 2 lun 0 (ada6,pass7)
   at scbus2 target 3 lun 0 (ada7,pass8)
   at scbus2 target 4 lun 0 (ada8,pass9)
at scbus2 target 15 lun 0 (pass10,pmp0)
   at scbus3 target 0 lun 0 (ada9,pass11)
   at scbus3 target 1 lun 0 (ada10,pass12)
   at scbus3 target 2 lun 0 (ada11,pass13)
   at scbus3 target 3 lun 0 (ada12,pass14)
at scbus3 target 15 lun 0 (pass15,pmp1)
at scbus6 target 0 lun 0 (ada13,pass20)
at scbus7 target 0 lun 0 (ada14,pass21)
at scbus8 target 0 lun 0 (ada15,pass22)
   at scbus11 target 0 lun 0 (ada16,pass23)


They are part of a zfs pool, but you could use them as individual drives.  If 
they are not part of some raid system, you will have of course no redundancy 
should a disk fail, unless you have some other plan for that.

For us, the pool is not usable if one of the drive cages fails, so its not the 
most reliable setup for high availability.  But its a backup server, so 
temporary down time should a PM fail is acceptable. Individual disks of course 
can be swapped out as needed.  Also, using ZFS allows us to easily add to the 
storage capacity for more backups or for longer snapshot retention.


---Mike
-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access to Time Warner cable network

On Mon, 02 Apr 2012 08:20:02 +1000
Da Rock articulated:

> Both networking in FreeBSD _and_ Winblows can be difficult at times.
> My point is that Winblows is not some magical fairy that can make 
> everything better. It doesn't. It quite often gets it wrong, and when
> it does its a b**ch to fix- especially now with the newer versions;
> it just just gets harder and harder to fix. And (forget your phd)
> considering both myself and the other tech have _Microsoft_ certs and
> I topped in networking in that same certification thats saying
> something, do you think?

A degree != practical knowledge. The only thing you are telling me is
that you are a failure with no practical knowledge of what you are
doing. You display an obvious disdain for the OS, so how can you even
pretend to be objective? That is like me going on a jury with a
predisposed hated of the defendant. Guess how that is going to turn
out. It is like me putting together model planes. I hate model planes
and end up destroying them and conversely blaming the destruction on
the planes. It is exactly what you are doing.

You obviously are a failure at networking in a Microsoft environment,
so go back to whatever it is that you are semi capable of doing, which
will also save your employer monies spent on time wasted. Unless of
course this happens to be your own unit, in which case run down the
block and find a 12 year old and have him/her fix it for you.

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access to Time Warner cable network


On 04/02/12 04:10, Fbsd8 wrote:
Well here is the results of my attempts to connect to Time Warner 
cable network.


After 4 calls to their call center which was in the Philippines where 
all the people just read a scripted answer FAQ and only had the 
ability to remotely reset the modem. I finally requested to talk to 
the top support level in the USA. Finally got a tech support person 
who knew something about how their network was configured.


Their modems at power up time run a script that is really a private 
LAN using 192.168.x.x to auto verify the cable modem mac address 
against a table of authorized accounts. At the conclusion the 10.2.0.1 
dhcp server issues a real routable ip address along with the routable 
2 dns ip address.


Now this long duration hand shake takes about 40 seconds and on a 
windows system, windows keeps looping through the ip and dns acquire 
code until it succeeds. Now on freebsd the ifconfig_fxp0="DHCP" seems 
to only cycle a single time and results in a "no carrier" status in 
the boot up msg log.


After the Freebsd 8.2 boot process completed and I saw "no carrier" 
status i issued "/etc/rc.d/netif restart" command which resulted in 
the same status. This is when I posted to the questions list for help. 
It was after the post that I had my conversation with the level 3 tech 
support guy and learned about the long hand shake process. I next 
tried  issuing (ifconfig fxp0 up) after the freebsd boot process 
completed and to my surprise I had a public routable ip address. So I 
have to find a way during the boot process to give the 
ifconfig_fxp0="DHCP" statement in the /etc/rc.conf some delay time. 
But I think Freebsd 9.0 has an built in "up" process in its boot up 
process that may solve this problem.


Another thing I learned from the level 3 support guy is that the cable 
modem has to be reset by unplugging it's power if I want to move the 
   output cable to a different device, such as from the window box 
to the freebsd box or to a router.


The bottom line is I have things working now and there was nothing 
wrong with either my window box or my freebsd box. Its just the Time 
Warner cable modem box and the non-standard way it's configured.


I had my suspicions, but I had no way to actually know. Cable modems 
work the same here: they become 'attached' to a given mac address and 
have to be reset when moved to a new device. Best to use a router to 
save that one.


Simply unplugging and plugging in the cable should have told FBSD to 
reconfigure that network.


Providing more complete information to the list for help may have given 
you the solution sooner.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: using clang


On 04/02/12 04:02, Conrad J. Sabatier wrote:

On Sun, 1 Apr 2012 09:06:08 -0400
Robert Huff  wrote:


Conrad J. Sabatier writes:


  Note, too, that none of these exceptions have anything to do with
  my /usr/src builds.  I've been using clang for buildworld and
  buildkernel for quite some time now.

I've heard that, but I think I'll wait until it becomes the
official default.  :-)

I can well understand your hesitation.  I didn't jump on the clang
bandwagon for a good while myself, either.

But, from examining and comparing clang's assembly language output
against gcc's, it does seem pretty apparent that clang produces
some pretty darned efficient code, frequently using notably fewer
machine instructions than gcc, so I try to use it now as much as
possible.  I also find its error and warning messages to be much more
precise and informative than gcc's, which is a real boon if you do any
coding yourself.
Tell me about it. I just found the real reason why libreoffice is 
failing when it gets to tests... :)


There's that, plus the fact that the base system's version of gcc (4.2)
doesn't fully support my processor family type (amdfam10), whereas
clang does (although, to be fair, gcc 4.6+ does as well).


  Hope this helps somewhat.  :-)

Very much.
Thank you.

You'll come around eventually, no doubt.  :-)



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access to Time Warner cable network


On 04/02/12 02:29, Jerry wrote:

On Mon, 02 Apr 2012 01:27:36 +1000
Da Rock articulated:


Until it loses that configuration and you're expected to delete it
and re-enter the connection details...

Or until elephants fly, or whatever.


No. This is the common mantra for any Windows net technician.



Explain why it would be so hard to configure various functions as
file sharing and some of the more 'new' features for networking on
Windows then? A fellow IT colleague and I could not figure it out for
the life of us on the newer versions while it worked perfectly on the
old '95, '98, NT, 2k, XP systems. So no, Windows does not make
networking easier- in fact it has just about completely taken the
guts out of networking to abstract it from the user, making it nearly
impossible for a networking expert to configure.

Just because an individual has a PHD does not make him an expert, in
fact it could stand for "Pin Headed Dope". Everyone is an expert in
something, just ask them. The fact that you were not smart enough to
complete the task means nothing. If we were to use your reasoning, then
if a single person could not configure networking in FreeBSD then
FreeBSD networking sucks. That is just using your rational.


Both networking in FreeBSD _and_ Winblows can be difficult at times. My 
point is that Winblows is not some magical fairy that can make 
everything better. It doesn't. It quite often gets it wrong, and when it 
does its a b**ch to fix- especially now with the newer versions; it just 
just gets harder and harder to fix. And (forget your phd) considering 
both myself and the other tech have _Microsoft_ certs and I topped in 
networking in that same certification thats saying something, do you think?



I digress. In this case we're all only speculating as the OP hasn't
provided more detail, but it could be as simple as an unplugged
cable :)

[...]
I recently ran into a case where a user had a static
IP assigned to a wireless printer. When he changed printers he could
not get it to print because it was not being assigned the same IP as
the old unit because he had failed to enter the new MAC address for the
newer printer. A simple problem that took a few  hours before it dawned
on him what the problem was. Actually, Windows did find the printer,
CUPS couldn't.



Again with the magical fairy?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: using clang (was: Re: ps, clang and make variables)

On Sun, 1 Apr 2012 14:11:29 -0500
"Conrad J. Sabatier"  wrote:

> On Sun, 1 Apr 2012 12:29:45 -0600 (MDT)
> Warren Block  wrote:
> > 
> > Have you tried clang with ccache?  Any tricks?
> 
> No, I haven't tried that.  Actually, I don't believe I've ever even
> tried using ccache at all (at least, not that I can recall).  :-)
> 

You've piqued my curiosity here.  :-)

I'm doing a buildworld at the moment using ccache with clang.  So far,
all is well, no problems.  Didn't do anything special to get started,
just "ccache make -DNO_CLEAN -j8 buildworld" (I have all that
clang-enabling stuff already in /etc/make.conf).  I know this first run
won't really show me much, other than that it *will* compile OK.
Subsequent runs should be interesting, though.  :-)

-- 
Conrad J. Sabatier
conr...@cox.net
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Wine-fbsd64 updated to 1.5.0 (32bit Wine for 64bit FreeBSD)

2012-04-01 Thread David Naylor

Hi,

Packages [1] for wine-fbsd64-1.5.0 have been uploaded to mediafire [2].

There are many reports that wine does not work with a clang compiled world
(help in fixing this problem is appreciated as it affects quite a few users).

The patch [3] for nVidia users is now included in the package and is run on
installation (if the relevant files are accessible).  Please read the
installation messages for further information.

Regards,

David

[1]
 MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.4,1.tbz) = 
0f6e1481ffc40e6f15df01893c632bcc
 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.4,1.txz) = 
68dcb36632f2ed7498316544db5c7abc
[2] http://www.mediafire.com/wine_fbsd64
[3] The patch is located at /usr/local/share/wine/patch-nvidia.sh


signature.asc
Description: This is a digitally signed message part.

fxp0 Link Going Up And Down

2012-04-01 Thread Tim Daneliuk


I am seeing this intermittently:

Apr  1 14:48:36 host kernel: fxp0: link state changed to DOWN
Apr  1 14:52:27 host kernel: fxp0: link state changed to UP

This is observed both on some 8.2-STABLE and 8.3-PRERELEASE versions
on the same server.  I have replaced the ethernet cable as well as the
device on the other end (a cable internet box), but the problem
intermittently persists.  It appears not to be a mechanical issue
insofar as I can wiggle the cable at each end and not introduce this
problem.

fxp0 in this case is the on-board NIC of an Intel mobo.

Ideas anyone?

Tim Daneliuk tun...@tundraware.com
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access to Time Warner cable network

On Sun, 01 Apr 2012 14:10:52 -0400
Fbsd8 articulated:

> Well here is the results of my attempts to connect to Time Warner
> cable network.
> 
> After 4 calls to their call center which was in the Philippines where 
> all the people just read a scripted answer FAQ and only had the
> ability to remotely reset the modem. I finally requested to talk to
> the top support level in the USA. Finally got a tech support person
> who knew something about how their network was configured.
> 
> Their modems at power up time run a script that is really a private
> LAN using 192.168.x.x to auto verify the cable modem mac address
> against a table of authorized accounts. At the conclusion the
> 10.2.0.1 dhcp server issues a real routable ip address along with the
> routable 2 dns ip address.
> 
> Now this long duration hand shake takes about 40 seconds and on a 
> windows system, windows keeps looping through the ip and dns acquire 
> code until it succeeds. Now on freebsd the ifconfig_fxp0="DHCP" seems
> to only cycle a single time and results in a "no carrier" status in
> the boot up msg log.
> 
> After the Freebsd 8.2 boot process completed and I saw "no carrier" 
> status i issued "/etc/rc.d/netif restart" command which resulted in
> the same status. This is when I posted to the questions list for
> help. It was after the post that I had my conversation with the level
> 3 tech support guy and learned about the long hand shake process. I
> next tried issuing (ifconfig fxp0 up) after the freebsd boot process
> completed and to my surprise I had a public routable ip address. So I
> have to find a way during the boot process to give the
> ifconfig_fxp0="DHCP" statement in the /etc/rc.conf some delay time.
> But I think Freebsd 9.0 has an built in "up" process in its boot up
> process that may solve this problem.
> 
> Another thing I learned from the level 3 support guy is that the
> cable modem has to be reset by unplugging it's power if I want to
> move the output cable to a different device, such as from the window
> box to the freebsd box or to a router.
> 
> The bottom line is I have things working now and there was nothing
> wrong with either my window box or my freebsd box. Its just the Time
> Warner cable modem box and the non-standard way it's configured.

I have TW with an ARRIS model: TM602G/115 cable modem. I assume you
have a battery backup in your unit. If so, you have to remove the
battery before resetting the unit to insure it is actually cleared.

Have your tried accessing your modem via http? Usually 192.168.1.0 or
192.168.1.1 will work. Give your stations static addresses and see if
that makes life easier. By the way, while I don't know what modem you
have, mine can accommodate multiple units simultaneously. I don't know
why you have to reset it to use a different device. Are you connected
via Ethernet or wireless. Even Ethernet should allow a minimum of four
unique connections.

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: using clang (was: Re: ps, clang and make variables)

On Sun, 1 Apr 2012 12:29:45 -0600 (MDT)
Warren Block  wrote:
> 
> Have you tried clang with ccache?  Any tricks?

No, I haven't tried that.  Actually, I don't believe I've ever even
tried using ccache at all (at least, not that I can recall).  :-)

-- 
Conrad J. Sabatier
conr...@cox.net
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: using clang (was: Re: ps, clang and make variables)

2012-04-01 Thread Warren Block


On Sun, 1 Apr 2012, Conrad J. Sabatier wrote:


I can well understand your hesitation.  I didn't jump on the clang
bandwagon for a good while myself, either.

But, from examining and comparing clang's assembly language output
against gcc's, it does seem pretty apparent that clang produces
some pretty darned efficient code, frequently using notably fewer
machine instructions than gcc, so I try to use it now as much as
possible.  I also find its error and warning messages to be much more
precise and informative than gcc's, which is a real boon if you do any
coding yourself.

There's that, plus the fact that the base system's version of gcc (4.2)
doesn't fully support my processor family type (amdfam10), whereas
clang does (although, to be fair, gcc 4.6+ does as well).


Have you tried clang with ccache?  Any tricks?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access to Time Warner cable network

2012-04-01 Thread Fbsd8

Well here is the results of my attempts to connect to Time Warner cable 
network.


After 4 calls to their call center which was in the Philippines where 
all the people just read a scripted answer FAQ and only had the ability 
to remotely reset the modem. I finally requested to talk to the top 
support level in the USA. Finally got a tech support person who knew 
something about how their network was configured.


Their modems at power up time run a script that is really a private LAN 
using 192.168.x.x to auto verify the cable modem mac address against a 
table of authorized accounts. At the conclusion the 10.2.0.1 dhcp server 
issues a real routable ip address along with the routable 2 dns ip address.


Now this long duration hand shake takes about 40 seconds and on a 
windows system, windows keeps looping through the ip and dns acquire 
code until it succeeds. Now on freebsd the ifconfig_fxp0="DHCP" seems to 
only cycle a single time and results in a "no carrier" status in the 
boot up msg log.


After the Freebsd 8.2 boot process completed and I saw "no carrier" 
status i issued "/etc/rc.d/netif restart" command which resulted in the 
same status. This is when I posted to the questions list for help. It 
was after the post that I had my conversation with the level 3 tech 
support guy and learned about the long hand shake process. I next tried 
 issuing (ifconfig fxp0 up) after the freebsd boot process completed 
and to my surprise I had a public routable ip address. So I have to find 
a way during the boot process to give the ifconfig_fxp0="DHCP" statement 
in the /etc/rc.conf some delay time. But I think Freebsd 9.0 has an 
built in "up" process in its boot up process that may solve this problem.


Another thing I learned from the level 3 support guy is that the cable 
modem has to be reset by unplugging it's power if I want to move the 
   output cable to a different device, such as from the window box 
to the freebsd box or to a router.


The bottom line is I have things working now and there was nothing wrong 
with either my window box or my freebsd box. Its just the Time Warner 
cable modem box and the non-standard way it's configured.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: using clang (was: Re: ps, clang and make variables)

On Sun, 1 Apr 2012 09:06:08 -0400
Robert Huff  wrote:

> Conrad J. Sabatier writes:
> 
> >  Note, too, that none of these exceptions have anything to do with
> >  my /usr/src builds.  I've been using clang for buildworld and
> >  buildkernel for quite some time now.
> 
>   I've heard that, but I think I'll wait until it becomes the
> official default.  :-)

I can well understand your hesitation.  I didn't jump on the clang
bandwagon for a good while myself, either.

But, from examining and comparing clang's assembly language output
against gcc's, it does seem pretty apparent that clang produces
some pretty darned efficient code, frequently using notably fewer
machine instructions than gcc, so I try to use it now as much as
possible.  I also find its error and warning messages to be much more
precise and informative than gcc's, which is a real boon if you do any
coding yourself.

There's that, plus the fact that the base system's version of gcc (4.2)
doesn't fully support my processor family type (amdfam10), whereas
clang does (although, to be fair, gcc 4.6+ does as well).

> >  Hope this helps somewhat.  :-)
> 
>   Very much.
>   Thank you.

You'll come around eventually, no doubt.  :-)

-- 
Conrad J. Sabatier
conr...@cox.net
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access to Time Warner cable network

On Mon, 02 Apr 2012 01:27:36 +1000
Da Rock articulated:

> Until it loses that configuration and you're expected to delete it
> and re-enter the connection details...

Or until elephants fly, or whatever.

> Explain why it would be so hard to configure various functions as
> file sharing and some of the more 'new' features for networking on
> Windows then? A fellow IT colleague and I could not figure it out for
> the life of us on the newer versions while it worked perfectly on the
> old '95, '98, NT, 2k, XP systems. So no, Windows does not make
> networking easier- in fact it has just about completely taken the
> guts out of networking to abstract it from the user, making it nearly
> impossible for a networking expert to configure.

Just because an individual has a PHD does not make him an expert, in
fact it could stand for "Pin Headed Dope". Everyone is an expert in
something, just ask them. The fact that you were not smart enough to
complete the task means nothing. If we were to use your reasoning, then
if a single person could not configure networking in FreeBSD then
FreeBSD networking sucks. That is just using your rational.

> I digress. In this case we're all only speculating as the OP hasn't 
> provided more detail, but it could be as simple as an unplugged
> cable :)

I am willing to bet that this will come down to a simple "PEBKAC"
scenario. I am assuming that the user has his cable connection enter
his home, and then connecting to a company Router/Modem. I would like to
know if the OP had checked out what IP's were being assigned to his
boxes by that unit. I recently ran into a case where a user had a static
IP assigned to a wireless printer. When he changed printers he could
not get it to print because it was not being assigned the same IP as
the old unit because he had failed to enter the new MAC address for the
newer printer. A simple problem that took a few  hours before it dawned
on him what the problem was. Actually, Windows did find the printer,
CUPS couldn't.


-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
Pryor's Observation:
How long you live has nothing to do
with how long you are going to be dead.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access to Time Warner cable network

2012-04-01 Thread Matthew Seaman

On 01/04/2012 15:59, Jerry wrote:
> Mathew, I don't know if it is as cut and dry as that. The OP claimed

That's Matthew with two t's.

> that his Microsoft PC connected properly but not his FreeBSD machine.
> That, in itself, is certainly not surprising. I have always had better
> luck setting up networks with Microsoft; however, why is it that he is
> apparently the only FreeBSD user who is exhibiting these problems? I
> suppose it is conceivable that he alone uses the northern Ohio Time
> Warner cable system. I find that rather hard, although not impossible
> to believe. Further more, is this one branch of the TW empire the only
> one using this configuration? I kind of doubt that myself. It would
> seem to me that the problem lies in the OP's configuration itself. He
> claimed it worked with "AT&T". Is it possible he has some left over
> remnants of that configuration that are causing this problem. Windows
> would not suffer that problem since it creates a new configuration for
> each new host.

You are correct in the sense that I was making general comments and not
really addressing the OP's specific problems at all.  Yes, quite
probably it is user error rather than TW producing a completely
non-sensical setup.  (I didn't say TW's setup wouldn't work, only that
it didn't seem to conform to the appropriate standards.)

Not knowing *anything* about how TW's cable network works, nor having
any detailed debugging information, all I can do is reiterate the old
mantra to the OP:

   1) Tell us exactly what you did.

   2) Tell us exactly what happened.

   3) Tell us what you expected to happen.

   4) Tell us why you think what happened was inconsistent with your
  actions in (1).

And when I say "tell" I mean /cut'n'paste relevant bits of config files/
and /show us what the output on your screen or in your log files was/.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey

signature.asc
Description: OpenPGP digital signature

Re: Access to Time Warner cable network


On 04/02/12 00:59, Jerry wrote:

On Sun, 01 Apr 2012 15:35:02 +0100
Matthew Seaman articulated:


On 01/04/2012 14:35, RW wrote:

I had a modem that did something similar, it issued a temporary
private ip address and the replaced it with a routable address.

It's fairly sad that they don't use the officially mandated[*]
169.254.0.0/16 netblock which is what DHCP clients/servers are
supposed to use when they need to temporarily grab an address.


The difference here is that the DHCP server is in a different
address block to the DHCP server, but I'm not sure that's a
problem. I think that FreeBSD associates  DHCP traffic with the
interface its operating on irrespective of normal routing.

Huh?  One of those servers should be a client perhaps?

Yes.  Contacting a DHCP server is done using Ethernet protocols (at
least initially.[+])  Not using IP.  That means DHCP client and server
have to be on the same ethernet segment, or there should be a
DHCP-relay on any routers between the client and server.  If that
fails, then the client can assign itself a link-local address and try
that, but it is pretty uncommon in the wild.

While you can run multiple different IP networks over the same
physical ethernet segment, and so have DHCP servers that dish out
addresses on networks distinct from any they have configured on their
own interfaces, you're more likely to run into this sort of scenario
if there are some DHCP relays in the picture.

Cheers,

Matthew

[*] RFC 5735

[+] Well, also except for IPv6 -- DHCP6 just uses the auto link-local
addresses which are pretty much always configured on any IPv6 capable
interface.

Mathew, I don't know if it is as cut and dry as that. The OP claimed
that his Microsoft PC connected properly but not his FreeBSD machine.
That, in itself, is certainly not surprising. I have always had better
luck setting up networks with Microsoft; however, why is it that he is
apparently the only FreeBSD user who is exhibiting these problems? I
suppose it is conceivable that he alone uses the northern Ohio Time
Warner cable system. I find that rather hard, although not impossible
to believe. Further more, is this one branch of the TW empire the only
one using this configuration? I kind of doubt that myself. It would
seem to me that the problem lies in the OP's configuration itself. He
claimed it worked with "AT&T". Is it possible he has some left over
remnants of that configuration that are causing this problem. Windows
would not suffer that problem since it creates a new configuration for
each new host.

Until it loses that configuration and you're expected to delete it and 
re-enter the connection details...


Explain why it would be so hard to configure various functions as file 
sharing and some of the more 'new' features for networking on Windows 
then? A fellow IT colleague and I could not figure it out for the life 
of us on the newer versions while it worked perfectly on the old '95, 
'98, NT, 2k, XP systems. So no, Windows does not make networking easier- 
in fact it has just about completely taken the guts out of networking to 
abstract it from the user, making it nearly impossible for a networking 
expert to configure.


I digress. In this case we're all only speculating as the OP hasn't 
provided more detail, but it could be as simple as an unplugged cable :)

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access to Time Warner cable network

On Sun, 01 Apr 2012 15:35:02 +0100
Matthew Seaman articulated:

> On 01/04/2012 14:35, RW wrote:
> > I had a modem that did something similar, it issued a temporary
> > private ip address and the replaced it with a routable address.
> 
> It's fairly sad that they don't use the officially mandated[*]
> 169.254.0.0/16 netblock which is what DHCP clients/servers are
> supposed to use when they need to temporarily grab an address.
> 
> > The difference here is that the DHCP server is in a different
> > address block to the DHCP server, but I'm not sure that's a
> > problem. I think that FreeBSD associates  DHCP traffic with the
> > interface its operating on irrespective of normal routing.
> 
> Huh?  One of those servers should be a client perhaps?
> 
> Yes.  Contacting a DHCP server is done using Ethernet protocols (at
> least initially.[+])  Not using IP.  That means DHCP client and server
> have to be on the same ethernet segment, or there should be a
> DHCP-relay on any routers between the client and server.  If that
> fails, then the client can assign itself a link-local address and try
> that, but it is pretty uncommon in the wild.
> 
> While you can run multiple different IP networks over the same
> physical ethernet segment, and so have DHCP servers that dish out
> addresses on networks distinct from any they have configured on their
> own interfaces, you're more likely to run into this sort of scenario
> if there are some DHCP relays in the picture.
> 
>   Cheers,
> 
>   Matthew
> 
> [*] RFC 5735
> 
> [+] Well, also except for IPv6 -- DHCP6 just uses the auto link-local
> addresses which are pretty much always configured on any IPv6 capable
> interface.

Mathew, I don't know if it is as cut and dry as that. The OP claimed
that his Microsoft PC connected properly but not his FreeBSD machine.
That, in itself, is certainly not surprising. I have always had better
luck setting up networks with Microsoft; however, why is it that he is
apparently the only FreeBSD user who is exhibiting these problems? I
suppose it is conceivable that he alone uses the northern Ohio Time
Warner cable system. I find that rather hard, although not impossible
to believe. Further more, is this one branch of the TW empire the only
one using this configuration? I kind of doubt that myself. It would
seem to me that the problem lies in the OP's configuration itself. He
claimed it worked with "AT&T". Is it possible he has some left over
remnants of that configuration that are causing this problem. Windows
would not suffer that problem since it creates a new configuration for
each new host.

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access to Time Warner cable network

2012-04-01 Thread Matthew Seaman

On 01/04/2012 14:35, RW wrote:
> I had a modem that did something similar, it issued a temporary private
> ip address and the replaced it with a routable address.

It's fairly sad that they don't use the officially mandated[*]
169.254.0.0/16 netblock which is what DHCP clients/servers are supposed
to use when they need to temporarily grab an address.

> The difference here is that the DHCP server is in a different address
> block to the DHCP server, but I'm not sure that's a problem. I think
> that FreeBSD associates  DHCP traffic with the interface its operating
> on irrespective of normal routing.

Huh?  One of those servers should be a client perhaps?

Yes.  Contacting a DHCP server is done using Ethernet protocols (at
least initially.[+])  Not using IP.  That means DHCP client and server
have to be on the same ethernet segment, or there should be a DHCP-relay
on any routers between the client and server.  If that fails, then the
client can assign itself a link-local address and try that, but it is
pretty uncommon in the wild.

While you can run multiple different IP networks over the same physical
ethernet segment, and so have DHCP servers that dish out addresses on
networks distinct from any they have configured on their own interfaces,
you're more likely to run into this sort of scenario if there are some
DHCP relays in the picture.

Cheers,

Matthew

[*] RFC 5735

[+] Well, also except for IPv6 -- DHCP6 just uses the auto link-local
addresses which are pretty much always configured on any IPv6 capable
interface.

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey

signature.asc
Description: OpenPGP digital signature

Re: log error..

2012-04-01 Thread Jon Radel


On 4/1/12 3:21 AM, Robert Bonomi wrote:


Since you seen incapable of reading and following the directions for
creating properly formatted BIND zone files, even after having been
directed to those resoures after your prior post, the best advice is
for you to either:
   1) Hire a knowledgable professional to set it up for you.
-or-
   2) Contract with a knowledgable operator to host your zones on *their*
  servers.


or

3) Find a fellow student locally who has figured it out and is willing 
to look over your files with you until you get it.


--Jon Radel
j...@radel.com

Re: log error..

2012-04-01 Thread Jon Radel


On 4/1/12 2:01 AM, jangkawij...@students.itb.ac.id wrote:


Apr  1 19:33:10 johannesang named[18782]: starting BIND 9.7.4-P1 -t /var/named 
-u bind
Apr  1 19:33:10 johannesang named[18782]: built with '--localstatedir=/var' 
'--disable-linux-caps' '--disable-symtable' '--with-randomdev=/dev/random' 
'--with-openssl=/usr/local' '--with-libxml2=/usr/local' '--without-idn' 
'--enable-ipv6' '--enable-threads' '--sysconfdir=/etc/namedb' '--prefix=/usr' 
'--mandir=/usr/share/man' '--infodir=/usr/share/info/' 
'--build=i386-portbld-freebsd7.3' 'build_alias=i386-portbld-freebsd7.3' 'CC=cc' 
'CFLAGS=-O2 -fno-strict-aliasing -pipe' 'LDFLAGS= -rpath=/usr/local/lib' 
'CPPFLAGS=' 'CPP=cpp' 'CXX=c++' 'CXXFLAGS=-O2 -fno-strict-aliasing -pipe'
Apr  1 19:33:10 johannesang named[18782]: Using 101 tasks for zone loading
Apr  1 19:33:11 johannesang named[18782]: max open files (3520) is smaller than 
max sockets (4096)
Apr  1 19:33:11 johannesang named[18782]: command channel listening on 
127.0.0.1#953
Apr  1 19:33:11 johannesang named[18782]: command channel listening on ::1#953
Apr  1 19:33:11 johannesang named[18782]: zone 127.in-addr.arpa/IN: NS 
'johannesang.com.127.in-addr.arpa' has no address records (A or )
Apr  1 19:33:11 johannesang named[18782]: zone 127.in-addr.arpa/IN: not loaded 
due to errors.
Apr  1 19:33:11 johannesang named[18782]: zone 79.205.167.in-addr.arpa/IN: has 
no NS records
Apr  1 19:33:11 johannesang named[18782]: zone 79.205.167.in-addr.arpa/IN: not 
loaded due to errors.
Apr  1 19:33:11 johannesang named[18782]: zone johannesang.com/IN: NS 
'host.johannesang.com' has no address records (A or )
Apr  1 19:33:11 johannesang named[18782]: zone johannesang.com/IN: not loaded 
due to errors.
Apr  1 19:33:11 johannesang named[18782]: 
/etc/namedb/master/localhost-forward.db:5: unknown RR type 'Serial,'
Apr  1 19:33:11 johannesang named[18782]: zone localhost/IN: loading from 
master file /etc/namedb/master/localhost-forward.db failed: unknown class/type
Apr  1 19:33:11 johannesang named[18782]: zone localhost/IN: not loaded due to 
errors.
Apr  1 19:33:11 johannesang named[18782]: running

can somene help me ??

can some help me to selve this thanks


Ah, the impatience of youthhe'd sent me essentially the same 
"question" directly and got impatient 30 minutes later and resent it here.


Those error messages are pretty explicit.

The one hint is that each zone file needs to have at least one NS record 
that uses a name for a server.  That name has to have at least one A (or 
 if you're using ipv6, but I'd suggest you stick with ipv4 until you 
have a clue) record that gives an IP address for the server.  You can't 
assign your servers names in in-addr.arpa.


Judging from the complaint about RR type 'Serial' you've still got 
uncommented-out garbage floating around.


Fix all that and it'll get better.  Better yet, compare what you've got 
against what's in the documentation and think a bit about what it *means*.


The question, of course, is how did you manage to completely break this 
since the last go around, where I believe you had the NS records working?


--Jon Radel
j...@radel.com

Re: Access to Time Warner cable network

2012-04-01 Thread Outback Dingo

On Sun, Apr 1, 2012 at 9:35 AM, RW  wrote:
> On Sat, 31 Mar 2012 20:52:26 -0400
> Fbsd8 wrote:
>
>> Da Rock wrote:
>> > On 04/01/12 09:52, Fbsd8 wrote:
>> >> Just purchased an account on the northern Ohio Time Warner cable
>> >> system. Having problem connecting to their service. Seems their
>> >> dhcp server has an ip address of 10.2.0.1 which is not public
>> >> routable. I know my Freebsd 8.2 box functions because it worked
>> >> fine under att service which I just left for Time Warner service.
>> >> MY xp laptop works fine with time warner. I can see that during
>> >> the connection hand shake they first issue ip addresses
>> >> 192.168.x.x then end up with real public routable ip address for
>> >> dns and my ip address. Just the dhcp ip is 10.2.0.1. XP seems to
>> >> handle this connection hand shake ok.
>
> I had a modem that did something similar, it issued a temporary private
> ip address and the replaced it with a routable address.
>
> The difference here is that the DHCP server is in a different address
> block to the DHCP server, but I'm not sure that's a problem. I think
> that FreeBSD associates  DHCP traffic with the interface its operating
> on irrespective of normal routing.
>
>
>> > Have you got a firewall or something else blocking dhcp from
>> > communicating? What does ifconfig say?
>> >
>> No firewall running and NIC status is "no carrier"
>
> This is what you get when something isn't plugged-in or turned-on.

or when autonegotiation fails between to ports due to
incompatibilities, ive seen it alot of times on older gear


> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access to Time Warner cable network

2012-04-01 Thread RW

On Sun, 1 Apr 2012 14:35:41 +0100
RW wrote:


> The difference here is that the DHCP server is in a different address
> block to the DHCP server, 

That should be: "the temporary address is in a different address
 block to the DHCP server"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Access to Time Warner cable network

2012-04-01 Thread RW

On Sat, 31 Mar 2012 20:52:26 -0400
Fbsd8 wrote:

> Da Rock wrote:
> > On 04/01/12 09:52, Fbsd8 wrote:
> >> Just purchased an account on the northern Ohio Time Warner cable
> >> system. Having problem connecting to their service. Seems their
> >> dhcp server has an ip address of 10.2.0.1 which is not public
> >> routable. I know my Freebsd 8.2 box functions because it worked
> >> fine under att service which I just left for Time Warner service.
> >> MY xp laptop works fine with time warner. I can see that during
> >> the connection hand shake they first issue ip addresses
> >> 192.168.x.x then end up with real public routable ip address for
> >> dns and my ip address. Just the dhcp ip is 10.2.0.1. XP seems to
> >> handle this connection hand shake ok.

I had a modem that did something similar, it issued a temporary private
ip address and the replaced it with a routable address.

The difference here is that the DHCP server is in a different address
block to the DHCP server, but I'm not sure that's a problem. I think
that FreeBSD associates  DHCP traffic with the interface its operating
on irrespective of normal routing.

> > Have you got a firewall or something else blocking dhcp from 
> > communicating? What does ifconfig say? 
> > 
> No firewall running and NIC status is "no carrier"

This is what you get when something isn't plugged-in or turned-on.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: using clang (was: Re: ps, clang and make variables)

2012-04-01 Thread Robert Huff

Conrad J. Sabatier writes:

>  Note, too, that none of these exceptions have anything to do with
>  my /usr/src builds.  I've been using clang for buildworld and
>  buildkernel for quite some time now.

I've heard that, but I think I'll wait until it becomes the
official default.  :-)


>  Hope this helps somewhat.  :-)

Very much.
Thank you.


Robert Huff

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: using clang (was: Re: ps, clang and make variables)

On Sat, 31 Mar 2012 11:11:25 -0400
Robert Huff  wrote:

> 
>   As long as we're talking about clang, I have two questions.
>   1) Is there any generic reason why a port compiled with clang
> won't work on a world compiled with gcc?

No, none that I'm aware of.  I've occasionally seen mention of
this-or-that port causing problems if built with clang, not always
directly, but sometimes affecting other ports that depend on it.

>   2) If not, how do I set that up?

The "standard" method is to include the following in
your /etc/make.conf (also see the comments after this):

#
# use clang unless gcc is explicitly required
#

.if !defined(USE_GCC)
.if !defined(CC) || ${CC} == "cc"
CC=clang
.endif
.if !defined(CXX) || ${CXX} == "c++"
CXX=clang++
.endif
.if !defined(CPP) || ${CPP} == "cpp"
CPP=clang-cpp
.endif
.endif

Over a span of several months, I've gradually amassed a list of ports
I use myself which either won't build successfully with clang, or have
some sort of runtime issues when built with clang (these have a
tendency to change over time with new releases of a given port).  For
these, I've added some "exception" lines to force them to be built
either with the base system gcc (4.2) or the lang/gcc port (4.6). 

Note that these exceptions have to *precede* the previous lines in
order for them to override the above clang settings.

You can also override the clang settings at the command line by doing
"make USE_GCC=4.2 (or 4.2+)" or "make USE_GCC=4.6 (or 4.6+)", for
example.  If you do do this from the command line, just be sure to be
consistent with it, i.e., you don't want to do a "make USE_GCC=4.6
configure" followed by a plain "make" or "make install".  Pretty much
sure to lead to trouble.  :-)

Note, too, that none of these exceptions have anything to do with my
/usr/src builds.  I've been using clang for buildworld and buildkernel
for quite some time now.

###
# (need to put this up here before the following clang stuff)
#
# ports which either won't build using clang, or that have
# runtime issues when built with clang
#
##

#
# default to using clang for all port builds, with the following
# exceptions

# ports which will only build with the base system GNU compiler (4.2)
#
# the "make index" target also seems to need this, for some reason

.if target(index) | \
${.CURDIR:M*/devel/antlr*} | \
${.CURDIR:M*/devel/google-perftools* } | \
${.CURDIR:M*/graphics/ImageMagick* } | \
${.CURDIR:M*/graphics/opencv*} | \
${.CURDIR:M*/www/libxul*} | \
${.CURDIR:M*/x11/kdelibs4*} | \
${.CURDIR:M*/x11-toolkits/swt-devel*}
USE_GCC?=4.2
.endif

# ports which need *some* version of the GNU compiler (won't build with
# clang or have runtime issues if built with clang)
# use the highest version of gcc we have installed from ports (4.6)

.if ${.CURDIR:M*/accessibility/jovie*} | \
${.CURDIR:M*/accessibility/kdeaccessibility4*} | \
${.CURDIR:M*/audio/grip*} | \
${.CURDIR:M*/audio/mpg123*} | \
${.CURDIR:M*/audio/rosegarden*} | \
${.CURDIR:M*/databases/virtuoso*} | \
${.CURDIR:M*/deskutils/kdepimlibs4*} | \
${.CURDIR:M*/devel/apache-ant*} | \
${.CURDIR:M*/devel/binutils*} | \
${.CURDIR:M*/devel/icu*} | \
${.CURDIR:M*/devel/kdevelop-kde4*} | \
${.CURDIR:M*/devel/kdevplatform*} | \
${.CURDIR:M*/devel/log4j*} | \
${.CURDIR:M*/games/kdegames4*} | \
${.CURDIR:M*/graphics/tonicpoint-viewer*} | \
${.CURDIR:M*/java/* } | \
${.CURDIR:M*/lang/gcc*} | \
${.CURDIR:M*/math/fftw3*} | \
${.CURDIR:M*/multimedia/avidemux2*} | \
${.CURDIR:M*/multimedia/kdemultimedia4*} | \
${.CURDIR:M*/multimedia/vlc*} | \
${.CURDIR:M*/multimedia/xbmc*} | \
${.CURDIR:M*/net/kdenetwork4*} | \
${.CURDIR:M*/net/mpich2*} | \
${.CURDIR:M*/net/opal3*} | \
${.CURDIR:M*/net-p2p/ktorrent*} | \
${.CURDIR:M*/net-p2p/vuze*} | \
${.CURDIR:M*/sysutils/lsof*} | \
${.CURDIR:M*/textproc/docbook-xsl*} | \
${.CURDIR:M*/textproc/fop*} | \
${.CURDIR:M*/www/firefox*} | \
${.CURDIR:M*/x11/kde4-baseapps*} | \
${.CURDIR:M*/x11/kde4-workspace*} | \
${.CURDIR:M*/x11/lxpanel*} | \
${.CURDIR:M*/x11-toolkits/swt*}
USE_GCC?=4.6+
.endif

Hope this helps somewhat.  :-)

-- 
Conrad J. Sabatier
conr...@cox.net
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: shutdown -p doesn't power-off USB

2012-04-01 Thread Polytropon

On Sat, 31 Mar 2012 17:38:11 +0200, Jens Schweikhardt wrote:
> I'm running 9-STABLE/amd64 and for a few months now, whenever I shut
> down with "shutdown -p now", the USB devices still have power. This is
> most visible on the USB keyboard, where *all* LEDs are turned on and
> stay on.

That's not a bug, it's a feature. :-) Many mainboards allow
switching-on per keyboard. There's typically a toggle in
the board's CMOS setup. Maybe there's also an option to
turn USB power completely off. However, USB powered on
seems to be the default as soon as the machine's power
supply is on line.

> The MB is an ASUS P5Q3 Deluxe.

Also check its documentation, maybe USB power is mentioned?

> Any help appreciated in telling me how to turn off USB power with shutdown.

I don't think this is any option in the OS. You should check
this per hardware.

-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Printer recommendation please

On 04/01/12 19:29, Polytropon wrote:

On Sat, 31 Mar 2012 14:01:43 -0700, per...@pluto.rain.com wrote:

I personally don't trust wireless, because it's well nigh impossible
to truly secure it.

In that case, one should also pay attention to secure the
printer. Wait - secure the printer? What am I talking about?

Firmware attacks!

Yes - malware has already reached printers. As they contain
all typical parts of a computer and are equipped with net-
working capabilities, they can cause trouble in networks
the same way as what hujacked "Windows" PCs typically do.
They can be turned into networked "allies", carrying out
the attackers orders within networks.

Those who are interested may find some information here:

Exclusive: Millions of printers open to devastating hack attack, researchers say
http://redtape.msnbc.msn.com/_news/2011/11/29/9076395-exclusive-millions-of-printers-open-to-devastating-hack-attack-researchers-say

ShmooCon 2011: Printers Gone Wild!
http://www.youtube.com/watch?v=GZgLX60U3sY#t=3m40s
ROFL! Sorry my mind went to an interesting place with this one
images of printers on spring break flashing their cartridges, opening
flaps to show off their drums... :D

The content isn't funny though. They really should consider their
headlines before releasing...

ShmooCon 2011: Printer to PWND: Leveraging Multifunction Printers During
http://www.youtube.com/watch?v=MPhisPLwm2A

Printer malware: print a malicious document, expose your whole LAN
http://boingboing.net/2011/12/30/printer-malware-print-a-malic.html

Print Me If You Dare
Firmware Modification Attacks and the Rise of Printer Malware
http://events.ccc.de/congress/2011/Fahrplan/events/4780.en.html

HP firmware to 'mitigate' LaserJet vulnerability
http://news.cnet.com/8301-1009_3-57347817-83/hp-firmware-to-mitigate-laserjet-vulnerability/

It seems that printers can be infected via specific network
traffic or closed-source malicious "drivers" (that nobody
can examine content-wise) that will find their way to the
device. Depending on your local legislation, that can develop
into dangerous (and expensive) directions...

2. Standard language.
Postscript and PCL. Make sure the printer understands at least
one of them.

or, alternatively, PDF (which some of the newer printers are reputed
to take directly, rather than requiring the host to convert it to PS
or PCL).

Jerry mentioned this, and I think it's a feature worth demanding
when buying a new printer. Still if PDF input is not possible,
PCL or PS should be looked for. All those considerations make
sure you can use the printer with _any_ OS you like, and due
to this fact it will be usable even after the "target OS" will
be out of support (and follow-up drivers won't be provided).

From my memory Xerox are pretty good with this. Besides schmoozing the
printed graphics industry they've been a _big_ proponent of the Unix
system; in particular the birth of X-Windows, and various print
standards long before and after M$ came on the scene. They have still
remained a strong supporter of the Unix and printing community. The
Phaser is a good choice.

Unfortunately they are a bit of an elite brand which puts them out of
most home users price range :)

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Printer recommendation please

2012-04-01 Thread Polytropon

On Sat, 31 Mar 2012 14:01:43 -0700, per...@pluto.rain.com wrote:
> I personally don't trust wireless, because it's well nigh impossible
> to truly secure it.

In that case, one should also pay attention to secure the
printer. Wait - secure the printer? What am I talking about?

Firmware attacks!

Yes - malware has already reached printers. As they contain
all typical parts of a computer and are equipped with net-
working capabilities, they can cause trouble in networks
the same way as what hujacked "Windows" PCs typically do.
They can be turned into networked "allies", carrying out
the attackers orders within networks.

Those who are interested may find some information here:

Exclusive: Millions of printers open to devastating hack attack, researchers say
http://redtape.msnbc.msn.com/_news/2011/11/29/9076395-exclusive-millions-of-printers-open-to-devastating-hack-attack-researchers-say

ShmooCon 2011: Printers Gone Wild!
http://www.youtube.com/watch?v=GZgLX60U3sY#t=3m40s

ShmooCon 2011: Printer to PWND: Leveraging Multifunction Printers During
http://www.youtube.com/watch?v=MPhisPLwm2A

Printer malware: print a malicious document, expose your whole LAN
http://boingboing.net/2011/12/30/printer-malware-print-a-malic.html

Print Me If You Dare
Firmware Modification Attacks and the Rise of Printer Malware
http://events.ccc.de/congress/2011/Fahrplan/events/4780.en.html

HP firmware to 'mitigate' LaserJet vulnerability
http://news.cnet.com/8301-1009_3-57347817-83/hp-firmware-to-mitigate-laserjet-vulnerability/

It seems that printers can be infected via specific network
traffic or closed-source malicious "drivers" (that nobody
can examine content-wise) that will find their way to the
device. Depending on your local legislation, that can develop
into dangerous (and expensive) directions...

> > 2. Standard language.
> > Postscript and PCL. Make sure the printer understands at least
> > one of them.
> 
> or, alternatively, PDF (which some of the newer printers are reputed
> to take directly, rather than requiring the host to convert it to PS
> or PCL).

Jerry mentioned this, and I think it's a feature worth demanding
when buying a new printer. Still if PDF input is not possible,
PCL or PS should be looked for. All those considerations make
sure you can use the printer with _any_ OS you like, and due
to this fact it will be usable even after the "target OS" will
be out of support (and follow-up drivers won't be provided).

-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: FreeBSD Security in Multiuser Environments

2012-04-01 Thread Matthew Seaman

On 01/04/2012 09:47, Peter Vereshagin wrote:
>> Also, thanks for Capsicum, it sure is useful.

> Who is that?

Robert Watson, Jonathan Anderson and Ben Laurie are the principle 'who'
behind Capsicum.   Now, if you'ld asked 'What is that?' I'd've pointed
you towards

   https://www.cl.cam.ac.uk/research/security/capsicum/

It's a "lightweight OS capability and sandbox framework," or in other
words a way of enforcing restrictions on what objects -- particularly
those built from foreign data eg. javascript in web pages -- can modify
or access on your local system.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey

signature.asc
Description: OpenPGP digital signature

Re: Printer recommendation please

2012-04-01 Thread Polytropon

On Sat, 31 Mar 2012 21:20:41 +0200, Lino Miklav wrote:
> On 31.03.2012 00:16, Peter A. Giessel wrote:
> > It doesn't surprise me that Gutenprint doesn't have a setting
> > specifically for the 6500 because Xerox provides one:
> 
> Uf, I have this idea to only use LPD and filters.

That should be no problem. If I read the specifications
for the Xerox Phaser 6280V DN correctly, it supports both
PS and PCL.

Here's an example for a PCL printer filter:

#!/bin/sh
printf "\033&k2G" || exit 2
gs -q -dBATCH -dNOPAUSE -dPARANOIDSAFER -dSAFER -sPAPERSIZE=a4 
-r600x600 \
-sDEVICE=ljet4 -sOutputFile=- - && exit 0
exit 2

The "ljet4" produces PCL, it can also be used to access
features like duplexer (add -dDuplex=true). It basically
does the same as the apsfilter filter, except that the
apsfilter one has support for "pretty printing" and
direct command line printing, so

% lpr foo.c

or

% lpr bar.png

can be issued directly, no need to create a PS stream
by another application.

You can easily add that filter to /etc/printcap's if= setting,
add rm= with the IP or hostname of the printer, prepare the
spool and it should work.

-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: FreeBSD Security in Multiuser Environments

2012-04-01 Thread Peter Vereshagin

Hello.

2012/03/30 22:44:16 -0300 schu...@ime.usp.br => To 
freebsd-questions@freebsd.org :

> P.S.: If you want to attain desktop security, matters get even more
> complicated. If anyone is interested, I can discuss what I did there
> (basically virtual X servers and building ports as regular users).

Sure I am interested.

I myself try to run Xorg server in a chroot and its clients from a different
jail(s) via tcp on lo0.  Trouble still is I can't get my VT ttyvXs because of
that strange 'console ownership' stuff.

> Also, thanks for Capsicum, it sure is useful.

Who is that?

--
Peter Vereshagin  (http://vereshagin.org) pgp: A0E26627 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: log error..

2012-04-01 Thread Jonathan Vomacka


On 4/1/2012 3:21 AM, Robert Bonomi wrote:

 From owner-freebsd-questi...@freebsd.org  Sun Apr  1 01:46:26 2012
Date: Sun, 1 Apr 2012 13:01:31 +0700 (WIT)
From: jangkawij...@students.itb.ac.id
To: questions
Cc:
Subject: log error..



[ snip numerous syslog messages indicating incorrect zone file syntax ]


can somene help me ??

can some help me to selve this thanks


Since you seen incapable of reading and following the directions for
creating properly formatted BIND zone files, even after having been
directed to those resoures after your prior post, the best advice is
for you to either:
   1) Hire a knowledgable professional to set it up for you.
-or-
   2) Contract with a knowledgable operator to host your zones on *their*
  servers.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


LOL. Well said.
Read docs and then ask for help, otherwise dont read docs and hire 
someone who knows what they are doing versus someone who doesnt care to 
learn.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: log error..