Re: Tools for FreeBSD development

[Garrett Cooper]

Giorgos Keramidas wrote:

On 2006-12-02 20:05, Kevin Sanders <[EMAIL PROTECTED]> wrote:

On 12/2/06, Alexander Kabaev <[EMAIL PROTECTED]> wrote:

I personally think that having a dedicated box in disk-less
configuration is the best option out there. [...]

Alexander, when you say disk-less configuration, are you
referring to booting from a network image/server?  That's an
interesting idea.  I'm fairly new to FreeBSD development also,
and prefer the speed of a dedicated box, but recently suffered
my first corrupted beyond repair system.


Yes, a "diskless" boot is a network-based boot :-)


Look into BOOTP for that: 
. 
You may want to just use vmware (best reliable solution, IMO but it 
costs money), depending on what resources you have on hand and what 
you're trying to accomplish.

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

Re: tracing AND intercepting syscalls?

[Robert Watson]

On Sat, 2 Dec 2006, Stanislav Ochotnicky wrote:

trustedbsd's MAC framework: i've read manual, looked at source etc. And I 
couldn't find a way to stop at every syscall certain process has made. There 
is mac_syscall() function but as far as I could tell, it only registers new 
syscall. All in all, it seems that it should have some way to do this, maybe 
I just couldn't find it.


As discussed elsewhere in the thread, ptrace() has a syscall trapping 
facility, although I've not used it so can't speak to how well it works.


There are patches to add system call entry and exit hooks to the MAC 
Framework, but they've not yet been merged.  I anticipate that they will ship 
in FreeBSD 7.0, and may get MFC'd, depending on schedule, etc.


Robert N M Watson
Computer Laboratory
University of Cambridge
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Tools for FreeBSD development

[Robert Watson]

On Sat, 2 Dec 2006, Kevin Sanders wrote:


On 12/2/06, Alexander Kabaev <[EMAIL PROTECTED]> wrote:
I personally think that having a dedicated box in disk-less configuration 
is the best option out there. The ability to quickly go through series of 
hands/reboots without any associated fsck runs and without the risk of 
terminally damaging any local FS is priceless. If qemu can be tricked into 
disk-less booting, it should be just as good though.


Alexander, when you say disk-less configuration, are you referring to 
booting from a network image/server?  That's an interesting idea.  I'm 
fairly new to FreeBSD development also, and prefer the speed of a dedicated 
box, but recently suffered my first corrupted beyond repair system.


This is exactly the setup I use also.  Most typically, the setup involves a 
central development server running -STABLE, with a private network link to a 
series of crash boxes.  The development server NFS exports a file system to 
use as an NFS root and for file sharing, as well as running tftp and dhcp 
servers.  The test boxes use PXE to boot fom the central server.  Each test 
system has its own exported root, so I can use individual loader.conf's to 
tell test systems to boot off NFS, boot off local disks, etc.  I always load 
the kernel over NFS using pxeboot, regardless of whether I boot boxes with a 
local root.


You get some very nice effects -- you can easily move boxes between FreeBSD 
versions by switching out root file system symlinks, you can be building the 
next kernel while the previous one dumps core, etc.


Robert N M Watson
Computer Laboratory
University of Cambridge
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Tools for FreeBSD development

[Robert Watson]

On Sun, 3 Dec 2006, Garrett Cooper wrote:


Giorgos Keramidas wrote:

On 2006-12-02 20:05, Kevin Sanders <[EMAIL PROTECTED]> wrote:

On 12/2/06, Alexander Kabaev <[EMAIL PROTECTED]> wrote:

I personally think that having a dedicated box in disk-less
configuration is the best option out there. [...]
Alexander, when you say disk-less configuration, are you referring to 
booting from a network image/server?  That's an interesting idea.  I'm 
fairly new to FreeBSD development also, and prefer the speed of a 
dedicated box, but recently suffered my first corrupted beyond repair 
system.


Yes, a "diskless" boot is a network-based boot :-)


Look into BOOTP for that: 
. 
You may want to just use vmware (best reliable solution, IMO but it costs 
money), depending on what resources you have on hand and what you're trying 
to accomplish.


If using FreeBSD on i386/amd64 boxes, use PXE.  There are quite a few "instant 
setup" web pages out there that tell you how to get it running.  pxeboot makes 
life incredibly easy, as you can load kernels, modules, configurations, etc, 
over NFS.


Robert N M Watson
Computer Laboratory
University of Cambridge
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: tracing AND intercepting syscalls?

[Stanislav Ochotnicky]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Robert Watson wrote:
> As discussed elsewhere in the thread, ptrace() has a syscall trapping
> facility, although I've not used it so can't speak to how well it works.

As I mentioned earlier, I didn't find any info about ptrace() syscall
trapping facility(PT_SYSCALL, PT_TO_SCE and PT_TO_SCX) because it wasn't
in the man nor info page about ptrace(). When I was noticeed about
theese interfaces, I checked the source and It looks like it should
solve my problem. Maybe the man page should be updated accordingly?

> There are patches to add system call entry and exit hooks to the MAC
> Framework, but they've not yet been merged.  I anticipate that they will
> ship in FreeBSD 7.0, and may get MFC'd, depending on schedule, etc.

That would be certainly nice, if this could be done at system level.
There would be certainly lots of tools that could use this (Dtrace perhaps?)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFcrvjul7h5FTXf/MRCCjLAJ9wgU4s8Juvu0GXRD8ck1R0gcQ4HACfeSGU
QpRT3q9PBBx2I8/9RMJCMkw=
=CTRr
-END PGP SIGNATURE-
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [ANN] unionfs patchset-17 release, lock mechanism changed for robust working

[Daichi GOTO]

Hi guys, it's congratulations!

It is a red-letter day for new FreeBSD unionfs. The unionfs-17.diff
(without patch for sys/kern/vfs_lookup.c) was  committed to FreeBSD
7-current of 2006-12-02 19:35:56 UTC by rodrigc, my src mentor.


>   Current English document of web has some Japanese contents. We
> need a translator ;-)

Hiroharu TAMARU-san gave us good English text. Thanks.
And we added some text around committed of current.

http://people.freebsd.org/~daichi/unionfs/  (English)
http://people.freebsd.org/~daichi/unionfs/index-ja.html  (Japanese)


Hopefully we can get more feedback from testers :)

-- 
  Daichi GOTO, http://people.freebsd.org/~daichi
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Tools for FreeBSD development

[Kevin Sanders]

On 12/3/06, Robert Watson <[EMAIL PROTECTED]> wrote:

If using FreeBSD on i386/amd64 boxes, use PXE.  There are quite a few "instant
setup" web pages out there that tell you how to get it running.  pxeboot makes
life incredibly easy, as you can load kernels, modules, configurations, etc,
over NFS.

Robert N M Watson
Computer Laboratory
University of Cambridge


Thanks for th tips everyone.  My shop has all the VMware tools, and
I've used QEMU, but I prefer to develop on a real box and debug over a
serial port on a second box.  I'll give pxeboot a shot tomorrow.

While we're on this topic, what is the best way to debug kernel
modules.  I would like the ability to kldload my kernel module, set a
couple break points and single step through a section of code (at
least).  I've read Greg Lehey's
http://www.lemis.com/papers/Taiwan/tutorial.pdf but it seems a little
out of date.  From what I gather, the situation with the kernel
debugger has changed since he wrote it.

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

Error burning CD

[ros]

Trying to burn a RW CDROM, I notice the CD-ROM device was freeze and
nothing happen. After a hard reboot (I turn off completly the computer),
I find this message on the /var/log/message file

Dec  3 19:04:40 bill kernel: acd0: req=0xc24e5258 SEND_OPC_INFO
semaphore timeout !! DANGER Will Robinson !!
Dec  3 19:04:42 bill kernel: acd0: req=0xc2063258 SETFEATURES SET
TRANSFER MODE semaphore timeout !! DANGER Will Robinson !!
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Burning RW cdrom error message

[ros]

Trying to burn a RW CDROM, I notice the CD-ROM device was freeze and
nothing happen. After a hard reboot (I turn off completly the computer),
I find this message on the /var/log/message file

Dec  3 19:04:40 bill kernel: acd0: req=0xc24e5258 SEND_OPC_INFO
semaphore timeout !! DANGER Will Robinson !!
Dec  3 19:04:42 bill kernel: acd0: req=0xc2063258 SETFEATURES SET
TRANSFER MODE semaphore timeout !! DANGER Will Robinson !!
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Tools for FreeBSD development

[Alexander Leidinger]

Quoting "Kevin Sanders" <[EMAIL PROTECTED]> (Sun, 3 Dec 2006 08:23:24 -0800):

> On 12/3/06, Robert Watson <[EMAIL PROTECTED]> wrote:
> > If using FreeBSD on i386/amd64 boxes, use PXE.  There are quite a few 
> > "instant
> > setup" web pages out there that tell you how to get it running.  pxeboot 
> > makes
> > life incredibly easy, as you can load kernels, modules, configurations, etc,
> > over NFS.
> >
> > Robert N M Watson
> > Computer Laboratory
> > University of Cambridge
> 
> Thanks for th tips everyone.  My shop has all the VMware tools, and
> I've used QEMU, but I prefer to develop on a real box and debug over a
> serial port on a second box.  I'll give pxeboot a shot tomorrow.
> 
> While we're on this topic, what is the best way to debug kernel
> modules.  I would like the ability to kldload my kernel module, set a
> couple break points and single step through a section of code (at
> least).

cd   # I'm using the old way of building
make gdbinit

In kgdb you can now use "getsyms" if you debug remotely (I haven't
tested this) or "kldsyms" if you debug locally to load the debug
symbols.

Bye,
Alexander.

-- 
Groundskeepers stole the root password
http://www.Leidinger.net  Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org  : PGP ID = 72077137
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Announce: FreeSBIE 2.0-RC1 is available

[Jeremie Le Hen]

Hi Matteo,

On Sun, Nov 26, 2006 at 08:51:24PM +0100, Matteo Riondato wrote:
> if you followed the development of FreeSBIE 2.0 a bit, you should
> remember that, back in Semptember, I said that FreeSBIE 2.0 would have
> been the last of a series of four ISO images. Three images were
> already published: FreeSBIE GMV back in August, FreeSBIE LVC in
> October, FreeSBIE 2.0-BETA in November.  Well, circustamces make
> me release a fourth ISO image which is *not* FreeSBIE 2.0, but
> FreeSBIE 2.0-RC1 (Release Candidate 1). This is due to the number of
> bugs which had been fixed after 2.0-BETA was release. 
> If no major bugs are found, FreeSBIE 2.0 is going to be released not
> too long after FreeBSD 6.2-RELEASE has been released. Hopefully you
> will be able to put a FreeSBIE 2.0 CD-ROM under your Christmas tree.
> :)
> 
> FreeSBIE 2.0-RC1 is based on the RELENG_6_2 branch of the FreeBSD
> source tree and on the RELEASE_6_2_0 branch of the ports tree.
> 
> Testing the ISO image, finding bugs and reporting them back to me or
> to the freesbie@gufi.org mailing list are the foci for those who want
> to give this ISO image a try, and I hope many of you will. There is
> still a lot of free space on the ISO image, so feel free to suggest
> additional software to include.

First, thank you for the work on FreeSBIE.  I've just booted it, and
it is simply neat.  I like it.

Unfortunately, I can't get X to work.  It seems to be correctly
launched but the screen is blank.

I've attached Xorg.0.log and my dmesg output.  Please, feel free to
ask for more informations.

Regards,
-- 
Jeremie Le Hen
< jeremie at le-hen dot org >< ttz at chchile dot org >

X Window System Version 6.9.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 6.9
Build Operating System: FreeBSD 6.2 i386 [ELF] 
Current Operating System: FreeBSD FreeSBIE.LiveCD 6.2-RC1 FreeBSD 6.2-RC1 #26: 
Thu Nov 23 22:49:20 UTC 2006 [EMAIL 
PROTECTED]:/usr/obj.gmv-i386/usr/src/sys/FREESBIE i386
Build Date: 25 October 2006
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec  3 20:10:45 2006
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Card0"
(**) |-->Input Device "Keyboard0"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Mouse0"
(WW) The directory "/usr/X11R6/lib/X11/fonts/Type1/" does not exist.
Entry deleted from font path.
(**) FontPath set to 
"/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/bitstream-vera/,/usr/X11R6/lib/X11/fonts/URW,/usr/X11R6/lib/X11/fonts/urwfonts-ttf/"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(**) ModulePath set to "/usr/X11R6/lib/modules"
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.2
X.Org Video Driver: 0.8
X.Org XInput driver : 0.5
X.Org Server Extension : 0.2
X.Org Font Renderer : 0.4
(II) Loader running on freebsd
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.so
(II) Module bitmap: vendor="X.Org Foundation"
compiled for 6.9.0, module version = 1.0.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 6.9.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.8
(--) Using syscons driver with X support (version 2.0)
(--) using VT number 9

(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,2590 card 1025,0066 rev 03 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,2591 card , rev 03 class 06,04,00 hdr 01
(II) PCI: 00:1c:0: chip 8086,2660 card , rev 04 class 06,04,00 hdr 81
(II) PCI: 00:1c:1: chip 8086,2662 card , rev 04 class 06,04,00 hdr 81
(II) PCI: 00:1c:2: chip 8086,2664 card , rev 04 class 06,04,00 hdr 81
(II) PCI: 00:1d:0: chip 8086,2658 card 1025,0066 rev 04 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,2659 card 1025,0066 rev 04 class 0c,03,00 hdr 00
(II) PCI: 00:1d:2: chip 8086,265a card 1025,0066 rev 04 class 0c,03,00 hdr 00
(II) PCI: 00:1d:3: chip 8086,265b card 1025,0066 rev 04 class 0c,03,00 hdr 00
(II) PCI: 00:1d:7: chip 8086,265c card 1025,0

Re: BootCache for FreeBSD

[Ivan Voras]

Vishal Patil wrote:
> Is anyone working on the idea of implementing BootCache for FreeBSD? MacOS
> has this idea implemented
> http://www.osxbook.com/book/bonus/misc/optimizations and I was wondering if
> FreeBSD had such an implementation. I think it would be especially usefull
> for laptops and desktops with slow drives that run FreeBSD.

It would be easy to do as a GEOM class, but for real-life usage it would
have to be directly in GEOM.

Actually, I've done the logging part twice before, but it's not
convenient to stop the geoms to insert a logging class in front of them.
PJD has talked for some time about making a sort-of "hot-pluggable"
mechanism in GEOM in which classes could be inserted in between two
other classes without stopping them, but this will take time...

There's another consideration: Apple can do it because OSX is shipped
"as-is" and doesn't change much when you install it, but FreeBSD is
always customized after installing. This doesn't prevent the mechanism
to be implemented, but it would require it to be very easy to use.

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