From owner-freebsd-current Fri Oct 5 7:27:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 2F44137B403; Fri, 5 Oct 2001 07:27:25 -0700 (PDT) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 15pVx8-0004o6-00; Fri, 05 Oct 2001 16:27:50 +0200 From: Sheldon Hearn To: julian@FreeBSD.org Cc: current@FreeBSD.org Subject: KSE settling in (smbfs broken) Date: Fri, 05 Oct 2001 16:27:50 +0200 Message-ID: <18481.1002292070@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Julian, I didn't realize that smbfs was a KSE casualty, but it's nice that you made this obvious with the following in sys/modules/Makefile: #removed while KSE settles in: # smbfs \ So at least it didn't take me long to figure out what was going on. My question is what sort of timeframe this "settling in" is likely to involve? I would have thought that a disconnected module would rot, but your settling in comment suggests that you have plans to reconnect it yourself? Or is this another way of saying "dead unless someone else fixes for KSE"? I copied the -current list because I doubt I'm the only one who's wondering how this is all going to work. Basically, I think a lot of us are wondering whether we can sit back and wait for you to fix the stuff that stopped working after the KSE import, or whether you're sitting back and waiting for us to do it. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message