Re: 3dfx.ko
On Wed, Nov 29, 2000 at 02:11:00PM +0900, Daniel C. Sobral wrote: Ugh. Evil stuff. Are environment variables starting with digits allowed in sh(1)? Nope: $ 3FOO=yes 3FOO=yes: not found $ export 3FOO=yes export: 3FOO: bad variable name To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
3dfx.ko
The standard way of loading a particular module at boot from /boot/loader.conf is 'modulename_load="YES"', right? This doesn't seem to be possible with the 3dfx module, however... Since it's name starts with a number, it causes a syntax error. Being FORTH-impaired, I have no idea how to work around this... Anybody know how to make this work? Also, it doesn't seem to be possible to compile 'device tdfx' statically into the kernel either, since it depends on symbols that only exist in the kernel when compat_linux is defined, and COMPAT_LINUX is no longer an option, is it? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3dfx.ko
"Donald J . Maddox" wrote: Also, it doesn't seem to be possible to compile 'device tdfx' statically into the kernel either, since it depends on symbols that only exist in the kernel when compat_linux is defined, and COMPAT_LINUX is no longer an option, is it? COMPAT_LINUX is still supported. It's broken on the Alpha though. If it's broken on i386 as well, let me know. I'm not aware of any brokeness at this time. -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3dfx.ko
I actually thought that COMPAT_LINUX had been completely removed, just causing opt_dontuse.h to be generated. I see now that it doesn't even warn about this being a deprecated option. *Is* it still considered a deprecated option? I'm sure config used to warn about COMPAT_LINUX being deprecated a while back... On Tue, Nov 28, 2000 at 06:22:33PM -0500, Marcel Moolenaar wrote: "Donald J . Maddox" wrote: Also, it doesn't seem to be possible to compile 'device tdfx' statically into the kernel either, since it depends on symbols that only exist in the kernel when compat_linux is defined, and COMPAT_LINUX is no longer an option, is it? COMPAT_LINUX is still supported. It's broken on the Alpha though. If it's broken on i386 as well, let me know. I'm not aware of any brokeness at this time. -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3dfx.ko
"Donald J . Maddox" wrote: I actually thought that COMPAT_LINUX had been completely removed, just causing opt_dontuse.h to be generated. I see now that it doesn't even warn about this being a deprecated option. *Is* it still considered a deprecated option? I'm sure config used to warn about COMPAT_LINUX being deprecated a while back... It's not a deprecated option. I'm not aware of config ever emitting a warning for it. -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3dfx.ko
"Donald J . Maddox" wrote: The standard way of loading a particular module at boot from /boot/loader.conf is 'modulename_load="YES"', right? This doesn't seem to be possible with the 3dfx module, however... Since it's name starts with a number, it causes a syntax error. Ugh. Evil stuff. Are environment variables starting with digits allowed in sh(1)? If so, I'll extend loader's syntax. Otherwise, see below. Anybody know how to make this work? Use two variables to control this. For instance: threedfx_load="YES" threedfx_name="3dfx" The way loader is set up, you put the _name line in /boot/defaults/loader.conf, so that the user only needs to put the threedfx_load="YES" line in his config. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "All right, Lieutenant, let's see what you do know. Whatever it is, it's not enough, but at least you haven't done anything stupid yet." "I've hardly had time, sir." "There's a naive statement." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3dfx.ko
Thanks! This works great. I remember reading the stuff at the bottom of /boot/defaults/loader.conf about the 'module_name' variable, etc. and wondering what on Earth it might be useful for :) Guess I know now :) Thanks again... "Daniel C. Sobral" wrote: Use two variables to control this. For instance: threedfx_load="YES" threedfx_name="3dfx" The way loader is set up, you put the _name line in /boot/defaults/loader.conf, so that the user only needs to put the threedfx_load="YES" line in his config. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
