Re: NEWBUS: multiple calls needed?

In message <[EMAIL PROTECTED]> Richard Hodges writes: : So of course, it is tempting to wonder whether it is really neccessary : to allocate three newbus entities for them. Yes, it is. Other mobo's bios may allocate thing differently and it might not wind up being contiguous. I had the pleas

modems, rp driver, stuck processes...

I've been trying to figure this out for some time now... I have several systems that have 8- and 16-port RocketPort boards in them, connected to banks of modems. (ISA cards on all of them - I just got a PCI RP board, but haven't installed it anywhere yet.) These modems make a lot of outgoing c

Re: regular coding?

* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [010131 19:30] wrote: > Hello everyone! > > First off, I would like to thank everyone on this list for there help > especially in response to my 'kernel hacking' question. Here is my question: > I am a beggining C programmer, I have written a simple calcu

Re: Moving to KLM's

ok, what would be the minimal kernel that i can compile :), or is there a document somewhere that says that info? We have LINT, should we make something called MIN for minimal kernel needed to boot? Thanks, - Daryl Chance | And which parallel universe did ValueData, LLC | YOU crawl out

fdescfs oddities

Hi, I run a 4.2-STABLE machine, world done this morning. I had some troubles with fdescfs. Reading the fdesc(5) manual page, I have to mount the fdescfs like I would mount procfs. But if I compile my kernel with options FDESC or if I load the fdesc.ko kernel module, I have access to /dev/

ncurses tic(1)

Is there a way to build tic(1) from the ncurses distribution in src/contrib/ncurses? I know there is one in the ncurses port, but for some reason it is not built in the base system. How do I go about enabling it in the build process? There are also several other utilities in src/contrib/ncurses

Re: removing setgid kmem from top, collecting per-device swap stats

> On Thu, 1 Feb 2001 17:11:35 + > Tony Finch <[EMAIL PROTECTED]> said: dot> Thomas Moestl <[EMAIL PROTECTED]> wrote: > >Most kmem_read calls are easy to replace (the variables are already >exported as sysctls), the only exception is nextproc (for which I might >add a sysctl, or just

Re: Atomic bit operations

On 01-Feb-01 Julian Elischer wrote: > John Baldwin wrote: >> >> On 31-Jan-01 Matthew Emmerton wrote: >> > Hi all, >> > >> > I've taken a look around for an implementation of atomic bit operations in >> > FreeBSD (similar to Linux' asm/bitopt.h, which include clear_bit() and >> > test_and_set_bit

Re: removing setgid kmem from top, collecting per-device swap stats

On Fri, Feb 02, 2001 at 02:28:29AM +0900, Hajimu UMEMOTO wrote: > > On Thu, 1 Feb 2001 17:11:35 + > > Tony Finch <[EMAIL PROTECTED]> said: > > dot> Thomas Moestl <[EMAIL PROTECTED]> wrote: > > > >Most kmem_read calls are easy to replace (the variables are already > >exported as sysct

NEED HELP: fiber card

has anyone had any success getting the FDDILINK 3com 3c805 pci fiber card to work with freebsd 4.2R or know anyone that could help develop a driver for this ? Please contact me [EMAIL PROTECTED] Nick Meverden To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freeb

a mtools wrapper (slight better control)

Hi, Here is my problem: I need to enable a group of workstations running XDM accesses to local disk floppies with FAT16/32 FS(es). Therefore, I considered ports/emulators/mtools. All users will have access to the floppy drives. All workstations will permit remote

Re: Atomic bit operations

John Baldwin wrote: > > > The current implementation for it can be found at > http://www.FreeBSD.org/~jhb/patches/refcount.patch. It's all done with simple > atomic operations right now. > what I do at the moment is: do { v = node->nd_

swap_pager: indefinite wait buffer: device: #ad/0x20001, blkno: 288,size: 4096

hi, there! what does the following error message mean: swap_pager: indefinite wait buffer: device: #ad/0x20001, blkno: 288, size: 4096 it happens when burncd is fixating disk /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message

Re: swap_pager: indefinite wait buffer: device: #ad/0x20001, blkno: 288, size: 4096

> In message , Max Khon writes > : > >what does the following error message mean: > >swap_pager: indefinite wait buffer: device: #ad/0x20001, blkno: 288, > >size: 4096 > > >it happens when burncd is fixating disk > > My intuitive guess is that

Re: Atomic bit operations

On 01-Feb-01 Julian Elischer wrote: > John Baldwin wrote: >> > >> >> The current implementation for it can be found at >> http://www.FreeBSD.org/~jhb/patches/refcount.patch. It's all done with >> simple >> atomic operations right now. >> > > what I do at the moment is: >

Re: FreeBSD specific strftime(3) format specifiers

On Sun, 28 Jan 2001, Alex Kapranoff wrote: > Hi to all. > gcc supports strftime format string checking and issues a warning when > it encounters some unknown format specifier. FreeBSD strftime has > several additional format chars which gcc knows nothing about. > > This can easily be seen when c

Re: Suboptimal mmap of devices on i86

On Mon, 29 Jan 2001, John Baldwin wrote: > Then only rename it in 4.x We can do an API change for 5.0. We'll be > renaming syscall2() back to syscall() in 5.0 for example. We don't > want to end up with syscall47() someday in FreeBSD 67.2. :-P And what happens to apps using the previous syscal

Re: fdescfs oddities

On Thursday, February 01, 2001, Maxime Henrion wrote: > I run a 4.2-STABLE machine, world done this morning. I had some troubles with > fdescfs. Reading the fdesc(5) manual page, I have to mount the fdescfs like I > would mount procfs. But if I compile my kernel with options FDESC or if I load > t

Re: removing setgid kmem from top, collecting per-device swap stats

Thomas Moestl <[EMAIL PROTECTED]> wrote: > >Most kmem_read calls are easy to replace (the variables are already >exported as sysctls), the only exception is nextproc (for which I might >add a sysctl, or just leave it out [anyone out there who needs the >lastpid display?]). It's useful for seein

dscheck(#idad/0x2000c): negative b_blkno -557039451

Hello, -Background info: The machine is a Compaq 5500 with 4 Pentium II Xeon's @ 450 Mhz and 256Megs of RAM. It's using the Compaq Smart Array 3200 with 3 9Gig drives in a RAID5 config, and 4 36Gig drives in a RAID0+1 config, with 56Megs allocated to the write cache. Please see the attached dmesg

Win a top of the range iMac, Palm Pilot or Discman

      Connect to your future and start 2001 as a winnerWin a top of the range iMac, Palm Pilot or Discman  All you have to do to win is register with planetgraduate, the new international site fo

Obtain a list of active vnodes

I tried to obtain a list of vnodes in the system. The command pstat -v no longer works. Is there any way to achieve this or hack the code a little bit to achieve this? Thanks. -Zhihui To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the messa

Re: Moving to KLM's

> ok, what would be the minimal kernel that i can compile :), > or is there a document somewhere that says that info? We have > LINT, should we make something called MIN for minimal kernel needed to boot? It's not really feasible to create a "minimal" kernal, since "minimal" really depends on yo

Re: regular coding?

> does anyone know a good programming > (C) mailing list I could subscribe too? Not as such. However, there are two usenet groups that cover C: comp.lang.c and comp.lang.c.moderated. If you have no news access, the c.l.c.m moderator has said he could probably set up a mail<->news gateway for t

Re: regular coding?

In message <[EMAIL PROTECTED]>, Greg Black writes: >> does anyone know a good programming >> (C) mailing list I could subscribe too? >Not as such. However, there are two usenet groups that cover C: >comp.lang.c and comp.lang.c.moderated. If you have no news >access, the c.l.c.m moderator has s

Re: Suboptimal mmap of devices on i86

On 01-Feb-01 Doug White wrote: > On Mon, 29 Jan 2001, John Baldwin wrote: > >> Then only rename it in 4.x We can do an API change for 5.0. We'll be >> renaming syscall2() back to syscall() in 5.0 for example. We don't >> want to end up with syscall47() someday in FreeBSD 67.2. :-P > > And wha

Re: swap_pager: indefinite wait buffer: device: #ad/0x20001, blkno: 288, size: 4096

In message , Max Khon writes : >what does the following error message mean: >swap_pager: indefinite wait buffer: device: #ad/0x20001, blkno: 288, >size: 4096 >it happens when burncd is fixating disk My intuitive guess is that the fixate command

Re: NEED HELP: fiber card

On Thu, 1 Feb 2001, Nick Meverden wrote: > has anyone had any success getting the FDDILINK 3com 3c805 pci fiber > card to work with freebsd 4.2R or know anyone that could help develop > a driver for this ? Please contact me If this isn't a DEFPA in disguise and adding the PCI IDs to the fpa driv

Re: watchdog bugging us.

At 08:18 PM 01/31/2001, Reddy Crashalott wrote: >[disclaimer: this is an invalid sender and return address; replies > should be posted to the list or perhaps better not posted at all, > finally i am rid of that cursed e-mail reachability, free at last] > > >:: When i do tail -f /var/log/messages

Re: a mtools wrapper (slight better control)

> I need to enable a group of workstations running XDM > accesses to local disk floppies with FAT16/32 FS(es). Therefore, I > considered ports/emulators/mtools. > All users will have access to the floppy drives. > All workstations will permit remote shell emulation > (sshd,...).

Re: bootstrap fails with FreeBSD make (fwd)

FYI, in case someone is interested. Gerald -- Forwarded message -- From: Marc Espie <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Date: Sun, 28 Jan 2001 03:08:33 +0100 In article <[EMAIL PROTECTED]> you write: >Hi, > >I just tried to bootstrap under FreeBSD 4.2. The build stoped aft

Re: NEED HELP: fiber card

I'm afraid a DEFPA is really != a 3COM. DEFPA is a DEC design, which I think uses DEC-specific chips My DEFPAs are at home so I cannot easily check right now. W/ > On Thu, 1 Feb 2001, Nick Meverden wrote: > > has anyone had any success getting the FDDILINK 3com 3c805 pci fiber > > card to work

Re: Realtek card support

We've had horrible luck with the realtek 8139 with a few of our 10MBps hubs. We've had OK luck with cross over cables, but not good enough to run with that configuration in our deployed systems. We've also found that this is due to autonegotiation is the cause of this and that if we explicitly

Re: EBCDIC -> ASCII

In message <[EMAIL PROTECTED]> Peter Pentchev writes: : Actually, dd(1) has four different EBCDIC encodings and two : different ASCII encodings. People might want to remember : that different BSD utilities might indeed have their roots : in EBCDIC times :) Even the name (dd) comes from IBM's con

Re: CVSup7.FreeBSD.org is back in service

In message <[EMAIL PROTECTED]> Julian Elischer writes: : I have the folowing suggestion for CVSup.. : the ability to specify several servers. : Cvsup can have a quick exchange with each to inquire about load and check the : latency and bandwidth : and the last time updated, and choose the best

Re: EBCDIC -> ASCII

> Warner Losh writes: > Even the name (dd) comes from IBM's control language (JSYS?). Huh! I never realized that. //GO.SYSIN DD * ... // Where are my punch cards? :-) Jean-Marc -- Jean-Marc Zucconi -- PGP Key: finger [EMAIL PROTECTED] [KeyID: 400B38E9] To Unsubscribe: send mail to [EM

__syscall

Hello, What exactly is the difference between syscall & __syscall ? And in in kern/init_sysent.c struct sysent sysent[] = { /* . */ { 3, accept}, /*...*/ } what does 3 denote ? I believe it's the total size of all the arguments in 32 bit words soumen To Uns

Re: __syscall

"Soumen Biswas" wrote: > Hello, > > What exactly is the difference between syscall & __syscall ? syscall() and __syscall() are pseudo-syscalls. They take arguments and evaluate them as though they were real syscalls. You can see the code in sys/i386/i386/trap.c. __syscall() has 64 bit al

Re: Obtain a list of active vnodes

Zhiui Zhang wrote: > > I tried to obtain a list of vnodes in the system. The command pstat -v no > longer works. Is there any way to achieve this or hack the code a little > bit to achieve this? Thanks. pstat -v used to call a sysctl to extract the list. THe problem was that it could be so b

Config doesn't understand wired SCSI devices any more

Hi, I cvsupped 4.2-STABLE last night and did a buildworld. This part was okay. Now I'm trying to build a kernel and config is complaining about the config lines that wire down my SCSI devices. Config says this: config: line 83: sym 0 not defined My Kernel config looks like this: 72 d

Re: mdconfig config file (was: cvs commit: src/sys/i386/conf GENERIC)

[cvs-(all|commiters) -> -hackers] > >> If anybody writes a patch to mdconfig to DTRT based on some > >> less bogus /etc/fstab entries, I'll happily review and commit it. > > > >Does this sort of functionality really belong in mdconfig? > > Not by definition, and I'm not religious about it. Okay

Re: docs/24035: ptrace(2) PT_STEP incorrect documentation

Folks, On Tue, Jan 02, 2001 at 09:05:29PM -0800, [EMAIL PROTECTED] wrote: > >Number: 24035 > >Category: docs > >Synopsis: ptrace(2) PT_STEP incorrect documentation > >Description: > > in the man pge > PT_STEP The traced process is single stepped one instruction.

capturing an early kernel dump

[Repost from last week, no answer then.] How do I capture an early kernel dump (before rc executes and sets dumpdev)? The dump partition used to be an option in the kernel config file, but that seems to have changed in 3.X or 4.X. Thanks, Lars -- Lars Eggert <[EMAIL PROTECTED]>

Re: Realtek card support

I usually don't recommend the 8139/29 for anything that is expected to work consistently. The cards work alright, but I prefer to stick to Digital or Intel based NICs for important tasks. Warner Losh had the audacity to say: > > We've had horrible luck with the realtek 8139 with a few of our 10M

Re: Realtek card support

In message <[EMAIL PROTECTED]> Coleman Kane writes: : I usually don't recommend the 8139/29 for anything that is expected : to work consistently. The cards work alright, but I prefer to stick : to Digital or Intel based NICs for important tasks. Same here. However, with the SBCs we buy, we have

Re: Really odd "BTX halted" problem booting - PXE/diskless

On Thu, 1 Feb 2001, Doug White wrote: > This is a bug in the adaptec BIOS. Don't do this for boot disks. Use > fdisk/real slices instead. Or possibly, dont do this for any disk in the system. Some bioses choke even on non-boot disks with DD partitioning... Fred -- Fred Clift - [EMAIL PROTECT

Re: EBCDIC -> ASCII

> > Warner Losh writes: > > > Even the name (dd) comes from IBM's control language (JSYS?). > > Huh! I never realized that. > //GO.SYSIN DD * > ... > // > Where are my punch cards? :-) man 6 bcd To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the b

pxeboot -> init does error 5

http://people.freebsd.org/~alfred/pxe/ But I get tired of dicking around with mfsroot vnode devices and such. The first thing I tried was taking the contents of the boot floppies and just sticking them in /usr/tftpboot. No dice, because then you end up with a read-only NFS root, which upsets sy

Re: Really odd "BTX halted" problem booting - PXE/diskless

On Mon, 29 Jan 2001, Danny Braniss wrote: > im now being bitten by this one, but with a twist: > on a compaq deskpro workstation it's ok > on a dell-precision 420, it bombs. > both bioses are configured to boot via the network/pxe. > > im using the same disks for both boxes. > > i labeled the

Re: panic: ufs_dirbad: bad dir

After a suggestion offlist, here's the additional information from a boot -v: Mounting root from ufs:/dev/ad0s1a ad0s1: type 0xa5, start 63, end = 2503871, size 2503809 : OK /: bad dir ino 2 at offset 0: mangled entry panic: ufs_dirbad: bad dir syncing disks 1 1 1 1 1 1 1 1..etc giving up

Re: panic: ufs_dirbad: bad dir

James writes: > What part of the kernel install did it panic on? (if you even saw that > part) Sorry, I forgot to mention that. Here is what was left on my remote screen after the panic: root@ducky:/usr/src/sys/compile/DUCKY] # make install chflags noschg /kernel mv /kernel /kernel.old inst

panic: ufs_dirbad: bad dir

I recently upgraded a box from 4.1-stable to 4.2-stable. An NFS mount was used for the install world and install kernel. During the kernel install the box panic'd (sorry, didn't see the message). Upon boot, the box give these messages: Mounting root from ufs:/dev/ad0s1a /: bad dir ino 2 at off

Re: panic: ufs_dirbad: bad dir

What part of the kernel install did it panic on? (if you even saw that part) Have you tried booting the previous kernel? I'm not sure if it'll even boot... but, you might want to try that. You might also wanna try installing the same /kernel and /modules that you were when it panic'd, while yo

Re: capturing an early kernel dump

Lars Eggert wrote: > [Repost from last week, no answer then.] > > How do I capture an early kernel dump (before rc executes and sets > dumpdev)? > > The dump partition used to be an option in the kernel config file, but that > seems to have changed in 3.X or 4.X. > > Thanks, > Lars How early?

Re: Config doesn't understand wired SCSI devices any more

Gardner Buchanan wrote: > Hi, > > I cvsupped 4.2-STABLE last night and did a buildworld. > This part was okay. Now I'm trying to build a kernel > and config is complaining about the config lines that > wire down my SCSI devices. > > Config says this: > >config: line 83: sym 0 not defined >

Re: capturing an early kernel dump

> Lars Eggert wrote: >> How do I capture an early kernel dump (before rc executes and sets >> dumpdev)? > > How early? We could dump if you were prepared to hardwire in the minor and > major device numbers to get to the devsw[] vectors and manually set the > offsets. Not that early :-) I'm pla

Re: mdconfig config file (was: cvs commit: src/sys/i386/conf GENERIC)

It doesn't make sense to pollute 'mdconfig' with functions that we already have an API available to perform. An API called 'mount'. Why not write a 'mount_md' program to do all the magic based on fstab options, similar to what mount_mfs used to do for MFS? A 'mount_md' would giv