Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server

2010-04-21 Thread pluknet
2010/4/21 Andrey V. Elsukov bu7c...@yandex.ru:
 On 21.04.2010 2:44, Maxim Sobolev wrote:

 Maxim Sobolev wrote:

 Maybe try adding

 hint.atkbdc.0.disabled=1
 hint.atkbd.0.disabled=1

 Actually it helped, thank you very much! The problem was that I have had
 my hints compiled into the kernel itself.

 Hi, Maxim.

 I tried to boot 9.0-CURRENT amd64 snapshot on IBM x3650 M2 and seems have
 the
 same problem, i set hints from loader prompt, but this didn't help.
 Can you explain what you did to boot FreeBSD faster?


Hmm.. That's strange to hear.
We have in production a number of x3650m2: 7.2-R, 7.3-R (all amd64).
All runs flawlessly.
 I'll try to boot it from head today if that matters.

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


Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server

2010-04-21 Thread Andrey V. Elsukov

On 21.04.2010 10:01, pluknet wrote:

Hmm.. That's strange to hear.
We have in production a number of x3650m2: 7.2-R, 7.3-R (all amd64).
All runs flawlessly.
  I'll try to boot it from head today if that matters.


It was about 1.5 hour ago when i entered autoboot in loader prompt.
It still show slowly rotated dash line at end of
/boot/kernel/kernel text=x |

--
WBR, Andrey V. Elsukov
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server

2010-04-21 Thread Daniel Braniss
 On 21.04.2010 10:01, pluknet wrote:
  Hmm.. That's strange to hear.
  We have in production a number of x3650m2: 7.2-R, 7.3-R (all amd64).
  All runs flawlessly.
I'll try to boot it from head today if that matters.
 
 It was about 1.5 hour ago when i entered autoboot in loader prompt.
 It still show slowly rotated dash line at end of
 /boot/kernel/kernel text=x |

I've seen this happen when there were problems with the serial port, either
missing or miss-configured.

HTH,
danny



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


netstat count option

2010-04-21 Thread Dmitry Banschikov
Hello,

I wrote small patch to the netstat utility.
The patch allows to specify how many times, the display output should be 
continue,
in case of option -w.
Usage:
# ./netstat -w2 -c2
input(Total)   output
   packets  errs  bytespackets  errs  bytes colls
15 0   2268 13 0   1190 0
 4 0240  5 0278 0
# 

Option -c [count] is simillar to the same option in iostat utility.
In linux -c means continious output:
   -c, --continuous
   This will cause netstat to print the selected information every second 
continuously.
   

-- 

Dmitry Banshchikov

patch-netstat
Description: Binary data
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org

Re: netstat count option

2010-04-21 Thread Brandon Gooch
On Wed, Apr 21, 2010 at 4:01 AM, Dmitry Banschikov ubi...@peterhost.ru wrote:
 Hello,

 I wrote small patch to the netstat utility.
 The patch allows to specify how many times, the display output should be 
 continue,
 in case of option -w.
 Usage:
 # ./netstat -w2 -c2
            input        (Total)           output
   packets  errs      bytes    packets  errs      bytes colls
        15     0       2268         13     0       1190     0
         4     0        240          5     0        278     0
 #

 Option -c [count] is simillar to the same option in iostat utility.
 In linux -c means continious output:
   -c, --continuous
       This will cause netstat to print the selected information every second 
 continuously.

This seems pretty useful, perhaps you should file a PR?

http://www.freebsd.org/send-pr.html

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


UFS endianness

2010-04-21 Thread Alex Dupre
Is there a way to mount (or extract files from) a big-endian UFS file 
system on a x86 FreeBSD machine?


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


/sys/amd64/conf/GENERIC COMPAT_FREEBSD7 a prerequisite for COMPAT_IA32

2010-04-21 Thread Julian H. Stacey
Hi hack...@freebsd.org
with amd64, but not with i386,
/sys/amd64/conf/GENERIC COMPAT_FREEBSD7 is an undocemneted
pre-requisite for COMPAT_IA32
(so those who enable COMPAT_IA32 for ports/emulators, but disable
COMPAT_FREEBSD7 as they compile all binaries on upgrade, will trip
up on it as I did).  Currently I see:

cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99 -g -Wall 
-Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes 
-Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign 
-fformat-extensions -nostdinc  -I. -I../../.. -I../../../contrib/altq -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -fno-omit-frame-pointer -mcmodel=kernel 
-mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  
-msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector 
-Werror  ../../../compat/freebsd32/freebsd32_misc.c
cc1: warnings being treated as errors
../../../compat/freebsd32/freebsd32_misc.c: In function 'freebsd32_semsys':
../../../compat/freebsd32/freebsd32_misc.c:1420: warning: implicit declaration 
of function 'freebsd7_freebsd32_semctl'
../../../compat/freebsd32/freebsd32_misc.c:1420: warning: nested extern 
declaration of 'freebsd7_freebsd32_semctl'
...
../../../compat/freebsd32/freebsd32_misc.c:1845: error: dereferencing pointer 
to incomplete type
*** Error code 1

It could be documented in GENERIC, but better to fix it.  I could
dig through sources, but I think there's people closer to config
who would prefer to commit their own fix, rather than me write a patch ?
(Does that translate as I'm lazy ? ;-)

Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Mail plain text,  Not HTML quoted-printable Base64 http://www.asciiribbon.org
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: Bug with fixit live 8.0 memstick.img running on F1 after MBR

2010-04-21 Thread Julian H. Stacey
Hi hackers@,
No replies in over 4 days to this, so this is a repost, 
I've also added re@ as newish memstick.img might interest them ?

Reference:
 From: Julian H. Stacey j...@berklix.com 
 Date: Sat, 17 Apr 2010 12:05:46 +0200 

Julian H. Stacey wrote:
 Hi Hackers,
 Bug found with fixit live 8.0 memstick.img running on F1 after MBR :
 
 First I checked my PC BIOS boots OK:
   I copied 8.0-RELEASE-i386-memstick.img to a raw 2G USB stick, it boots
   fine,  one can go into fixit menu, using image on stick
 
 Next
   I fdisk partitioned an 8G stick  copied 8.0-RELEASE-i386-memstick.img
   to F1 (da0s1), set F1 active, booted OK, went into fixit, selected
   USB stick for the live media,  it failed to find a USB media.
 
   (The live command prompt on F4 wasn't much use, no ls yet.)
 
   I tried telling it to install to F2 (6.5 G ufs), using files from
   local FS on stick, (I told it path 8.0-RELEASE ) but on 2 attempts,
   it couldnt find where to install to get bins from.
 
   I since confirmed those files are there on F1 8.0-RELEASE/ , see below.
 
 Conclusion:
   Would be nice if others tried too, to tell if it's my mistake or a bug.
   WOrth doing as it also sets you up ready with a stick that can rescue/
   fixit + has enough space for other file systemes with your own
   personal /usr/local inc. X, ready for eg testing laptops in shops.
 
   I since mounted my 8G stick on a normal 8.0 PC  installed F2
   from /usr/src  /usr/local from hard disc. I have another 4G I
   could test with MBR, but testing here is disruptive as only my
   main machine has boot- off- USB functionality).
 
 I mounted both sticks later to document what I was using:
 
 2G stick with no MBR, (`dangerously dedicated', that worked OK:
   ls -l /devusb/red - /dev/da0a
 
   df | grep usb
   Filesystem  SizeUsed   Avail Capacity  Mounted on
   /devusb/red 921M858M-11M   101%/usb/red
 
   disklabel da0
   # /dev/da0:
   8 partitions:
   #size   offsetfstype   [fsize bsize bps/cpg]
 a:  1803124   16unused0 0   
 c:  18031400unused0 0 # raw part, don't 
 edit
   disklabel: partition c doesn't cover the whole unit!
   disklabel: An incorrect partition c may cause problems for standard system 
 utilities
 
 8G stick with MBR:
   fdisk da0
 *** Working on device /dev/da0 ***
 parameters extracted from in-core disklabel are:
 cylinders=977 heads=255 sectors/track=63 (16065 blks/cyl)
 
 parameters to be used for BIOS calculations are:
 cylinders=977 heads=255 sectors/track=63 (16065 blks/cyl)
 
 Media sector size is 512
 Warning: BIOS sector numbering starts with sector 1
 Information from DOS bootblock is:
 The data for partition 1 is:
 sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
 start 63, size 2988027 (1458 Meg), flag 0
 beg: cyl 0/ head 1/ sector 1;
 end: cyl 185/ head 254/ sector 63
 The data for partition 2 is:
 sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
 start 2988090, size 12707415 (6204 Meg), flag 80 (active)
 beg: cyl 186/ head 0/ sector 1;
 end: cyl 976/ head 254/ sector 63
 The data for partition 3 is:
 UNUSED
 The data for partition 4 is:
 UNUSED
 
   mount 
 /dev/da0s1a  on /usb/sanblack.img (ufs, local)
 /dev/da0s2a  on /usb/sanblack.ufs (ufs, local, soft-updates)
 
   df 
 Filesystem  SizeUsed   Avail Capacity  Mounted on
 /dev/da0s1a 921M858M-11M   101%/usb/sanblack.img
 /dev/da0s2a 6.3G2.7M5.8G 0%/usb/sanblack.ufs
 
   cd /usb/sanblack.img/8.0-RELEASE
 du -s kernels # 60M
 ls base   # base.aa - base.bl, base.inf base.mtree install.sh*
 
   disklabel da0s1
 #size   offsetfstype   [fsize bsize bps/cpg]
   a:  1803124   16unused0 0   
   c:  29880270unused0 0 
 
   disklabel da0s2
   a: 12707399   164.2BSD0 0 0 
   c: 127074150unused0 0 

Cheers,
Julian
-- 
Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Mail plain text,  Not HTML quoted-printable Base64 http://www.asciiribbon.org
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: /etc in CVS

2010-04-21 Thread Sergey Babkin
Doug Barton wrote:
 
 On 4/20/2010 11:30 AM, Bakul Shah wrote:
 
  My suggestion was in the context of upgrding a system to a
  new release. There are changes to /**/etc/**/*(.) files going
  from release R to R+1.  I was pointing out that what
  mergemaster does (merging in these changes to your locally
  modified etc files) is almost exactly the same as merging in
  a vendor branch under CVS (vendor here would be freebsd.org).
  But merge conflicts have to be resolved carefully and before
  any reboots!
 
 That's not accurate. By default mergemaster does nothing, it will not
 change your installed /etc at all. At this point the -U option will
 handle major release upgrades quite painlessly, leaving only those files
 that actually have local mods for the user to deal with manually.
 
 Of course, I have always said that if anyone feels compelled to create a
 better solution for etc merging that they should feel free, and I still
 mean that. :)

I wonder if a version control system, like SVN, could be used
to keep track of all the changes in /etc. (Or maybe it
already is and I'm simply out of date).

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


Re: regenerating /var/db/pkg

2010-04-21 Thread Doug Barton
On 4/20/2010 7:11 PM, Aryeh M. Friedman wrote:
 I acciddentally rm'ed my /var/db/pkg and want to know is it possible to 
 rgenerate it (I have portmaster and portupgrade installed)

Portmaster certainly can't do this, it uses the information from
/var/db/pkg. I'm not sure if portupgrade can do it or not.

Your most likely course of success is to generate a list of ports that
you know you're using (root and leaf ports in portmaster
terminology), back up any config or other key files from /usr/local,
then delete everything and reinstall.


Good luck,

Doug

-- 

... and that's just a little bit of history repeating.
-- Propellerheads

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

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