Re: Reserving Resources

On Sun, Apr 02, 2000 at 02:29:55PM -0600, Warner Losh wrote: > The whole purpose of unknown is to CONSUME the resources that others > might try to use. This can't easily be done in the base bus w/o it > actually consuming them. Maybe we need a flag that means "I'm a > pseudo device that was cre

GDB 5

(I'm not on freebsd-hackers, i read it every few days through the web interface. Too much mail already. So if you have a reply, be sure to cc me). Kris, you wrote " You're more likely to get an answer by asking the gdb developers on the gdb "mlist" :-) " when asked about why GDB 5 doesn't have su

Warning: Object directory not changed from original

I am writing a new graphical screen saver, based on an existing one (rain_saver.c) in 3.4-STABLE. The system is freshly CVSupped to RELENG_3 using src-all. I found the list of modules in /usr/src/sys/modules/syscons/Makefile and updated that. But the new program won't compile cleanly. Even whe

Re: Autogenerated sources

In message <[EMAIL PROTECTED]> Assar Westerlund writes: : > That's just a small part of the problem... : : Sure, but it's a part of the problem. And it's a part of the problem : that I care about, as in it would make things simpler. I think it should be handled in a similar manner that the foo_

Re: Autogenerated sources

Warner Losh <[EMAIL PROTECTED]> writes: > : Anyways, (and it's really orthogonal) having a generated vnode_if.h > : (in /sys/kern or /usr/include/sys) makes it easier for the developer > : of third-party file systems (i.e. me :-), by not having to figure out > : how to generate vnode_if.h from vno

Re: Autogenerated sources

In message <[EMAIL PROTECTED]> Assar Westerlund writes: : Warner Losh <[EMAIL PROTECTED]> writes: : > Yes. They must be compiled against the kernel, just like modules : > provided by freebsd. : : Even if I knew that the files in /usr/include/sys/* correspond with : the kernel? Yes, because they

Re: Autogenerated sources

Warner Losh <[EMAIL PROTECTED]> writes: > Yes. They must be compiled against the kernel, just like modules > provided by freebsd. Even if I knew that the files in /usr/include/sys/* correspond with the kernel? Anyways, (and it's really orthogonal) having a generated vnode_if.h (in /sys/kern or

Re: Autogenerated sources

In message <[EMAIL PROTECTED]> Assar Westerlund writes: : Warner Losh <[EMAIL PROTECTED]> writes: : > Hmmm. I've always found that the kernel only files need to be : > compiled with a kernel installed. This included loadable modules. : : What about third-party loadable modules? Yes. They must

Re: Autogenerated sources

Warner Losh <[EMAIL PROTECTED]> writes: > Hmmm. I've always found that the kernel only files need to be > compiled with a kernel installed. This included loadable modules. What about third-party loadable modules? > Bruce and I have been working out a patch to make it possible to > compile load

Re: Autogenerated sources

In message <[EMAIL PROTECTED]> Assar Westerlund writes: : Talking about this, was there any opinions on what to do with : vnode_if.h? (See my PR kern/17613). I do think that it should also : be checked in or at least installed in /usr/include/sys/ so that code : can be built without having the k

Re: Autogenerated sources

Warner Losh <[EMAIL PROTECTED]> writes: > There are also other generated files in the tree. syscalls.c is > another example that is generated once, and then committed to the > tree. Talking about this, was there any opinions on what to do with vnode_if.h? (See my PR kern/17613). I do think tha

Re: Reserving Resources

In message Nick Hibma writes: : Um, in that case you should update subr_bus.c. Change committed two : weeks ago. I got annoyed to by that too :-) H. This work was on a 4.0-RELEASE system Makes sense. BTW, I have a hack to subr_bus tha

Re: Autogenerated sources

In message <[EMAIL PROTECTED]> Peter Jeremy writes: : I notice that there seem to be some autogenerated files related to USB : and PCCARD in the repository. Shouldn't the repository just contain : the master files, with the header files generated as required during : the make process? How do the

Re: cvs commit: src/share/skel dot.cshrc dot.login src/etc/rootd

On 02-Apr-00 Peter Jeremy wrote: > [Catching up on some old mail] > > On Sun, Mar 26, 2000 at 06:56:36PM +1000, Doug Barton wrote: >> >PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:/usr/games:$HOME/bin > > Two comments: > a) The sbin directories are for sysad

Re: cvs commit: src/share/skel dot.cshrc dot.loginsrc/etc/rootdot.cshrc dot.login

[Catching up on some old mail] On Sun, Mar 26, 2000 at 06:56:36PM +1000, Doug Barton wrote: > >PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:/usr/games:$HOME/bin Two comments: a) The sbin directories are for sysadmin functions and probably shouldn't be in u

Autogenerated sources

I notice that there seem to be some autogenerated files related to USB and PCCARD in the repository. Shouldn't the repository just contain the master files, with the header files generated as required during the make process? How do these files differ from the device/bus files (/sys/kern/*.m), e

Re: Reserving Resources

In message Nick Hibma writes: : The issue is pretty hairy and for now I think the solution is to make : any stub use DEVICE_NOMATCH (see pci.c), which does not attach a driver : to a device, just mentions it during boot. And during every reprobe

Re: Unicode on FreeBSD

Anatoly Vorobey <[EMAIL PROTECTED]> wrote: > What do you think? For what it's worth (me not being a committer and generally not on the productive side of things), I morally support this idea. To push certain buttons: what you are suggesting is to bring syscons up to what the Linux console alrea

Re: JetDirect 500X and FreeBSD

Thus spake Andrew MacIntyre ([EMAIL PROTECTED]): > they weren't particularly reliable, particularly when multiple jobs were > queued simultaneously. I hope their more recent stuff is better behaved. It is now. A further thing is: If your LaserJet doesn't understand PostScript, you have to use

Re: JetDirect 500X and FreeBSD

Jeremiah Gowdy wrote: > > Does anyone have any experiance or information about using HP JetDirect 500X > Printer Hubs with FreeBSD ? This is mission critical for my company, so any > information greatly appriciated. Ah...printers...my next to modems, my least favorite periphial to deal with.