Re: boot menu option to disable graphics mode
On Thu, 07 Jun 2012 12:57:41 +0300, Gleb Kurtsou wrote: On (07/06/2012 11:56), Andriy Gapon wrote: A user doesn't have to select the option unless he needs to. A simple user can just reboot without selecting the option to get back his X. A user doesn't have to learn anything about the code, just about kenv and magic inhibit_gui variable. What do you think about adding generic support for overriding *_enable options in rc.conf? I'd like to be able to disable services at boot prompt, e.g. # set rc.slim_enable=no -- overrides slim_enable=yes in rc.conf Similarly rc.pf_enable=no Then introduce x_enable knob (=yes by default) to disable login managers. User will be able to override this setting with # service xdm forcestart That's trivial to implement: http://lists.freebsd.org/pipermail/freebsd-current/2007-November/079241.html Still applies with minor reject that can be ignored or easily resolved. It also brings support for overriding path to rc.conf, allowing multiple boot configurations. ___ 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: zfs + uma
FWIW, kvm_read taking the second argument as unsigned long instead of void* seems a bit inconsistent: I think it done on purpose, since address in the kernel address space has nothing to do with pointers for mere userland mortals. We shouldn't bother compiler with aliasing and other stuff in case of kernel addresses. //Marcin ___ 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
inet_* functions in kernel?
Hi. Currently I'm writing a kernel module using MAC Framework to control binding to local IP addresses (kind of mac_portacl variation) and I need some advice. I want to be able to write rules for module through sysctl (rule will contain IP addresses in human-readable format, e.g. uid:1002:192.168.2.3) and I'm wondering how to translate addresses to network byte order without inet_* functions. Well, they look like they're available to use in kernel (using netinet/in.h) but it's no able to compile module with inet_* functions using typical Makefile (this one with .include bsd.kmod.mk line) - it just produces warnings, and all warnings are treated as errors in this case. So, possible solutions are: just add custom CFLAGS without -Werror to Makefile (but it's quite ugly though) or write an userspace application that will write an addresses in NBO to sysctl (but now sysctl won't be easy to read and modify by hand). What do you think? Thanks in advance for any useful hints. -- SIGSTOP ___ 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: make pkg_install suite reusable, please
On Sun, 11 Apr 2010 12:37:27 +0100, Robert Watson wrote: On Fri, 9 Apr 2010, Alexander Churanov wrote: 2010/4/9 Leinier Cruz Salfran salfrancl.lis...@gmail.com i want to ask you one thing: can you make the 'pkg_install' suite reusable .. means install 'libinstall.a' as a shared object in order to make it reusable by others devs I'd like to add my 50 cents. From my point of view, the true UNIX way is re-using whole programs. This provides unbelievable isolation and correctness. If you don't want to fork myriads of processes each second, then, it's, probably, better to ask for pipe mode of pkg_* tools. For example, aspell works that way. You start a process, write commands and queries and read results. While there are clearly benefits to process isolation, there are countless situations in UNIX where I've said to myself Oh, I wish I had a libfoo not just a foo command. This is particularly the case for monitoring tools, where third-party applications have a lot of trouble parsing and tracking the output of tools like ps(1), etc. This is why recently we've been working on libmemstat(3), libprocstat(3), libnetstat(3), etc -- so that tools can avoid rewriting that code as well as avoid the parsing problem. A middle-ground solution to this is to standardise on a common data exchange format with a schema definition language. With schema you can autogenerate high level parsers and generators, validators and other things for free. It does not have to be XML with XML-Schema (though there are good plaintext schema languages like RelaxNG-compact and you could possibly find less verbose text encoding for XML). Fine human readable competitors to XML exists like OGDL, YAML or JSON. OGDL project even have patches for OGDL output in GNU utlities. If, say ps or ipfw, had a switch like '--format-output-yaml' and '--print-output-schema' (alternatively schema files could be stored somewhere in $prefix/share) it would be trivial to use them anywhere. Similar approach could be adopted to input passing with possibility of pipe mode. Any utilitily, with mere tweaks to output formatting and pipe mode would in fact be a class that you could instantiate (run) and use like any other object in your programming language and all of that for free, autogenerated from schema descriptions ;) The only problem I see is agreeing on a single format and forcing everyone to use it. Which is probably why it will never happen :( ___ 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: lzma compression/decompression in bsdtar/libarchive?
On Tue, 25 Nov 2008 19:02:02 +0100, Ivan Voras wrote: How useful would LZMA be without supporting the .7z file format? Probably not at all, since there isn't a gzip-like file format or wrapper that supports LZMA. tar.lzma is quite popular ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Locale woes.
On Wed, 30 Jul 2008 23:50:13 +0200, Václav Haisman wrote: Václav Haisman wrote, On 30.7.2008 20:40: Hi, I have some problem with locales on FreeBSD 6.3. The attached test case fails with uncaught std::runtime_error exception: [...] I am able to run the test case successfuly when I compile it with STLport. So it seems there is something odd going on with just the libstdc++ that ships with GCC. On the other hand, it works fine with GCC 4.1.2 on Gentoo/Linux. Yes it is somewhat known problem that libstdc++ on FreeBSD does not support locales. I've seen some discussions about this in the past on freebsd lists. You can try searching archives, but AFAIR there was no solution except hints how to implement it. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is Elf formatdocumented anywhere?
Yuri wrote: ELF is fairly well documented and standardized. No, I would say ELF is somewhat documented. Just googling for 'ELF' quickly yields the Wikipedia page http://en.wikipedia.org/wiki/Executable_and_Linkable_Format which contains several links to documents describing plenty of details. These links only go that far. Googling many if not most of the constants that are in /usr/include/sys/elf_common.h only gives some discussion references. You can also read the elf(5) manpage in FreeBSD Not many details here too. For introductory material, please see the Linkers and Loaders book: http://www.iecc.com/linker/ --Marcin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Examples of sysctl/sysctlbyname/sysctlnametomib?
Jeremy Chadwick wrote: Does anyone know of some documentation which would help explain how to walk the sysctl MIB tree for such things as dev.cpu? The sysctl(3) documentation is not very clear in regards to how to do this, and the closest thing I can find is what's in src/usr.sbin/powerd/powerd.c. Does sysctl_all() of src/sbin/sysctl/sysctl.c does that what you need? Mightt be easier to iterate a whole subtree and skipping things you don't need. --Marcin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
interfacing uhid devs from kernel module
Hello Is it possible to use functions from libusbhid in kernel module? It would really ease some things for me, but I realize it is a userland library. Still, is there some way to do this? Bye Marcin Cylke ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interfacing uhid devs from kernel module
On 6/15/06, Hans Petter Selasky [EMAIL PROTECTED] wrote: What functions do you need? Have you looked at uhid.c under /sys/dev/usb ? I would like to use the whole infrastructure: struct hid_item hid_usage_page() hid_usage_in_page() hid_init() hid_get_report_desc() Bye ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
proxy device
Hi I'd like to write a proxy device for another usb device. I'd like it to be able to create a device only when an usb dev is attached, then destroy it when detached. What should I do? Where can I find information about this matter? Marcin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
VIA 6420 RAID 0 problem
I have (had?) two issues, perhaps connected:
(I posted a question to freebsd-questions about it some time ago. It
contains some additional information:
http://lists.freebsd.org/pipermail/freebsd-questions/2005-November/103991.html)
The first one is a problem with RAID 0, where ar0 device shows size of
one disk instead of the whole array (others report the same problem):
atapci0: VIA 6420 SATA150 controller port
0xec00-0xec07,0xe800-0xe803,0xe400-0xe407,0xe000-0xe003,0xdc00-0xdc0f,0xd800-0xd8ff
irq 20 at device 15.0 on pci0
[...]
ad0: 29314MB IBM DTLA-307030 TX4OA60A at ata0-master UDMA100
ad4: 76319MB WDC WD800JD-00HKA0 13.03G13 at ata2-master SATA150
ad6: 76319MB WDC WD800JD-00HKA0 13.03G13 at ata3-master SATA150
ar0: 76319MB VIA Tech V-RAID RAID0 (stripe 16 KB) status: READY
ar0: disk0 READY using ad4 at ata2-master
ar0: disk1 READY using ad6 at ata3-master
I could not access slices that started past the first half of array.
After trying different things and settings with sysinstall and
linux-fdisk port I inspected src/sys/dev/ata/ata-raid.c and in
ata_raid_via_read_meta() changed a line:
switch (meta-type VIA_T_MASK) {
case VIA_T_RAID0:
raid-type = AR_T_RAID0;
raid-width = meta-stripe_layout VIA_L_MASK;
- raid-total_sectors = meta-total_sectors;
+ raid-total_sectors = meta-total_sectors * raid-width;
break;
to multiply the number of total_sectors by the number of disks (I guess
that's what raid-width stands for). I don't know if it is the right
thing to do, it just seemed a reasonable fix :)
It works fine for me. I can access (read-write) a FAT32 slice that
starts near the end of the array and the data is ok, can be read in
FreeBSD and Windows with VIA's drivers. A UFS2 partition at the
beginning of the array which I use for /usr also works fine, as before
the change in kernel, so I think I haven't broken anything, at least for
my configuration.
Can anybody comment on it? Or maybe I just should send a PR?
The other, perhaps connected with this, issue is that I lost an extended
partition while creating FreeBSD partition. It had happened before I
started trying to fix the size problem described above.
After slicing the newly created RAID 0 array with sysinstall and
installing Windows, formatting NTFS and FAT slices (with Windows) I
created BSD partitions on the first slice and lost the extended
partition (slice). (a more detailed description of what I did is in the
original posting to freebsd-questions).
Today, after the change in kernel, I have removed FreeBSD partitions
from the first slice and recreated them (with some differences). Nothing
wrong happened.
Could this be connected with the bug in VIA ata raid driver? Or maybe it
was just a coincidence and/or was entirely my fault?
--
Marcin Simonides
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VIA RAID controller problem
Orestis Papakonstantinou wrote: I recently purchased a laptop (Amilo M3438G) that uses VIA's VT6421 RAID controller. I have problem installing FreeBSD (6.0) on that laptop because [...] compatibility layer after the install). Has anyone with similar hardware found a solution? Thanks for your time! I'm using a similar VIA VT6420 with FreeBSD 6.0 though the system is installed on a single IDE disk and only uses VIA's RAID for /usr. I've had problems with RAID0 (I'm going to post more information soon, I need to make a few tests), but I think RAID1 should work fine (I haven't tried). -- Marcin Simonides ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: compiling the kernel faster
On Thu, 27 Oct 2005 04:54:10 -0700 (PDT) kamal kc [EMAIL PROTECTED] wrote: hello everybody, i am new to kernel programming. i am developing a compression/decompression functionality in the ip layer. i want to compile the kernel faster. it would be ok if the kernel doesn't have support for sound devices, or other devices like scsi,usb etc. because i would be using the compiled kernel for network data compression only. how could i do that. which source files and where in the makefiles do i make modifications thanks for any suggestions Read the handbook - http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html Next time remember to post to questions@ when asking begginer questions. Cheers Marcin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Advice on psm driver interface ?
Hello Hackers, I'm playing with the psm driver and a symantics touchpad - I'd like to send the touch pressure along with x/y coordinates/buttons and then chenge the behaviour of mouse in moused using the pressure. What would be better: 1. Extend the struct mousestatus with additional pressure field. 2. Use the mousestatus's z axis movement (dz field). It in fact IS the third dimension, right? The whole concept of z being used for scrolling at times, and at times scrolling being just additional buttons is odd to me. 3. Use another ioctl like MOUSE_SYN_GETHWINFO to fetch the pressure value. What would be best? m. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Tracking FreeBSD performance over time - what hackers want?
Hello Hackers!
I have an idea which could be used to track FreeBSD performance and regression
testing. Please take a look and give Your opinion on how usefull that would be
for the FreeBSD project.
The basis for this system would be hijacking certain functions execution with
injected code. Hijacker program runs target binary with LD_PRELOAD to inject
some code (code doing statistics, tests, etc..) and installs redirections using
ptrace (injecting jump instructions here and there). It then deattaches and the
program runs almost as normal. (A little demo of how this might look later).
This approach has its pros and cons:
+ no context switch to fire hijacking code
+ flexible - You can hijack any function that has a symbol. Hijacking PLT
(done) and relocations in shared libraries (will be done) included.
+ transparent - there needs to be no modiffication in target binary; hackers
don't own all the hardware. It's hard to ask people with interesting equipement
to recompile their binaries with profiling options. This would allow them to
measure performance without changing their system.
+ small performance impact - put code only in places You want, and put there
only the code which is needed there. (can be made O(1) unless You make it worse)
- ABI / Architecture dependent
- needs all the shared library mechanism to inject code (LD_PRELOAD)
- needs symbols
- writes the ro code pages on installing the redirections (negligible?)
And here is the demo of poc code (not particulary usefull..but..)
This hijack code has a static table indexed by read sizes in which we count how
many times a read of this size was called.
#include hijack.h
#include stdio.h
#define PROBES 400
#define QUANT 0x10
static int stats[PROBES];
static int max_read;
// RV(type) gives return value of the code
HIJACK(int, read, (int fd, char *buf, size_t size),
/* before call*/
,
/* after call*/
printf(read() = %d\n, RV(int));
if (max_read RV(int))
max_read = RV(int);
if ((RV(int) =0) (RV(int) QUANT * PROBES))
{
stats[RV(int) / QUANT]++;
}
)
HIJACK(int, main, (),
printf(hello hijacking!\n);
,
)
HIJACK(int, exit, (),
int i;
for (i=0; iPROBES; i++)
if (stats[i])
fprintf(stdout,%04d %04d\n, i*QUANT, stats[i]);
fprintf(stdout,and max read was %d\n, max_read);
fclose(stdout);
printf(finish!\n);
return RV(int);
,
)
--
i compile it
gcc -o apa.so -shared -I. apa.c hijack.c
(hijack.c has some required runtime functions)
I run it on apache:
./hijack -c ./apa.so -h *libc.so.5:read -h *libc.so*:exit -h main
/usr/local/sbin/httpd -X
hello
read() = 4096
read() = 4096
read() = 2732
(some of these)
read() = 0
read() = 961
read() = 425
read() = 0
(here i press ^C)
0010
0112 0002
0256 0002
0416 0003
0512 0002
0656 0002
0960 0001
1120 0002
2720 0002
4096 0046
and max read was 4096
So, again, please send Your opinions on this idea. Do You think this (+ all
needed utilities to do statistics etc) would be applicable to Summer Of Code
Tracking performance over time project?
best regards,
--
Marcin Koziej
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Determine location of LD_PRELOAD'ed shared libraries/functions.
Hello Hackers, I'd like to find locations of functions exported by shared lib loaded into the running ptrace'd process via LD_PRELOAD. I want do determine this from tracing process. For shared libraries linked with a program i can just open the program file and search for relocation sections, which eventually point to the plt function entries. My problem is that i cannot figure out how to start searching for symbols which are loaded with LD_PRELOAD. I can see where the library is mapped in /proc/*/map (isn't there a better, less freebsd-specific place to search for this info?) but I'm not quite sure how to interpret the mmapped pages. Searching Elf doc's just makes me run in circles; usually the LD_PRELOAD option is just mentioned as it was obvious; I't isn't quite. Sections describing program memory image are in program file. LD_PRELOAD'ed lib is only in the memory, to which programs sections do not apply. Libraries sections can't know to what address they will be mmapped to, so where to search? Program has relocation entries, but there is no spare space there for something unexpected like LD_PRELOADed library (?) Please point me to right direction, because i've got only one idea left: grep dynamic loader for LD_PRELOAD ;). -- m. Brain power of a glass of water. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Determine LD_PRELOAD'ed symbols. (UPDATE)
Hello Hackers!, My first post got stuck waiting for moderator, and after some investigation I'd like to ask a bit more substantial question on the topic anyway: With program A ptrace'ing program B which runs with LD_PRELOAD'ed library libC.so, how can i find from program A where functions from libC are located in B's memory? The dump generated with LD_DUMP_REL_PRE shows only symbols which already were in B, but were masked by LD_PRELOAD'ing libC.so, does it mean that other symbols exported by libC.so are unaccessible from B? If not, where to search for their locations? Will sections in B and libC.so give any hints? Pointers to doc/code (but please something smaller than src/libexec/rtld-elf ;) welcome. -- m. Brain power of a glass of water. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Future of RAIDFrame and Vinum (was: Future of RAIDFrame)
Mark Linimon wrote: But, in the real world of software engineering, He Who Breaketh It, Must Fixeth It. Your mileage may vary. Yes it vaires. In the real world He Who Reaketh It, will hire someone who known what he is doing to fix the problem... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Assembler coding help needed.
Martin Nilsson wrote: I'm trying to find out why I can't boot 5.2 from USB CDROM on Supermicro motherboards. (I have an old Gateway P3 that can!). I've found out that that only 0x20 of 0x4c sectors of the loader are read in and it therfor traps when executed. (read is only called once). My last attempt at programming x86 assembler was ~15years ago so I'm a bit rusty :-) The below loop from cdboot.s is what I'm having problem understanding, how can this fail on one box but not on another? # # Load the binary into the buffer. Due to real mode addressing limitations # we have to read it in in 64k chunks. # mov DIR_SIZE(%bx),%eax# Read file length add $SECTOR_SIZE-1,%eax# Convert length to sectors shr $11,%eax %eax is 0x4c here on both machines! cmp $BUFFER_LEN,%eax jbe load_sizeok mov $msg_load2big,%si# Error message call error load_sizeok:movzbw %al,%cx# Num sectors to read mov DIR_EXTENT(%bx),%eax# Load extent xor %edx,%edx mov DIR_EA_LEN(%bx),%dl add %edx,%eax# Skip extended mov $MEM_READ_BUFFER,%ebx# Read into the buffer load_loop:mov %cl,%dh cmp $MAX_READ_SEC,%cl# Truncate to max read size jbe load_notrunc mov $MAX_READ_SEC,%dh load_notrunc:sub %dh,%cl# Update count push %eax# Save call read# Read it in The fun will be here. The rest is self contained and doesn't depend on CPU variant or periphery. pop %eax# Restore add $MAX_READ_SEC,%eax# Update LBA add $MAX_READ,%ebx# Update dest addr jcxz load_done# Done? jmp load_loop# Keep going load_done: ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Power consumption in desktop computers
Erich Dollansky wrote: The actual power can go down to less than 10% if the CPU is idle. Are these business-grade ones maybe equipped with mobile P-4s? No, it is just the fact that modern CPU are most of the time just idle. Which is bullshit becouse most of the CPUs those days don't run desktops and text processing. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: I'm resigning from FreeBSD
Lucas Holt wrote: Funny, I see people switching to *BSD from Linux all the time. I've converted quite a few people at Western Michigan where i'm a student. Most people think of FreeBSD as the new linux. You have to think to use it, as opposed to the redhat idiot wizards. Personally I just love a system which even detracted from defaulting to perl like most UNICEs out ther nowadays (AIX/Solaris). Boy do I hate those Java based admin tools or comparably the perl/python/ruby/whatever/petscriptinglanguageoftheweek library mess found on Linux-distros. FreeBSD gives me just what I need - an OS which is working - the rest is up to my choice. Even looking at the kernel I can't find anything strikingly in need of immediate personal action. Quite contrary to the Linux world where you don't have to shop for too long... However I can't find the GEOM related XML formatted sysctl, which was giving me bad feelings anymore... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Darwin/OSX Bluetooth code
Peter Pentchev wrote: You've done some great work on BlueTooth. IMHO, it would be a mistake to try to un-NetGraph it; there have been lots of rumours about people porting the NetGraph framework to other OS's, and if BlueTooth support will provide yet one more reason for the need to do this, so be it :) I doubt it I came across NetGraph by trying to get my USB-USB link going under FreeBSD. It is extremely cumbersome to be used and seems to be *too low level* as interface design. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hyperthreading slowdown
Richard Coleman wrote: Kris Kennaway wrote: On Sat, Oct 04, 2003 at 03:20:03PM -0400, Richard Coleman wrote: Kris Kennaway wrote: On Sat, Oct 04, 2003 at 04:39:03PM +0200, Mikulas Patocka wrote: I installed FreeBSD 4.9RC1 on P4 3GHz with hyperthreading and I see drastic slowdown when kernel with hyperthreading is booted. For example program compilation took this time: hyperthreading kernel, make -j 1 --- 1:09 hyperthreading kernel, make -j 2 --- 0:42 singlethreading kernel, make -j 1 --- 0:45 singlethreading kernel, make -j 2 --- 0:41 Compilation does very few system calls so when I compile with only one process (-j 1), it should be as fast as with singlethreading kernel. Do you have any idea why is it so slow? Do you realise that hyperthreading != a secret extra CPU in your system? Kris I didn't see anywhere in the message where he implied that. To me, the interesting thing is that there is such a larger difference between the compile time for -j1 and -j2 when using hyperthreading as compared to the difference between -j1 and -j2 for a single threaded kernel. It's over a 50% slowdown. Yes, that's because (as discussed in the archives) the kernel treats it like an extra, completely decoupled physical CPU and schedules processes on it without further consideration. This is presumably the cause of the slowdown, because it's only efficient to use the virtual CPU under certain workload patterns. HTT is not magic performance beans. Kris Sigh. No one is claiming HTT is magic performance beans. The 50% slowdown I'm talking about is between -j1 and -j2 BOTH ARE WHICH ARE USING HTT. It's just an interesting observation. That's all. It's not interresting. It is to be expected. The only gains one could exepect are in the case where sufficently differrent execution units of the CPU would be used. Like for example doing floating point vers. integer calculations. But exen then Amdahl will bite you by the incurrend synchronisation verhead anyway.. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ugly Huge BSD Monster
Peter Jeremy wrote: On Mon, Sep 01, 2003 at 12:38:34PM -0700, Greg Shenaut wrote: Has it ever been suggested to create one or more dependencies ports (or more to the point, packages)? I think it might be pretty useful to have something like that so that all of the prerequisites can be installed at once. Maybe I'm missing something but how would that be an improvement on what FreeBSD does now? If I try to install package X, it will automatically install dependencies A, B and C, as well as their dependencies. What I hate somehow is the proliferation of scripting plugin interfaces which are optional in the src bunch but are not opt-in switches in the actual packages. One example can be vim sucking in perl ruby python and what a not. Esp. annoying is the pyhon stuff visible in libxml2 and libxslt - not usefull at all. One measure to controll this is under FreeBSD to place the following inside /etc/make.conf: # Kerberes. What the heck I never saw this in use. NO_KERBEROS=yes # My own site specific additions: WITH_MOTIF= true WITHOUT_PYTHON= true WITHOUT_RUBY= true # Options for openoffice-pl: WITH_BSD_JDK=TRUE WITH_TTF_BYTECODE_ENABLED=YES WITH_GIF_LZW_COMPRESSION=YES # Options for Java NATIVE_BOOTSTRAP=yes Howver I strongly think that the WITHOYUT_PYTHON and WITHOUT_RUBY items at least should be the defaults. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Missing system call in linux emulation
Marcel Moolenaar wrote: On Tue, Aug 12, 2003 at 05:42:51PM +0100, Steven Hartland wrote: Any one know how I can track down what function is missing and hence look at fixing it? In the linux kernel source tree, look in arch/i386/kernel/entry.S. There you'll find all the syscall entry points. Currently they go all the way to 271. Also look at arch/alpha/kernel/entry.S... Then, in /sys/i386/linux look in syscalls.master. There you'll see we only have syscalls up to 221. See also /sys/alpha/linux... One could: o Add proper prototypes to syscalls.master of the 50 new syscalls we don't know about, o Declare all these syscalls as dummies (see linux_dummy.c) to begin with, o Really implement those syscalls that are used in practice. Syscall 252 is exit_group(2). Most of them are of the sime kind of immature API as for example the whole Linux kvect trash. Don't worry it's very unlikeley they will ever be seriously used and it will be a long time still until kernel 2.6 first will be released at all and second widely deployed. I would vote for dealing with them case by case. Thus keeping to the paramount principle of: don't do interfaces on the heap. FYI, ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libedit and g++
Priit Piipuu wrote:
Hi!
There seems to be a problem using libedit from C++. Small test case:
cat test.c
#include stdio.h
#include histedit.h
int
main(void) {
EditLine *ed;
ed = el_init(foo, stdin, stdout, stderr);
el_end(ed);
return 0;
}
gcc -ledit -ltermcap -o test test.c
g++ -ledit -ltermcap -o test test.c
/var/tmp//ccAVIwg7.o: In function `main':
/var/tmp//ccAVIwg7.o(.text+0x28): undefined reference to `el_init(char const*,
__sFILE*, __sFILE*, __sFILE*)'
/var/tmp//ccAVIwg7.o(.text+0x39): undefined reference to `el_end(editline*)'
What did I miss?
Some lectures in C++ classroom. Hint: extern C
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nscd for freebsd
Michael Bushkov wrote: Good day! Can anyone tell me if there is an implementation of nscd for FreeBSD? If there is no, who's currently working on it? You can use bind in caching only mode. A far suprerior solution to the problem at hand. So there is no need for takoje malenkoje gawno as nscd is under Linux. Michael A. Bushkov Computer Center of Rostov State University mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nscd for freebsd
Jan Grant wrote: On Thu, 19 Jun 2003, Marcin Dalecki wrote: Michael Bushkov wrote: Good day! Can anyone tell me if there is an implementation of nscd for FreeBSD? If there is no, who's currently working on it? You can use bind in caching only mode. A far suprerior solution to the problem at hand. So there is no need for takoje malenkoje gawno as nscd is under Linux. Recent discussions on -arch surprisingly managed to avoid the knee-jerk reactions due to other nscd _implementations_ while discussing the need to make /bin dynamically loaded to support NSS co. The alternative (lookupd) approach was raised and seemed to find favour, but I don't know if that tactic has been adopted. FWIW I think it makes a lot of sense. Never mind I was just still under the impression of the nscd from the glibc package. It's making for example mozilla mourn for ages when you misstype an URL... Even for the common case of APACHE log analysis it's unusable, becouse quite commonly it will just overload the system bejoind hope... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Retrieving disk geometry
Andrew wrote: Hi, Under FreeBSD 4.x the ioctl DIOCGDINFO could be used to retrieve the number of cylinders, heads and sectors of a drive. This could be called on /dev/ad0 for example. Under FreeBSD 5 it seems to produce Inappropriate ioctl for device unless you call it on an individual partition (/dev/ad0s1a for example). Is there a way around this? No. Becouse there is in fact no such thing like a geometry on modern ATA drives. There is just a quigmare of values which serve only one single purpose - satisfying rotten code in stinking BIOS. Not more not less. (Modern is here on the scale of about 8 or even more years.) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hi!Dear FreeBSD!
Kreiser Kirov wrote: Hello,Dear FreeBSD! My name is Gleb. I wrote to you from Ukraine(this country is situated in Europe,near Russia). Now you are explaning where the Ukraina is. Next time you will tell us where childs are comming from?! I live in Kiev -the capital of Ukraine. I'm a student of National Politecnical University of Ukraine . I'm very sorry for my english,I know it only for reading some handbooks and man pages. In my computer class there are several mashins with FreeBSD installed for teaching students. But I don't want only work with FreeBSD.I want help to develop it's kernel,write programs,drivers. Please help find more doc's about architecture of it's kernel,how it works, kernel structs and functions. I had already read developers-handbook,but it is to hard for me to write something with this book.I know C and Assembler and good in writing applications. Help me join some simple project,I would work hardly!Thank you very much! You could go hunt for the russian translation of the design of the UNIX operating system. It is freely available on the net as a bunch of plain text files. -- Marcin Dalecki To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Synaptics touchpad extendid support.
Rahul Siddharthan wrote: Marcin Dalecki wrote: Here is my first cut at support for the Synaptics touchpads, which are commonly used on notebooks. Contrary to the default Windows installation mode those devices come up at boot, this is enabling full support for all buttons present on the device and works nicely with moused together. I just tried it. Couple of issues: 1. The speed of the pointer on the screen is way faster now. I corrected that with some XF86Config options. Yes that was intentional, since there are two ways to scale the speed, namely moused and XFree. However the speed you can see is already scaled down by an significant amount anyway. Unfortunately the current sysmouse dosn't understand a witt about absolute mouse coordinates as far as I understand the code... 2. The pad has 4 buttons; left and right work as before. In between, there are a small up and down button. Now the up button acts as the middle button (button 3?) -- ie I can paste with it. The down button still does nothing. I tried playing with the moused parameters and the XF86Config ZAxisMapping settings, to no avail. Well for certain the down button does something in esp. it is posting button 4 events. Watch out xev please - you should see it there. Having a middle button was the reaon per se I did this hack in first place, so this choice of numbering is likely here to stay. 3. Earlier, tapping on the touchpad would emulate a left click. It no longer does anything (not sure whether that's good or bad). Yes this kind of functionality is still not there, since it would involve quite a lot of code, which I didn't find apriopriate to place in kernel space. What I'd like is to emulate 3 buttons with simultaneous left-right clicking, as before; have the up button behave like scrolling a mousewheel up; and have the down button behave like scrolling a mousewheel down. I thought the Option ZAxisMapping 4 5 Option Buttons 5? in XF86Config, and moused -m 4=3 -m 5=4 would do it. But no luck (though the above moused options do stop the up button from acting like a middle button). moused -m 4=2 -m 5=4 should do it. left is 1 upis 2 right is 3 down is 4 Any ideas, anyone? Yes. The next cut should define a custom SYNAPTICS mouse protocol and move the whole logics out of the kernel to moused. There it should be possible to implement all the extendid features one desires without too much hassle. And without in esp. frequent reboots due to kernel crashing :-). Thanks I'm glad this thingee works not just for my own hardware. Would you dare to report the firmware version on your system. Rahul -- Marcin Dalecki To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Synaptics touchpad extendid support.
Rahul Siddharthan wrote: Marcin Dalecki wrote: Here is my first cut at support for the Synaptics touchpads, 2. The pad has 4 buttons; left and right work as before. In between, there are a small up and down button. Now the up button acts as the middle button (button 3?) -- ie I can paste with it. The down button still does nothing. Well for certain the down button does something in esp. it is posting button 4 events. Watch out xev please - you should see it there. Actually, I don't. If I run moused without button options, ie moused -t auto -d /dev/psm0 I see the up button but not the down button. If I run either moused -t auto -d /dev/psm0 -3 or moused -t auto -d /dev/psm0 -m 4=2 -m 5=4 I see neither the up button nor the down button in xev. Please take a look at your dmesg. Here is what I get reported: Synaptics Touchpad: model: 1 firmware ver.: 4.6 rot180: Yes portrait: No sensor: 18 hardware: 47 newABS: Yes capPen: No simpleCmd: Yes geometry: 1 capExtended:Yes capSleep: Yes capFourButtons: Yes capMultiFinger: Yes capPalmDetect: Yes psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Synaptics TouchPad, device ID 0 orm0: Option ROM at iomem 0xc-0xcbfff on isa0 What I'd like is to emulate 3 buttons with simultaneous left-right clicking, as before; have the up button behave like scrolling a mousewheel up; and have the down button behave like scrolling a mousewheel down. I thought the Option ZAxisMapping 4 5 Option Buttons 5? Yes, that was there. in XF86Config, and moused -m 4=3 -m 5=4 would do it. But no luck (though the above moused options do stop the up button from acting like a middle button). moused -m 4=2 -m 5=4 should do it. No luck, see above. Perhaps my hardware isn't a Synaptics touchpad? (although it gets detected as one with your patch). It's a Compaq Presario 1200 around a year old. This is very unlikely. Becouse in case it wouldn't be a synaptics would make it very very unlikely to do anything at all after the detection :-). And you get at the middle button. If you like you could please try to enable the following: #if 0 -log(LOG_DEBUG, psmintr: %02x %02x %02x %02x %02x %02x\n, - sc-ipacket[0], sc-ipacket[1], sc-ipacket[2], - sc-ipacket[3], sc-ipacket[4], sc-ipacket[5]); + log(LOG_DEBUG, psmintr: %02x %02x %02x %02x %02x %02x\n, + sc-ipacket[0], sc-ipacket[1], sc-ipacket[2], + sc-ipacket[3], sc-ipacket[4], sc-ipacket[5]); #endif debugging code in the psm.c driver code to see whatever there is some kind of button reporting at all if you press the down button. And I would recommand that you take a look at the documentation at www.synaptics.com. Yes they actually provide *full documentation* on the web! There are minor differences in the packet format for older firmware revisions as well. So plase compare your dmesg with what I have reported above. Have fun! -- Marcin Dalecki To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Synaptics touchpad extendid support.
Here is my first cut at support for the Synaptics touchpads, which
are commonly used on notebooks. Contrary to the default Windows installation mode
those devices come up at boot, this is enabling full support for all buttons
present on the device and works nicely with moused together.
Have fun!
--
Marcin Dalecki
diff -urN src-old/sys/isa/psm.c src/sys/isa/psm.c
--- src-old/sys/isa/psm.c Tue Dec 31 00:35:19 2002
+++ src/sys/isa/psm.c Tue Dec 31 01:05:35 2002
@@ -277,6 +277,7 @@
static probefunc_t enable_4dplus;
static probefunc_t enable_mmanplus;
static probefunc_t enable_versapad;
+static probefunc_t enable_synaptics;
static int tame_mouse(struct psm_softc *, mousestatus_t *, unsigned char *);
static struct {
@@ -309,6 +310,8 @@
0x80, MOUSE_PS2_PACKETSIZE, enable_kmouse, },
{ MOUSE_MODEL_VERSAPAD,/* Interlink electronics VersaPad */
0xe8, MOUSE_PS2VERSA_PACKETSIZE, enable_versapad, },
+{ MOUSE_MODEL_SYNAPTICS, /* Synaptics TouchPad */
+ 0xc0, MOUSE_PS2SYNAP_PACKETSIZE, enable_synaptics, },
{ MOUSE_MODEL_GENERIC,
0xc0, MOUSE_PS2_PACKETSIZE, NULL, },
};
@@ -570,6 +573,7 @@
{ MOUSE_MODEL_EXPLORER,IntelliMouse Explorer },
{ MOUSE_MODEL_4D, 4D Mouse },
{ MOUSE_MODEL_4DPLUS, 4D+ Mouse },
+ { MOUSE_MODEL_SYNAPTICS,Synaptics TouchPad },
{ MOUSE_MODEL_GENERIC, Generic PS/2 mouse },
{ MOUSE_MODEL_UNKNOWN, NULL },
};
@@ -1964,7 +1968,7 @@
* the table to turn PS/2 mouse button bits (MOUSE_PS2_BUTTON?DOWN)
* into `mousestatus' button bits (MOUSE_BUTTON?DOWN).
*/
-static int butmap[8] = {
+static const int butmap[8] = {
0,
MOUSE_BUTTON1DOWN,
MOUSE_BUTTON3DOWN,
@@ -1974,7 +1978,7 @@
MOUSE_BUTTON2DOWN | MOUSE_BUTTON3DOWN,
MOUSE_BUTTON1DOWN | MOUSE_BUTTON2DOWN | MOUSE_BUTTON3DOWN
};
-static int butmap_versapad[8] = {
+static const int butmap_versapad[8] = {
0,
MOUSE_BUTTON3DOWN,
0,
@@ -1987,18 +1991,18 @@
register struct psm_softc *sc = arg;
mousestatus_t ms;
struct timeval tv;
-int x, y, z;
+int x, y, z, w;
int c;
int l;
int x0, y0;
/* read until there is nothing to read */
while((c = read_aux_data_no_wait(sc-kbdc)) != -1) {
-
+
/* discard the byte if the device is not open */
if ((sc-state PSM_OPEN) == 0)
continue;
-
+
getmicrouptime(tv);
if ((sc-inputbytes 0) timevalcmp(tv, sc-inputtimeout, )) {
log(LOG_DEBUG, psmintr: delay too long; resetting byte count\n);
@@ -2014,9 +2018,9 @@
continue;
#if 0
-log(LOG_DEBUG, psmintr: %02x %02x %02x %02x %02x %02x\n,
- sc-ipacket[0], sc-ipacket[1], sc-ipacket[2],
- sc-ipacket[3], sc-ipacket[4], sc-ipacket[5]);
+ log(LOG_DEBUG, psmintr: %02x %02x %02x %02x %02x %02x\n,
+ sc-ipacket[0], sc-ipacket[1], sc-ipacket[2],
+ sc-ipacket[3], sc-ipacket[4], sc-ipacket[5]);
#endif
c = sc-ipacket[0];
@@ -2320,6 +2324,80 @@
}
break;
+ case MOUSE_MODEL_SYNAPTICS:
+ /* TouchPad PS/2 absolute mode message format
+*
+* Bits:7 6 5 4 3 2 1 0 (LSB)
+*
+* ipacket[0]: 1 0 W3 W2 0 W1 R L
+* ipacket[1]: Yb Ya Y9 Y8 Xb Xa X9 X8
+* ipacket[2]: Z7 Z6 Z5 Z4 Z3 Z2 Z1 Z0
+* ipacket[3]: 1 1 Yc Xc 0 W0 D U
+* ipacket[4]: X7 X6 X5 X4 X3 X2 X1 X0
+* ipacket[5]: Y7 Y6 Y5 Y4 Y3 Y2 Y1 Y0
+*
+* Legend:
+* L: left physical mouse button
+* R: right physical mouse button
+* D: down button
+* U: up button
+* W: wrist value
+* X: x position
+* Y: x position
+* Z: pressure
+*
+* Absolute reportable limits:0 - 6143.
+* Typical bezel limites: 1472 - 5472.
+* Typical edge marings: 1632 - 5312.
+*/
+
+ /* Sanity check for out of sync packets. */
+ if ((sc-ipacket[0] 0xc8) != 0x80 || (sc-ipacket[3] 0xc8) != 0xc0)
+ continue;
+
+ ms.button = 0;
+ x = y = x0 = y0 = 0;
+
+ /* pressure */
+ z = sc-ipacket[2];
+ w = ((sc-ipacket[0] 0x30) 2) |
+ ((sc-ipacket[0] 0x04) 1) |
+ ((sc-ipacket[3] 0x04) 2);
+
+ ms.button = 0;
+ if (sc-ipacket[0] 0x01)
+ ms.button |= MOUSE_BUTTON1DOWN;
+ if (sc-ipacket[0] 0x02)
+ ms.button |= MOUSE_BUTTON3DOWN;
+ if ((sc-ipacket[3] 0x01) !(sc
Re: Framebuffer howto?
Hiten Pandya wrote: --- Pedro F. Giffuni [EMAIL PROTECTED] wrote: Actually I suggested on private email to use GGI. GGI can work on top of VGL or Linux's framebuffer, and when KGI becomes available it will work fine. Hmm, someone said earlier on in this thread, that FreeBSD does not have a framebuffer device; if so: 1) What is the FB_INSTALL_CDEV kernel option for? 2) What is the purpose of sys/fbio.h? Clarification will be appreciated. Cheers. Well as far as I can see the text console is considered as kind of a frame buffer. Surely not what quite what you are looking for. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
PS/2 Mice device - synaptics touch pad.
Hello everybody. Well currently right now I'm trying to make all the buttons (4 of them) of my synaptics touch pad to work under BSD. Despite beeing embedid in a notebook, this device is physically attached to the PS/2 port. It knows about two operating modes - relative, aka normal PS/2 mouse protocoll, basically just usable for windows installs, - absolute, which gives full access to all buttons and not just two as well as absolute coordinates of the pressing point on the pad. I have already an XFree86 input device driver for it, which is working fine if run under Linux. Under FreeBSD the driver doesn't work as expected. A little bit of digging turned up that writing to the /dev/psm0 device fails. But I certainly *have* to write to the device to put it in to absolute mode. Looking further I discovered that the writing method is filled with a global nowrite() function. What should I do about it: 1. Just provide the trivial psmwrite() augmenting kernel level function, thus presering the higher level driver for XFree? 2. Move everything in to the kernel space?! (The driver isn't exactly small due to many features like border detection and so on...) -- Marcin Dalecki To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: PS/2 Mice device - synaptics touch pad.
Daniel O'Connor wrote: On Sat, 2002-11-30 at 02:54, Marcin Dalecki wrote: Looking further I discovered that the writing method is filled with a global nowrite() function. What should I do about it: 1. Just provide the trivial psmwrite() augmenting kernel level function, thus presering the higher level driver for XFree? 2. Move everything in to the kernel space?! (The driver isn't exactly small due to many features like border detection and so on...) I think number 1 is probably best, IMHO it should go into moused, but given the way the moused code is written that is pretty tough :( OK. I'm going for nr 1. augmented with moused. This will have the advantage of making it globally abstracted on the system no matter whatever XFree86 or not. Also if you follow step 1 you will have to provide some way of telling the psm device not to validate the input stream, because otherwise it will barf on the absolute packets. (I have done a little tinkering, but the moused/psm code makes my head explode) Yes the psm code is a bit rotten. But it's nothing in comparision to stuff I got used too under Linux ;-). I have looked at the 2 other BSE systems as well. OpenBSD has a bit of nice code separation and reordering but less functionality there. Where NetBSD did hide the PS/2 mice code I couldn't find out. Right now I have augmented the current psm.c with the device detection code for Synaptics touch pads: one sends a magic command sequence and gets a magic reply containing model info and stuff. Thus the tinkering in psm.c will certainly not affect any other PS/2 device type. psm0: current command byte:0045 HERE WE GO psm0: found Synaptics touch pad psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Synaptics touch pad, device ID 0-00, 2 buttons psm0: config:, flags:, packet size:3 psm0: syncmask:c0, syncbits:00 orm0: Option ROM at iomem 0xc-0xcbfff on isa0 Now it's time to elaborate on device type printing and to write a psmwrite for this type of devices... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
System crash 4 times/hour.
Hello ! I'm using old dual pentium Pro 200MHz box with 256 MB RAM. Instaled system is FreeBSd 4.6-STABLE. Every time after 15-30 min since boot up system showing something like: -- cut here -- Fatal trap 12: page fault while in kernel mode mp_lock = 0103; cpuid = 1; lapic.id = fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0278acd stack pointer = 0x10:0xcf547af4 frame pointer = 0x10:0xcf547afc code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam - SMP: XXX trap number = 12 panic: page fault bla bla .. Uptime: 13m59s cpu_reset called on cpu#1 cpu_reset: Stopping orher CPUs -- cut here -- Any sugestions ? Best regards... Marcin Jurczuk - [EMAIL PROTECTED] Network/System Administartor. Bialystok Cable Television. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: fbsdboot.exe can't load elf kernels (flash cards off topic)
On Wed, 12 Jan 2000, Warner Losh wrote: The linear flash cards don't have an ata interface, so PAO and soon -current won't recognize them. They don't have and we don't need it. Once can easily read them with low-level pccardc interface. In general, flash cards are not meant to be written too often, so I belive we won't put a real filesystem on them. Just a kernel and mfsroot image perhaps? [Added -hackers and please, remove -stable] -- Marcin Cieslak // [EMAIL PROTECTED] - SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
syscons: SC_MOUSE_CHAR value rationale
Is there any _particular_ reason why this is #define'd to (0xd0) in /sys/dev/syscons/syscons.c? Nearly everyone who wants to set up their national locale needs to recompile the kernel, since some important characters are hidden under mouse cursor. I sure that at least these are affected: (from /usr/share/syscons/font) iso-8859-2-8x16.fnt iso02-8x8.fnt koi8-r-8x8.fnt iso02-8x14.fnt koi8-r-8x14.fnt koi8-rb-8x16.fnt iso02-8x16.fnt koi8-r-8x16.fnt koi8-rc-8x16.fnt Will changing it to 0x08 break anything? -- Marcin Cieslak // [EMAIL PROTECTED] - SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
