Search results

What about structures? Where are most structures and their handling functions defined? I'm beginning to see that there is no general purpose solution to this...

I'm just curiously browsing through the code to see anything I find interesting. Mainly what structures do, syscalls, internal routines, etc. It's just such a pain to have to identify where everything happens.

Awesome, thanks. In the future, what should I use? As of now, I use grep -r "exit" * But the problem with this is that this shows every single instance of the string "exit" in /usr/src/. I have to sift through it to try to find the declaration itself. IDEA: Maybe if I build my kernel with...

I've read a great book on BSD rootkits, and one of the examples that I found interesting suggested that I find where exit() is implemented, and use the implementation details to write a process-hiding system call. In the sources for libc, exit() is implemented as a wrapper around _exit(), which...

As totally stunned as I am right now, it doesn't change my question. How can I get ahold of that typeface?

I see a lot of .fnt files, but I'd rather not go through the trouble of converting all that to ttf. Does it have a name, or was it created just for this purpose, and called "the default console font?"

I really like the generic, default font that is used in the framebuffer, but now that I have to use Mac OS X for development, and I'm permanently wedded to emacs, I'm finding it a huge pain to use the fonts they have. What font does the framebuffer use, so that I might set it as my default in...

Ok, so I found a solution. It seems that VMware does not have a VESA BIOS at all, so trying to make it work with VESA was a lost cause. Instead, it takes nothing more than adding allscreens_flags="MODE_<mode number>" to /etc/rc.conf to enable a high resolution console in, I suspect, VGA. Also...

Yes it does. It seems to have something to do with the fact that the line for SC_PIXEL_MODE is not present in /usr/src/sys/conf/options.i386. So, what I've tried doing is taking the relevant SC_PIXEL_MODE line from /usr/srs/sys/conf/options and pasting it into the options.i386 file. It is...

Ok, now I know something is up because I downloaded and set up 6.0-RELEASE, and it gives me the same error even there. I had considered the possibility that the option might have been removed in recent releases, but apparently there is something deeper here. Any ideas?

-------------------------------------------------------------- >>> Kernel build for VESAKERN started on Mon Aug 10 13:42:52 UTC 2009 -------------------------------------------------------------- ===> VESAKERN mkdir -p /usr/obj/usr/src/sys...

Here is my kernel configure file: include GENERIC ident VESAKERN # VESA framebuffer support options VESA options SC_PIXEL_MODE

Nope. At first I decided to run on AMD64, and then i discovered that VESA is not supported in the 64 bit kernel. Since making virtual machines is easy as cake, I simply switched to FreeBSD i386.

While I do see MODE_34 when I run vidcontrol -i mode, when I run that I get an Invalid argument error.

Sorry, just one more note. I'm using this on VMWare on a Macbook Pro, so that might raise some issues. I've tried compiling the kernel with just options VESA, whenever I try to change to a higher resolution, I get: vidcontrol: cannot activate raster display: Inappropriate ioctl for device...

I'm trying to compile a nice kernel to get VESA support. I'm using the usual route of compiling the kernel with: options VESA options SC_PIXEL_MODE and make buildkernel KERNCONF=MYCONF gives me a syntax error on the line containing SC_PIXEL_MODE. What gives? I'm using 7.2-STABLE.