From owner-freebsd-arch Sun Jul 9 15: 8:43 2000 Delivered-To: freebsd-arch@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id ED27C37BAAB for ; Sun, 9 Jul 2000 15:08:34 -0700 (PDT) (envelope-from john@baldwin.cx) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id PAA16292; Sun, 9 Jul 2000 15:08:28 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id PAA00589; Sun, 9 Jul 2000 15:09:14 -0700 (PDT) (envelope-from john) Message-Id: <200007092209.PAA00589@john.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 09 Jul 2000 15:09:14 -0700 (PDT) From: John Baldwin To: Adam Subject: Re: making the snoop device loadable. Cc: arch@FreeBSD.ORG Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Jul-00 Adam wrote: > On Sun, 9 Jul 2000, John Baldwin wrote: > >> >>On 09-Jul-00 Adam wrote: >>> On Sun, 9 Jul 2000, Poul-Henning Kamp wrote: >>> >>>>In message , Adam >>>>writes: >>>>>On Sun, 9 Jul 2000, Poul-Henning Kamp wrote: >>>>> >>>>>> >>>>>>>If this change goes in, what do you do if you wish not to have snooping >>>>>>>capable through the snp device and do not wish to lock unneccessary parts >>>>>>>of the system down with securelevel? >>>>>> >>>>>>You do the same as before: Hold on tight to your root password. >>>>> >>>>>I dont like kernel changes that make the kernel do less babysitting and me >>>>>more. Tough, I guess. >>>> >>>>You have always needed to babysit your root password. >>> >>> Ok, I give in to the argument. I would just like to make a wish. On Jan >>> 24 1999 peter took the NO_LKM option out of LINT. I assume the support >>> for it in other files was removed around that time also. Could someone >>> implement a NO_KLD option so you dont need to use securelevel > 0 so >>> people have an obvious option and dont have to know the kernel well enough >>> to hack syscalls.master? >> >>Patches accepted. :) Seriously, if you come up with a patchset >>I'll look at it and see about getting it in the tree. >> >>John Baldwin -- http://www.FreeBSD.org/~jhb/ > > Okay, I have no idea what these SYSINIT's are supposed to do but this file > seems to be the KLD equiv of kern_lkm. options NO_LKM (as added in 1.47 > and cleaned up in 1.48 of kern_lkm.c) added an #ifndef around the line > SYSINIT(lkmdev,SI_SUB_DRIVERS,SI_ORDER_MIDDLE+CDEV_MAJOR,lkm_drvinit,NULL) > > The lines with SYSINIT in kern_linker.c are: > SYSINIT(linker, SI_SUB_KLD, SI_ORDER_FIRST, linker_init, 0); > SYSINIT(linker_kernel, SI_SUB_KLD, SI_ORDER_ANY, > linker_init_kernel_modules, 0); > SYSINIT(preload, SI_SUB_KLD, SI_ORDER_MIDDLE, linker_preload, 0); > > I'm not quite sure which one would get #ifndef'ed, or if thats even still > the right way to do it, any ideas? I'm working on updating an old > -current box to check it out. Hmm, the person to ask is Peter Wemm, or to just read the source. I can look at it tomorrow at work though. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message