Re: Limiting closed port RST response from XXX to 200...
At 09:48 PM 10/17/2005 -0400, Mike Silbersack wrote: | > Hi, | > | > On a server I'm benchmark testing, via local host, I'm getting Limiting | > closed | > port RST response from to 200 packets/sec on the console when I'm | > running a | > lot of local connections very quickly all at once (about 7500 per second). | > I've | > added the following: | > | > net.inet.tcp.log_in_vain: 0 | > net.inet.udp.log_in_vain: 0 | > | > but still does it. Is there any way to disable it short of installing | > ipf? I'd | > like to see what the theoretical limit of the machine is without it | > perhaps | > limiting connections in some manner. | > | > Thanks! | > | > Ray | | Er, if you're seeing those messages, your benchmark is going very awry! | | The kernel is telling you that 7500 junk packets per second are coming in, | but that it has chosen to send RST packets in response to only 200 of | them. What you should be asking is - why are 7500 junk packets per second | coming into the system? This could be due to a flaw in how your benchmark | is setup (if you're trying to connect to a port that has no listening | service or DNS lookups to a nonexistent DNS server?), or it could be some | kernel bug you've uncovered. If it's the latter, then I would be very | interested in helping you get it fixed. | | There is a sysctl for disabling the reset rate limiting, but I would | suggest that you track down the source of the problem before resorting to | disabling the feature. | | Mike "Silby" Silbersack | | Hi Mike, Thanks for the pointers. I will check some of those areas you mention. Since I just threw this machine together real fast, I may have some DNS off the mark or something. BTW, the benchmark I'm using is 'ab' in apache/bin. I'm running it with -c 50 and -n 1000. Seems to only cause the RST thing on small files. Thanks again for the tips. Ray ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: system password's file --failed
On Tue, 18 Oct 2005 07:17:54 -0500, <[EMAIL PROTECTED]> wrote: Hi all, I failed this steps. FreeBSD cannot recognized my username. I will try it again. Have anybody another solution ?? Did you read link that I have given? Cheers, Mezz Thanks before. regards. Thanks for you all, I will do this step. regards. Hi, I would suggest you to try the below and make sure this works 1 ) Install a new freebsd server 2 ) create a user on your linux machine say with username freebsd and some password 3 ) now copy the data in your /etc/passwd file of linux machine to freebsd machine 4 ) Also copy the /etc/shadow file to freebsd server and renmae it as /etc/master.passwd 5 ) Also copy /etc/groups 6 ) Now try to login to freebsd machine with the new user created on the linux machine. Note : Please create a copy of the original file on freebsd machine before you change the real file If the test is successful. I suppose you can migrate from linux to freebsd with all the users and their passwords. Also while coping the file make sure that the default enteries are there. That just transfer the user details and not the system user details On 10/14/05, Jiawei Ye <[EMAIL PROTECTED]> wrote: On 10/14/05, Simon Roberts <[EMAIL PROTECTED]> wrote: > Try /etc/passwd and /etc/shadow > User id and basic stuff in passwd, the encrypted passwords in shadow. I > don't know if the encryption algorithms are compatible between linux > and bsd or not. > > hth > Simon Make sure you don't have >16 chars username before migrating. FreeBSD doesn't support really long usernames. Jiawei -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [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: system password's file --failed
Hi all, I failed this steps. FreeBSD cannot recognized my username. I will try it again. Have anybody another solution ?? Thanks before. regards. > Thanks for you all, > I will do this step. > > regards. > >> Hi, >> >> I would suggest you to try the below and make sure this >> works >> >> 1 ) Install a new freebsd server >> 2 ) create a user on your linux machine say with >> username >> freebsd and some >> password >> 3 ) now copy the data in your /etc/passwd file of linux >> machine to freebsd >> machine >> 4 ) Also copy the /etc/shadow file to freebsd server and >> renmae it as >> /etc/master.passwd >> 5 ) Also copy /etc/groups >> 6 ) Now try to login to freebsd machine with the new >> user >> created on the >> linux machine. >> >> Note : Please create a copy of the original file on >> freebsd machine before >> you change the real file >> >> If the test is successful. I suppose you can migrate >> from >> linux to freebsd >> with all the users and their passwords. >> >> Also while coping the file make sure that the default >> enteries are there. >> That just transfer the user details and not the system >> user details >> >> >> On 10/14/05, Jiawei Ye <[EMAIL PROTECTED]> wrote: >>> >>> On 10/14/05, Simon Roberts <[EMAIL PROTECTED]> >>> wrote: >>> > Try /etc/passwd and /etc/shadow >>> > User id and basic stuff in passwd, the encrypted >>> passwords in shadow. I >>> > don't know if the encryption algorithms are >>> compatible >>> between linux >>> > and bsd or not. >>> > >>> > hth >>> > Simon >>> Make sure you don't have >16 chars username before >>> migrating. FreeBSD >>> doesn't support really long usernames. >>> >>> Jiawei >>> -- >>> "Without the userland, the kernel is useless." >>> --inspired by The Tao of Programming >>> ___ >>> 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: nvi for serious hacking
At 1:25 PM -0600 10/17/05, M. Warner Losh wrote: In message: <[EMAIL PROTECTED]> Gary Kline <[EMAIL PROTECTED]> writes: : vi was the first screen/cursor-based editor in computer : history. Are you sure about this? I was using screen oriented editors over a 1200 baud dialup line in 1977 on a PDP-11 running RSTS/E on a Behive BH-100. Seems like one year from vi to being deployed at Berkeley to a completely different video editor being deployed on a completely different os in the schools that I used this in seems fast. So I did some digging. vi started in about 1976[1] as a project that grew out of the frustration taht a 200 line Pascal program was too big for the system to handle. These are based on recollections of Bill Joy in 1984. It appears that starting in 1972 Carl Mikkelson added screen editing features to TECO[2]. In 1974 Richard Stallman added macros to TECO. I don't know if Carl's work was the first, but it pre-dates the vi efforts. Other editors may have influanced Carl. Who knows. I arrived in RPI in 1975. In December of 1975, we were just trying out a mainframe timesharing system called "Michigan Terminal System", or "MTS", from the university of Michigan. The editor was called 'edit', and was a Command Language Subsystem (CLS) in MTS. That meant it had a command language of it's one. One of the sub-commands in edit was 'visual', for visual mode. It only worked on IBM 3270-style terminals, but it was screen-based and cursor-based. The editor would put a bunch of fields up on the screen, some of which you could modify and some you couldn't. The text of your file was in the fields you could type over. Once you finished with whatever changes you wanted to make on that screen, you would hit one of 15 or 20 interrupt-generating keys on the 3270 terminal (12 of which were "programmable function keys", in a keypad with a layout similar to the numeric keypad on current keyboards). The 3270 terminal would then tell the mainframe which fields on the screen had been modified, and what those modifications were. The mainframe would update the file based on that info. I *THINK* the guy who wrote that was ... Bill Joy -- as a student at UofM. I can't find any confirmation of that, though. The closest I can come is the web page at http://www.jefallbright.net/node/3218 , which is an article written by Bill. In it he mentions: By 1967, MTS was up and running on the newly arrived 360/67, supporting 30 to 40 simultaneous users. ... By the time I arrived as an undergraduate at the University of Michigan in 1971, MTS and Merit were successful and stable systems. By that point, a multiprocessor system running MTS could support a hundred simultaneous interactive users, ... But he doesn't happen to mention anything about editors or visual mode. My memory of his connection to MTS's visual-mode could very well be wrong, since I didn't come along until after visual-mode already existed. I just remember his name coming up in later discussions. However, I also think there was someone named Victor who was part of the story of 3270 support in MTS. And Dave Twyver at University of British Columbia was the guy who wrote the 3270 DSR (Device Support Routine), as mentioned on the page at: http://mtswiki.westwood-tech.com/mtswiki-index.php/Dave%20Twyver In any case, I *am* sure that MTS had a visual editor in December of 1975, which puts before vi if vi started in 1976. Unfortunately, all of the documentation of MTS lived in the EBCDIC world, and pretty much disappeared when MTS did (in the late 1990's). -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [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: Limiting closed port RST response from XXX to 200...
> Hi, > > On a server I'm benchmark testing, via local host, I'm getting Limiting > closed > port RST response from to 200 packets/sec on the console when I'm > running a > lot of local connections very quickly all at once (about 7500 per second). > I've > added the following: > > net.inet.tcp.log_in_vain: 0 > net.inet.udp.log_in_vain: 0 > > but still does it. Is there any way to disable it short of installing > ipf? I'd > like to see what the theoretical limit of the machine is without it > perhaps > limiting connections in some manner. > > Thanks! > > Ray Er, if you're seeing those messages, your benchmark is going very awry! The kernel is telling you that 7500 junk packets per second are coming in, but that it has chosen to send RST packets in response to only 200 of them. What you should be asking is - why are 7500 junk packets per second coming into the system? This could be due to a flaw in how your benchmark is setup (if you're trying to connect to a port that has no listening service or DNS lookups to a nonexistent DNS server?), or it could be some kernel bug you've uncovered. If it's the latter, then I would be very interested in helping you get it fixed. There is a sysctl for disabling the reset rate limiting, but I would suggest that you track down the source of the problem before resorting to disabling the feature. Mike "Silby" Silbersack ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: adding new device to base system
On Tue, 18 Oct 2005 02:22, [EMAIL PROTECTED] wrote: > /usr/src/sys/i386/conf/TARTAR ../../conf/files: FreeBSD: must be count, > optional, mandatory or > standard > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. Looks like you broke sys/conf/files somehow. Do a cvs diff on it and post it here. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpHKoT52vmVE.pgp Description: PGP signature
Limiting closed port RST response from XXX to 200...
Hi, On a server I'm benchmark testing, via local host, I'm getting Limiting closed port RST response from to 200 packets/sec on the console when I'm running a lot of local connections very quickly all at once (about 7500 per second). I've added the following: net.inet.tcp.log_in_vain: 0 net.inet.udp.log_in_vain: 0 but still does it. Is there any way to disable it short of installing ipf? I'd like to see what the theoretical limit of the machine is without it perhaps limiting connections in some manner. Thanks! Ray ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvi for serious hacking
Hi, (wondering off on a tangent), re: > I was using screen oriented editors over a > 1200 baud dialup line in 1977 on a PDP-11 running RSTS/E on a Behive... Around this time I think full-screen editors from DEC that took advantage of the VT-52 (and later VT-100) included KED, EDT, and maybe SOS? EDT and KED took good advantage of the alternate keypad, basically the same keypad as on PC keyboards today. Weren't there full-screen editors on PDP-8's before this? Doug Engelbart's NLS demo in 1968 may not qualify as "available", but he demoed full-screen editing with a mouse: http://arstechnica.com/articles/paedia/gui.ars/2 "The demo featured hypertext linking, full-screen document editing, context-sensitive help, networked document collaboration, e-mail, instant messenging, even video conferencing!" NLS ran on a version of UC Berkeley's Genie system, which can be considered an ancestor of Unix (maybe more-so than Multics?) Although early versions of TECO may not have supported direct-cursor addressing, TECO might have played a role in popularizing the notion of full-screen editors. From the wikipedia: "TECO became well-known following a DEC PDP-6 implementation developed at MIT's Project MAC in 1964. This implementation continuously displayed the edited text visually on a CRT screen, and was used as an interactive online editor. This was, however, neither its origin nor its originally intended mode of use. Later versions of TECO were capable of driving full-screen mode on various DEC RS232 video terminals." - bruce ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvi for serious hacking
In message: <[EMAIL PROTECTED]> Gary Kline <[EMAIL PROTECTED]> writes: : vi was the first screen/cursor-based editor in computer : history. Are you sure about this? I was using screen oriented editors over a 1200 baud dialup line in 1977 on a PDP-11 running RSTS/E on a Behive BH-100. Seems like one year from vi to being deployed at Berkeley to a completely different video editor being deployed on a completely different os in the schools that I used this in seems fast. So I did some digging. vi started in about 1976[1] as a project that grew out of the frustration taht a 200 line Pascal program was too big for the system to handle. These are based on recollections of Bill Joy in 1984. It appears that starting in 1972 Carl Mikkelson added screen editing features to TECO[2]. In 1974 Richard Stallman added macros to TECO. I don't know if Carl's work was the first, but it pre-dates the vi efforts. Other editors may have influanced Carl. Who knows. Warner [1] http://www.cs.pdx.edu/~kirkenda/joy84.html [2] http://www.emacswiki.org/cgi-bin/wiki/EmacsHistory ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvi for serious hacking
2005/10/17, Marc Fonvieille <[EMAIL PROTECTED]>: > On Mon, Oct 17, 2005 at 02:46:56AM +0400, Oleg Petrov wrote: > > Hello, FreeBSD people. > > > > First thing to mention is that I'm very experienced Emacs user. I was using > > it > > for 4-5 years or so. But sometime ago i began to feel myself so > > uncomfortable > > with it for some reasons: first, i use many different systems and emacs > > isn't > > default application for FreeBSD or any other *BSD\Linux distribution. > > Second, > > remote machines aren't powerful enough to start Emacs fast. I tried many > > small > > Emacs clones like jed, joe, uemacs and several others i just can't remember. > > But for different reasons i disliked all of them. Later I noticed default > > `nvi' editor, that has some nice features: it comes with FreeBSD by default > > and according to documentation it has powerful editing mechanism. > > > > So, my question goes to all FreeBSD hackers who uses `nvi' as their general > > editor. Is it possible to do serious hacking with it? More accurate: > > > > I'd say "s/nvi/vim" (see http://www.vim.org/) if you want to really do > everything with your Vi. Actually the first thing that I do after minimal installing of new system is to install vim from the ports tree. (in fact, installing cvsup, of course :-) I remember once upon a time someone (david?) made a suggestion that nvi in our tree should be changed to vim-lite(or something.) I'm tend to agree with that.. (Although vim is GPL'd, nvi is in the src/contrib anyway..) Regards, Sangwoo Shim > > Marc > ___ > 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: malloc() in kernel and increasing mbuf and cluster size
2005/10/17, kamal kc <[EMAIL PROTECTED]>: > > > sys/malloc.h has function prototypes for malloc() > > > kern/kern_malloc.c defines the malloc() > > > > > > the malloc() definition is > > > > > > void * > > > malloc(size, type, flags) > > > unsigned long size; > > > struct malloc_type *type; > > > int flags; > > > > > > i understand the size and flags but what shall i > > > do with the malloc_type. > > > > man 9 malloc :-) > > > > i saw the man pages. > > it says to use malloc_type via > > MALLOC_DEFINE(type,shortdesc,longdesc) > MALLOC_DECLARE(type) > > the man pages use M_FOOBUF(where did it come from ??) > in the field type. > > Now how should i code it. > > struct malloc_type mytype; > mytype=MALLOC_DEFINE(.,"mybuffers","mybuffers"); > > what should i put in the type field ?? > > thanks in advance, > kamal malloc type is defined for some kind of statistics/trackings. If you define some specific malloc types for your module/driver etc., you can track the memory usage more accurately. For example, if you do vmstat -m you can see how much memories are used for specific allocations by looking at type field. Regards, Sangwoo Shim > > > > > > > > > __ > Yahoo! Music Unlimited > Access over 1 million songs. Try it free. > http://music.yahoo.com/unlimited/ > ___ > 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]"
adding new device to base system
Hello list, I am trying to add a new directory (NIC) to my base system (FreeBSD5.4) to support an experimental card. But I have this error trying to build the kernel. -- >>> Kernel build for TARTAR started on Mon Oct 17 09:48:55 PDT 2005 -- ===> TARTAR mkdir -p /usr/obj/usr/src/sys -- >>> stage 1: configuring the kernel -- cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/usr/obj/usr/src/i386/legacy/usr/bin:/usr/obj/usr/src/i386/legacy/usr/games:/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj/usr/src/sys/TARTAR /usr/src/sys/i386/conf/TARTAR ../../conf/files: FreeBSD: must be count, optional, mandatory or standard *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I have created /usr/src/sys/dev/tartar and put all it's source code there. in my kernel file I have added: device tartar in /sys/conf/files: dev/tartar/if_tartar.coptional tartar pci Why the error message? Same thing even with GENERIC. Thank you, Jerry ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvi for serious hacking
On Mon, Oct 17, 2005 at 04:49:20PM +0200, Marc Fonvieille wrote: > > I'd say "s/nvi/vim" (see http://www.vim.org/) if you want to really do > everything with your Vi. > Err, sorry for the cross-post :( Marc ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvi for serious hacking
On Mon, Oct 17, 2005 at 02:46:56AM +0400, Oleg Petrov wrote: > Hello, FreeBSD people. > > First thing to mention is that I'm very experienced Emacs user. I was using it > for 4-5 years or so. But sometime ago i began to feel myself so uncomfortable > with it for some reasons: first, i use many different systems and emacs isn't > default application for FreeBSD or any other *BSD\Linux distribution. Second, > remote machines aren't powerful enough to start Emacs fast. I tried many small > Emacs clones like jed, joe, uemacs and several others i just can't remember. > But for different reasons i disliked all of them. Later I noticed default > `nvi' editor, that has some nice features: it comes with FreeBSD by default > and according to documentation it has powerful editing mechanism. > > So, my question goes to all FreeBSD hackers who uses `nvi' as their general > editor. Is it possible to do serious hacking with it? More accurate: > I'd say "s/nvi/vim" (see http://www.vim.org/) if you want to really do everything with your Vi. Marc ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to determine link of umass/da devices
Hi. I need to write some user interface to perform some tasks with USB storage devices. One of the tasks is to show a list of all USB storage connected and all slices/partitions and filesystems in them. With tools like usbdevs and sysctl, I can find out what USB devices are connected, and also what USB drivers handle them (so I can see, for example, that there is a SanDisk Cruzer Micro connected to port 2 in bus 3 and the umass driver under it). I can also find out what da devices there are using camcontrol. However, how can I find out which da device was assigned to which umass/usb device? I see this info in some inconvenient form in dmesg. But I need something easier to handle programmatically to write a program that uses that data. I prefer not to resort to some ugly hack like trying to parse dmesg. Also, I'd be interested if it were possible to have my program informed when devices are connected/disconnected. Can a process ask usbd to send it some signal and somehow provide the details of the event when a device is connected/disconnected? Thanks, -- Tom -- Tom Alsberg - certified insane, complete illiterate. Homepage: http://www.cs.huji.ac.il/~alsbergt/ * An idea is not responsible for the people who believe in it. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: malloc() in kernel and increasing mbuf and cluster size
On Mon, 17 Oct 2005 21:56, kamal kc wrote: > the man pages use M_FOOBUF(where did it come from ??) > in the field type. 'foo' is a generic term for a random variable name. > Now how should i code it. > > struct malloc_type mytype; > mytype=MALLOC_DEFINE(.,"mybuffers","mybuffers"); > > what should i put in the type field ?? Read the man page!! /* sys/something/foo_extern.h */ MALLOC_DECLARE(M_FOOBUF); /* sys/something/foo_main.c */ MALLOC_DEFINE(M_FOOBUF, "foobuffers", "Buffers to foo data into the ether"); /* sys/something/foo_subr.c */ ... MALLOC(buf, struct foo_buf *, sizeof *buf, M_FOOBUF, M_NOWAIT); Read other code, there are plenty of examples in the tree. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpwPfcG0B6N3.pgp Description: PGP signature
Re: malloc() in kernel and increasing mbuf and cluster size
Hi, Kamal On 17.10.2005 04:49:01, kamal kc wrote: > this may be a trivial question for many of you > but i am confused in doing memory allocation in the > kernel. > > sys/malloc.h has function prototypes for malloc() > kern/kern_malloc.c defines the malloc() > > the malloc() definition is > > void * > malloc(size, type, flags) > unsigned long size; > struct malloc_type *type; > int flags; > > i understand the size and flags but what shall i > do with the malloc_type. man 9 malloc :-) -- Nick Strebkov Public key: http://humgat.org/~nick/pubkey.txt fpr: 552C 88D6 895B 6E64 F277 D367 8A70 8132 47F5 C1B6 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvi for serious hacking
On Mon, Oct 17, 2005 at 02:46:56AM +0400, Oleg Petrov wrote: > Hello, FreeBSD people. > > First thing to mention is that I'm very experienced Emacs user. I was using it > for 4-5 years or so. But sometime ago i began to feel myself so uncomfortable > with it for some reasons: first, i use many different systems and emacs isn't > default application for FreeBSD or any other *BSD\Linux distribution. Second, > remote machines aren't powerful enough to start Emacs fast. I tried many small > Emacs clones like jed, joe, uemacs and several others i just can't remember. > But for different reasons i disliked all of them. Later I noticed default > `nvi' editor, that has some nice features: it comes with FreeBSD by default > and according to documentation it has powerful editing mechanism. > > So, my question goes to all FreeBSD hackers who uses `nvi' as their general > editor. Is it possible to do serious hacking with it? More accurate: > > * What programming features it support? (Does it have something like etags? > Does it have interface to gdb? And such other things..) > > * Is it possible to use it comfortable with Dvorak layout? (I noticed some > bindings that relies on keys arrangement) > > * How to setup it to standard FreeBSD C code indentation? And don't use > tabs as well. > > It's hard choice for me to switch old good Emacs to something new, so please > give me your opinions. > > I'm not subscribed to list, so please CC me. > vi was the first screen/cursor-based editor in computer history. Written by Bill Joy when he was in his early 20's. I've been using vi almost since Bill released his first draft; my fingers know it by default. And even after almost 30years there are still things I don't know. Nutshell, I've hacked hundreds of thousands of line using vi; millions of words of prose. I've used *tags, debuggers, and other tools with it. Have tried *emacs; just can't get the hang of it. With tools like [n]vi and ctags, plus a debugger you've got your own IDE. Since you've learned emacs, you'll learn vi in a flash. gary kline -- Gary Kline [EMAIL PROTECTED] www.thought.org Public service Unix ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nvi for serious hacking
Hello, FreeBSD people. First thing to mention is that I'm very experienced Emacs user. I was using it for 4-5 years or so. But sometime ago i began to feel myself so uncomfortable with it for some reasons: first, i use many different systems and emacs isn't default application for FreeBSD or any other *BSD\Linux distribution. Second, remote machines aren't powerful enough to start Emacs fast. I tried many small Emacs clones like jed, joe, uemacs and several others i just can't remember. But for different reasons i disliked all of them. Later I noticed default `nvi' editor, that has some nice features: it comes with FreeBSD by default and according to documentation it has powerful editing mechanism. So, my question goes to all FreeBSD hackers who uses `nvi' as their general editor. Is it possible to do serious hacking with it? More accurate: * What programming features it support? (Does it have something like etags? Does it have interface to gdb? And such other things..) * Is it possible to use it comfortable with Dvorak layout? (I noticed some bindings that relies on keys arrangement) * How to setup it to standard FreeBSD C code indentation? And don't use tabs as well. It's hard choice for me to switch old good Emacs to something new, so please give me your opinions. I'm not subscribed to list, so please CC me. Thanks! ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: malloc() in kernel and increasing mbuf and cluster size
On Mon, 17 Oct 2005 21:19, kamal kc wrote: > void * > malloc(size, type, flags) > unsigned long size; > struct malloc_type *type; > int flags; > > i understand the size and flags but what shall i > do with the malloc_type. man 9 malloc It is used to do basic sanity checking and for statistics. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgp1THOobuOBO.pgp Description: PGP signature
Re: malloc() in kernel and increasing mbuf and cluster size
> > sys/malloc.h has function prototypes for malloc() > > kern/kern_malloc.c defines the malloc() > > > > the malloc() definition is > > > > void * > > malloc(size, type, flags) > > unsigned long size; > > struct malloc_type *type; > > int flags; > > > > i understand the size and flags but what shall i > > do with the malloc_type. > > man 9 malloc :-) > i saw the man pages. it says to use malloc_type via MALLOC_DEFINE(type,shortdesc,longdesc) MALLOC_DECLARE(type) the man pages use M_FOOBUF(where did it come from ??) in the field type. Now how should i code it. struct malloc_type mytype; mytype=MALLOC_DEFINE(.,"mybuffers","mybuffers"); what should i put in the type field ?? thanks in advance, kamal __ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
malloc() in kernel and increasing mbuf and cluster size
this may be a trivial question for many of you but i am confused in doing memory allocation in the kernel. sys/malloc.h has function prototypes for malloc() kern/kern_malloc.c defines the malloc() the malloc() definition is void * malloc(size, type, flags) unsigned long size; struct malloc_type *type; int flags; i understand the size and flags but what shall i do with the malloc_type. suppose i want to allocate 1024 bytes then how should i call the malloc ? i set --> size=1024 flags=M_WAITOK type= (i don't know what/how to initialize the type) Next thing is that i want to make the kernel process network packets very fast. i think of increasing the mbuf and cluster size. i want to if there will be any effect on increasing the mbuf and cluster size. what would be an appropriate size of mbuf and cluster if I use i. 512 MB RAM iI. 1024 MB RAM which parts of the kernel will be affected by changing the mbuf and cluster size ? i think somebody maybe able to help me. thanks folks. kamal __ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
