Re: valgrind or workalike on FreeBSD/amd64 7.0/8.0?
On Sat, 16.02.2008 at 17:50:01 -0600, Christian S.J. Peron wrote: > On Tue, Feb 12, 2008 at 11:51:19AM -0800, Xin LI wrote: > [..] > > > > Hi, > > > > Is there anyone working on valgrind on newer FreeBSD releases, or some > > work-alikes? > > > > Cheers, > > Yes, check out the //depot/projects/valgrind/... perforce project. It > works pretty well. When will mere mortals like us get a chance to play with it? I found valgrind _very_ useful back in the 5.x and 6.x days. Thanks for the porting! Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: valgrind or workalike on FreeBSD/amd64 7.0/8.0?
Am Montag, 18. Februar 2008 09:53:23 schrieb Ulrich Spoerlein: > When will mere mortals like us get a chance to play with it? I found > valgrind _very_ useful back in the 5.x and 6.x days. I just wanted to say that I'd also be very interested in testing it out (if you need testers for it), because currently I always (have to try to) compile applications I want to memcheck (which is my main reason for using valgrind) on Linux, which is a slight PITA. I'd be running it on i386, anyway. Thanks for any feedback in advance, and thanks for the effort! -- Heiko Wundram Product & Application Development ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
pci support for /usr/share/example/drivers?
Hi, all, the scripts in /usr/share/examples/drivers, Author: Julian Elischer create two isa skeletons for drivers. i would like to create a skeleton for a pci driver. Please, can you help me by pointing out all diffs needed for this purpose? Thanks for your suggestions. [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: valgrind or workalike on FreeBSD/amd64 7.0/8.0?
"Heiko Wundram (Beenic)" <[EMAIL PROTECTED]> writes: > Ulrich Spoerlein <[EMAIL PROTECTED]> writes: > > When will mere mortals like us get a chance to play with it? I found > > valgrind _very_ useful back in the 5.x and 6.x days. > I just wanted to say that I'd also be very interested in testing it > out (if you need testers for it), because currently I always (have to > try to) compile applications I want to memcheck (which is my main > reason for using valgrind) on Linux, which is a slight PITA. > > I'd be running it on i386, anyway. The ports version is a little outdated, but it works fine on i386. What peter@ and phk@ are doing in p4 is to port a newer version to FreeBSD and add amd64 support. Hopefully, the upstream vendor will adopt those patches so it doesn't have to be done over for every major valgrind release. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: valgrind or workalike on FreeBSD/amd64 7.0/8.0?
Am Montag, 18. Februar 2008 12:50:36 schrieben Sie: > The ports version is a little outdated, but it works fine on i386. What > peter@ and phk@ are doing in p4 is to port a newer version to FreeBSD > and add amd64 support. Hopefully, the upstream vendor will adopt those > patches so it doesn't have to be done over for every major valgrind > release. Not true. The ports version(s, both valgrind and valgrind-snapshot) don't work on FreeBSD 7, simply because the system call table for 7.0 hasn't been updated yet, and it also fails to compile on the current GCC (whereas the latter is an easy fix, which I could post as a pr, but didn't so far, because of the unresolved issues wrt. the new system calls, which I can't/don't have time to fix). I last tried installing valgrind about a week ago; if you tell me that something changed in that week (haven't done a csup since then), I'll gladly try again, but AFAIK, nothing's changed (i.e., it doesn't work on 7 so far). -- Heiko Wundram Product & Application Development ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Giulio, Mon, Feb 18, 2008 at 01:39:50PM +0100, Giulio Ferro wrote: > first of all thanks for your effort. No problems ;)) > Unfortunately I couldn't still get the synaptyc driver work on my laptop. > > Here's what I did: > 1) I extracted the port driver with "make extract patch" > 2) put your patch in /usr/ports/x11-drivers/synaptics/files (I named it > "newpatch") > 3) applied the patch with that directory with patch < newpatch No, the patch I had supplied is the patch-to-the-patch ;)) So you should 1) Do 'make clean' in the port's directory. 2) Apply the patch with 'patch -p1 < /path/to/the/supplied/patchfile'. 3) Build and install the port. Sorry, I was not clear enough on how to apply the modification. Please, try again if you have some spare time. Thanks! -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: Giulio, good day. Long time ago, in December 2007, we discuissed the problem with Synaptics touchpad driver for FreeBSD in the freebsd-hackers list. I had corrected the problem and driver seems to work, but I need more testing with real hardware. I had opened the FreeBSD PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=120783 It will be great if you will be able to try the patch in the PR (I assume that you still have FreeBSD/amd64 and Xorg on some of your machines) and report the result either to the list or as the PR followup. Thank you! Hi Eygene, first of all thanks for your effort. Unfortunately I couldn't still get the synaptyc driver work on my laptop. Here's what I did: 1) I extracted the port driver with "make extract patch" 2) put your patch in /usr/ports/x11-drivers/synaptics/files (I named it "newpatch") 3) applied the patch with that directory with patch < newpatch 4) compiled the driver with make install clean 5) loaded the driver in /boot/loader.conf (as per pkg-message) 6) modified the /etc/X11/xorg.conf (//) 7) disabled the moused demon (//) When I launched startx the xorg server aborted with the same "No Device specified" I got the last time. I attach the complete log of the server. I hope it will be of help to you. Regards. X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-PRERELEASE amd64 Current Operating System: FreeBSD aurynmob2.giulioferro.it 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Wed Jan 30 22:06:30 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AURYNMOB2 amd64 Build Date: 18 February 2008 10:16:05AM 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: Mon Feb 18 13:23:34 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Simple Layout" (**) |-->Screen "Screen 1" (0) (**) | |-->Monitor "My Monitor" (**) | |-->Device "* Generic VESA compatible" (**) |-->Input Device "Keyboard1" (**) |-->Input Device "Synaptics_Touchpad" (**) Option "DontVTSwitch" (**) Option "DontZap" (**) Option "DontZoom" (==) Automatically adding devices (==) Automatically enabling devices (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/fonts/local/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/local/"). (==) Including the default font path /usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/lib/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/. (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (==) RgbPath set to "/usr/local/share/X11/rgb" (==) ModulePath set to "/usr/local/lib/xorg/modules" (II) No default mouse found, adding one (**) |-->Input Device "" (II) Loader magic: 0x680ce0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: "pcidata" (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (WW) OS did not count PCI devices, guessing wildly (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2a00 card 104d,9016 rev 0c class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2a01 card , rev 0c class 06,04,00 hdr 01 (II) PCI: 00:1a:0: chip 8086,2834 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1a:1: chip 8086,2835 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1a:7: chip 8086,283a card 104d,9016 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1b:0: chip 8086,284b card 104d,9016 rev 03 class 04,03,00 hdr 00 (II) PCI: 00:1c:0: chip 8086,283f card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:1: chip 8086,2841 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:2: chip 8086,2843 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2830 card 104d,9016 rev 03 cl
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: Please, try again if you have some spare time. Ok. Now the server starts, but the mouse pointer isn't moving... in the ServerLayout section I have this: #InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" InputDevice "Synaptics_Touchpad""CorePointer" and I didn't start the moused demon. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Mon, Feb 18, 2008 at 02:49:00PM +0100, Giulio Ferro wrote: > Eygene Ryabinkin wrote: >> Please, try again if you have some spare time. > > Ok. Now the server starts, Good ;)) > but the mouse pointer isn't moving... Bad :(( > in the ServerLayout section I have this: >#InputDevice "Mouse1" "CorePointer" >InputDevice "Keyboard1" "CoreKeyboard" > InputDevice "Synaptics_Touchpad""CorePointer" And if you'll try 'InputDevice "Synaptics_Touchpad" "CorePointer" "SendCoreEvents"'? I have it in my Synaptics config @i386 and I vaguely recall that this was needed to enable the touchpad and USB mouse to work together. May be this will fix your problems. If not, drop me a letter, I'll try to get the real hardware into my hands and test it. But this likely won't be done until the end of the week, sorry. -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: in the ServerLayout section I have this: #InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" InputDevice "Synaptics_Touchpad""CorePointer" And if you'll try 'InputDevice "Synaptics_Touchpad" "CorePointer" "SendCoreEvents"'? Nothing changes, sorry... If not, drop me a letter, I'll try to get the real hardware into my hands and test it. But this likely won't be done until the end of the week, sorry. Thanks again. I include the complete log of the xorg session, I hope it can help you somehow. If you need me further tests just say so... Bye. X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-PRERELEASE amd64 Current Operating System: FreeBSD aurynmob2.giulioferro.it 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Wed Jan 30 22:06:30 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AURYNMOB2 amd64 Build Date: 18 February 2008 10:16:05AM 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: Mon Feb 18 15:46:59 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Simple Layout" (**) |-->Screen "Screen 1" (0) (**) | |-->Monitor "My Monitor" (**) | |-->Device "* Generic VESA compatible" (**) |-->Input Device "Keyboard1" (**) |-->Input Device "Synaptics_Touchpad" (**) Option "DontVTSwitch" (**) Option "DontZap" (**) Option "DontZoom" (==) Automatically adding devices (==) Automatically enabling devices (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/fonts/local/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/local/"). (==) Including the default font path /usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/lib/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/. (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (==) RgbPath set to "/usr/local/share/X11/rgb" (==) ModulePath set to "/usr/local/lib/xorg/modules" (II) No default mouse found, adding one (**) |-->Input Device "" (II) Loader magic: 0x680ce0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: "pcidata" (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (WW) OS did not count PCI devices, guessing wildly (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2a00 card 104d,9016 rev 0c class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2a01 card , rev 0c class 06,04,00 hdr 01 (II) PCI: 00:1a:0: chip 8086,2834 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1a:1: chip 8086,2835 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1a:7: chip 8086,283a card 104d,9016 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1b:0: chip 8086,284b card 104d,9016 rev 03 class 04,03,00 hdr 00 (II) PCI: 00:1c:0: chip 8086,283f card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:1: chip 8086,2841 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:2: chip 8086,2843 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2830 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2831 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,2832 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,2836 card 104d,9016 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card , rev f3 class 06,04,01 hdr 01 (II) PCI: 00:1f:0: chip 8086,2811 card 104d,9016 rev 03 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,2850 card 104d,9016 rev 03 class 01,01,8a hdr 00 (II) PCI: 00:1f:2: chip 8086,282a card 104d,9016 rev 03 class 01,04,00 hdr 00 (II) PCI: 00:1f:3: chip 8086,283e card 104d,9016 rev 03 class 0c,05,00 hdr 00 (II) PCI: 01:00:0: chip 10de,04
Re: Synaptics Xorg driver for FreeBSD/amd64
Giulio, Mon, Feb 18, 2008 at 04:00:43PM +0100, Giulio Ferro wrote: > Eygene Ryabinkin wrote: >> And if you'll try >> 'InputDevice "Synaptics_Touchpad" "CorePointer" "SendCoreEvents"'? >> >> > Nothing changes, sorry... > >> If not, drop me a letter, I'll try to get the real hardware into >> my hands and test it. But this likely won't be done until the end >> of the week, sorry. >> > > Thanks again. I include the complete log of the xorg session, I hope it can > help you somehow. Yes, the following lines are very suspicious: - > (WW) : No Device specified, looking for one... > (II) : Setting Device option to "/dev/psm0" > (--) : Device: "/dev/psm0" > (==) : Protocol: "Auto" > (**) Option "AlwaysCore" > (**) : doesn't report core events > (==) : Emulate3Buttons, Emulate3Timeout: 50 > (**) : ZAxisMapping: buttons 4 and 5 > (**) : Buttons: 9 > (**) : Sensitivity: 1 > (II) evaluating device () > (II) XINPUT: Adding extended input device "" (type: MOUSE) > (II) evaluating device (Synaptics_Touchpad) > (II) XINPUT: Adding extended input device "Synaptics_Touchpad" (type: MOUSE) > (II) evaluating device (Keyboard1) > (II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD) > Synaptics DeviceInit called > SynapticsCtrl called. > (II) : SetupAuto: hw.iftype is 3, hw.model is 13 > (II) : SetupAuto: protocol is SysMouse > (WW) fcntl(9, O_ASYNC): Inappropriate ioctl for device > Synaptics DeviceOn called > (EE) xf86OpenSerial: Cannot open device /dev/psm0 > Device busy. > (WW) Synaptics_Touchpad: cannot open input device > couldn't enable device 3 - It seems to me that you have another mouse device called '' that uses "auto" protocol and finds your mouse at /dev/psm0 and being SysMouse. Can you show your full xorg.conf? Thanks! -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sched_ule: roundrobin_callout replacement ?
I see that sched_4bsd has a NOP callout with a purpose of forcing a context switch (via softclock), so that something like a preemption could happen (e.g. for threads in a tight calculation loop). What serves the similar purpose for sched_ule? Or, how sched_ule deals with the issue without needing softclock's help? -- Andriy Gapon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Mon, Feb 18, 2008 at 04:49:13PM +0100, Giulio Ferro wrote: > Eygene Ryabinkin wrote: >> Yes, the following lines are very suspicious: >> - >> - >> >> It seems to me that you have another mouse device called '> pointer>' that uses "auto" protocol and finds your mouse at /dev/psm0 >> and being SysMouse. Can you show your full xorg.conf? >> > > > Sure, find it attached... Aargh, this is the funny thing: you have no devices that are handled by the 'mouse' driver. And Xorg automatically adds one. Please, uncomment your 'Mouse1' device inside "ServerLayout", start moused and try again. The '' should disappear. And probably mices will start working. It will be good to see Xorg.log from this attempt. Thank you! -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: Yes, the following lines are very suspicious: - - It seems to me that you have another mouse device called '' that uses "auto" protocol and finds your mouse at /dev/psm0 and being SysMouse. Can you show your full xorg.conf? Sure, find it attached... # File generated by xorgconfig. # # Copyright 2004 The X.Org Foundation # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of The X.Org Foundation shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from # The X.Org Foundation. # # ** # Refer to the xorg.conf(5) man page for details about the format of # this file. # ** # ** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ** # Section "Module" # This loads the DBE extension module. Load"dbe" # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection "extmod" Option"omit xfree86-dga" # don't initialise the DGA extension EndSubSection # This loads the font modules #Load"type1" Load"freetype" #Load"xtt" # This loads the GLX module Load "glx" # This loads the DRI module Load "dri" Load"synaptics" EndSection # ** # Files section. This allows default font and rgb paths to be set # ** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. #RgbPath"/usr/local/share/X11/rgb" # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # FontPath "/usr/local/lib/X11/fonts/misc/" FontPath "/usr/local/lib/X11/fonts/TTF/" FontPath "/usr/local/lib/X11/fonts/OTF" FontPath "/usr/local/lib/X11/fonts/Type1/" FontPath "/usr/local/lib/X11/fonts/100dpi/" FontPath "/usr/local/lib/X11/fonts/75dpi/" FontPath "/usr/local/lib/X11/fonts/local/" #FontPath "/usr/local/lib/X11/fonts/Speedo/" #FontPath "/usr/local/lib/X11/fonts/TrueType/" #FontPath "/usr/local/lib/X11/fonts/freefont/" # The module search path. The default path is shown here. #ModulePath "/usr/local/lib/modules" EndSection # ** # Server flags section. # ** Section "ServerFlags" # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging #Option "NoTrapSignals" # Uncomment this to disable the VT switch sequence # (where n is 1 through 12). This allows clients to receive these key # events. Option "DontVTSwitch" # Uncomment this to disable the server abort sequence # This allows clients to receive this key event. Option "DontZap" # Uncomment this to disable the / mode switching # sequences. This allows clients to receive these key events. Option "Dont Zoom" # Uncomment this to disable tuning with the xvidtune client. With # it the client can still run and fetch card and monitor attributes, # but it wi
Re: if_start() and sending packets problem
Hi, > > Doing tcpdump on the interface and pinging does not show any packets > flowing. Please note that tcpdump shows the arp who-has request right > after I assign the ip address. > If think you have to use the BPF macros before you get anything in tcpdump. BTW: Have you looked at any other USB network drivers ? --HPS ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Hi Eygene, thanks for your summary! On Mon, 18 Feb 2008 19:04:13 +0300 Eygene Ryabinkin <[EMAIL PROTECTED]> wrote: > >> It seems to me that you have another mouse device called ' >> pointer>' that uses "auto" protocol and finds your mouse at /dev/psm0 > >> and being SysMouse. Can you show your full xorg.conf? > > Sure, find it attached... > Aargh, this is the funny thing: you have no devices that are handled > by the 'mouse' driver. And Xorg automatically adds one. > Please, uncomment your 'Mouse1' device inside "ServerLayout", start > moused and try again. The '' should disappear. > And probably mices will start working. > It will be good to see Xorg.log from this attempt. I'm using x11-drivers/synaptics on FreeBSD/i386. I don't have any problem which many people said. I have two questions: a. Anyone, do you install x11-drivers/xf86-input-void? I didn't install x11-drivers/xf86-input-void. b. If you install x11-drivers/xf86-input-void, please check following setting. Section "InputDevice" Identifier "dummy" Driver "void" EndSection I read source files of Xserver and void driver, but I didn't understand these relations:-(. So I don't know that it's correct to fix this problem by way of b. And, if x11-drivers/ xf86-input-void is not installed, that's solution will be crashed. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Giulio, Roman, Mon, Feb 18, 2008 at 07:04:13PM +0300, Eygene Ryabinkin wrote: > Aargh, this is the funny thing: you have no devices that are handled > by the 'mouse' driver. And Xorg automatically adds one. > > Please, uncomment your 'Mouse1' device inside "ServerLayout", start > moused and try again. The '' should disappear. > And probably mices will start working. There is a better way that I had found while was answering to Norikatsu's letter: add the string - Option "AllowEmptyInput" - to your xorg.conf "ServerFlags" section and you should see no additional mouse devices and probably Synaptics mice will be alive. Roman, this concerns you too ;)) Please, try it if you prefer to use single pointer from touchpad. -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pci support for /usr/share/example/drivers?
[EMAIL PROTECTED] wrote: Hi, all, the scripts in /usr/share/examples/drivers, Author: Julian Elischer create two isa skeletons for drivers. i would like to create a skeleton for a pci driver. Please, can you help me by pointing out all diffs needed for this purpose? Thanks for your suggestions. [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]" Wonderful Idea. Warner was going to do this about 4 years ago He may even have some code sitting around.. :-) ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Norikatsu, good day. Tue, Feb 19, 2008 at 02:35:24AM +0900, Norikatsu Shigemura wrote: > Hi Eygene, thanks for your summary! You're welcome! > On Mon, 18 Feb 2008 19:04:13 +0300 > Eygene Ryabinkin <[EMAIL PROTECTED]> wrote: > > >> It seems to me that you have another mouse device called ' > >> pointer>' that uses "auto" protocol and finds your mouse at /dev/psm0 > > >> and being SysMouse. Can you show your full xorg.conf? > > > Sure, find it attached... > > Aargh, this is the funny thing: you have no devices that are handled > > by the 'mouse' driver. And Xorg automatically adds one. > > Please, uncomment your 'Mouse1' device inside "ServerLayout", start > > moused and try again. The '' should disappear. > > And probably mices will start working. > > It will be good to see Xorg.log from this attempt. > > I'm using x11-drivers/synaptics on FreeBSD/i386. I don't have > any problem which many people said. > > I have two questions: > > a. Anyone, do you install x11-drivers/xf86-input-void? > I didn't install x11-drivers/xf86-input-void. Personally, I am not using xf86-input-void, because I am using standard system mouse with synaptics touchpad, so I don't need 'void' input device. > b. If you install x11-drivers/xf86-input-void, please check > following setting. > > Section "InputDevice" > Identifier "dummy" > Driver "void" > EndSection > > I read source files of Xserver and void driver, but I didn't > understand these relations:-(. If you'll look at http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=blob;h=dbe158efc6e365cd5bd064d848df3a4f0c0d35f4;hb=43d9edd31e31b33b9da4a50d8ab05004881c8d5a;f=hw/xfree86/common/xf86Config.c#l1611 you will see that server tries to add the mouse driver if there is no drivers of type 'mouse' or 'void'. The hack with adding the "dummy" input device with type "void" disables generation of default mouse driver. This was the true hack and it was a bit beautified in http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commit;h=ba9f5138fc32a7a7b97bcf941bc92751b7c6c2c0 now there is a boolean option "AllowEmptyInput" that inhibits creation of core mouse and keyboard in any case. > So I don't know that it's > correct to fix this problem by way of b. And, if x11-drivers/ > xf86-input-void is not installed, that's solution will be crashed. Xorg server 1.4 already has "AllowEmptyInput", so Giulio and others who want to run only Synaptics driver, can add the string - Option "AllowEmptyInput" - to their "ServerFlags" section and see no automagically added devices. -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: Aargh, this is the funny thing: you have no devices that are handled by the 'mouse' driver. And Xorg automatically adds one. Please, uncomment your 'Mouse1' device inside "ServerLayout", start moused and try again. The '' should disappear. And probably mices will start working. It will be good to see Xorg.log from this attempt. Ok, now I've uncommented both mouse1 and synaptics: InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" InputDevice "Synaptics_Touchpad""CorePointer" and the moused demon. Here's is what I get: 1) The mouse pointer now moves 2) The drag and drop with double click on the touchpad _doesn't_ work 3) Window scrolling with the touchpad _doesn't_ work (either horizontally or vertically) I attach the log of the attempt. X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-PRERELEASE amd64 Current Operating System: FreeBSD aurynmob2.giulioferro.it 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Wed Jan 30 22:06:30 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AURYNMOB2 amd64 Build Date: 18 February 2008 10:16:05AM 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: Mon Feb 18 15:46:59 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Simple Layout" (**) |-->Screen "Screen 1" (0) (**) | |-->Monitor "My Monitor" (**) | |-->Device "* Generic VESA compatible" (**) |-->Input Device "Keyboard1" (**) |-->Input Device "Synaptics_Touchpad" (**) Option "DontVTSwitch" (**) Option "DontZap" (**) Option "DontZoom" (==) Automatically adding devices (==) Automatically enabling devices (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/fonts/local/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/local/"). (==) Including the default font path /usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/lib/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/. (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (==) RgbPath set to "/usr/local/share/X11/rgb" (==) ModulePath set to "/usr/local/lib/xorg/modules" (II) No default mouse found, adding one (**) |-->Input Device "" (II) Loader magic: 0x680ce0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: "pcidata" (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (WW) OS did not count PCI devices, guessing wildly (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2a00 card 104d,9016 rev 0c class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2a01 card , rev 0c class 06,04,00 hdr 01 (II) PCI: 00:1a:0: chip 8086,2834 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1a:1: chip 8086,2835 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1a:7: chip 8086,283a card 104d,9016 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1b:0: chip 8086,284b card 104d,9016 rev 03 class 04,03,00 hdr 00 (II) PCI: 00:1c:0: chip 8086,283f card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:1: chip 8086,2841 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:2: chip 8086,2843 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2830 card 104d,9016 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2831 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,2832 card 104d,9016 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,2836 card 104d,9016 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card , rev f3 class 06,04,01 hdr 01 (II) PCI: 00:1f:0: chip 8086,2811 card 104d,9016 rev 03 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,2850 card 104d,9016 rev 03 class 01
Re: Synaptics Xorg driver for FreeBSD/amd64
Giulio, Mon, Feb 18, 2008 at 10:54:35PM +0100, Giulio Ferro wrote: > Eygene Ryabinkin wrote: >> Please, uncomment your 'Mouse1' device inside "ServerLayout", start >> moused and try again. The '' should disappear. >> And probably mices will start working. > > Ok, now I've uncommented both mouse1 and synaptics: > > InputDevice "Mouse1" "CorePointer" > InputDevice "Keyboard1" "CoreKeyboard" > InputDevice "Synaptics_Touchpad""CorePointer" > > > and the moused demon. > > Here's is what I get: > 1) The mouse pointer now moves Cool. > 2) The drag and drop with double click on the touchpad _doesn't_ work Never tried this feature myself. Will try it tomorrow on my notebook. Did it ever worked for you? > 3) Window scrolling with the touchpad _doesn't_ work (either horizontally or > vertically) Is something reported if you spawn 'xev' and try to scroll via touchpad while the pointer is upon the xev window? > I attach the log of the attempt. Seems like this is the old one: > (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 18 15:46:59 2008 > [...] > (WW) : No Device specified, looking for one... > (II) : Setting Device option to "/dev/psm0" > (--) : Device: "/dev/psm0" > (==) : Protocol: "Auto" > (**) Option "AlwaysCore" > (**) : doesn't report core events > (==) : Emulate3Buttons, Emulate3Timeout: 50 > (**) : ZAxisMapping: buttons 4 and 5 > (**) : Buttons: 9 > (**) : Sensitivity: 1 > (II) evaluating device () > (II) XINPUT: Adding extended input device "" (type: MOUSE) > (II) evaluating device (Synaptics_Touchpad) > (II) XINPUT: Adding extended input device "Synaptics_Touchpad" (type: MOUSE) > (II) evaluating device (Keyboard1) > (II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD) > Synaptics DeviceInit called > SynapticsCtrl called. > (II) : SetupAuto: hw.iftype is 3, hw.model is 13 > (II) : SetupAuto: protocol is SysMouse > (WW) fcntl(9, O_ASYNC): Inappropriate ioctl for device > Synaptics DeviceOn called > (EE) xf86OpenSerial: Cannot open device /dev/psm0 > Device busy. > (WW) Synaptics_Touchpad: cannot open input device > couldn't enable device 3 > > Fatal server error: > Caught signal 10. Server aborting > > Synaptics DeviceOff called -- Eygene ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Synaptics Xorg driver for FreeBSD/amd64
Eygene Ryabinkin wrote: There is a better way that I had found while was answering to Norikatsu's letter: add the string - Option "AllowEmptyInput" - to your xorg.conf "ServerFlags" section and you should see no additional mouse devices and probably Synaptics mice will be alive. Ok, I'll try tomorrow... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
encrypted executables
Good afternoon list, anybody knows of a tool to encrypt executables under FreeBSD? may be from the ports? I am not talking about simple file encryption. I found something called 'burneye' but it's for Linux. Thank you all, Jerry ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: encrypted executables
On 2008-02-19 02:18, Jerry Toung wrote: > anybody knows of a tool to encrypt executables under FreeBSD? may be from > the ports? > I am not talking about simple file encryption. Can you elaborate on what you *are* talking about then? Some security-by-obscurity scheme, perhaps? :) ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: encrypted executables
On 2008-02-19 02:39, Dimitry Andric <[EMAIL PROTECTED]> wrote: >On 2008-02-19 02:18, Jerry Toung wrote: >> anybody knows of a tool to encrypt executables under FreeBSD? may be >> from the ports? >> >> I am not talking about simple file encryption. > > Can you elaborate on what you *are* talking about then? Some > security-by-obscurity scheme, perhaps? :) Encrypted executables, using some sort of stream or block cipher may not be something which looks *very* useful, but there are a few interesting things which can be done with executable encryption and signatures. One of them is described here: http://blogs.sun.com/darren/entry/signed_solaris_10_binaries ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: encrypted executables
On Feb 18, 2008 5:39 PM, Dimitry Andric <[EMAIL PROTECTED]> wrote: > On 2008-02-19 02:18, Jerry Toung wrote: > > anybody knows of a tool to encrypt executables under FreeBSD? may be > from > > the ports? > > I am not talking about simple file encryption. > > Can you elaborate on what you *are* talking about then? Some > security-by-obscurity scheme, perhaps? :) I need to encrypt elf binaries. I'd like to make it harder for the bad guy to reverse engineer my app. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: encrypted executables
On 2008-02-18 19:54, Jerry Toung <[EMAIL PROTECTED]> wrote: >On Feb 18, 2008 5:39 PM, Dimitry Andric <[EMAIL PROTECTED]> wrote: >>On 2008-02-19 02:18, Jerry Toung wrote: >>> anybody knows of a tool to encrypt executables under FreeBSD? may be >>> from the ports? I am not talking about simple file encryption. >> >> Can you elaborate on what you *are* talking about then? Some >> security-by-obscurity scheme, perhaps? :) > > I need to encrypt elf binaries. I'd like to make it harder for the bad > guy to reverse engineer my app. You know about truss/ktrace/strace already, right? It may be moot to encrypt the ELF binary, if the `bad guy' can access the running image of the process *after* it has been decrypted to execute. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: encrypted executables
On Mon, 18 Feb 2008 19:54:14 -0800 "Jerry Toung" <[EMAIL PROTECTED]> wrote: > On Feb 18, 2008 5:39 PM, Dimitry Andric <[EMAIL PROTECTED]> wrote: > > On 2008-02-19 02:18, Jerry Toung wrote: > > > anybody knows of a tool to encrypt executables under FreeBSD? may be > > from > > > the ports? > > > I am not talking about simple file encryption. > > > > Can you elaborate on what you *are* talking about then? Some > > security-by-obscurity scheme, perhaps? :) > I need to encrypt elf binaries. I'd like to make it harder for the bad guy > to reverse engineer my app. Basically the DRM problem (only executing your property under conditions you specify, not under those the end user might want). A *lot* of money has been spent trying to do this, but nobody has done it yet. Some very smart people have concluded it can't be done. That said, you did say "harder", not "impossible". Making it harder is certainly possible, depending on the conditions. What are they conditions you want this to work under? FWIW, the only thing that in this area is to not let them run the critical parts of your app on their hardware. Put those on your service, exported via the network, and then give the end user a UI that talks to that. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: encrypted executables
On Feb 18, 2008 8:13 PM, Mike Meyer < [EMAIL PROTECTED]> wrote: > > Basically the DRM problem (only executing your property under > conditions you specify, not under those the end user might want). A > *lot* of money has been spent trying to do this, but nobody has done > it yet. Some very smart people have concluded it can't be done. > > That said, you did say "harder", not "impossible". Making it harder is > certainly possible, depending on the conditions. What are they > conditions you want this to work under? > > FWIW, the only thing that in this area is to not let them run the > critical parts of your app on their hardware. Put those on your > service, exported via the network, and then give the end user a UI > that talks to that. > thank you all for the feedback. Yep, DRM issues, it doesn't hurt to try. Jerry > > -- > Mike Meyer <[EMAIL PROTECTED]> > http://www.mired.org/consulting.html > Independent Network/Unix/Perforce consultant, email for more information. > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: encrypted executables
In message: <[EMAIL PROTECTED]> Giorgos Keramidas <[EMAIL PROTECTED]> writes: : On 2008-02-18 19:54, Jerry Toung <[EMAIL PROTECTED]> wrote: : >On Feb 18, 2008 5:39 PM, Dimitry Andric <[EMAIL PROTECTED]> wrote: : >>On 2008-02-19 02:18, Jerry Toung wrote: : >>> anybody knows of a tool to encrypt executables under FreeBSD? may be : >>> from the ports? I am not talking about simple file encryption. : >> : >> Can you elaborate on what you *are* talking about then? Some : >> security-by-obscurity scheme, perhaps? :) : > : > I need to encrypt elf binaries. I'd like to make it harder for the bad : > guy to reverse engineer my app. : : You know about truss/ktrace/strace already, right? : : It may be moot to encrypt the ELF binary, if the `bad guy' can access : the running image of the process *after* it has been decrypted to : execute. kill -ABRT will generate a core file. Often times, the core file can be quite useful in recovering the original executable. emacs has used this technique for years to 'preload' stuff, take a core dump, then re-run the core file after some post-processing. Warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
