Re: find date of last boot

[Matthew Seaman]

On 08/06/2012 07:23, Chris Knipe wrote:
>> It's not that.  'last reboot' seems to be broken at the moment, at least
>> on stable/9:
> 
>> but last(1) isn't coming up with the goods:
>>
>> lucid-nonsense:~:% last reboot
>>
>> wtmp begins Fri Jun  1 06:14:46 BST 2012
> 
> last reads from /var/log/wtmp - which more than likely got rotated
> since your last reboot.

No.  Please read more carefully.

last(1) used to use /var/log/wtmp, but not on 9.x or above, which uses
/var/log/utx.log -- a different binary format, but basically the same
idea as wtmp.

And, no: as I showed, that file was not rotated since my last reboot.

Cheers,

Matthew

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





signature.asc
Description: OpenPGP digital signature

OT - enjoy it

[jb]

Chinese advertising of soccer championship Euro 2012

http://avaxnews.com/wow/Chinese_Advertising_UEFA_Euro_2012.html


___
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: find date of last boot

[Chris Knipe]

> It's not that.  'last reboot' seems to be broken at the moment, at least
> on stable/9:

> but last(1) isn't coming up with the goods:
>
> lucid-nonsense:~:% last reboot
>
> wtmp begins Fri Jun  1 06:14:46 BST 2012

last reads from /var/log/wtmp - which more than likely got rotated
since your last reboot.


-- 

Regards,
Chris Knipe
___
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: find date of last boot

[Matthew Seaman]

On 08/06/2012 05:50, Randal L. Schwartz wrote:
> Sure, but the question was likely involving a stock system, so yes, your
> mileage may vary, but let's consider a solution that works for a default
> system.  "last reboot" isn't it.

It's not that.  'last reboot' seems to be broken at the moment, at least
on stable/9:

lucid-nonsense:~:% uname -a
FreeBSD lucid-nonsense.infracaninophile.co.uk 9.0-STABLE FreeBSD
9.0-STABLE #15 r236465: Sat Jun  2 23:14:59 BST 2012
r...@lucid-nonsense.infracaninophile.co.uk:/usr/obj/usr/src/sys/LUCID-NONSENSE
 amd64

I rebooted a few days ago:

lucid-nonsense:~:% uptime
 7:14AM  up 3 days,  8:18, 1 user, load averages: 0.03, 0.01, 0.01

And the utx.log file was last rotated over a week ago:

lucid-nonsense:~:% ls -la /var/log/utx*
-rw-r--r--  1 root  wheel394 Jun  7 17:51 /var/log/utx.lastlogin
-rw-r--r--  1 root  wheel  16841 Jun  8 07:06 /var/log/utx.log
-rw-r--r--  1 root  wheel  24878 May 31 22:41 /var/log/utx.log.0
-rw-r--r--  1 root  wheel  13741 Apr 30 08:50 /var/log/utx.log.1
-rw-r--r--  1 root  wheel  27886 Mar 31 22:52 /var/log/utx.log.2

but last(1) isn't coming up with the goods:

lucid-nonsense:~:% last reboot

wtmp begins Fri Jun  1 06:14:46 BST 2012

(nor does it work if I tell last to use the older utx.log files)

Cheers,

Matthew

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





signature.asc
Description: OpenPGP digital signature

Re: find date of last boot

[Matthew Seaman]

On 08/06/2012 00:15, Fbsd8 wrote:
> dmesg command does not show date of last boot.
> 
> Are there some other commands to find date of last boot?

% last reboot

will show the date of the last reboot if it is still in the current
/var/log/utx.log

Or at least it should: testing on my own system while writing this
failed to show the date of my last reboot.  Looks like you've stumbled
across a bug.

Cheers,

Matthew

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





signature.asc
Description: OpenPGP digital signature

Re: Configuration problem with IPv6 router ("cannot forward src")

[Matthew Seaman]

On 07/06/2012 23:36, Bruce Cran wrote:
> I'm trying to set up a IPv6 router (running -current) on my home
> network. My ISP gives me a /128 via PPP and I have a /48 allocation,
> which I use to give em0 and tun0 public addresses in different subnets
> (tun0 is assigned the address via ppp.linkup).
> I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable,
> ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites
> from the router.

rtadvd can be limited to operate on a specific interface.  Try setting

rtadvd_interfaces="em0"

in /etc/rc.conf

> The problem is that rtadvd continues advertising the default gateway as
> tun0's link-local address - and pinging from a machine on the network
> results in "cannot forward src" messages on the router (strangely,
> despite hisaddr being fe80::205:... in ppp.log, the kernel logs the
> address as fe80:f::205:...).

Try setting:

ipv6_default_interface="tun0"

and possibly also

ipv6_defaultrouter="-interface tun0"

I use a gif tunnel (IPv6 over IPv4) for my IPv6 connectivity -- no
native support for IPv6 in my ADSL router -- so not exactly equivalent
but pretty similar in many ways.

> Is there some extra configuration I've likely missed that's needed when
> using IPv6 via PPP?

Probably.  The good news is that once you've got it running the IPv6
support in FreeBSD is rock solid and works like a charm.

Cheers,

Matthew

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





signature.asc
Description: OpenPGP digital signature

Re: FreeBSD on the ASUS P8H67-M LGA1155 H67 motherboard

[Victor Sudakov]

Victor Sudakov wrote:
> 
> 2. It looses one of the HDDs during intensive read/write operations:
> 
> Jun  2 00:55:33 vas kernel: ahcich1: Timeout on slot 4 port 0
> Jun  2 00:55:33 vas kernel: ahcich1: is  cs 00c0 ss 00f0 rs 
> 00f0 tfd c0 serr  cmd c617
> Jun  2 00:56:48 vas kernel: ahcich1: Timeout on slot 0 port 0
> Jun  2 00:56:48 vas kernel: ahcich1: is  cs 0001 ss  rs 
> 0001 tfd c0 serr  cmd c017
> Jun  2 00:57:20 vas kernel: ahcich1: AHCI reset: device not ready after 
> 31000ms (tfd = 0080)
> 
> I shall of course check the HDD and cable, but they worked flawlessly on
> the previous system.

The cable is OK. I have tried different SATA slots on the motherbord too,
the HDD losses persist. How can a rule out a kernel driver bug in ahci
or ada, perhaps a PR is due?

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
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 on the ASUS P8H67-M LGA1155 H67 motherboard

[Victor Sudakov]

Peter Vereshagin wrote:
> VS> What video card would the collective mind of FreeBSD users recommend?
> VS> I'm not a gamer, this box runs FreeBSD only with a recent xorg, I
> VS> often watch movies on it.
> 
> I'd try with nvidia. Any modern one has support of 'xvideo' extension with the
> 'driver nv' that is 'just enough' for watching movies.
> 
> I've no modern hardware but the model that works good for years for
> me is: tnt2 agp 32M. Just the same as out of every TransNeft's
> trashcan around the corner these days. ;-)

They gave me the following from the TransNeft trashcan, indeed:

VendorName  "NVIDIA Corporation"
BoardName   "NV18 [GeForce4 MX 440 AGP 8x]"
Driver  "nv"

It says "AGP" but in reality it is PCI, perhaps some very rare species
:) It has X-Video Extension version 2.2, my movies are back, hurrah!

In the meanwhile, I'll wait for the development of the SandyBrdige
Intel driver.

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
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: Somewhat OT - A Makefile Question

[parv]

in message <4fd0adfb.8030...@tundraware.com>,
wrote Tim Daneliuk thusly...
>
> On 06/07/2012 12:19 AM, Parv wrote:
> > in message<4fcf48af@tundraware.com>,
> > wrote Tim Daneliuk thusly...
> >>
> > ...
> >> Within a makefile, I need to assign the name of a program as
> >> in:
> >>
> >> FOO = "bar".
> >>
> >> The problem is that 'bar' may also be know as, say, "bar.sh".
> > ...
> >> Is there a simple way to determine which form "bar" or "bar.sh"
> >> on on a given system *at the time the make is run*?  If both
> >> exist, I will pick one arbitrarily,
> > ...
> >>   For example I don't think this works when both are there:
> >>
> >> FOO = $(shell `which bar bar.sh)
> >
> > Modify the subshell command to ...
> >
> >which bar bar.sh | head -n 1
> >
> >
> > ... as in (for FreeBSD make) ...
> >
> >shell=`which zsh sh tcsh csh 2>/dev/null | fgrep -v 'not found' | head 
> > -n 3`
...
> Thanks.

Happy to help.


> I came up with something similar, but I think your recipe is a bit
> more elegant ...

It was "If both exist, I will pick one arbitrarily ... " that
helped much in modification of the original.


  - parv

-- 

___
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: find date of last boot

[Randal L. Schwartz]

> "Chuck" == Chuck Swiger  writes:

Chuck> FreeBSD aggressively rotates the utmp/wtmp databases; most other
Chuck> platforms leave it in place until the sysadmin decides to rotate
Chuck> it per local policy.

Chuck> Tweaking the monthly? periodic entries would change this, I'd
Chuck> imagine

Sure, but the question was likely involving a stock system, so yes, your
mileage may vary, but let's consider a solution that works for a default
system.  "last reboot" isn't it.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
 http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion
___
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: find date of last boot

[Randal L. Schwartz]

> "Chris" == Chris Hill  writes:

Chris> I'll credit Doug Hardie with the best solution:
Chris> $ ls -l /var/run/dmesg.boot
Chris> -rw-r--r--  1 root  wheel  7248 Dec 26  2010 /var/run/dmesg.boot

Ouch!  There've been some security patches since then.  Are you sure you
want to tell someone that a machine has been running for over 18 months?

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
 http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion
___
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: find date of last boot

[Carl Johnson]

Fbsd8  writes:

> dmesg command does not show date of last boot.
>
> Are there some other commands to find date of last boot?

In addition to the other responses:

sysctl kern.boottime

-- 
Carl Johnsonca...@peak.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: find date of last boot

[Chuck Swiger]

On Jun 7, 2012, at 6:32 PM, Randal L. Schwartz wrote:
> You must reboot a lot.  My "last" log goes back only to the first of the
> month, and my uptime is 16 days right now, so I can't see the most
> recent reboot with last.

FreeBSD aggressively rotates the utmp/wtmp databases; most other platforms
leave it in place until the sysadmin decides to rotate it per local policy.

Tweaking the monthly? periodic entries would change this, I'd imagine

Regards,
-- 
-Chuck

___
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: find date of last boot

[Karl Vogel]

>> On Thu, 7 Jun 2012 21:35:19 -0400 (EDT), 
>> Chris Hill  said:

C> $ ls -l /var/run/dmesg.boot
C> -rw-r--r-- 1 root wheel 7248 Dec 26 2010 /var/run/dmesg.boot

   For the sake of completeness:

   me% stat -f %Sm /var/run/dmesg.boot
   Jan 10 14:56:45 2012

   me% ls -l -D '%d-%b-%Y %T' /var/run/dmesg.boot
   -rw-r--r--  1 root  wheel  6319 10-Jan-2012 14:56:45 /var/run/dmesg.boot

-- 
Karl Vogel  I don't speak for the USAF or my company

Dirt and grease under the fingernails is a social no-no, as they tend to
detract from a woman's jewelry and alter the taste of finger foods.
   --Martha Stewart's hygiene tips for Rednecks
___
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: find date of last boot

[Michael Sierchio]

On Thu, Jun 7, 2012 at 7:34 PM, Polytropon  wrote:

> Maybe introducing something along the /etc/rc execution?
> An /etc/rc.local entry like
>
>        /bin/date "+%Y-%m-%d %H:%M:%S" > /var/log/thisboot.log
>
> and then just look at the file. Requires at least one reboot
> to take effect. :-)
>

You could just put the following in /etc/rc.local

date

and it would be retained in /var/run/dmesg.boot
___
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: find date of last boot

[Polytropon]

On Thu, 7 Jun 2012 21:02:57 -0500 (CDT), Robert Bonomi wrote:
> > From owner-freebsd-questi...@freebsd.org  Thu Jun  7 20:26:46 2012
> > Date: Thu, 07 Jun 2012 20:24:49 -0500
> > From: Chris 
> > To: freebsd-questions@freebsd.org
> > Subject: Re: find date of last boot
> >
> > On 6/7/2012 8:14 PM, Chris Hill wrote:
> > Why create something that is already built in?
> > As I mentioned previously, the last command lists when the system was
> > rebooted.
> 
> Probably, because last does *not* reliably do so.  
> 
> To wit:
>  $ date
>  Thu Jun  7 20:59:44 CDT 2012
>  $ uptime
>  8:58PM  up 8 days, 22:30, 1 user, load averages: 0.07, 0.03, 0.01
>  $ last reboot
>  wtmp begins Tue Jun  5 17:00:58 CDT 2012
>  $
> 
> 'wtmp' has been rotated twice since the system was booted.

Maybe introducing something along the /etc/rc execution?
An /etc/rc.local entry like

/bin/date "+%Y-%m-%d %H:%M:%S" > /var/log/thisboot.log

and then just look at the file. Requires at least one reboot
to take effect. :-)



-- 
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: find date of last boot

[Robert Bonomi]

> From owner-freebsd-questi...@freebsd.org  Thu Jun  7 20:26:46 2012
> Date: Thu, 07 Jun 2012 20:24:49 -0500
> From: Chris 
> To: freebsd-questions@freebsd.org
> Subject: Re: find date of last boot
>
> On 6/7/2012 8:14 PM, Chris Hill wrote:
> > On Thu, 7 Jun 2012, Fbsd8 wrote:
> > 
> >> dmesg command does not show date of last boot.
> >>
> >> Are there some other commands to find date of last boot?
> > 
> > That was fun. Google helped me with this; the crappy skillz are all mine.
> > 
> >  --- cut here ---
> > #!/bin/sh
> > #
> > # Find date of last boot
> > #
> > DAYS_UP=`uptime | awk '{print $3}'`
> > SEC_UP=`echo "${DAYS_UP} * 86400" | bc`
> > DATE=`date`
> > EPOCH_DATE=`date -j -f "%a %b %d %T %Z %Y" "${DATE}" "+%s"`
> > BOOT_SEC=`echo "${EPOCH_DATE} - ${SEC_UP}" | bc`
> > BOOT_DATE=`gawk -v duh=${BOOT_SEC} 'BEGIN{print strftime("%Y-%m-%d",duh)}'`
> > echo "Last boot on ${BOOT_DATE}"
> >  --- cut here ---
> > 
> > Example from this machine:
> > $ ./boot_date.sh
> > Last boot on 2010-12-26
> > $
> > 
> > Enjoy.
> > 
>
> Why create something that is already built in?
> As I mentioned previously, the last command lists when the system was
> rebooted.

Probably, because last does *not* reliably do so.  

To wit:
 $ date
 Thu Jun  7 20:59:44 CDT 2012
 $ uptime
 8:58PM  up 8 days, 22:30, 1 user, load averages: 0.07, 0.03, 0.01
 $ last reboot
 wtmp begins Tue Jun  5 17:00:58 CDT 2012
 $

'wtmp' has been rotated twice since the system was booted.



___
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: find date of last boot

[Chris]

On 6/7/2012 8:32 PM, Randal L. Schwartz wrote:
>> "Chris" == Chris   writes:
> 
> Chris> Why create something that is already built in?
> Chris> As I mentioned previously, the last command lists when the system was
> Chris> rebooted.
> 
> You must reboot a lot.  My "last" log goes back only to the first of the
> month, and my uptime is 16 days right now, so I can't see the most
> recent reboot with last.
> 
> YMMV, I guess.
> 

Good point, I didn't take into account the command goes about a month
back. I run FBSD in a vbox, and its only console anyways.

I run Debian by default but in any event, there are many reasons for
reboots and for me (typically) I see about 4 reboots a month mostly due
to patching and sec-fixes.

So indeed, YMMV is correct.

My fault for the assumption that folks boot more often than not.

-- 
Keep well,

Chris
 <><
___
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: Which FreeBSD for Intel i7-2600S and DQ67SWB3?

[Daniel Staal]

--As of June 7, 2012 3:30:52 PM -0700, David Christensen is alleged to have 
said:



For a new computer, I wouldn't go with anything earlier than FreeBSD
9.0, and in my case, upgrading to 9.0-STABLE proved stabler than the 9.0
release.


STFW:

http://lists.freebsd.org/pipermail/freebsd-questions/2012-March/239742.ht
ml

It looks like -STABLE are daily development/ test builds (?):


It's a bit more nuanced: -STABLE is -RELEASE plus features that are 
believed to be complete and tested.  -CURRENT is -STABLE plus features that 
are still under development.  I'd call -STABLE test - but not quite 
development - builds, if that makes sense.



ftp://ftp.allbsd.org/pub/FreeBSD-snapshots/amd64-amd64/

I'm looking for stability.  I'll try the 9.0-RELEASE:

ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/


This generally my choice.  You can be sure it's considered final-product 
ready.  It also allows you to use freebsd-update to get patches.  (Unless 
you compile your own.)



I don't recognize or don't remember DQ67SWB3 motherboard model, is it
from MSI?


Intel:

http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/
desktop-board-dq67sw.html

I'm not sure what the "B3" suffix means, but it's on the box.


A few other questions for the list, please:

1.  Does FreeBSD support encrypted disk partitions (slices)?


Yes, see the Handbook:

(Actually, many of your questions can be answered from the handbook.  ;) )

Using them in conjunction with ZFS is a bit complicated, but can be done. 
(Generally, you'd want to use an encrypted slice as a disk to put ZFS on.) 
ZFS itself does not currently support encryption.



2.  Does the X server in FreeBSD (?) support Intel HD 2000 integrated
graphics?


That's Sandy Bridge, and is supported as of 9.0.

Daniel T. Staal

---
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---
___
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: find date of last boot

[Randal L. Schwartz]

> "Chris" == Chris   writes:

Chris> Why create something that is already built in?
Chris> As I mentioned previously, the last command lists when the system was
Chris> rebooted.

You must reboot a lot.  My "last" log goes back only to the first of the
month, and my uptime is 16 days right now, so I can't see the most
recent reboot with last.

YMMV, I guess.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
 http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion
___
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: find date of last boot

[Chris Hill]

On Thu, 7 Jun 2012, Chris wrote:


On 6/7/2012 8:14 PM, Chris Hill wrote:

On Thu, 7 Jun 2012, Fbsd8 wrote:


dmesg command does not show date of last boot.

Are there some other commands to find date of last boot?


That was fun. Google helped me with this; the crappy skillz are all mine.


-snip-


Why create something that is already built in?


Because I learned something by doing it.

As I mentioned previously, the last command lists when the system was 
rebooted.


I'm not sure it does:

$ last reboot
wtmp begins Fri Jun  1 08:31:38 EDT 2012
$ uptime
 9:30PM  up 529 days,  8:25, 4 users, load averages: 0.02, 0.18, 0.17

...and even so, would it show a cold boot, or only a reboot?

I'll credit Doug Hardie with the best solution:
$ ls -l /var/run/dmesg.boot
-rw-r--r--  1 root  wheel  7248 Dec 26  2010 /var/run/dmesg.boot


Keep well,


You too.

--
Chris Hill   ch...@monochrome.org
** [ Busy Expunging  ]
___
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: find date of last boot

[Chris]

On 6/7/2012 8:14 PM, Chris Hill wrote:
> On Thu, 7 Jun 2012, Fbsd8 wrote:
> 
>> dmesg command does not show date of last boot.
>>
>> Are there some other commands to find date of last boot?
> 
> That was fun. Google helped me with this; the crappy skillz are all mine.
> 
>  --- cut here ---
> #!/bin/sh
> #
> # Find date of last boot
> #
> DAYS_UP=`uptime | awk '{print $3}'`
> SEC_UP=`echo "${DAYS_UP} * 86400" | bc`
> DATE=`date`
> EPOCH_DATE=`date -j -f "%a %b %d %T %Z %Y" "${DATE}" "+%s"`
> BOOT_SEC=`echo "${EPOCH_DATE} - ${SEC_UP}" | bc`
> BOOT_DATE=`gawk -v duh=${BOOT_SEC} 'BEGIN{print strftime("%Y-%m-%d",duh)}'`
> echo "Last boot on ${BOOT_DATE}"
>  --- cut here ---
> 
> Example from this machine:
> $ ./boot_date.sh
> Last boot on 2010-12-26
> $
> 
> Enjoy.
> 

Why create something that is already built in?
As I mentioned previously, the last command lists when the system was
rebooted.

-- 
Keep well,

Chris
 <><
___
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: find date of last boot

[Chris Hill]

On Thu, 7 Jun 2012, Fbsd8 wrote:


dmesg command does not show date of last boot.

Are there some other commands to find date of last boot?


That was fun. Google helped me with this; the crappy skillz are all 
mine.


 --- cut here ---
#!/bin/sh
#
# Find date of last boot
#
DAYS_UP=`uptime | awk '{print $3}'`
SEC_UP=`echo "${DAYS_UP} * 86400" | bc`
DATE=`date`
EPOCH_DATE=`date -j -f "%a %b %d %T %Z %Y" "${DATE}" "+%s"`
BOOT_SEC=`echo "${EPOCH_DATE} - ${SEC_UP}" | bc`
BOOT_DATE=`gawk -v duh=${BOOT_SEC} 'BEGIN{print strftime("%Y-%m-%d",duh)}'`
echo "Last boot on ${BOOT_DATE}"
 --- cut here ---

Example from this machine:
$ ./boot_date.sh
Last boot on 2010-12-26
$

Enjoy.

--
Chris Hill   ch...@monochrome.org
** [ Busy Expunging  ]
___
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"

setting gcc46 as default compiler?

[Jeff Hamann]

I've built and installed the gcc46 compiler(s) - need gfortran - and I can't 
seem to find the correct documentation on how to update /etc/make.conf for 
including the gfortran46. 

This is what mine currently looks like:

$ cat make.conf
# added by use.perl 2012-06-07 03:03:21
PERL_VERSION=5.10.1
.if !empty(.CURDIR:M/usr/ports/*) && exists(/usr/local/bin/gcc46)
CC=gcc46
CXX=g++46
CPP=cpp46
FC=gfortran46
.endif

FFLAGS=-O2 -mtune=athlon64
CC=gcc46
CXX=g++46
CPP=cpp46
FC=gfortran46

$ 

Am I close? Help?

Respectfully,
Jeff.


Jeff Hamann, PhD
PO Box 1421
Corvallis, Oregon 97339-1421
230 SW 3rd Street Suite #310
Corvallis, Oregon 97333
541-602-5438 (c)
541-754-2457 (h)
jeff.hamann[at]forestinformatics[dot]com
jeff.d.hamann[at]gmail[dot]com
http://www.forestinformatics.com
http://en.wikipedia.org/wiki/Forest_informatics

To ensure that your email is processed, include a subject entry in your email.




___
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: find date of last boot

[Chuck Swiger]

On Jun 7, 2012, at 4:15 PM, Fbsd8 wrote:
> dmesg command does not show date of last boot.
> 
> Are there some other commands to find date of last boot?

Try "last | grep reboot".  

Regards,
-- 
-Chuck

___
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: find date of last boot

[Doug Hardie]

On 7 June 2012, at 16:33, Polytropon wrote:

> On Thu, 07 Jun 2012 19:15:25 -0400, Fbsd8 wrote:
>> dmesg command does not show date of last boot.
>> 
>> Are there some other commands to find date of last boot?
> 
> Check the lines in /var/log/messages. Unless you're not
> experiencing a newsyslog message (new log file started),
> the "kernel: Copyright (c) 1992-2011 The FreeBSD Project."
> string (first line of typical dmesg, check for your particular
> OS version!) indicates when the system was booted. But
> note that the date format is not the common sortable
> kind of `date "+%d.%m.%Y"`.
> 
> Another idea (as already mentioned) is to subtract `uptime`
> from current `date`. :-


Check the timestamp on /var/run/dmesg.boot  That is only written to when the 
system boots.___
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: find date of last boot

[Karl Vogel]

>> On Thu, 07 Jun 2012 19:15:25 -0400, 
>> Fbsd8  said:

F> dmesg command does not show date of last boot.  Are there some other
F> commands to find date of last boot?

   Try "last reboot".

-- 
Karl Vogel  I don't speak for the USAF or my company

He is not only dull himself; he is the cause of dullness in others.
--Samuel Johnson
___
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: find date of last boot

[Robert Bonomi]

> From owner-freebsd-questi...@freebsd.org  Thu Jun  7 18:16:50 2012
> Date: Thu, 07 Jun 2012 19:15:25 -0400
> From: Fbsd8 
> To: FreeBSD Questions 
> Subject: find date of last boot
>
> dmesg command does not show date of last boot.
>
> Are there some other commands to find date of last boot?

'man uptime'

___
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: find date of last boot

[Fish Kungfu]

Try:  who -b

Cheers...Fish


07.06.2012, 18:31, "Bill Yuan" :
> If you store the time in a file as log everytime when it boots up,
> then that means you can have more then "now -  uptime"
>
> On Fri, Jun 8, 2012 at 7:20 AM, Chris Hill  wrote:
>
>>  On Thu, 7 Jun 2012, Fbsd8 wrote:
>>
>>  dmesg command does not show date of last boot.
>>>  Are there some other commands to find date of last boot?
>>  Perhaps somehow subtract `uptime` from today's date?
>>
>>  --
>>  Chris Hill   ch...@monochrome.org
>>  ** [ Busy Expunging  ]
>>
>>  __**_
>>  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"
___
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: find date of last boot

[Chris]

On 6/7/2012 6:31 PM, Bill Yuan wrote:
> If you store the time in a file as log everytime when it boots up,
> then that means you can have more then "now -  uptime"
> 
> On Fri, Jun 8, 2012 at 7:20 AM, Chris Hill  wrote:
> 
>> On Thu, 7 Jun 2012, Fbsd8 wrote:
>>
>> dmesg command does not show date of last boot.
>>>
>>> Are there some other commands to find date of last boot?
>>>
>>
>> Perhaps somehow subtract `uptime` from today's date?
>>
>> --
>> Chris Hill   ch...@monochrome.org
>> ** [ Busy Expunging  ]
>>
>> __**_
>> 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"
> 
> 
> 


Try the command,  last
maybe that will give you some info that you are looking for.


-- 
Keep well,

Chris
 <><
___
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: find date of last boot

[Polytropon]

On Thu, 07 Jun 2012 19:15:25 -0400, Fbsd8 wrote:
> dmesg command does not show date of last boot.
> 
> Are there some other commands to find date of last boot?

Check the lines in /var/log/messages. Unless you're not
experiencing a newsyslog message (new log file started),
the "kernel: Copyright (c) 1992-2011 The FreeBSD Project."
string (first line of typical dmesg, check for your particular
OS version!) indicates when the system was booted. But
note that the date format is not the common sortable
kind of `date "+%d.%m.%Y"`.

Another idea (as already mentioned) is to subtract `uptime`
from current `date`. :-)



-- 
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: find date of last boot

[Bill Yuan]

If you store the time in a file as log everytime when it boots up,
then that means you can have more then "now -  uptime"

On Fri, Jun 8, 2012 at 7:20 AM, Chris Hill  wrote:

> On Thu, 7 Jun 2012, Fbsd8 wrote:
>
> dmesg command does not show date of last boot.
>>
>> Are there some other commands to find date of last boot?
>>
>
> Perhaps somehow subtract `uptime` from today's date?
>
> --
> Chris Hill   ch...@monochrome.org
> ** [ Busy Expunging  ]
>
> __**_
> 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"

how to filter network by MAC and IP at the same time

[Bill Yuan]

hi all,

i am using freebsd 9.0 as a firewall and i want to filter the traffic by
the mac and the ip at the same time,

for example, i only allow my laptop  can go throught the
firewalll when it's using IP 

for how to config the firewall rules?


I tried to configure the firewall by  the rule below , but it doesnt work

 ipfw add  1 allow all from  to any MAC  any
 ipfw add  1 allow all from any to   MAC any 

but it doesnt work. also found the explanation on google, someone already
asked this question before.

but I did not find the solution for this requirement.  can someone tell me
how ? thanks in advance.


Best Regards,
BYCN82
___
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: find date of last boot

[Chris Hill]

On Thu, 7 Jun 2012, Fbsd8 wrote:


dmesg command does not show date of last boot.

Are there some other commands to find date of last boot?


Perhaps somehow subtract `uptime` from today's date?

--
Chris Hill   ch...@monochrome.org
** [ Busy Expunging  ]
___
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: dumping file system subtree (/var)

[Warren Block]

On Thu, 7 Jun 2012, Gary Aitken wrote:

When I originally set up my SSD, the stuff I was following indicated 
there was no need to put anythng on a separate filesystem.  I'm now 
trying to build a backup system on a usb drive and I want a separate 
/var and /tmp.


I had originally set the nodump flag on /tmp and /var, so my snapshot 
is empty for those.


There are several things in /var that are worth keeping, and they are 
pretty small.


I don't think there's any reason to preserve /tmp, but is there any 
good way to copy /var from the running system on the SSD to another 
filesystem (and still preserve everything, including flags)?  My 
impression is both mksnap_ffs and dump should only be used on a 
complete filesystem, not a subtree.


Or do I need to unset the nodump flag on /var, make a snapshot of /, 
take a dump :-), and then split the /var out upon restore?


Snapshots don't have to be made separately, dump's -L option does that 
automatically:

http://www.wonkity.com/~wblock/docs/html/backup.html

Restoring from a dumpfile is an easy way.  net/rsync has a config option 
to support flags, but I haven't tried it.


And would it be wise to repartition the SSD to put /var and /tmp on 
their own partitions?


When I did that recently, I put /var on a small separate partition but 
used tmpfs(5) for /tmp.

___
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"

find date of last boot

[Fbsd8]

dmesg command does not show date of last boot.

Are there some other commands to find date of last boot?
___
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: Configuration problem with IPv6 router ("cannot forward src")

[Robert Bonomi]

> From: Bruce Cran 
>
> I'm trying to set up a IPv6 router (running -current) on my home 
> network. My ISP gives me a /128 via PPP and I have a /48 allocation, 
> which I use to give em0 and tun0 public addresses in different subnets 
> (tun0 is assigned the address via ppp.linkup).
> I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable, 
> ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites 
> from the router.
>
> The problem is that rtadvd continues advertising the default gateway as 
> tun0's link-local address - and pinging from a machine on the network 
> results in "cannot forward src" messages on the router (strangely, 
> despite hisaddr being fe80::205:... in ppp.log, the kernel logs the 
> address as fe80:f::205:...).
>
> Is there some extra configuration I've likely missed that's needed when 
> using IPv6 via PPP?

Please provide the output from these two commands:
   ifconfig  -a
   netstat -nr
on both the router and on an 'inside' machine. (identifying which is which :)

There is also a question of 'where' the /48 comes from -- and how 
traffic to those addresses is being routed from the outside world.

___
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"

Configuration problem with IPv6 router ("cannot forward src")

[Bruce Cran]

I'm trying to set up a IPv6 router (running -current) on my home 
network. My ISP gives me a /128 via PPP and I have a /48 allocation, 
which I use to give em0 and tun0 public addresses in different subnets 
(tun0 is assigned the address via ppp.linkup).
I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable, 
ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites 
from the router.


The problem is that rtadvd continues advertising the default gateway as 
tun0's link-local address - and pinging from a machine on the network 
results in "cannot forward src" messages on the router (strangely, 
despite hisaddr being fe80::205:... in ppp.log, the kernel logs the 
address as fe80:f::205:...).


Is there some extra configuration I've likely missed that's needed when 
using IPv6 via PPP?


--
Bruce Cran
___
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: dumping file system subtree (/var)

[Bernt Hansson]

2012-06-07 22:05, Gary Aitken skrev:

When I originally set up my SSD, the stuff I was following indicated there was 
no need to put anythng on a separate filesystem.  I'm now trying to build a 
backup system on a usb drive and I want a separate /var and /tmp.

I had originally set the nodump flag on /tmp and /var, so my snapshot is empty 
for those.

I don't think there's any reason to preserve /tmp, but is there any good way to 
copy /var from the running system on the SSD to another filesystem (and still 
preserve everything, including flags)?  My impression is both mksnap_ffs and 
dump should only be used on a complete filesystem, not a subtree.

Or do I need to unset the nodump flag on /var, make a snapshot of /, take a 
dump :-), and then split the /var out upon restore?

And would it be wise to repartition the SSD to put /var and /tmp on their own 
partitions?



http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NEW-HUGE-DISK
___
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: Which FreeBSD for Intel i7-2600S and DQ67SWB3?

[David Christensen]

On 06/06/2012 08:33 PM, Thomas Mueller wrote:

This looks like the processor I have, I think you would use amd64.  Almost 
certainly your system is 64-bit as opposed to 32-bit.


Thanks for the reply.  :-)


Yes, definitely 64-bit.



For a new computer, I wouldn't go with anything earlier than FreeBSD 9.0, and 
in my case, upgrading to 9.0-STABLE proved stabler than the 9.0 release.


STFW:

http://lists.freebsd.org/pipermail/freebsd-questions/2012-March/239742.html

It looks like -STABLE are daily development/ test builds (?):

ftp://ftp.allbsd.org/pub/FreeBSD-snapshots/amd64-amd64/

I'm looking for stability.  I'll try the 9.0-RELEASE:

ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/



Base system includes ZFS.


Good.



I've never used virtual machines, but VirtualBox is popular for this purpose.


VirtualBox does seem to be popular.  It played with it on Debian Testing 
(Wheezy), but I believe the shared folder feature filled my root 
partition and I couldn't locate or remove the blockage.




Samba is in ports.


Okay.



I don't recognize or don't remember DQ67SWB3 motherboard model, is it from MSI?


Intel:

http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq67sw.html

I'm not sure what the "B3" suffix means, but it's on the box.


A few other questions for the list, please:

1.  Does FreeBSD support encrypted disk partitions (slices)?

2.  Does the X server in FreeBSD (?) support Intel HD 2000 integrated 
graphics?



David
___
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: Is this something we (as consumers of FreeBSD) need to be aware of?

[Edward M]

On 06/06/2012 01:35 PM, Alejandro Imass wrote:

But this is more to do with the BIOS than with Intel as such. Wasn't
there a FreeBIOS, later LinuxBIOS, now coreboot I believe..?
So replacing the BIOS entirely wouldn't suffice to override all this nonsense?
___
anybody will be free  to disable secure boot in x86 systems and run 
any OS, so this is not really a big deal.


___
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: dumping file system subtree (/var)

[Mark Felder]

Would rsync or cpdup from single user mode cover your needs? Should cover  
everything and then you can just reboot into your newly partitioned system.

___
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"

dumping file system subtree (/var)

[Gary Aitken]

When I originally set up my SSD, the stuff I was following indicated there was 
no need to put anythng on a separate filesystem.  I'm now trying to build a 
backup system on a usb drive and I want a separate /var and /tmp.

I had originally set the nodump flag on /tmp and /var, so my snapshot is empty 
for those.

I don't think there's any reason to preserve /tmp, but is there any good way to 
copy /var from the running system on the SSD to another filesystem (and still 
preserve everything, including flags)?  My impression is both mksnap_ffs and 
dump should only be used on a complete filesystem, not a subtree.

Or do I need to unset the nodump flag on /var, make a snapshot of /, take a 
dump :-), and then split the /var out upon restore?

And would it be wise to repartition the SSD to put /var and /tmp on their own 
partitions?

Gary



___
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"

doesn't dummynet work with vlan ?

[Yavuz Maşlak]

Hello there 
I use freebsd8.2
I added dummynet and other followings into the kernel;
options IPFIREWALL #firewall
options IPFIREWALL_VERBOSE #print information about
options IPFIREWALL_FORWARD #enable trasparent proxy support 
options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default
options HZ=1000
options DUMMYNET
options IPDIVERT
options DEVICE_POLLING

I have 4 networks which seperate from eachother with vlan.
I wish to bandlimit for every vlan network using dummynet.
I have 2 ethernet cards for that. one of them is wan other one is inbound is
tagged.
vlan works well
I configured a network to limit using dummynet; ipfw.sh
###
ipfw -f flush

ipfw pipe 11 config bw 2Mbit/s # Vlan104
ipfw pipe 12 config bw 2Mbit/s # 6.Port on the switch

ipfw add pipe 11 ip from any to 10.12.4.0/24 in via em0
ipfw add pipe 12 ip from 10.12.4.0/24 to any out xmit em0
###
em0 is for outside in the server.
as a client my pc is in vlan104 namely i am behind the firewall
when i execute the ipfw.sh, I can't reach to the internet.

ipfw add pipe 12 ip from 10.12.4.0/24 to any out xmit em0 
above line works it actually limits but ;
ipfw add pipe 11 ip from any to 10.12.4.0/24 in via em0 
above line doesn't work properly
it obstructs my http and icmp requests. so i can't reach to internet.

Whereas i remove "ipfw add pipe 11 ip from any to 10.12.4.0/24 in via em0"
from ipfw.sh
I can either ping at outbound or reach to internet. 

I tried vlan104 instead of em0 "in via em0" 
that doesn't help me.

I don't use proxy. I use nat  
What can be the problem ?

Thanks

___
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: FreeBSD9 - I can't get my mouse to work

[Jerry]

On Thu, 7 Jun 2012 19:17:42 +0200
C. P. Ghost articulated:

>On Thu, Jun 7, 2012 at 7:14 PM, C. P. Ghost  wrote:
>> On Wed, Jun 6, 2012 at 1:14 AM, Walter Hurry 
>> wrote:
>>> Firstly, sorry if this is a bit of a newbie question. I am quite
>>> new to FreeBSD (though fairly experienced at Linux). Almost
>>> everything in FreeBSD is fine, except that no matter what I try I
>>> cannot get the (USB) mouse to work.
>>
>> IMHO, you've hit the same problem as this:
>>
>> http://lists.freebsd.org/pipermail/freebsd-questions/2012-May/241148.html
>
>Sorry, I forgot to add the original mail:
>
>http://lists.freebsd.org/pipermail/freebsd-questions/2012-May/241042.html
>
>> Unfortunately, there was no follow-up, and nobody seems
>> to have enough skills to fix hald.

HAL is now deprecated on GNU/Linux systems, with functionality being
merged into udev as of 2008–2010. Why would anyone try to resurrect a
dead application. As of 2011, GNU/Linux distributions such as Ubuntu,
Debian, and Fedora, and projects such as KDE, GNOME and X.org are in
the process of deprecating HAL as it has "become a large monolithic
unmaintainable mess".

-- 
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: driver for cell phone modem

[Lars Eighner]

On Thu, 7 Jun 2012, Fbsd8 wrote:


Running 9.0 and thinking about changing to this verizon model 551L usb
cell phone modem.



http://www.verizonwireless.com/b2c/store/controller?\
item=phoneFirst&action=viewPhoneDetail&selectedPhoneId=5632


Your link does not lead to specific information about this device.  However,
I gather it is a LTE device, which is good because at least some are
supported (whereas no WiMax devices are supported).  Moreover, the promise
of Linux and Mac 10.4+ compatibility seems a positive sign.  But I can't
find anything that flatly says it will work with FreeBSD.

Have you considered a mobile (or base station) hotspot?  Since these will
connect with up to five wi-fi devices, and you can almost certainly find a
dongle that will work with your ethernet card, maybe you should take a look
at them.



It's a usb plugin cell modem for internet access.

Before I go through the purchase and signup process I want to verify
Freebsd has a driver that works with this 4G cell device.


--
Lars Eighner
http://www.larseighner.com/index.html
8800 N IH35 APT 1191 AUSTIN TX 78753-5266

___
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: Is this something we (as consumers of FreeBSD) need to be aware of?

[Nomen Nescio]

> Totally off-topic, but I actually used mine to run gameboy and gameboy
> advance emulators ^^'

And I use mine to write PPC code. But Sony's business model wasn't about
software development or doing what you and I are doing. 

> > Windows activation can check the firmware level and Intel's management BIOS
> > is connected to the net even when your new PC is shut off (as long as it is
> > plugged in). If you go along with this they can do whatever you want. You're
> > submitting to true remote management/control over YOUR hardware and life.
> > 
> 
> Well, I don't know about that... how do you suggest the BIOS gets its IP ?
> The 8-STABLE box that acts as my router is not going to serve one over
> DHCP or BOOTP any time soon.

You seem to be focusing on the .01% cases. The UEFI was specifically
designed to allow TCP/IP from the BIOS with the machine powered off, well
before secure boot was on the table. Just because you can firewall it off
doesn't mean everybody else understands the issues or knows how, because
they don't. For all we know Intel or Microshaft have plenty of DHCP servers
ready for this.

> As for sniffing the network to guess the router + DNS servers, that one
> might be a bit far-fetched.

It's not going to be like Skype and do NAT traversals by itself and find
it's way out of your box. It's just that if you leave your computer plugged
in like everybody in the world does, the BIOS will be able to do whatever
they program it to do, including downloading and flashing BIOS updates and
whatever malware the dreaded Chinese hackers and Russian botnets
create. Microshaft is pretty stupid because every time they create something
"secure" the Russians or Chinese hack it in a day. I'll be surprised if they
don't crack Verisigns keys and create exploits and this will be a better
attack vector than they ever had because now they can flash your BIOS. All
they could do before was replace your boot sector.

> Seriously you need to stop with the "wintel", "microshaft", "mafia" and
> all the stuff.

Why?

> However, there are literally thousands of people reading this list and
> just because they do not share your ideals doesn't necessarily make them
> advocates of this so-called "mafia", or blind sheep.

Aside from the one ostrich I spanked I don't think they are either.

> Finally, I can't come up with a scenario where my CEO is going to okay
> alpha boxes for our regular web servers and such.
> Our x86 servers run just fine and are roughly 12.000% cheaper.

Yeah but nobody cares about that because they're not talking about doing
this to server boxes. It's home PCs where people are usually not well
informed and are usually defenseless. Try to stay focused on the discussion.

> I can hardly see Dell shipping x86 servers with locked-in Windows
> installs, that just won't do for their business.

Right, so this doesn't apply. Why do you keep bringing it up? Even if it did
apply, who cares? It's not your problem. The target is commodity WinTel
crapware boxes.


> I have to admit I'd love to see it though, I've always wanted us to try
> Cisco or IBM's blade servers in lieu of Dell's.

Intel is bad not just because of UEFI and secure boot. They're bad because
they have conspired many times over the years with Microshaft to create a
monopoly. Everybody should object to that.

Say NO to the WinTel Mafia! (had to add that ;-))
___
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: Proper Port Forwarding

[Chuck Swiger]

On Jun 7, 2012, at 10:29 AM, Michael Sierchio wrote:
> On Thu, Jun 7, 2012 at 10:27 AM, Michael Sierchio  wrote:
>> net.inet.tcp.finwait2_timeout: 6  <- ms, ten minutes
> 
> I can't do arithmetic, but you get the idea. A full minute.

Yes; that's already shorter than possible MAXTTL value of packets, which can be 
anywhere up to 255 seconds (~= 5 minutes).

Well, it's usually OK for a webserver to decide that it doesn't need to wait 
around for clients to properly shutdown their HTTP connections, but one might 
want to be more careful about zapping sockets early for HTTPS/SSL connections 
(ie, an online store doing a CC transaction or the like).

Regards,
-- 
-Chuck

___
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: Proper Port Forwarding

[Michael Sierchio]

On Thu, Jun 7, 2012 at 10:27 AM, Michael Sierchio  wrote:

> net.inet.tcp.finwait2_timeout: 6  <- ms, ten minutes

I can't do arithmetic, but you get the idea. A full minute.
___
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: Proper Port Forwarding

[Michael Sierchio]

On Thu, Jun 7, 2012 at 10:15 AM, Michael Powell  wrote:

> There is also this you can place in /etc/sysctl.conf:
>
> net.inet.tcp.fast_finwait2_recycle=1
>

Good catch.  The defaults are perhaps not ideal in all cases:

net.inet.tcp.finwait2_timeout: 6  <- ms, ten minutes
net.inet.tcp.fast_finwait2_recycle: 0
___
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: List total traffic amount across external nic

[Dean E. Weimer]

On 06/07/2012 11:14, Fbsd8 wrote:

Running ipfilter and trying to list the total amount of the traffic
passing through the external NIC.

Maybe there is some other command to show this info.

Any help is appreciated.
___
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"


try: systat -ifstat

--
Thanks,
 Dean E. Weimer
 http://www.dweimer.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: FreeBSD9 - I can't get my mouse to work

[C. P. Ghost]

On Thu, Jun 7, 2012 at 7:14 PM, C. P. Ghost  wrote:
> On Wed, Jun 6, 2012 at 1:14 AM, Walter Hurry  wrote:
>> Firstly, sorry if this is a bit of a newbie question. I am quite new to
>> FreeBSD (though fairly experienced at Linux). Almost everything in FreeBSD
>> is fine, except that no matter what I try I cannot get the (USB) mouse to
>> work.
>
> IMHO, you've hit the same problem as this:
>
> http://lists.freebsd.org/pipermail/freebsd-questions/2012-May/241148.html

Sorry, I forgot to add the original mail:

http://lists.freebsd.org/pipermail/freebsd-questions/2012-May/241042.html

> Unfortunately, there was no follow-up, and nobody seems
> to have enough skills to fix hald.
>
> Good luck,
> -cpghost.

-- 
Cordula's Web. http://www.cordula.ws/
___
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: driver for cell phone modem

[Matthias Apitz]

El día Thursday, June 07, 2012 a las 12:00:26PM -0400, Fbsd8 escribió:

> Running 9.0 and thinking about changing to this verizon model 551L usb
> cell phone modem.
> http://www.verizonwireless.com/b2c/store/controller?item=phoneFirst&action=viewPhoneDetail&selectedPhoneId=5632
> 
> It's a usb plugin cell modem for internet access.
> 
> Before I go through the purchase and signup process I want to verify
> Freebsd has a driver that works with this 4G cell device.

I haven't accessed the above specifications (if there are any at all)
because the page asks data I'm unwilling to enter;

In general, it depends. If the cellphone (like my Openmoko Freerunner)
acts on USB as an Ethernet device (man cdce) and itself then as a router
to the provider, it will work; if it gives direct serial access to the
chips, it must be checked based on the USB vendorID and productID.

Look for a dealer who allows to connect it once to your laptop and read
the ID with usbconfig(8).

HIH

matthias

-- 
Matthias Apitz
e  - w http://www.unixarea.de/
UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5
___
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: FreeBSD9 - I can't get my mouse to work

[Erich]

Hi,

On 07 June 2012 12:51:05 Jerry wrote:
> On Thu, 07 Jun 2012 18:33:43 +0200
> Bernt Hansson articulated:
> 
> >2012-06-06 04:21, Walter Hurry skrev:
> >> On Wed, 06 Jun 2012 01:22:51 +0200, Bernt Hansson wrote:
>  Option "AutoAddDevices" "On"
> >>>
> >>> Set this to off.
> >>>
> >> Thanks for the reply. Yes, I've tried setting it to "Off", but there
> >> is no apparent difference; only a new set of messages in Xorg.0.log:
> >>
I might was not clear in my former message. I use the parameters given for 
playing until I have a combination which works. The settings there are my 
current working settings.

Sometime I will have to change parameters after updating X, sometimes they 
continue to work. It all seems more or less random to me. The settings also 
differ for the same version of X on different hardware.

> >Have you tried without a xorg.conf file I do not have one.
> 
Not having this file does not work for me either. It actually never worked for 
me.

> when the keyboard is not even recognized. For the record, my Microsoft
> friends are really impressed with this. They have started a pool to see
> how many attempts it takes before it starts correctly.
> 
Hey, your friends have a good sense of humour.  They should join here.

Erich
___
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: Proper Port Forwarding

[Michael Powell]

Michael Sierchio wrote:

> On Wed, Jun 6, 2012 at 11:31 AM, Simon  wrote:
> 
>> This easily causes DoS for when too many FIN_WAIT_2 are created and IPFW
>> stops forwarding using the rule above because of "too many dynamic rules"
> 
> Change the defaults for the fw.dyn sysctl MIB nodes
> 
> to something like
> 
> net.inet.ip.fw.dyn_short_lifetime=3
> net.inet.ip.fw.dyn_udp_lifetime=3
> net.inet.ip.fw.dyn_rst_lifetime=1
> net.inet.ip.fw.dyn_fin_lifetime=1
> net.inet.ip.fw.dyn_syn_lifetime=10

There is also this you can place in /etc/sysctl.conf:

net.inet.tcp.fast_finwait2_recycle=1

I do this for my web servers. It helps reduce the volume somewhat  of 
FIN_WAIT_2 from building up by expiring them sooner. 

-Mike


___
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: FreeBSD9 - I can't get my mouse to work

[C. P. Ghost]

On Wed, Jun 6, 2012 at 1:14 AM, Walter Hurry  wrote:
> Firstly, sorry if this is a bit of a newbie question. I am quite new to
> FreeBSD (though fairly experienced at Linux). Almost everything in FreeBSD
> is fine, except that no matter what I try I cannot get the (USB) mouse to
> work.

IMHO, you've hit the same problem as this:

http://lists.freebsd.org/pipermail/freebsd-questions/2012-May/241148.html

Unfortunately, there was no follow-up, and nobody seems
to have enough skills to fix hald.

Good luck,
-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/
___
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: List total traffic amount across external nic

[Matthias Apitz]

El día Thursday, June 07, 2012 a las 12:14:56PM -0400, Fbsd8 escribió:

> Running ipfilter and trying to list the total amount of the traffic 
> passing through the external NIC.
> 
> Maybe there is some other command to show this info.
> 
> Any help is appreciated.

In the past I used for this:

$ cd /usr/ports/net/trafshow
$ cat pkg-descr 
TrafShow continuously displays the information regarding packet
traffic on the configured network interface that matches the boolean
expression. It periodically sorts and updates this information. It
may be useful for locating suspicious network traffic on the net.

WWW: http://soft.risp.ru/trafshow/index_en.shtml

HIH

matthias
-- 
Matthias Apitz
e  - w http://www.unixarea.de/
UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5
___
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: FreeBSD9 - I can't get my mouse to work

[Jerry]

On Thu, 07 Jun 2012 18:33:43 +0200
Bernt Hansson articulated:

>2012-06-06 04:21, Walter Hurry skrev:
>> On Wed, 06 Jun 2012 01:22:51 +0200, Bernt Hansson wrote:
 Option "AutoAddDevices" "On"
>>>
>>> Set this to off.
>>>
>> Thanks for the reply. Yes, I've tried setting it to "Off", but there
>> is no apparent difference; only a new set of messages in Xorg.0.log:
>>
>> (EE) config/hal: couldn't initialise context: unknown error (null)
>> (EE) config/hal: NewInputDeviceRequest failed (8)
>> (EE) config/hal: NewInputDeviceRequest failed (8)
>> (EE) config/hal: NewInputDeviceRequest failed (8)
>> (EE) config/hal: NewInputDeviceRequest failed (8)
>> (EE) config/hal: NewInputDeviceRequest failed (8)
>> (EE) config/hal: NewInputDeviceRequest failed (8)
>> (WW) Mouse0: No Device specified, looking for one...
>
>Have you tried without a xorg.conf file I do not have one.

I have had the same frigging problem since updating Xorg and have tried
every suggestion made on  this list so far which includes activating &
deactivating "hald", which is actually deprecated; however, I don't
think that anyone here cares. In any case, when the mouse hangs I
simple do a forced shutdown of Xorg and then restart it. There is
approximately a 50/50 chance it will work on the next attempt. I just
keep doing it until it works correctly. Furthermore, the real fun is
when the keyboard is not even recognized. For the record, my Microsoft
friends are really impressed with this. They have started a pool to see
how many attempts it takes before it starts correctly.

-- 
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: Contribution to PUC driver

[Fernando Apesteguía]

On Thu, Jun 7, 2012 at 4:29 PM, Dennis Oyama  wrote:
> Patch to update pucdata.c to support the Perle Systems Ltd. Multiport Speed 
> LE Serial cards.

Maybe you could post this at freebsd-hackers@ for discussion or send
the patch using send-pr[1]

Cheers.

[1] http://www.freebsd.org/send-pr.html

>
>
>
> --- pucdata.orig.c      2012-02-10 12:24:47.0 -0500
> +++ pucdata.c   2012-02-10 12:40:34.0 -0500
> @@ -668,11 +668,35 @@
>         */
>        {   0x155f, 0x0331, 0x, 0,
> -           "Perle Speed4 LE",
> +           "Perle Ultraport4 Express",
>            DEFAULT_RCLK * 8,
>            PUC_PORT_4S, 0x10, 0, 8,
>        },
> +        {   0x155f, 0xB012, 0x, 0,
> +            "Perle Speed2 LE",
> +            DEFAULT_RCLK * 8,
> +            PUC_PORT_2S, 0x10, 0, 8,
> +        },
> +
> +        {   0x155f, 0xB022, 0x, 0,
> +            "Perle Speed2 LE",
> +            DEFAULT_RCLK * 8,
> +            PUC_PORT_2S, 0x10, 0, 8,
> +        },
> +
> +        {   0x155f, 0xB004, 0x, 0,
> +            "Perle Speed4 LE",
> +            DEFAULT_RCLK * 8,
> +            PUC_PORT_4S, 0x10, 0, 8,
> +        },
> +
> +        {   0x155f, 0xB008, 0x, 0,
> +            "Perle Speed8 LE",
> +            DEFAULT_RCLK * 8,
> +            PUC_PORT_8S, 0x10, 0, 8,
> +        },
> +
>        {   0x14d2, 0x8010, 0x, 0,
>            "VScom PCI-100L",
>            DEFAULT_RCLK * 8,
>
>
>
>
> ___
>         Dennis Oyama
>   Technical Sales Engineer
>      Perle Systems Ltd.
>        1-800-467-3753
>     Direct: 905-946-5037
>       doy...@perle.com
>       CompTIA Security+
> ___
>
>
> ___
> 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: Proper Port Forwarding

[Ian Smith]

In freebsd-questions Digest, Vol 418, Issue 10, Message: 7
On Wed, 06 Jun 2012 14:31:24 -0400 "Simon"  wrote:

 > Can someone suggest an alternative/proper way to port forward using ipfw. 
 > Right
 > now I have the following and some bad clients cause too many FIN_WAIT_2 state
 > 
 > fwd IP,PORT2 tcp from any to me dst-port PORT1 keep-state
 > 
 > This easily causes DoS for when too many FIN_WAIT_2 are created and IPFW
 > stops forwarding using the rule above because of "too many dynamic rules"

Michael's and Dan's suggestions of adjusting sysctl net.inet.ip.fw.dyn* 
variables are good; consider also using 'limit' instead of 'keep-state', 
which works the same except limiting the number of open connections to a 
specified number.  See ipfw(8) /limit and /EXAMPLES for more, but eg:

 fwd IP,PORT2 tcp from any to me dst-port PORT1 limit src-addr 9

to prevent any one source address opening more than 9 connections, or

 fwd IP,PORT2 tcp from any to me dst-port PORT1 limit dst-port 42

to limit total open connections by everyone to dst-port PORT1 to 42.

cheers, Ian
___
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"

List total traffic amount across external nic

[Fbsd8]

Running ipfilter and trying to list the total amount of the traffic 
passing through the external NIC.


Maybe there is some other command to show this info.

Any help is appreciated.
___
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"

driver for cell phone modem

[Fbsd8]

Running 9.0 and thinking about changing to this verizon model 551L usb
cell phone modem.
http://www.verizonwireless.com/b2c/store/controller?item=phoneFirst&action=viewPhoneDetail&selectedPhoneId=5632

It's a usb plugin cell modem for internet access.

Before I go through the purchase and signup process I want to verify
Freebsd has a driver that works with this 4G cell device.

Thanks

___
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: Is this something we (as consumers of FreeBSD) need to be aware of?

[Damien Fleuriot]

On 6/7/12 3:43 PM, Nomen Nescio wrote:
>>> But my point is that MS doesn't issue the updates, they have to ask the
>>> BIOS vendors to do so, and then the MB vendors have to take the update,
>>> and then the users have to install the update. The incentive at each
>>> level is generally very small. It does create some confusion, but is
>>> hardly an enforcement mechanism. It would disable older versions of
>>> FreeBSD on newer hardware, but not much else.
> 
> This can be automated. Many mobo manufacturers have software that searches
> for new BIOS and flashes it "for" you. All they have to do is get on board
> and make this automatic like Windows Updates. Don't think they haven't
> thought this far ahead. I believe some offer this now.
> 
>>> A previous poster has pointed out that MS can't revoke a certificate
>>> belonging to RH, but I suppose the could ask the BIOS vendors to treat
>>> it as revoked. I don't know what the response would be.
> 
> MS and Intel are running this. If Verisign is just a trusted 3rd party
> (without administrative duties) they can well defer to the Microshaft Mafia
> and do as they're told. It wouldn't be the first time. For example, did
> everybody already forget the Microshaft Mafias' initiation of the FBI server
> raids on the botnet? Many innocent companies and peoples hosting got screwed
> during this takeover. But it was all in the name of "justice". If we can get
> a few Russian hackers then it's well worth damaging your business and
> property. We're from Microshaft Mafia and the FBI and we're here to help.
> 
>> This is akin to, for example, Sony's race against Homebrewers on the
>> good ol' PSP.
>>
>> When hackers found a hardware flaw that enabled them to install custom
>> firmware, Sony had to release new versions of the consoles with fixed
>> hardware.
>>
>> The old ones were still exploitable but the new ones weren't.
> 
> That is a little different, possibly. For one thing, Sony detected whether
> you had the updates they wanted you to install and if you don't have them
> installed you can't play on their PlayStation network. For 99.99% of
> PlayStation users this is the whole point of buying their console. So if you
> don't upgrade all you have is a box for playing local games which most
> people don't seem to want to do. 
> 


Totally off-topic, but I actually used mine to run gameboy and gameboy
advance emulators ^^'



> All the Intel and Microshaft Mafia have to do is a similar thing, and make
> your PC or Windows stop working unless you install their updates, or tell
> the FBI your PC is possibly "infected" and part of a Russian botnet etc. and
> you won't be allowed on the internet until you upgrade your system to a safe
> level to avoid these horrible threats. This idea was floated publicly even
> unrelated to so-called "secure boot".
> 

I refer you to the years old threads about Palladium and the TCPA that
Microsoft dreamed back in the days.



> Windows activation can check the firmware level and Intel's management BIOS
> is connected to the net even when your new PC is shut off (as long as it is
> plugged in). If you go along with this they can do whatever you want. You're
> submitting to true remote management/control over YOUR hardware and life.
> 

Well, I don't know about that... how do you suggest the BIOS gets its IP ?
The 8-STABLE box that acts as my router is not going to serve one over
DHCP or BOOTP any time soon.

As for sniffing the network to guess the router + DNS servers, that one
might be a bit far-fetched.



> This is the beginning of a lot of bad Big Brother stuff and if people accept
> it now they get what they deserve tomorrow.
> 
> Say "NO" to the Intel/Microshaft Mafia. Say "NO" to "Secure" boot.
> 
> Run MIPS and Alpha hardware if you have to, just DUMP INTEL AND THE
> MICROSHAFT MAFIA.

Seriously you need to stop with the "wintel", "microshaft", "mafia" and
all the stuff.

We get it, you don't like them.

However, there are literally thousands of people reading this list and
just because they do not share your ideals doesn't necessarily make them
advocates of this so-called "mafia", or blind sheep.




Finally, I can't come up with a scenario where my CEO is going to okay
alpha boxes for our regular web servers and such.
Our x86 servers run just fine and are roughly 12.000% cheaper.

"We need to distance ourselves from Intel, apparently they run their
business like darned brigands" is not going to cut it.


Things aren't that easy in a corporate world, you get a volume contract
with a supplier, Dell for example, and purchase your hardware from them.

I can hardly see Dell shipping x86 servers with locked-in Windows
installs, that just won't do for their business.
I have to admit I'd love to see it though, I've always wanted us to try
Cisco or IBM's blade servers in lieu of Dell's.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questio

Contribution to PUC driver

[Dennis Oyama]

Patch to update pucdata.c to support the Perle Systems Ltd. Multiport Speed LE 
Serial cards.



--- pucdata.orig.c  2012-02-10 12:24:47.0 -0500
+++ pucdata.c   2012-02-10 12:40:34.0 -0500
@@ -668,11 +668,35 @@
 */
{   0x155f, 0x0331, 0x, 0,
-   "Perle Speed4 LE",
+   "Perle Ultraport4 Express",
DEFAULT_RCLK * 8,
PUC_PORT_4S, 0x10, 0, 8,
},
+{   0x155f, 0xB012, 0x, 0,
+"Perle Speed2 LE",
+DEFAULT_RCLK * 8,
+PUC_PORT_2S, 0x10, 0, 8,
+},
+
+{   0x155f, 0xB022, 0x, 0,
+"Perle Speed2 LE",
+DEFAULT_RCLK * 8,
+PUC_PORT_2S, 0x10, 0, 8,
+},
+
+{   0x155f, 0xB004, 0x, 0,
+"Perle Speed4 LE",
+DEFAULT_RCLK * 8,
+PUC_PORT_4S, 0x10, 0, 8,
+},
+
+{   0x155f, 0xB008, 0x, 0,
+"Perle Speed8 LE",
+DEFAULT_RCLK * 8,
+PUC_PORT_8S, 0x10, 0, 8,
+},
+
{   0x14d2, 0x8010, 0x, 0,
"VScom PCI-100L",
DEFAULT_RCLK * 8,




___
 Dennis Oyama
   Technical Sales Engineer
  Perle Systems Ltd.
1-800-467-3753
 Direct: 905-946-5037
   doy...@perle.com
   CompTIA Security+
___

___
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: Is this something we (as consumers of FreeBSD) need to be aware of?

[Nomen Nescio]

> > But my point is that MS doesn't issue the updates, they have to ask the
> > BIOS vendors to do so, and then the MB vendors have to take the update,
> > and then the users have to install the update. The incentive at each
> > level is generally very small. It does create some confusion, but is
> > hardly an enforcement mechanism. It would disable older versions of
> > FreeBSD on newer hardware, but not much else.

This can be automated. Many mobo manufacturers have software that searches
for new BIOS and flashes it "for" you. All they have to do is get on board
and make this automatic like Windows Updates. Don't think they haven't
thought this far ahead. I believe some offer this now.

> > A previous poster has pointed out that MS can't revoke a certificate
> > belonging to RH, but I suppose the could ask the BIOS vendors to treat
> > it as revoked. I don't know what the response would be.

MS and Intel are running this. If Verisign is just a trusted 3rd party
(without administrative duties) they can well defer to the Microshaft Mafia
and do as they're told. It wouldn't be the first time. For example, did
everybody already forget the Microshaft Mafias' initiation of the FBI server
raids on the botnet? Many innocent companies and peoples hosting got screwed
during this takeover. But it was all in the name of "justice". If we can get
a few Russian hackers then it's well worth damaging your business and
property. We're from Microshaft Mafia and the FBI and we're here to help.

> This is akin to, for example, Sony's race against Homebrewers on the
> good ol' PSP.
> 
> When hackers found a hardware flaw that enabled them to install custom
> firmware, Sony had to release new versions of the consoles with fixed
> hardware.
> 
> The old ones were still exploitable but the new ones weren't.

That is a little different, possibly. For one thing, Sony detected whether
you had the updates they wanted you to install and if you don't have them
installed you can't play on their PlayStation network. For 99.99% of
PlayStation users this is the whole point of buying their console. So if you
don't upgrade all you have is a box for playing local games which most
people don't seem to want to do. 

All the Intel and Microshaft Mafia have to do is a similar thing, and make
your PC or Windows stop working unless you install their updates, or tell
the FBI your PC is possibly "infected" and part of a Russian botnet etc. and
you won't be allowed on the internet until you upgrade your system to a safe
level to avoid these horrible threats. This idea was floated publicly even
unrelated to so-called "secure boot".

Windows activation can check the firmware level and Intel's management BIOS
is connected to the net even when your new PC is shut off (as long as it is
plugged in). If you go along with this they can do whatever you want. You're
submitting to true remote management/control over YOUR hardware and life.

This is the beginning of a lot of bad Big Brother stuff and if people accept
it now they get what they deserve tomorrow.

Say "NO" to the Intel/Microshaft Mafia. Say "NO" to "Secure" boot.

Run MIPS and Alpha hardware if you have to, just DUMP INTEL AND THE
MICROSHAFT MAFIA.
___
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: UEFI Secure Boot Specs - And some sanity

[Anonymous Remailer (austria)]

> > Isn't there a lot of needless handwaving going on when the spec is
> > pretty clear that installing your own complete PKI tree will all
> > boil down to what is effectively a jumper on the motherboard?

No, considering 99.99% of of current Windows victims can't even install a
fresh copy of Windows.

> > Users could fully utilize the UEFI Secure Boot hardware by say:
> >
> > - Using openssl to generate their keys
> > - Jumper the board, burn it into the BIOS in UEFI SB SetupMode
> > - Have all the MBR, slice, partition, installkernel, etc tools
> > install and manage the signed disk/loader/kernel/module bits
> > - Have the BIOS check sigs on whatever first comes off the media

Yeah that's trivial for 99.99% of users. I have no idea what everyone is on
about.  I just program my own PROM and make my own motherboards.

Now back to reality, most people don't know how to use openssl. They don't
want to break the seal on their PC and void the warranty. They don't want to
play with jumpers. They don't know how to use Linux fdisk or BSD
disklabel. They can't set up their BIOS. They may not be the typical BSD or
Linux poweruser but they represent most users. And sadly even a significant
percentage of BSD and even a more significant percentage of Linux users
(thank you Ubuntu) aren't capable of doing these things.

> > And if they really were that dumb, there's Gigabyte, Asus, Msi,
> > Supermicro, Biostar, etc who will not be so dumb and will soak up
> > all the remaining sales gravy.

We're going to see if that happens but it won't. The WinTel Mafia controls
more than what you think and these vendors know they get many magnitudes
more money from selling Windows commodity shitboxes than they ever will from
all the BSD and Linux users multiplied together.

___
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: Somewhat OT - A Makefile Question

[Tim Daneliuk]

On 06/07/2012 12:19 AM, Parv wrote:

in message<4fcf48af@tundraware.com>,
wrote Tim Daneliuk thusly...



...

Within a makefile, I need to assign the name of a program as in:

FOO = "bar".

The problem is that 'bar' may also be know as, say, "bar.sh".

...

Is there a simple way to determine which form "bar" or "bar.sh" on
on a given system *at the time the make is run*?  If both exist, I
will pick one arbitrarily,

...

  For example I don't think this works when both are there:

FOO = $(shell `which bar bar.sh)


Modify the subshell command to ...

   which bar bar.sh | head -n 1


... as in (for FreeBSD make) ...

   shell=`which zsh sh tcsh csh 2>/dev/null | fgrep -v 'not found' | head -n 3`

   all:
 @printf "%s\n" ${shell}



   - parv



Thanks.  I came up with something similar, but I think your recipe is a bit
more elegant ...

--

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: mount failure

[Warren Block]

On Wed, 6 Jun 2012, Gary Aitken wrote:


Running under X with xfce, just did this:

 gpart show -l da0
 gpart delete -i 1 da0
 gpart destroy da0

 gpart create -s GPT da0
 gpart bootcode -b /boot/pmbr da0

 gpart add -t freebsd-boot -i 1 -s 512K -l gptboot da0
 gpart bootcode -b /boot/gptboot -i 1 da0

 gpart add -t freebsd-ufs -a 4K -s 35G -i 2 -l fbsdroot da0
 gpart add -t freebsd-swap -a 4K -s 512M -i 3 -l fbsdswap da0
 gpart add -t freebsd-ufs -a 4K -s 1G -i 4 -l fbsdvar da0
 gpart add -t freebsd-ufs -a 4K -s 512M -i 5 -l fbsdtmp da0
 gpart add -t freebsd-ufs -a 4K -s 893G -i 6 -l fbsdusr da0

 newfs /dev/gpt/fbsdroot
 newfs -U /dev/gpt/fbsdvar
 newfs -U /dev/gpt/fbsdtmp
 newfs -U /dev/gpt/fbsdusr

 mount /dev/gpt/fbsdroot /mnt/goflex

I then tried to create a snapshot of /
X immediately slowed to less than a crawl, and I couldn't do anything.
At first I could move the pointer a little, but then I lost it.
After a half hour or so, I power-cycled and rebooted.

When I tried to mount the usb drive, I (not surprisingly) got this:

 #mount /dev/gpt/fbsdroot /mnt/goflex/root
 mount: /dev/gpt/fbsdroot : operation not permitted
 WARNING: RW mount of /mnt/goflex denied.  File system is not clean - run fsck.

But when I try to do an fsck, I can't:
 #fsck /dev/gpt/fbsdroot
 fsdk: could not determine filesystem type
(same msg for /dev/gpt and /dev/da0p2)


# fsck -y -t ufs /dev/gpt/fbsdroot

I don't see any obvious problem with the procedure.
___
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: Is this something we (as consumers of FreeBSD) need to be aware of?

[Thomas Mueller]

Snippet from Jerry :

> I don't know of any user personally who purchased a new PC and then
> threw FreeBSD on it. Most users that I have come into contact with use
> 2+ year old units that have been replaced by shiny new Windows units. I
> don't see that changing anytime soon.

I did, or almost.  Before installing FreeBSD, I tried unsuccessfully to install 
NetBSD, figuring I'd start with the least stable of (NetBSD, FreeBSD, Linux) 
and not risk messing up good Linux and FreeBSD installations.

Then FreeBSD 9.0-BETA1 was released, and I went with that: now on 9.0-STABLE #9.

That was on a computer that I built from parts in May-June 2011, meaning modern 
hardware including UEFI, but no "secure boot".


Tom
___
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"

changes to ioctl has me flumoxed

[David Tilbrook]

To support my line editor I used to use:

sgtty.c_lflag = ISIG;
sgtty.c_iflag = BRKINT | IGNPAR | IXON | ICRNL;
sgtty.c_oflag &= (ONLCR | OPOST | TAB3);
sgtty.c_cc[VMIN] = 1;
sgtty.c_cc[VTIME] = 1;
iotcl(0, TCSETAW, &sgtty);

but this no longer appears to work in that input lines are repeated
and  the writes to reflect chanes are not done.

What should I be changing in the above, or what do I need to add?

-- david
___
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: Is this something we (as consumers of FreeBSD) need to be aware of?]

[Damien Fleuriot]

On 6/6/12 9:55 PM, Robert Simmons wrote:
> On Wed, Jun 6, 2012 at 3:05 PM, Jerry  wrote:
>> On Wed, 06 Jun 2012 12:49:53 -0400
>> Daniel Staal articulated:
>>
>>> On 2012-06-05 17:20, Jerry wrote:
>>>
 The question that I have not seen answered in this thread is what
 FreeBSD intents to do. From what I have seen, most FreeBSD users do
 not
 use the latest versions of most hardware, so it may be a while before
 its user base is even effected.
>>>
>>> I don't believe at this point FreeBSD has any intent one way or
>>> another, really.  It's not an immediate problem for any platform
>>> supported by the FreeBSD project, at least for a technically-inclined
>>> user who's willing to check out their BIOS.  (Even if they are using
>>> the latest hardware, the x86-derived platforms aren't going to require
>>> this code signing yet.)  So it'll probably be a 'wait and see if it's
>>> something the FreeBSD community needs a solution for' at this point.
>>> But this is just my impression.
>>
>> I totally agree with you. Unfortunately that speaks to the sad state of
>> affairs that FreeBSD appears to be in. When it comes to supporting the
>> latest technologies, it tends to be behind the curve when compared to
>> other operating systems. Wireless networking and USB support are only a
>> few examples.
>>
>> I don't know of any user personally who purchased a new PC and then
>> threw FreeBSD on it. Most users that I have come into contact with use
>> 2+ year old units that have been replaced by shiny new Windows units. I
>> don't see that changing anytime soon.
> 
> I would have to disagree with you there.  I know of quite a few users
> who happen to run one of the world's largest content distribution
> networks (accounting for about one third of the internet's traffic; up
> there with pornography).  They purchased more than just a handful of
> new computers and threw FreeBSD on them:
> 
> http://lists.freebsd.org/pipermail/freebsd-stable/2012-June/068129.html


You're talking about servers here, I think Jerry was speaking more
generally, about a lambda user buying a computer and *definitely* not
installing FBSD (or anything else) on it.

The typical users just wants to buy "internet and emails" without a care
in the world about the OS.

___
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: Is this something we (as consumers of FreeBSD) need to be aware of?]

[Damien Fleuriot]

On 6/5/12 10:19 PM, Colin Barnabas wrote:
> On Tue, Jun 05, 2012 at 11:19:26AM -0700, Kurt Buff wrote:
>> UEFI considerations drive Fedora to pay MSFT to sign their kernel binaries
>> http://cwonline.computerworld.com/t/8035515/1292406/565573/0/
>>
>> This would seem to make compiling from source difficult.
>>
>> Kurt
>>
> History show us that _everything_ will eventually run *nix. Take a
> look at the Sony PS3 debacle. After Sony yanked support for
> installing other OS's, the community ripped apart their
> hypervisor in a matter of months. If these boot keys do gain any
> momentum, sooner than later the community with poke holes in the
> system.
> 

This, however, raises the problem of the legality of it.

George HOTZ was sued by Sony for releasing the master key.

While Anonymous responded very aggressively (and while I do not
generally condone their actions, this one I can both understand and
support), in the end the consensus reached was that Geohotz agreed to
not work on bypassing the PS3's protections anymore.
___
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: Is this something we (as consumers of FreeBSD) need to be aware of?

[Damien Fleuriot]

On 6/6/12 9:43 PM, Daniel Feenberg wrote:
> 
> 
> On Wed, 6 Jun 2012, Damien Fleuriot wrote:
> 
>>
>>
>> On 6/6/12 6:45 PM, Daniel Feenberg wrote:
>>>
>>>
>>> On Wed, 6 Jun 2012, Julian H. Stacey wrote:
>>>
> I do wonder about that. What incentive does the possesor of a signing
> key
> have to keep it secret?

 Contract penalty clause maybe ? Lawyers ?
>>>
>>> A limited-liability company with no assets is judgement-proof.
>>>

 Otherwise one of us would purchase a key for $99, & then publish
 the key so we could all forever more compile & boot our own kernels.
 But that would presumably break the trap Microsoft & Verisign seek
 to impose.

>>>
>>> Could it really be that simple? As for hardware vendors putting revoked
>>> keys in the ROM - are they really THAT cooperative? Seems like they
>>> would drag their feet on ROM updates if they had to add a lot of stuff
>>> that won't help them, so that doesn't seem like a great enforcement
>>> tool.
>>>
>>> dan feenberg
>>
>>
>> Oh god...
>>
>> Please realize that once the key is divulged, it gets revoked at the
>> BIOS' next update.
> 
> But my point is that MS doesn't issue the updates, they have to ask the
> BIOS vendors to do so, and then the MB vendors have to take the update,
> and then the users have to install the update. The incentive at each
> level is generally very small. It does create some confusion, but is
> hardly an enforcement mechanism. It would disable older versions of
> FreeBSD on newer hardware, but not much else.
> 
> A previous poster has pointed out that MS can't revoke a certificate
> belonging to RH, but I suppose the could ask the BIOS vendors to treat
> it as revoked. I don't know what the response would be.
> 
> Daniel Feenberg
> 

That is indeed the case.


This is akin to, for example, Sony's race against Homebrewers on the
good ol' PSP.

When hackers found a hardware flaw that enabled them to install custom
firmware, Sony had to release new versions of the consoles with fixed
hardware.

The old ones were still exploitable but the new ones weren't.
___
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: Is this something we (as consumers of FreeBSD) need to be aware of?]

[Erich]

Hi,

On 06 June 2012 21:10:14 p...@pair.com wrote:
> in message <1849552.ouqdgjx...@x220.ovitrap.com>,
> wrote Erich thusly...
> >
> > On 06 June 2012 23:27:39 Chad Perrin wrote:
> ...
> > > I have immediately installed FreeBSD on the last four or five
> > > laptops I
> >
> > I do this since 5.2 is out with all my purchases.
> ...
> > I have to admit, that I have had to install twice Fedora because
> > the notebook hardware was not supported at that moment of time.
> >
> > The second Fedora installation will go as soon as get finished my
> > travelling or I get me hands on a new hard disk.
> 
> Erich, could you please list the offending Lenovo models?

it is the X220.

There is a solution available which needs a bit more time as I have had on hand 
before I left.

As I have said several times already, I will be back with this machine to 
FreeBSD after my return.
> 
> 
> ...
> > What also has to be mentioned is the fact that people have to be
> > more careful when shopping for new hardware with FreeBSD in mind.
> > AMD based hardware is here of advantage at the moment. But it has
> > other disadvantages.
> ...
> 
> What would be the said disadvantages?

Some say that the AMD CPUs are slower per core. This X220 with the 2640 CPU 
seems to be very, very fast for me. I was surprised how it performed running 
plain FreeBSD.

I would not have expected this much performance out of a small notebook.

As this is my first Intel CPU since the good, old 80586, I cannot tell you more 
about Intel CPUs.

Erich
___
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: Is this something we (as consumers of FreeBSD) need to be aware of?

[Damien Fleuriot]

On 7 Jun 2012, at 01:54, Robert Bonomi  wrote:

>> From owner-freebsd-questi...@freebsd.org  Wed Jun  6 18:13:09 2012
>> Date: Thu, 07 Jun 2012 00:09:54 +0100
>> From: Bruce Cran 
>> To: Robert Bonomi 
>> Cc: freebsd-questions@freebsd.org
>> Subject: Re: Is this something we (as consumers of FreeBSD) need to be aware
>> of?
>> 
>> On 06/06/2012 20:27, Robert Bonomi wrote:
>>> Suppose I put up a web app that takes an executable as input, signs it 
>>> with my key, and returns the signed filt to the submitter. I don't 
>>> divulge the key to anyone, just use it on 'anything'. Anybody 
>>> attempting to revoke on _that_ basis is asking for a lawsuit.
>> 
>> To me it would be perfectly reasonable to revoke the key as soon as you 
>> signed the first piece of malware.
> 
> It may seem reasonable to you, but is there -legal- basis to do so? 
> 
> 'signing' only provides assurance of the identity of the signer. I did
> sign it.  The key has not been compromised.  The software in question 
> is tracable to the signer, but the signer never claimed it was 'error free',
> what conract or statute did they breach by doing the signing?  
> 

Signing anything and everything defeats the purpose the key and this whole 
charade are implemented for.

Under the contract's undoubtedly carefully penned clauses, this would allow for 
a key revocation.

Make no mistake, they'll go over that contract for several weeks, giving 
themselves as much manoeuvring room as 
possible.___
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: Is this something we (as consumers of FreeBSD) need to be aware of?]

[parv]

in message <1849552.ouqdgjx...@x220.ovitrap.com>,
wrote Erich thusly...
>
> On 06 June 2012 23:27:39 Chad Perrin wrote:
...
> > I have immediately installed FreeBSD on the last four or five
> > laptops I
>
> I do this since 5.2 is out with all my purchases.
...
> I have to admit, that I have had to install twice Fedora because
> the notebook hardware was not supported at that moment of time.
>
> The second Fedora installation will go as soon as get finished my
> travelling or I get me hands on a new hard disk.

Erich, could you please list the offending Lenovo models?


...
> What also has to be mentioned is the fact that people have to be
> more careful when shopping for new hardware with FreeBSD in mind.
> AMD based hardware is here of advantage at the moment. But it has
> other disadvantages.
...

What would be the said disadvantages?


  - parv


-- 

___
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"