Re: cannot compile net/mosquitto port 10.1-STABLE

2015-07-20 Thread Beat Siegenthaler
 

Am 2015-07-20 7:25, schrieb Olli Hauer: 

 Hi Beat,
 
 it is possible mosquitto builds against an older lib or header that is not up 
 to date.
 
 Can you run the following command.to [1] create a backup
 $ cd empyy_space 
 $ pkg create mosquitto
 
 Now remove the old.mosquotto package if you have a baxkup.and try to 
 build.the new version.

Ok, found it (partially) 

rebuilt libxslt cmake and python27 did not solve the problem.
The old mosquitto version itself seeed to be the problem. 
then: make deinstall / make install was a success. 

normally i use portmaster, or years ago portupgrade for this tasks and
it is very rarely that this is not working... 

regards, Beat 

Links:
--
[1] http://command.to
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


cannot compile net/mosquitto port 10.1-STABLE

2015-07-19 Thread Beat Siegenthaler
Hi,
there seems to be some problem with the port, which i cannot resolve
with my poor compiler knowledge. Maintainers did not answer.
Any hint?

regards, Beat

[root@myserver:~] # uname -a
FreeBSD my.server.com 10.1-STABLE FreeBSD 10.1-STABLE #0 r282210:
Wed Apr 29 17:38:56 CEST 2015

[root@myserver:/usr/ports/net/mosquitto] # make
===  License BSD3CLAUSE accepted by the user
===  Found saved configuration for mosquitto-1.3.2
===   mosquitto-1.4.2 depends on file: /usr/local/sbin/pkg - found
=== Fetching all distfiles required by mosquitto-1.4.2 for building
===  Extracting for mosquitto-1.4.2
= SHA256 Checksum OK for mosquitto-1.4.2.tar.gz.
===  Patching for mosquitto-1.4.2
===  Applying FreeBSD patches for mosquitto-1.4.2
/usr/bin/sed -i.bak -e '/ldconfig/d'
/usr/ports/net/mosquitto/work/mosquitto-1.4.2/src/CMakeLists.txt
/usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/CMakeLists.txt
/usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/cpp/CMakeLists.txt
===   mosquitto-1.4.2 depends on executable: xsltproc - found
===   mosquitto-1.4.2 depends on file: /usr/local/bin/cmake - found
===   mosquitto-1.4.2 depends on file: /usr/local/bin/python2.7 - found
===   mosquitto-1.4.2 depends on executable: python2 - found
===   mosquitto-1.4.2 depends on shared library: libcares.so - found
(/usr/local/lib/libcares.so)
===  Configuring for mosquitto-1.4.2
===  Performing in-source build
/bin/mkdir -p /usr/ports/net/mosquitto/work/mosquitto-1.4.2
-- The C compiler identification is Clang 3.4.1
-- The CXX compiler identification is Clang 3.4.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found OpenSSL: /usr/local/lib/libssl.so;/usr/local/lib/libcrypto.so
(found version 1.0.2d)
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_CXX_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS
Python_ADDITIONAL_VERSIONS
THREADS_HAVE_PTHREAD_ARG


-- Build files have been written to:
/usr/ports/net/mosquitto/work/mosquitto-1.4.2
===  Building for mosquitto-1.4.2
Scanning dependencies of target libmosquitto
Scanning dependencies of target mosquitto
[  2%] Building C object lib/CMakeFiles/libmosquitto.dir/logging_mosq.c.o
[  4%] Building C object src/CMakeFiles/mosquitto.dir/conf.c.o
/usr/ports/net/mosquitto/work/mosquitto-1.4.2/src/conf.c:1427:36:
warning: comparison of unsigned expression  0 is always false
[-Wtautological-compare]
[  6%] Building C object lib/CMakeFiles/libmosquitto.dir/memory_mosq.c.o
if(config-message_size_limit 
0 || config-message_size_limit  MQTT_MAX_PAYLOAD){
   ~~ ^ ~
[  8%] Building C object lib/CMakeFiles/libmosquitto.dir/messages_mosq.c.o
[ 10%] Building C object lib/CMakeFiles/libmosquitto.dir/mosquitto.c.o
/usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:555:5:
warning: implicit declaration of function 'mosquitto_pub_topic_check' is
invalid in C99 [-Wimplicit-function-declaration]
if(mosquitto_pub_topic_check(topic) != MOSQ_ERR_SUCCESS){
   ^
/usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:617:5:
warning: implicit declaration of function 'mosquitto_sub_topic_check' is
invalid in C99 [-Wimplicit-function-declaration]
if(mosquitto_sub_topic_check(sub)) return MOSQ_ERR_INVAL;
   ^
/usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1009:9:
error: use of undeclared identifier 'MOSQ_ERR_PROXY'; did you mean
'MOSQ_ERR_ERRNO'?
case MOSQ_ERR_PROXY:
 ^~
 MOSQ_ERR_ERRNO
/usr/local/include/mosquitto.h:100:2: note: 'MOSQ_ERR_ERRNO' declared here
MOSQ_ERR_ERRNO = 14,
^
/usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1011:9:
error: duplicate case value 'MOSQ_ERR_ERRNO'
case MOSQ_ERR_ERRNO:
 ^
/usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1009:9:
note: previous case defined here
case MOSQ_ERR_PROXY:
 ^
/usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1191:53:
warning: declaration of 'enum mosq_opt_t' will not be visible outside of
this function [-Wvisibility]
int mosquitto_opts_set(struct mosquitto *mosq, enum mosq_opt_t option,
void *value)
^

Re: [SOLVED] Re: missing /boot/menusets.4th

2013-08-09 Thread Beat Siegenthaler
On 09.08.13 16:19, Teske, Devin wrote:
 Again, apologies...

 Patched stable/9 with forgotten MFC of r242688 (see recent SVN r254146).
Accepted!

that was the worst outage that hit me since a decade or more.
It was really STABLE for longtime ;-) But In that stage of boot i was a
bit helpless.

Tried half a day to recover. Found some issues with fixit and mounting
zfs on root in /mnt

could not find menusets.4th on any place in the system. At the end I
simply copied the file from 
http://svnweb.freebsd.org/base/head/sys/boot/forth/menusets.4th?revision=242667view=copathrev=242667
on a usb-drive and copied to /mnt/boot
Hope to help others.

Now i have to figure out, why

|Fixit# zpool import -R /mnt -f poolname|
|Fixit# mount -t zfs poolname /mnt|

did not worked as expected, and the 9.2-RC1 image was not installable...

good night,
Beat

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


Re: Unable to get sendmail submission port to listen on IPv6

2013-04-20 Thread Beat Siegenthaler
On 19.04.13 16:00, Jeremy Chadwick wrote:
 Hi all,

 I did not recognize that 587 is only listening onIy on IPv4. Maybe it's
 new, maybe it was alltime so.

 sendmail  25090  root  4u  IPv4 0xfe01e810f3d0  0t0   TCP *:25 
 (LISTEN)
 sendmail  25090  root  5u  IPv6 0xfe01a988f000  0t0   TCP *:25 
 (LISTEN)
 sendmail  25090  root  6u  IPv4 0xfe011c53d000  0t0   TCP *:587 
 (LISTEN)

Still no luck...

 Multiple things:

 1. The files that control sendmail are `hostname`.mc and
 `hostname`.submit.mc.  The freebsd.mc and freebsd.submit.mc are stock
 examples.

 I assume you're already familiar with the need to run make in
 /etc/mail.
Of course. Yes.

 2. `hostname`.mc controls options/features for the daemon -- i.e. the
 thing that is listening on TCP ports.  `hostname`.submit.mc is for
 outbound mail.  You're wanting sendmail to listen on TCP port 587, which
 is what's used by SMTP clients (ex. Eudora, Thunderbird, etc.) trying to
 send mail to sendmail (rather than the classic model/method of using
 port 25).
Yes, You are right. I was confused, about `hostname`.submit.mc and
port 587 named submission in /etc/services

 3. What you need to add is here:

 http://lists.freebsd.org/pipermail/freebsd-questions/2004-March/040006.html
I tried this and many other things, believe me. Result is always the same.
(Many Providers block 25 for residential networks nowadays)
And I hate it when i have delays caused by ports not listening on IPv6.
Did somebody managed to have 587 listening v6? with 9-STABLE

Kind regards,
Beat
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Unable to get sendmail submission port to listen on IPv6

2013-04-19 Thread Beat Siegenthaler
Hi all,

I did not recognize that 587 is only listening onIy on IPv4. Maybe it's
new, maybe it was alltime so.

sendmail  25090root4u  IPv4 0xfe01e810f3d0  0t0   
TCP *:25 (LISTEN)
sendmail  25090root5u  IPv6 0xfe01a988f000  0t0   
TCP *:25 (LISTEN)
sendmail  25090root6u  IPv4 0xfe011c53d000  0t0   
TCP *:587 (LISTEN)

FreeBSD 9.1-STABLE #8 r248707

freebsd.submit.mc states:

dnl If you use IPv6 only, change [127.0.0.1] to [IPv6:::1]
FEATURE(`msp', `[127.0.0.1]')dnl

But IPv6:::1 makes no difference, same picture only listen v4.

hostname.domain.com grown over the years. TLS, some milters, SRS Hack.
And working fine so far.

Any hint for me?

kind regards,
Beat
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


troubles with buildworld/sendmail/sasl/clang

2013-03-18 Thread Beat Siegenthaler
Hi all,

since some days i try to make buildworld, but have some errors in
sendmail.
The make conf is not changed since years (in this case) . Adding
NO_WERROR= in src.conf helps, but i think it is not the optimal solution?

# SASL (cyrus-sasl v2) sendmail build flags...
SENDMAIL_CFLAGS+=-I/usr/local/include -DSASL=2
SENDMAIL_LDFLAGS+=-L/usr/local/lib
SENDMAIL_LDADD+=-lsasl2
SENDMAIL_CFLAGS+= -D_FFR_SMTP_SSL

SENDMAIL_MC = /etc/mail/xyz.mc
WITH_SSL_AND_PLAINTEXT=yes # for imaps and cclient

==src.conf===

CC=clang
CXX=clang++
CPP=clang-cpp
# This setting to build world without -Werror:
# NO_WERROR=
# This setting to build kernel without -Werror:
# WERROR=

=buildworld===

/usr/src/usr.sbin/sendmail/../../contrib/sendmail/src/usersmtp.c:1864:8:
error: incompatible pointer types passing 'void ()' to parameter of type
'void (*)(char *, bool, MAILER *, struct mailer_con_info *, ENVELOPE *)'
[-Werror,-Wincompatible-pointer-types]
   getsasldata, NULL, XS_AUTH);
   ^~~
/usr/src/usr.sbin/sendmail/../../contrib/sendmail/src/sendmail.h:2519:67: note:
passing argument to parameter here
extern int  reply __P((MAILER *, MCI *, ENVELOPE *, time_t, void
(*)__P((char *, bool, MAILER *, MCI *, ENVELOPE *)), char **, int));
   ^
/usr/obj/usr/src/tmp/usr/include/sys/cdefs.h:129:21: note: expanded from
macro '__P'
#define __P(protos) protos  /* full-blown ANSI C */
^
3 errors generated.
*** [usersmtp.o] Error code 1
1 error
*** [all] Error code 2
1 error
*** [usr.sbin.all__D] Error code 2
1 error
*** [everything] Error code 2
1 error
*** [buildworld] Error code 2
1 error

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


Re: troubles with buildworld/sendmail/sasl/clang

2013-03-18 Thread Beat Siegenthaler
On 18.03.13 18:19, Dimitry Andric wrote:

 We used to build sendmail with NO_WERROR.clang= to disable -Werror
 specifically for clang, because there were some warnings that could
 not be suppressed otherwise. So if you need a customized build of
 sendmail, would it not be better to use the mail/sendmail port
 instead? There you can easily enable all bells and whistles that are
 not enabled by default in base.
Ok, good point... force of habit. Since years. Will use Port...

regards, Beat




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


OpenSSL from Ports

2012-07-30 Thread Beat Siegenthaler
Hello,

Until today, when I was asked what WITH_OPENSSL_PORT=yes should do.. i
was obviously wrong:
I think whole openssl should be replaced, but :

[mym:~] # which openssl
/usr/bin/openssl
[mym:~] # openssl version
OpenSSL 0.9.8x 10 May 2012

there IS a 1.0.1 version but it is not found whit which or whereis:

[mym:~] # /usr/local/bin/openssl version
OpenSSL 1.0.1c 10 May 2012

Maybe I simply miss some shell basics?
Regards, Beat



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


Re: OpenSSL from Ports

2012-07-30 Thread Beat Siegenthaler
On 30.07.12 20:36, O. Hartmann wrote
 I guess you need to ensure that the path /usr/local/bin is searched BEFORE 
 /usr/bin. If you're using
sh(1) as the standard shell of yours, you should ensure this by using
something like the following in .profile (or .cshrc, if csh(1)):
Never tweaked that:
bash: PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin
sh:   PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin
csh:  path(/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin
/usr/local/bin /root/bin)
zsh:  path(/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin
/usr/local/bin /root/bin)

It seems to be important to know, what build from port means. There is
still some tweaking necessary.

thanks


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


Re: Solution [Was: Re: ahci.ko and IXP700/800 - no disk found]

2011-02-15 Thread Beat Siegenthaler
On 04.02.11 23:31, Harald Schmalzbauer wrote:
 Will there be a errata for 8.2 regarding that issue?
 Anybody unpacking a HP N36L will probably think the controller is not
 working...

Exactly...
found this after my odyssey with my N36L ahci/zfs-mirror .
Not exactly the same issue but similar a ahci failure.
8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #1: Sun Feb 13 02:02:04 CET 2011
With ahci loaded dbench 1000 or copy a 20G file ends with timeouts on
ahcich0 and ahcich1 and a complete unresponsive system. No way to
recover. Only rebooting helps. There is no damage seen on zfs. But
anyway it's not really usable for production. Now running ata again...

FreeBSD 8.2-PRERELEASE #1: Sun Feb 13 02:02:04 CET 2011
r...@abcd.xyz.com:/usr/obj/usr/src/sys/ATOM_amd64 amd64
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) II Neo N36L Dual-Core Processor (1297.85-MHz
K8-class CPU)
  Origin = AuthenticAMD  Id = 0x100f63  Family = 10  Model = 6 
Stepping = 3
 
Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT
  Features2=0x802009SSE3,MON,CX16,POPCNT
  AMD
Features=0xee500800SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow!
  AMD
Features2=0x8377fLAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,Prefetch,OSVW,IBS,SKINIT,WDT,b19
  TSC: P-state invariant
real memory  = 8589934592 (8192 MB)
avail memory = 8120823808 (7744 MB)
ACPI APIC Table: HP ProLiant
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
atapci0: ATI IXP700/800 SATA300 controller port
0xd000-0xd007,0xc000-0xc003,0xb000-0xb007,0xa000-0xa003,0x9000-0x900f
mem 0xfe6ffc00-0xfe6f irq 19 at device 17.0 on pci0
atapci1: ATI IXP700/800 UDMA133 controller port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0

ad4: 1430799MB SAMSUNG HD154UI 1AG01118 at ata2-master UDMA100 SATA 3Gb/s
ad6: 1430799MB SAMSUNG HD154UI 1AG01118 at ata3-master UDMA100 SATA 3Gb/s




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


Re: fxp unusable after make world

2009-03-09 Thread Beat Siegenthaler



Bruce Simpson wrote:


Now that the descriptor ring format is fairly well known for fxp, reverse
engineering is feasible, as the setup uses the normal NDIS hooks which
Microsoft added for offloading cryptographic operations. Those *are*
documented.

Making it work is another matter entirely...


Cryptographic functions where never a needed option. I had this card 
running for maybe three Years. And my observations are for the records, 
if somebody have the same issues since one month or so...


I will also check the commands from Pyun. I will post the results here 
too..


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


fxp unusable after make world

2009-03-08 Thread Beat Siegenthaler
Hi,

last week I made a rebuild on my system (7.1 RELENG_7 amd64).

After this i could not reach my system from outside the LAN. It was
extremely slow. I suspected Modem, Firewall and so on, because inside my
LAN I could work. But then with tshark I found, that also there where
many retransmissions and checksum errors.

Then, short in time I replaced the dual EtherExpress PRO/100

f...@pci0:2:4:0:class=0x02 card=0x10158086 chip=0x12298086
rev=0x0d hdr=0x00
vendor = 'Intel Corporation'
device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter'
class  = network
subclass   = ethernet
f...@pci0:2:5:0:class=0x02 card=0x10158086 chip=0x12298086
rev=0x0d hdr=0x00
vendor = 'Intel Corporation'
device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter'
class  = network
subclass   = ethernet

With two cheap Realtek cards and the problem was gone...

r...@pci0:0:12:0:class=0x02 card=0x001a6409 chip=0x816910ec
rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8110SB Single-Chip Gigabit LOM Ethernet Controller'
class  = network
subclass   = ethernet
r...@pci0:0:13:0:class=0x02 card=0x001a6409 chip=0x816910ec
rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8110SB Single-Chip Gigabit LOM Ethernet Controller'
class  = network
subclass   = ethernet


I see that the fxp-code was touched short time ago.

P.S This is the first time since Years, that make world made one of my
Systems unusable
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


fxp unusable after make world

2009-03-08 Thread Beat Siegenthaler
Hi,

last week I made a rebuild on my system (7.1 RELENG_7 amd64).

After this i could not reach my system from outside the LAN. It was
extremely slow. I suspected Modem, Firewall and so on, because inside my
LAN I could work. But then with tshark I found, that also there where
many retransmissions and checksum errors.

Then, short in time I replaced the dual EtherExpress PRO/100

f...@pci0:2:4:0:class=0x02 card=0x10158086 chip=0x12298086
rev=0x0d hdr=0x00
vendor = 'Intel Corporation'
device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter'
class  = network
subclass   = ethernet
f...@pci0:2:5:0:class=0x02 card=0x10158086 chip=0x12298086
rev=0x0d hdr=0x00
vendor = 'Intel Corporation'
device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter'
class  = network
subclass   = ethernet

With two cheap Realtek cards and the problem was gone...

r...@pci0:0:12:0:class=0x02 card=0x001a6409 chip=0x816910ec
rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8110SB Single-Chip Gigabit LOM Ethernet Controller'
class  = network
subclass   = ethernet
r...@pci0:0:13:0:class=0x02 card=0x001a6409 chip=0x816910ec
rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8110SB Single-Chip Gigabit LOM Ethernet Controller'
class  = network
subclass   = ethernet


I see that the fxp-code was touched short time ago.

P.S This is the first time since Years, that make world made one of my
Systems unusable

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


Re: fxp unusable after make world

2009-03-08 Thread Beat Siegenthaler
Pyun YongHyeon wrote:

 
 I touched fxp(4) to add more hardware assistance so it could cause
 problems on your box. Please show me dmesg output and
 ifconfig fxp0
 output.
 
 If you doubt checksum offloading or TSO issues, try
 ifconfig fxp0 -tso -txcsum -rxcsum.
 

As I remember this Dual card is out of a Symantec/RaQ/Raptor/Firewall
and has a 3DES CryptoChip onboard.

[r...@atom:~] # ifconfig fxp0
fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4
ether 00:02:b3:b8:e5:7f
inet6 fe80::202:b3ff:feb8:e57f%fxp0 prefixlen 64 scopeid 0x3
media: Ethernet autoselect (none)
status: no carrier
[r...@atom:~] # ifconfig fxp1
fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4
ether 00:02:b3:b8:e5:80
inet6 fe80::202:b3ff:feb8:e580%fxp1 prefixlen 64 scopeid 0x4
media: Ethernet autoselect (none)
status: no carrier


[r...@atom:~] # dmesg
Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.1-STABLE #3: Thu Mar  5 17:03:54 CET 2009
r...@atom.beatsnet.com:/usr/obj/usr/src/sys/ATOM_amd64
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 Processor 3200+ (2002.57-MHz K8-class CPU)
  Origin = AuthenticAMD  Id = 0x10ff0  Stepping = 0

Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2
  AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow!
  AMD Features2=0x1LAHF
usable memory = 2137423872 (2038 MB)
avail memory  = 2061045760 (1965 MB)
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
agp0: VIA K8T800Pro host to PCI bridge on hostb0
pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
pci0: network, ethernet at device 10.0 (no driver attached)
re0: RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet
port 0x8800-0x88ff mem 0xfb40-0xfb4000ff irq 17 at device 12.0 on pci0
re0: Chip rev. 0x1000
re0: MAC rev. 0x
miibus0: MII bus on re0
rgephy0: RTL8169S/8110S/8211B media interface PHY 1 on miibus0
rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
re0: Ethernet address: 00:30:4f:60:3e:16
re0: [FILTER]
re1: RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet
port 0x9000-0x90ff mem 0xfb60-0xfb6000ff irq 18 at device 13.0 on pci0
re1: Chip rev. 0x1000
re1: MAC rev. 0x
miibus1: MII bus on re1
rgephy1: RTL8169S/8110S/8211B media interface PHY 1 on miibus1
rgephy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
re1: Ethernet address: 00:30:4f:60:3e:2b
re1: [FILTER]
pcib2: PCI-PCI bridge at device 14.0 on pci0
pci2: PCI bus on pcib2
fxp0: Intel 82550 Pro/100 Ethernet port 0xe400-0xe43f mem
0xfbd0-0xfbd00fff,0xfbc0-0xfbc1 irq 19 at device 4.0 on pci2
miibus2: MII bus on fxp0
inphy0: i82555 10/100 media interface PHY 1 on miibus2
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:02:b3:b8:e5:7f
fxp0: [ITHREAD]
fxp1: Intel 82550 Pro/100 Ethernet port 0xe800-0xe83f mem
0xfbf0-0xfbf00fff,0xfbe0-0xfbe1 irq 16 at device 5.0 on pci2
miibus3: MII bus on fxp1
inphy1: i82555 10/100 media interface PHY 1 on miibus3
inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: Ethernet address: 00:02:b3:b8:e5:80
fxp1: [ITHREAD]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: 1.3G of my /var missing

2007-10-24 Thread Beat Siegenthaler
NCDU.. http://www.freshports.org/sysutils/ncdu/ is your friend ;-))



 
  As in most cases the problem was sitting between the chair and the
  keyboard. I
  simply overlooked the G when I read that /var/log contained 1.3G of
 data.
 


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