Re: sysctl filesystem ?

2012-06-25 Thread Boris Popov
On 26.06.2012 6:56, Arnaud Lacombe wrote:
 purpose. However, if I can avoid to re-design that wheel too, by
 getting access to scfs(4) code, I will.

  It is interesting, that the old drive with this code are still alive.
Most likely, FS related part will need serious attention because of
numerous changes in the VFS subsystem. Here is the link:

http://www.vertex.kz/scfs.tgz

-- 
Boris Popov

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: User mounts could not use character conversions (libkiconv is just for roots)

2003-12-02 Thread Boris Popov
On Tue, Dec 02, 2003 at 05:38:05PM +0100, Rudolf Cejka wrote:
 
   I have found, that user mounts using libkiconv.so (msdosfs, cd9660, ...)
 could not use character code conversions, beause writing to sysctl
 kern.iconv.add is allowed just for root. Personally, I have created
 small patch, which allows to change kern.iconv.add to anybody, so it does
 work for me. Does anybody know, if there are security drawbacks and if
 it can or can not be commited?

Probably it is not a good idea to allow users to load kernel iconv
tables because one can waste a lot of memory by loading of all possible
conversion schemes.  The better solution is to add some kind of preload
ability which could be used on startup.

-- 
Boris Popov
http://rbp.euro.ru
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: null_lookup() vnode locking wierdness

2003-11-23 Thread Boris Popov
On Sun, Nov 23, 2003 at 04:16:10PM -0800, Don Lewis wrote:
 On 23 Nov, I wrote:
  I was trying to figure out why the VOP_UNLOCK() call in null_lookup()
  was violating a vnode locking assertion, so I tossed a bunch of
  ASSERT_VOP_LOCKED() calls into null_lookup().  I found something I don't
  understand ...
  
 It looks like the easiest fix is to skip the VOP_UNLOCK() call in
 null_lookup() if dvp-v_vnlock == ldvp-v_vnlock.

Yes, this seems to be correct and necessary addition.  At first sight,
the later code shouldn't blow because of that.  BTW, buildworld -jN on top of
the null mount together with another buildword -jN on the underlying file 
system helps a lot to discover vnode locking problems.

-- 
Boris Popov
http://rbp.euro.ru
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Removal of netns

2003-03-04 Thread Boris Popov
On Wed, 5 Mar 2003, Tim Robbins wrote:

 Is there a compelling reason why I shouldn't remove netns? That is, does
 it serve a purpose now that it could not serve if it was moved to the
 Attic?

netns could be safely moved to Attic. I'm receive enough IPX
related questions, and never got any about XNS.

netns stack was used by NetCon package which implemented TFS
filesystem for NetWare connectivity. Guess, which protocol they used to
communicate with servers ? Right, it was IPX. So, if netns were still
supported it became just a parallel implementation of netipx.

Last version of FreeBSD supported by NetCon was 2.2.X. Lack of
support for FreeBSD 3.X encouraged me to write nwfs because it was
necessary for my daily tasks.

BTW, NetCon still offers their product for FreeBSD 2.2: 
http://www.netcon.com/download/download.htm

-- 
Boris Popov
http://rbp.euro.ru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message


Re: smbfs broken?

2002-10-30 Thread Boris Popov
On Tue, 22 Oct 2002, Vitaly Markitantov wrote:

 When i tries to copy a file from smbfs share mounted by mount_smbfs
 i get an error:
  cp: ./filename: Bad address
 
 But when i copy a file to share i get kernel panic like this:
 
  Fatal trap 12: page fault while in kernel mode

Early started set of changes is not finished yeat and that panic
might be caused by this.  I'm sorry for leaving things broken for such
long time, but really can't help right now.

BTW, I'm looking for smbfs co-maintainer and if anyone
interested in this, please mail me (obviously one are supposed to have
knowledge of kernel and smbfs internals).

-- 
Boris Popov
http://rbp.euro.ru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Request for review testing of VFS locking patch

2002-09-20 Thread Boris Popov

On Thu, 19 Sep 2002, Jeff Roberson wrote:

 This patch touches every filesystem.  I have tested with several but I
 would appreciate more extensive testing especially if you use one of the
 lesser used filesystems (ie non ufs).  Please test with WITNESS and
 DEBUG_VFS_LOCKS enabled.  If you find that it drops into the debugger
 please get a back trace and then do the following:

Well, haven't tested it with smbfs, but may point that patch for
nwfs contains two vref()s instead of vgetref().

-- 
Boris Popov
http://rbp.euro.ru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: OT: FreeBSD-current works great!

2002-04-18 Thread Boris Popov

On Thu, 18 Apr 2002, Thomas Wuerfl wrote:

 Am Donnerstag, 18. April 2002 05:00 schrieb Craig Boston:
  My only trouble so far has been mount_smbfs panicking the machine when
  connecting to certain servers (but not others, weird).  I'm compiling a
  debug kernel now and will attempt to get a good backtrace to post.
 
 I have the same problem, when I mount a smb-share from a Win2000sp2 machine 
 and try to _move_ files from the win-machine to mine (kernel-panic). When I 
 try to mount the same share again after reboot  - kernel panic. I first have 
 to reboot the win-machine to get rid of that. Only by moving files, not copy 
 or delete. Very strange.

Yes, now I'm see this panic too.  Something chaged after Apr 7
broke smbfs.  Not sure what exactly, though.

-- 
Boris Popov
http://rbp.euro.ru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: smbfs in -current?

2002-03-08 Thread Boris Popov

On Fri, 8 Mar 2002, Robert Watson wrote:

 Ok, I've committed a slight reorg to NOTES on -CURRENT to reflect the much
 more logical layout in LINT on -STABLE WRT NETSMB, SMBFS, and
 NETSMBCRYPTO.  No idea where the weird ordering came from, but I think
 it's fixed now. :-)

Thank you. Probably these lines falled of the board on initial
import and later Bruce included them into 'undocumented' section.

-- 
Boris Popov
http://rbp.euro.ru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: smbfs in -current?

2002-03-07 Thread Boris Popov

On Wed, 6 Mar 2002, Seth Hettich wrote:

 I have both:
 options SMBFS
 options NETSMB
 
 
 in my config.
 
 Perhaps someone could give a little explanation, and add it to NOTES?

Thanks for pointing to it. For some reason LINT from -stable have
this explanation and NOTES doesn't.

For now quote from LINT:

cut
# SMB/CIFS requester  
   
# NETSMB enables support for SMB protocol, it requires LIBMCHAIN and LIBICONV
# options.
# NETSMBCRYPTO enables support for encrypted passwords.
options NETSMB  #SMB/CIFS requester
options NETSMBCRYPTO#encrypted password support for SMB
cut

-- 
Boris Popov
http://rbp.euro.ru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: smbfs support

2001-12-03 Thread Boris Popov

On Mon, 3 Dec 2001, Julian Elischer wrote:

 do these patches include the proc-thread changes needed?


According to cvs logs - yes.

-- 
Boris Popov
http://rbp.euro.ru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: smbfs support

2001-12-02 Thread Boris Popov

On Wed, 28 Nov 2001, Sheldon Hearn wrote:

 | I have some untested patches in my tree and I will contact bp this
 | week about them (I wanted to import smbfs userland to the tree and
 | already got ok from bp but could not test it because kernel-side smbfs
 | is not compilable yet).
 
 Excellent news!

Indeed.

 Presumably, if bp doesn't respond by the end of the year, you'll go
 ahead regardless? :-)

Actually, bp responded much faster than you expected :)
Patches submitted by Max were mostly correct except for two or three
lines and now committed to the tree. Again, special thanks to him for very
good work.

However, I'm still don't have enough spare time and really hope
Max will import userland part of smbfs soon.

-- 
Boris Popov
http://rbp.euro.ru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: KSE settling in (smbfs broken) again

2001-10-14 Thread Boris Popov

On Fri, 5 Oct 2001, Sheldon Hearn wrote:

  I need to look at it again.. (I figured I just didn't have the time to try
  understand it all AND do the rest of the kernel.) Of course the best woudl
  be if Mr. Popov did the conversion but I believe he's incredibly busy at 
  the moment.. Certainly if someone else wants to make an effort at it.
  they are welcome to do it.. otherwise I will eventually get to it.
  (but I have no way to test them).
 
 Boris goes through phases, like the rest of us. :-)

Yes, this is correct. Doing hardware stuff consumes a lot of
my time :(

 His last round of changes from Mac OS X sorted out my panics quite
 nicely.

Good to hear. I've selected most critical bugfixes and there is
still big diffs to merge.

 It sounds like the message is I'd like to help with smbfs, but don't
 have time right now, and it'd make a whole lot more sense for someone
 closer to the code to take a look.

Obviously, I'll do the job at some moment. If someone can do it
before - feel free to do this. This may even include import of userland
part in the /contrib hierarchy.

-- 
Boris Popov
http://rbp.euro.ru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Junior Kernel Hacker task: improve vnode-v_tag

2001-09-04 Thread Boris Popov

On Tue, 4 Sep 2001, Maxim Sobolev wrote:

  The places which inspect v_tag will have to be changed to use
  strcmp() then...
 
 I think that we can add a new vnode flag, say VCANLOCK, so that each
 particular VFS can set it if it supports locking, which should allow
 to remove pre-defined VFS list from the IS_LOCKING_VFS macro. I can
 produce a patch if it sounds reasonably.

I'm not sure if this a right thing to do. Under SMPng each
filesystem is ought to implement correct vnode locking, i.e. vop_nolock()
and friends shouldn't exist.

-- 
Boris Popov
http://rbp.euro.ru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: devfs deficiencies (was: devfs and Vinum (was: any -current vinum problems?))

2001-08-16 Thread Boris Popov

On Thu, 16 Aug 2001, Poul-Henning Kamp wrote:

 Julian feels he has no avenue of recourse and gives up..--
 
   if (!strcmp(DEVFS, SLICE))
   return (ECONFUSED);
 
 Julian, you had four years, during which you didn't even manage to
 make half of the commits made to the DEVFS code during that period.
 
 If it is to be counted as my only achivement on -core that I timed
 out SLICE and DEVFS, I'll still be proud of what I did there.

Umm, your timeouts are very strange - you're timed out too quickly
in my case. Of course, you're talked something about that GEOM stuff will
be committed in July (of 2000) and it needs devfs. But we didn't see it
even now. Well, I'm don't mind about waste of my time spent on a design of
new devfs. But one can make corresponding conclusions about your
timeouts ...

-- 
Boris Popov
http://rbp.euro.ru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Stack hogs revisited..

2001-08-15 Thread Boris Popov

On Wed, 15 Aug 2001, Julian Elischer wrote:

 
 I put up a sorted list in order of severity 
 http://people.freebsd.org/~julian/stack-hogs
 This one is from LINT and is more inclusive..

Wow, very interesting reading :)

--
Boris Popov
http://rbp.euro.ru


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: mount_mfs (Re: smbfs)

2001-05-29 Thread Boris Popov

On Fri, 25 May 2001, Brooks Davis wrote:

 On Fri, May 25, 2001 at 10:04:09PM +0700, Boris Popov wrote:
  There is no any technical problems in doing that. But I'm unsure
  if this should be done (code is not very small). On other hand, people
  expect it in the base system... Probably we should collect more votes on
  this topic.
 
 I'll definatly vote for inclusion.  IMO, it makes no sense to have a
 filesystem in the base you can't mount.  If it really is so hugh that
 people complain, there's always the ugly NO_MOUNT_SMBFS make.conf option
 route.  Those who really need small systems have to strip all sorts of
 things out already anyway, one more won't hurt.

Ok, now I've received about fifty votes for inclusion of userland
part in the base tree and zero objections. Import process will be done in
the -current first and then MFCed to -stable.

--
Boris Popov
http://www.butya.kz/~bp/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Mandatory DEVFS (was cvs commit: src/sys/conf files options ...)

2001-05-13 Thread Boris Popov

On Sun, 13 May 2001, Poul-Henning Kamp wrote:

   Log:
   Convert DEVFS from an opt-in to an opt-out option.
   
   If for some reason DEVFS is undesired, the NODEVFS option is
   needed now.

Right step.

   Pending any significant issues, DEVFS will be made mandatory in
   -current on july 1st so that we can start reaping the full
   benefits of having it.

I'm not sure if this move in the right direction. Current devfs
implementation is weak compared to the static device entries in the /dev.
And sometimes it is better to have a precreated device nodes in the ufs
filesystem. Having dual interface is not all that hard if you'll spend
enough time on design.

--
Boris Popov
http://www.butya.kz/~bp/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: mounting netware fs

2001-04-17 Thread Boris Popov

On Wed, 18 Apr 2001, User  wrote:

 mount -a -t nonfs
 
 to
 
 # Mount everything except nfs filesystems.
 mount -a -t nonfs,nwfs
 
 In the first case at boot time the machine stops and wants me to enter
 in shell and fix the problem. I don't know whether I'm right, but I
 think that my modification can help.

Well, nwfs and smbfs can be added to the list along with
nfs. However I would recommend to use 'noauto' modifier and the shell
script like one in the /usr/share/examples/nwclient

--
Boris Popov
http://www.butya.kz/~bp/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: mount_smbfs missing, SAMBA package installed, where is it?

2001-04-17 Thread Boris Popov

On Tue, 17 Apr 2001 [EMAIL PROTECTED] wrote:

 I'm running 5.0-Current-4.12.2001, X-Kern-Developer with all binaries,
 have just installed the samba package (pkg_add -r samba) but the smb
 client services, specifically mount_smbfs, aren't installed.  

mount_smbfs doesn't belong to the Samba package. Take a look at
ports/net/smbfs.

--
Boris Popov
http://www.butya.kz/~bp/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: world (still) having trouble (after gdb.291/gdb/defs.h)

2001-04-11 Thread Boris Popov

On Wed, 11 Apr 2001, David Wolfskill wrote:

 In "stage 4: building everything...", it got well past that point, but
 blew up in usr.bin/kdump:

Sorry, delta was committed to smb_dev.h. It should be ok now.

--
Boris Popov
http://www.butya.kz/~bp/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: random reboots...

2001-03-14 Thread Boris Popov

On Wed, 14 Mar 2001, Alex Zepeda wrote:

 I haven't been able to track this down since the kernel won't panic.. but 
 with more recent kernels I've noticed:
 
 * options NCP prevents the kernel from linking

You need options LIBMCHAIN as well. We don't have mechanism for
specifying dependancies between options as of yet. (sorry, should put a
note in the NOTES).

--
Boris Popov
http://www.butya.kz/~bp/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: random reboots...

2001-03-14 Thread Boris Popov

On Wed, 14 Mar 2001, Garrett Wollman wrote:

  You need options LIBMCHAIN as well. We don't have mechanism for
  specifying dependancies between options as of yet. (sorry, should put a
  note in the NOTES).
 
 Actually, yes we do, although it's not often used.  If the relevant
 sources are listed twice in `files', conditional on each option, then
 `config' will do the right thing.  For example:
 
 dev/pccard/card_if.moptional card
 dev/pccard/card_if.moptional pccard

Yes, thats why I don't like this method :)

--
Boris Popov
http://www.butya.kz/~bp/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: how's vinum these days with DEVFS?

2001-03-11 Thread Boris Popov

On Sun, 11 Mar 2001, Poul-Henning Kamp wrote:

 In message [EMAIL PROTECTED], Alfred Perlstein writes:
 
 What's up with devfs not gc'ing itself?  Ie, after a directory
 becomes empty it seems to still exist within the devfs namespace
 instead of disappearing.
 
 That was a deliberate decision, removing a directory(-inode) which
 might have a valid vnode is kind of a nasty thing to attempt.

Err, "might" ?  These things are well defined by VFS interface.

--
Boris Popov
http://www.butya.kz/~bp/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: occasional filesystem corruption

2001-03-11 Thread Boris Popov

On Tue, 20 Feb 2001, Vallo Kallaste wrote:

 I have experienced two filesystem corruption cases recently. Both
 took place in /usr filesystem, the first was file with very big
[skip]
 lock order reversal
 ../../kern/kern_synch.c:429: sleeping with "vnode interlock" locked from 
/usr/ports/net/smbfs/work/smbfs-1.3.5/kernel/modules/smbfs2/../../fs/smbfs/smbfs_vnops.c:280

Thanks, this particular bug is fixed. Not sure if it can cause
filesystem corruption (in fact it shouldn't). However, it is not advisable
to use kernel modules with WITNESS enabled.

P.S. setting more appropriate subject might give a faster response :)
--
Boris Popov
http://www.butya.kz/~bp/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: mount: /dev/ad0s1e: File name too long

2001-03-04 Thread Boris Popov

On Sun, 4 Mar 2001, Adrian Chadd wrote:

  Blame Adrian Chadd ([EMAIL PROTECTED]) :)  Apparently the limit he's enforcing
  on mount names is rather short... :)
 
 For those who asked, I'll MFC this to -stable once its settled down
 a little. There are a few other bits I need to do that have been pointed
 out to me before I'm happy with the change.

I'm unsure if this necessary (and valid) because these things make
incompatible changes in API. Lets keep at least -stable consistent :)

P.S. Even minor MFC of kobj gave me a huge heap of mail...
--
Boris Popov
http://www.butya.kz/~bp/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: DEVFS newbie...

2001-01-29 Thread Boris Popov

On Tue, 30 Jan 2001, Greg Lehey wrote:

  You can create symlinks in /dev, you cannot mknod there.
 
 What is the reason for this?  How does a program or script know
 whether the system is running DEVFS or not?

I don't see any good reason why this can't be supported. We may
talk about 'broken' devices, etc., but while there any - mknod needs to be
supported to make transition more smooth.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: NTFS issue (was: Panic w/crash dump (looks like atomic.h problem))

2001-01-19 Thread Boris Popov

On Fri, 19 Jan 2001, Rogier Mulhuijzen wrote:

 During normal operation on my NTFS partition I got no messages, so I took a 
 bold step and added 'ip-i_devvp = ntmp-ntm_devvp;' just before the VREF call.

You're absolutely right here. This line definitely should be
presented in the code.

 Am I on the right track here?

Yes, thanks :)

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: NTFS issue (was: Panic w/crash dump (looks like atomic.h problem))

2001-01-19 Thread Boris Popov

On Sat, 20 Jan 2001, Boris Popov wrote:

 On Fri, 19 Jan 2001, Rogier Mulhuijzen wrote:
 
  During normal operation on my NTFS partition I got no messages, so I took a 
  bold step and added 'ip-i_devvp = ntmp-ntm_devvp;' just before the VREF call.
 
   You're absolutely right here. This line definitely should be
 presented in the code.

Hmm, scratch this. This field initialized when ntnode is born and
it should be valid while ntnode is alive (I've looked at the wrong place
first time).

This probably caused by vnode or ntnode being recycled due to a
locking problem or missing reference.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Boris Popov

On Wed, 17 Jan 2001, Alfred Perlstein wrote:

 I have a patch here that removes await/asleep from the kernel API.
 
 http://people.freebsd.org/~alfred/noasleep.diff
 
 Matt Dillon implemented alseep/await quite some time ago and the
 only thing that's using it is ata.  In order to clean up some of
 the schduler and vm system I'm removing support for it.

Hmm, I've found this API usable for synchronization between two
kernel threads/processes:

alseep(somewhere);
wakeup(anotherprocess);
await(somewhere);

where 'anotherprocess' do some job and call wakeup(somewhere).

I suspect that this can be emulated with mutexes and/or
conditional variables. So, it is possible to keep the API, but change its
implementation to allow mentioned cleanup of scheduler ?

P.S. it is already too hard to maintain external kernel modules even
within various releng_4s, not to mention -current and releng_3...
--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Unicode support in cd9660 [patch for review]

2000-12-27 Thread Boris Popov

On Wed, 27 Dec 2000, Maxim Sobolev wrote:

 Several days ago I got a CD with Russian filenames on it and discovered that
 I'm unable to read those filenames. After some hacking I produced a patch,
 which should solve this problem in the manner similar to what we have in
 msdosfs module (i.e. user-provided conversion table). I have to emphasize that
 it's a temporary solution until we will have iconv support in kernel.

The patch seems to be ok as temporary solution for CDs with
Russian file names. And as temporary solution it well suits to the ports
collection, not to the main tree.

In the near future we'll have iconv interface in the kernel which
uses libiconv library written by Konstantin Chuguev. I'm really sorry for
delays, but my current job leaves nearly zero spare time to me and there
is a hope that January will be less busy.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Laptops and sc0/vt0 consoles

2000-11-22 Thread Boris Popov

On Wed, 22 Nov 2000, Nate Williams wrote:

  In my past experience, FreeBSD hasn't agreed very well with IBM
  thinkpad laptops, unless you were using the vt0 console driver.
 
 This is *VERY* old information.  When Pentium's were introduced
 (755/560) series, it has no longer been a necessity.
 
 The old 486 laptops need vt0, but anything newer works fine with sc0.

Hmm, then I'm the lucky one :). There is an old ThinkPad 340
(486/4MB/120MB) which runs heavily trimmed down preSMPNG -current with sc
driver. The only caveat is that one should specify a flag which disables
keyboard reset, because without it machine will silently reboot. Besides
that this ThinkPad works as gateway (even with PCMCIA ethernet card)
without any problems.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: CURRENT is freezing again ...

2000-11-16 Thread Boris Popov

On Thu, 16 Nov 2000, Soren Schmidt wrote:

  After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in
  10 min after boot...
 
 You mean "is still freezing" right ?
 
 Current has been like this for longer than I care to think about, it
 seems those in charge doesn't take these problems seriously (enough)...

I think info about where/how it freezing would be more helpful.

 I've started doing development on -stable instead, it goes nowhere
 on -current

shurg - works fine for me even with my new evil hacks :)

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: NTFS patch ready to be committed

2000-11-15 Thread Boris Popov

On Wed, 15 Nov 2000, Rogier R. Mulhuijzen wrote:

 NTFS is still broken in -CURRENT
 
 I've submitted a patch to gnats (and posted about it):
 
 http://www.freebsd.org/cgi/query-pr.cgi?pr=22756
 
 I've been running it for a while now, without problems. Can someone commit it?

Yes, patch is correct and matches the one in my tree. I'll commit
it this evening if no one will do it before :)

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: nwfs problems

2000-11-03 Thread Boris Popov

On Fri, 3 Nov 2000, Andrey Rouskol wrote:

 This problem presents minimum for two weeks and but today I have connected
 a serial terminal and grabbed ddb output.

Thank you for report. Fix just committed.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: INVARIANTS and -current

2000-10-31 Thread Boris Popov

On Tue, 31 Oct 2000, Eivind Eklund wrote:

 I want to enable INVARIANTS by default in -current.  This result in some
 slowdown, but it also makes it more likely that we'll find bugs quickly.
 People that want to run -current should know enough to disable it if it is
 in the way, anyway.
 
 Well-reasoned objections welcome.

Yes, running kernel with INVARIANTS is a very good idea (in fact,
my -current setup runs it for over a year now). But this option will
produce inconsistent data structures in the kernel and modules (just like
with SMP case). While it is recommended to avoid modules on -current - I'm
don't agree with this statement because many people use them.

In any way, fix for this is very simple (it assumes that
INVARIANTS defined somewhere in the make.conf or sys.mk):

Index: conf/kmod.mk
===
RCS file: /home/ncvs/src/sys/conf/kmod.mk,v
retrieving revision 1.83
diff -u -r1.83 kmod.mk
--- conf/kmod.mk2000/09/05 22:37:46 1.83
+++ conf/kmod.mk2000/09/30 05:55:55
@@ -90,6 +90,10 @@
 CFLAGS+=   ${COPTS} -D_KERNEL ${CWARNFLAGS}
 CFLAGS+=   -DKLD_MODULE
 
+.if defined(INVARIANTS)
+CFLAGS+=   -DINVARIANTS
+.endif
+
 # Don't use any standard or source-relative include directories.
 # Since -nostdinc will annull any previous -I paths, we repeat all
 # such paths after -nostdinc.  It doesn't seem to be possible to

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



'dup alloc' panic - more details needed

2000-10-10 Thread Boris Popov

Hello,

Call to all who experienced this panic - please provide mount(8)
output for filesystem in question, so one can gather statistic about
mount/ffs options.

It seems that the one of the recent commits just disclosed a very
old bug somewhere in ffs and/or VFS.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Problems with kthread_exit() and SMPng

2000-10-05 Thread Boris Popov

Hello,

Currently I'm trying to make KLD which uses kernel threads
unloadable under recent -current. The prototype of functions looks like
this:

void
my_thread(void*arg)
{
while(wearewanted) {
do_something();
tsleep();
}
exited = 1;
kthread_exit(0);
}

void
my_unload()
{
wearewanted = 0;
while (!exited)
tsleep(1sec);
}

my_unload() function called from the module unload event which
issued from the kldunload() syscall.

Unfortunately, kernel panics in the mtx_exit_hard() function.
After some examination I've found that two fields in the Giant mutex
structure set to unexpected values:

empty mtx_blocked for mutex Giant
mtx_contested not in any list for mutex Giant


These messages printed by added diagnostics code. With this patch
(see attachment) it is possible to load and unload KLD without any
problems on UP machine except that the above messages printed. However,
I'm don't know if they are correct. (btw, 4.1 doesn't have this problem).

Any ideas why this happened and how to fix it ?
--
Boris Popov
http://www.butya.kz/~bp/


Index: synch_machdep.c
===
RCS file: /home/ncvs/src/sys/i386/i386/synch_machdep.c,v
retrieving revision 1.5
diff -u -r1.5 synch_machdep.c
--- synch_machdep.c 2000/10/04 01:20:49 1.5
+++ synch_machdep.c 2000/10/05 10:23:33
@@ -355,10 +355,16 @@
p = CURPROC;
p1 = TAILQ_FIRST(m-mtx_blocked);
MPASS(p-p_magic == P_MAGIC);
-   MPASS(p1-p_magic == P_MAGIC);
-   TAILQ_REMOVE(m-mtx_blocked, p1, p_procq);
+   if (p1) {
+   MPASS(p1-p_magic == P_MAGIC);
+   TAILQ_REMOVE(m-mtx_blocked, p1, p_procq);
+   } else
+   printf("empty mtx_blocked for mutex %s\n", 
+m-mtx_description);
if (TAILQ_EMPTY(m-mtx_blocked)) {
-   LIST_REMOVE(m, mtx_contested);
+   if (m-mtx_contested.le_prev != NULL)
+   LIST_REMOVE(m, mtx_contested);
+   else
+   printf("mtx_contested not in any list for mutex %s\n", 
+m-mtx_description);
atomic_cmpset_int(m-mtx_lock, m-mtx_lock,
  MTX_UNOWNED);
CTR1(KTR_LOCK, "mtx_exit: 0x%p not held", m);
@@ -373,12 +379,15 @@
if (pri  p-p_nativepri)
pri = p-p_nativepri;
SET_PRIO(p, pri);
-   CTR2(KTR_LOCK, "mtx_exit: 0x%p contested setrunqueue 0x%p",
-   m, p1);
-   p1-p_blocked = NULL;
-   p1-p_stat = SRUN;
-   setrunqueue(p1);
-   if ((type  MTX_NOSWITCH) == 0  p1-p_priority  pri) {
+   if (p1) {
+   CTR2(KTR_LOCK, "mtx_exit: 0x%p contested setrunqueue 0x%p",
+   m, p1);
+   p1-p_blocked = NULL;
+   p1-p_stat = SRUN;
+   setrunqueue(p1);
+   }
+   if ((type  MTX_NOSWITCH) == 0 
+   (p1 == NULL || p1-p_priority  pri)) {
 #ifdef notyet
if (p-p_flag  (P_ITHD | P_SITHD)) {
ithd_t *it = (ithd_t *)p;



RE: Problems with kthread_exit() and SMPng

2000-10-05 Thread Boris Popov

On Thu, 5 Oct 2000, John Baldwin wrote:

 You need Giant before calling kthread_exit().

Ok.

  After some examination I've found that two fields in the Giant mutex
  structure set to unexpected values:
 
 It should have died much earlier if you had INVARIANTS turned on. :(  It
 looks like you are releasing a mutex you probably do not own because
 cpu_exit() (called by exit1() - exit() - kthread_exit()) releases Giant
 as one of its final tasks.

This is probably the bug somewhere in the diagnostic code. I have
INVARIANTS/INVARIANT_SUPPORT/DIAGNOSTIC turned on and UP machine just
panics in the mtx_exit_hard() while SMP machine silently reboots :(

 This patch is bogus I'm afraid.  A contested mutex should always have a
 process waiting to grab it when it is released.

Yes, it should be bogus. But diagnostic is rather useful :)

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: IPX requires 'device random'

2000-09-29 Thread Boris Popov

On Fri, 29 Sep 2000, Kevin M. Dulzo wrote:

   I am not aware of the full status of IPX networking support in -current,
 but I migrated my -stable kernel config as best I could.  Kernel compilation
 completes, but linking fails due to a rand_ function not being present ( I do
 not have the exact error handy, but can generate for anyone who wants it.) A
 simple 'device random' to compile the support in statically rectifies the 
 problem.

Yes, 'device random' is required for now.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Fsck wrappers, revisited

2000-09-22 Thread Boris Popov

On Sat, 23 Dec 2000, Adrian Chadd wrote:

 So now is a problem which I'm sure the NetBSD people came up against.
 The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed
 this by creating a new list 'mountnames[]', which maps the fs type to
 a string.

Probably a hard link to fsck_ffs will do the job fine and makes it
clear to see which fs'es are supported:

# ls -ail fsck*
6338 -r-xr-xr-x  1 root  wheel   66032 22 ÓÅÎ 16:24 fsck
6334 -r-xr-xr-x  3 root  wheel  290896 22 ÓÅÎ 15:41 fsck_4.2BSD
6334 -r-xr-xr-x  3 root  wheel  290896 22 ÓÅÎ 15:41 fsck_ffs
6334 -r-xr-xr-x  3 root  wheel  290896 22 ÓÅÎ 15:41 fsck_ufs

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Fsck wrappers, revisited

2000-09-22 Thread Boris Popov

On Sat, 23 Dec 2000, Adrian Chadd wrote:

 On Fri, Sep 22, 2000, Boris Popov wrote:
  On Sat, 23 Dec 2000, Adrian Chadd wrote:
  
   So now is a problem which I'm sure the NetBSD people came up against.
   The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed
   this by creating a new list 'mountnames[]', which maps the fs type to
   a string.
  
  Probably a hard link to fsck_ffs will do the job fine and makes it
  clear to see which fs'es are supported:
  
  # ls -ail fsck*
  6338 -r-xr-xr-x  1 root  wheel   66032 22 sen 16:24 fsck
  6334 -r-xr-xr-x  3 root  wheel  290896 22 sen 15:41 fsck_4.2BSD
  6334 -r-xr-xr-x  3 root  wheel  290896 22 sen 15:41 fsck_ffs
  6334 -r-xr-xr-x  3 root  wheel  290896 22 sen 15:41 fsck_ufs
 
 The trouble is that some of the FS strings have spaces in their filenames.
 This might confuse a few people.

These (and probably other confusing) characters can be replaced
with underscores without much harm.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: New Fatal trap in Current SMP (random.dev changes ??)

2000-09-10 Thread Boris Popov

On Sun, 10 Sep 2000, John Baldwin wrote:

  I think the random dev kicks in at this point
  
  Fatal trap 12: page fault while in kernel mode
  cpuid = 1; lapic.id = 0c00
  fault virtual address = 0x2c
  fault code  = supervisor read, page not present
  instruction pointer = 0x8:0xc014f280
  stack pointer   = 0x10:0xc9a74f84
  frame pointer   = 0x10:0xc9a74f9c
  code segment= base 0x0, limit 0xf, type 0x1b
  = DPL 0, pres 1,def 32 1,gran 1
  processor flags = interrupt enabled, resume, IOPL = 0
  current process = 2 (random)
  trap number = 12
  panic: page fault
  cpuid = 1; lapic.id = 0x00
  boot() called on cpu#1
  
  syncing disks...
  
  The machine then is frozen and needs a reset to work again
  the debugger is unavailable
 
 ddb works fine here with this new trap, but I can't get remote gdb to work
 to save my life.  I think that remote gdb must not like me or something.

Yes, after trap is occured ddb works. But it is impossible to
continue from ddb because after typing 'center' machine becomes frozen.
The same thing occur after any other panic (this is with SMP kernel).

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



devfs patch for review

2000-08-26 Thread Boris Popov

Hello,

I've made some fixes in the fs layer of new devfs. First version
of this patch was passed via Poul and new version includes parts of his
suggestions.

Here is a brief decription of the patch:

Rename de_dir to de_parent with appropritate code changes.
Implement proper logic and locking in the devfs_lookup().
Fix behaviour for '.' and '..' directories with corresponding changes
in the devfs_readdir().
Implement devfs_read() operation for directories.
Return proper mount owner in the devfs_statfs().
Fix panic related to the incorrect handling of root vnode.
Few cosmetic changes as well.

Code is still not SMP safe.

--
Boris Popov
http://www.butya.kz/~bp/


Index: devfs.h
===
RCS file: /home/ncvs/src/sys/fs/devfs/devfs.h,v
retrieving revision 1.2
diff -u -r1.2 devfs.h
--- devfs.h 2000/08/24 15:36:47 1.2
+++ devfs.h 2000/08/26 12:28:52
@@ -48,10 +48,12 @@
 #defineDE_ORPHAN   0x1
 #defineDE_DOT  0x2
 #defineDE_DOTDOT   0x4
-   struct dirent *de_dirent;
+   int de_type;
+   char *  de_name;
+   int de_namelen;
TAILQ_ENTRY(devfs_dirent) de_list;
TAILQ_HEAD(, devfs_dirent) de_dlist;
-   struct devfs_dirent *de_dir;
+   struct devfs_dirent *de_parent;
int de_links;
mode_t  de_mode;
uid_t   de_uid;
@@ -68,7 +70,6 @@
 };
 
 struct devfs_mount {
-   struct vnode*dm_root;   /* Root node */
struct devfs_dirent *dm_rootdir;
struct devfs_dirent *dm_basedir;
unsigneddm_generation;
@@ -84,6 +85,7 @@
 
 
 #define VFSTODEVFS(mp) ((struct devfs_mount *)((mp)-mnt_data))
+#define VNTODEVFS(vp)  ((struct devfs_dirent *)(vp)-v_data)
 
 extern vop_t **devfs_vnodeop_p;
 extern vop_t **devfs_specop_p;
@@ -93,6 +95,9 @@
 void devfs_purge __P((struct devfs_dirent *dd));
 struct devfs_dirent * devfs_vmkdir __P((char *name, int namelen,
 struct devfs_dirent *dotdot));
+int devfs_allocv(struct devfs_dirent *de, struct mount *mp, struct vnode **vpp,
+   struct proc *proc);
+
 #endif /* DEVFS_INTERN */
 
 typedef void (*devfs_clone_fn) __P((void *arg, char *name, int namelen, dev_t 
*result));
Index: devfs_devs.c
===
RCS file: /home/ncvs/src/sys/fs/devfs/devfs_devs.c,v
retrieving revision 1.3
diff -u -r1.3 devfs_devs.c
--- devfs_devs.c2000/08/24 15:36:47 1.3
+++ devfs_devs.c2000/08/26 11:49:49
@@ -46,16 +46,13 @@
 {
int i;
struct devfs_dirent *de;
-   struct dirent d;
 
-   d.d_namlen = namelen;
-   i = sizeof (*de) + GENERIC_DIRSIZ(d);
+   i = sizeof (*de) + namelen + 1;
MALLOC(de, struct devfs_dirent *, i, M_DEVFS, M_WAITOK);
bzero(de, i);
-   de-de_dirent = (struct dirent *)(de + 1);
-   de-de_dirent-d_namlen = namelen;
-   de-de_dirent-d_reclen = GENERIC_DIRSIZ(d);
-   bcopy(name, de-de_dirent-d_name, namelen + 1);
+   de-de_name = (char *)(de + 1);
+   de-de_namelen = namelen;
+   bcopy(name, de-de_name, namelen);
nanotime(de-de_ctime);
de-de_mtime = de-de_atime = de-de_ctime;
de-de_links = 1;
@@ -63,36 +60,23 @@
 }
 
 struct devfs_dirent *
-devfs_vmkdir(char *name, int namelen, struct devfs_dirent *dotdot)
+devfs_vmkdir(char *name, int namelen, struct devfs_dirent *parent)
 {
-   struct devfs_dirent *dd;
struct devfs_dirent *de;
 
-   dd = devfs_newdirent(name, namelen);
+   de = devfs_newdirent(name, namelen);
 
-   TAILQ_INIT(dd-de_dlist);
+   TAILQ_INIT(de-de_dlist);
 
-   dd-de_dirent-d_type = DT_DIR;
-   dd-de_mode = 0755;
-   dd-de_links = 2;
-   dd-de_dir = dd;
-
-   de = devfs_newdirent(".", 1);
-   de-de_dirent-d_type = DT_DIR;
-   de-de_dir = dd;
-   de-de_flags |= DE_DOT;
-   TAILQ_INSERT_TAIL(dd-de_dlist, de, de_list);
-
-   de = devfs_newdirent("..", 2);
-   de-de_dirent-d_type = DT_DIR;
-   if (dotdot == NULL)
-   de-de_dir = dd;
-   else
-   de-de_dir = dotdot;
-   de-de_flags |= DE_DOTDOT;
-   TAILQ_INSERT_TAIL(dd-de_dlist, de, de_list);
+   de-de_type = DT_DIR;
+   de-de_mode = 0755;
+   de-de_links = 2;
 
-   return (dd);
+   if (parent) {
+   de-de_parent = parent;
+   TAILQ_INSERT_TAIL(parent-de_dlist, de, de_list);
+   }
+   return (de);
 }
 
 static void
@@ -125,7 +109,6 @@
FREE(dd, M_DEVFS);
 }
 
-
 int
 devfs_populate(struct devfs_mount *dm)
 {
@@ -145,7 +128,7 @@
continue;
}
if (dev == NULL  de != NULL) {
- 

Re: PATCH: devfs mkIII test review please.

2000-08-26 Thread Boris Popov

On Fri, 18 Aug 2000, Poul-Henning Kamp wrote:

 Missing:
 Rename
 Subdirs.
 Close some race conditions using guaranteed atomic operations.
 Mountoption (ro ?) to prevent new devices from appearing in an instance.
 All uses of cdevsw_add() needs to be use devfs_clone() instead.

How should 3rd party KLDs implement cloning function ? For now it
seems to be impossible to use a single binary for DEVFS and non-DEVFS
case.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: official devfs patch for review

2000-08-26 Thread Boris Popov

On Sat, 26 Aug 2000, Poul-Henning Kamp wrote:

 This incorporates the functional bits from the patch Boris posted
 here earlier as I've been able to extract them from his patch.

No, not all bits are incorporated. At least you've missed two
important things. First:

# cd /dev/fd
# ls
0   1   2
# cd ..
# ls
0   1   2

And second - directory names supplied by readdir() function
contains junk characters at the end.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: kernel hash table implementation?

2000-08-25 Thread Boris Popov

On Fri, 25 Aug 2000, Archie Cobbs wrote:

 Is there a generic hash table implementation in the kernel somewhere?

Yes, see kern/kern_subr.c for hashinit() function.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Patch test review: vop_stdaccess()

2000-08-16 Thread Boris Popov

On Wed, 16 Aug 2000, Poul-Henning Kamp wrote:

 Please test and review this patch:
 
 http://phk.freebsd.dk/patch/vop_stdaccess.patch

Looks fine to me except vop_stdaccess() itself. Since VREAD,
VWRITE and VEXEC bits are carefully layed this function can be rewritten
to use single shift operation instead of 3 'or's:

if (cred-cr_uid != uid) {
amode = 3;
if (!groupmember(gid, cred))
amode = 3;
}
return (fmode  amode) == amode ? 0 : EACCES;

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: randomdev entropy gathering is really weak

2000-07-16 Thread Boris Popov

On Sun, 16 Jul 2000, Mike Smith wrote:

 The problem is that the randomdev stuff should be a delete option, ie. it 
 should be built as part of the kernel unless EXPLICITLY excluded, not the 
 wrong way around as it is at the moment.

Exactly, randomdev should be compiled-in by default. This way it
will make much less problems than it does now.

--
Boris Popov



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: smbfs problem

2000-07-13 Thread Boris Popov

On Sun, 9 Jul 2000, A G F Keahan wrote:

 I have a strange problem with smbfs, where the mounted share times out
 and becomes inaccessible after a period of time.  I haven't been able to
 pinpoint the exact moment when it happens, but basically:

This was a bug in the processing of keep-alive packets - fixed.

 Also, smbutil doesn't seem to work:
 
 hightemplar:~$ smbutil view //alex@pluto
 smbutil: can't get handle to requester
 smbutil: could not login to server PLUTO: syserr = Invalid argument

You have to change permissions for the /dev/net/nsmb0 device to
give access to plain users (no devfs yet).

New version (1.2.4) can be downloaded from
ftp://ftp.butya.kz/pub/smbfs/smbfs.tar.gz

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: New version of TAP driver for FreeBSD -current

2000-07-10 Thread Boris Popov

On Mon, 10 Jul 2000, Yevmenkin, Maksim N, CSCIO wrote:

 Long time back i sent request to the list and asked about including this
 driver into the source tree. i still did not receive any reply. Some people
 seems to be using this driver for Ethernet tunneling (with VTUN software).
 Somebody even requested for OpenBSD port. So it would be really nice to
 hear from one of the commiters.

You might want to post request for review to the net@ list. If
inclusion of if_tap driver will be considered as reasonable I can bring it
in the tree.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: /sys hierarchy

2000-07-05 Thread Boris Popov

On Wed, 5 Jul 2000, John Baldwin wrote:

 Here is my proposal, adjusted a little as per suggestions.  It attempts to
 follow these loose guidelines:
 
 - MD code under sys/${MACHINE_ARCH}
 - device drivers (including bus's such as cam and usb) under sys/dev
 - file systems under fs/
 - networking under net/

I would like also suggest a directory for optional kernel
interfaces which doesn't belong to drivers (syscall and sysctl extensions
for example) and can't go under sys/dev/. They can be considered as
'kernel libraries' and may live under sys/lib directory (it should be
organized as sys/dev, eg. one directory per interface).

Comments ?

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: /sys hierarchy

2000-07-05 Thread Boris Popov

On Wed, 5 Jul 2000, John Baldwin wrote:

  I would like also suggest a directory for optional kernel
  interfaces which doesn't belong to drivers (syscall and sysctl extensions
  for example) and can't go under sys/dev/. They can be considered as
  'kernel libraries' and may live under sys/lib directory (it should be
  organized as sys/dev, eg. one directory per interface).
  
  Comments ?
 
 OpenBSD has a precedent for this with sys/lib containing libkern, libz,
 and some other library.  Boris has a libiconv that he needs to import
 for
 Netware stuff if I'm correct.  If we deem that it needs to go in the
 kernel,
 then I can add sys/lib to the list.

It will be shared by both smbfs and nwfs. One also can convert
msdosfs to use it too.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: smbfs second mount

2000-06-20 Thread Boris Popov

On Sun, 18 Jun 2000, kit wrote:

 On Freebsd 4.0-Release
 I am trying the smbfs-1.2.1 to mount a couple of NT shares so
 that I can read some files and copy them to a web server.  
 
 The problem I am having is that the second mount kills the first.

Ok, this problem fixed along with others NT related things. An
updated version (1.2.2) can downloaded from

ftp://ftp.butya.kz/pub/smbfs/smbfs.tar.gz

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: smbfs second mount

2000-06-20 Thread Boris Popov

On Sun, 18 Jun 2000, Brandon D. Valentine wrote:

 Out of curiosity, are there any plans to commit the smbfs stuff?  It is
 really useful and I'd love to see it in the base system.

Yes, I'm get much more responses about smbfs compared to nwfs. So,
probably it should be in the base system.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: smbfs second mount

2000-06-18 Thread Boris Popov

On Sun, 18 Jun 2000, kit wrote:

 The problem I am having is that the second mount kills the first.
 
 
 then on ls BP I get 
 ls: BP: Broken pipe

Thats strange, I have four smbfs mounts on my machine.

 I thought that that might be because I had only 1 device entry in 
 /dev/net so I did 

No, device entry used only at the mount time and freed when
mount_smbfs command terminated.

 Which didn't help.  What else should I check or try to get more
 than one concurent smbfs mounted?

Please send the output of 'smbutil -v lc' and 'df' commands
to me. Exact version of NT server and SP number will be also useful.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: mktemp() patch

2000-06-09 Thread Boris Popov

On Thu, 8 Jun 2000, Kris Kennaway wrote:

  Count both, nwfs and smbfs, because any program can attempt to
  create temporary file on these filesystems. File with an invalid file name
  will be rejected, and this will cost an additional lookup operation(s).
 
 I'm not sure that weird filesystems are a valid argument against mktemp()
 naming - there are LOTS of UNIX code which assumes UNIX namespace
 conventions, and it's not just mktemp() which is going to break on weird
 filesystems. For example, should we limit all FreeBSD file names to 8.3
 single-case in case someone wants to run from an old-style MSDOS
 partition?

Well, nwfs and smbfs filesystems usually used when one need to
integrate FreeBSD machine in the already existing environment. So, the
question is simple - do we need to help interoperability or not ?

8.3 format filenames are probably obsolete, and there is no reason
to support them because nearly all server platforms support long file
names.
 
 Basically, I think the answer is not to use a nwfs or smbfs filesystem as
 your TMPDIR :-)

With mktemp() function you can create tempoary files anywhere, not
just in TMPDIR.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: mktemp() patch

2000-06-08 Thread Boris Popov

On Thu, 8 Jun 2000, John LoVerso wrote:

  Symbols '=' and '+' are prohibited in some other filesystems.
 
 Specific examples of filesystems supported by FreeBSD and likely used by
 programs invoking mktemp(), please!  (I'm not sure that the NetWare filesystem
 counts!)

Count both, nwfs and smbfs, because any program can attempt to
create temporary file on these filesystems. File with an invalid file name
will be rejected, and this will cost an additional lookup operation(s).

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: mktemp() patch

2000-06-07 Thread Boris Popov

On Wed, 7 Jun 2000, Kris Kennaway wrote:

 This patch was developed by Peter Jeremy and myself and increases the
 number of possible temporary filenames which can be generated by the
 mktemp() family, by more densely encoding the PID and using a larger set
 of characters to randomly pad with.
 
 Instead of using only alphabetic characters, the patch uses the following
 character set:
 
 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~

Symbols '=' and '+' are prohibited in some other filesystems. It
is possible to avoid using them ?

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: SMP + APM = panic - fixed!

2000-06-06 Thread Boris Popov

On Wed, 7 Jun 2000, Mitsuru IWASAKI wrote:

 We're having this problem for long time (from the old 4.0-CURRENT
 days), but Mr. SUMITANI discovered a bug and fixed it.
 The problem was that we got worng gdt pointer for the current cpu,
 then panic...
 The followings is a patch to fix the problem.  Thanks a lot, SUMITANI-san!

Yes, this fixes panic and even 'halt -p' works as expected. 'zzz'
command works too, but machine never come back from the suspend mode
(looks like interrupt controller programmed incorrectly or something
like this).

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: vmware1/linux broken

2000-06-03 Thread Boris Popov

On Sat, 3 Jun 2000, Julian Elischer wrote:

 kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon.ko: Exec
 format error
 kldload: can't load /usr/local/lib/vmware/lib/modules/vmnet.ko: Exec
 format error
 vmware.sh: cannot create /dev/vmnet1: no such device or address
 jules# dmesg
 [...]
 link_elf: symbol linux_ioctl_register_handler undefined
 link_elf: symbol linux_ioctl_register_handler undefined
 jules# 

Could you check if vmmon and vmnet sources contains the following
lines:

MODULE_DEPEND(vmmon, linux, 1, 1, 1); , and
MODULE_DEPEND(vmnet, linux, 1, 1, 1); respectively ?

If not, add one line to the each module and recompile them. I'm
unsure if vmware1 port was updated to reflect recent changes in the
kernel. (vmware2 runs fine for me, the only grief is that license will
expire soon :)

 the symbols are present and the linux module is loaded.
 link-elf is just incapable of seeing symbols in the module, 
 only in the actual kernel.

The symbols looked up in the module name space only if dependency
tag is present. This effectively allows us to have multiple versions of
kernel interfaces to be loaded simultaneously.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Anyone else seeing jumpy mice?

2000-05-23 Thread Boris Popov

On Tue, 23 May 2000, Bruce Evans wrote:

 The patch seems to have completely broken fast interrupts.
 GET_FAST_INTR_LOCK is neither necessary nor sufficient as far as I can see.
 The necessary and sufficient locking is done by COM_LOCK() in individual
 drivers.  The patch changed GET_FAST_INTR_LOCK from s_lock(fast_intr_lock),
 which does nothing very well, to `sti(); get_mplock(); cli();', which
 essentially de-prioritizes "fast" interrupts from "higher than the highest"
 (higher than clock interrupts which are nominally highest) to "lower than
 the lowest" (lower than all normal interrupts, all software interrupts,
 and all MP-unsafe syscalls).

Yes, this explains problems with sio.

 Untested fix:

Thank you. It works and no crashes experienced yet.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



HEADS UP: loader updated to handle module metadata

2000-05-01 Thread Boris Popov

Loader was updated to handle module metadata which was introduced
by recent updates in kernel linker. This is related to a new way of
declaration of module dependencies.


--
Boris Popov



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: kernel breakage in ng_base.c

2000-04-30 Thread Boris Popov

On Sun, 30 Apr 2000, Gary Jennejohn wrote:

 Here's a simple patch which works for me.

This patch is not 100% correct. ng_base should make an attempt to
load module, not KLD. There was a new module_load() function proposed to
inclusion in the API, but for some reason it is not committed yet.

--
Boris Popov



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: kernel breakage in ng_base.c

2000-04-30 Thread Boris Popov

On Sun, 30 Apr 2000, Jeroen Ruigrok van der Werven wrote:

 -On [2430 16:50], Boris Popov ([EMAIL PROTECTED]) wrote:
  This patch is not 100% correct. ng_base should make an attempt to
 load module, not KLD. There was a new module_load() function proposed to
 inclusion in the API, but for some reason it is not committed yet.
 
 When Peter committed this all he had worked a few days untill too early
 in the morning.

I should correct myself: this function exists, but declared as
static and called linker_load_module(). Gary, you may try to use it:

linker_load_module(name, NULL);

--
Boris Popov



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: SMP changes and breaking kld object module compatibility

2000-04-25 Thread Boris Popov

On Tue, 25 Apr 2000, Jake Burkholder wrote:

 Has anyone thought about using kobj(9) for this?
 
 For example, it should be possible to make simple_lock and lockmgr locks
 safe for use from modules by introducing a lock_if.h, which has
 abstract version of all the lock routines.  A class would be compiled
 with null implementations for UP, or the 'lock'ed implementations for SMP.

kobj is a nice interface (I'm converted my NLS kernel module to
use it), but may be unsuitable for lock family functions due to an
additinal overhead invloved in the method call. I think that the
empty-body functions will be more efficient in this case.

--
Boris Popov



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: buildworld broken

2000-04-24 Thread Boris Popov

On Tue, 25 Apr 2000, Alexander Matey wrote:

 Cvsupped 2 hours ago:
 
 ...
 === sys/modules/syscons/fire
 @ - /usr/src/sys
 machine - /usr/src/sys/i386/include
 rm -f .depend
 mkdep -f .depend -a   -nostdinc -I/usr/src/sys/modules/syscons/fire/.. -D_KERNEL 
-DKLD_MODULE -I- -I/usr/src/sys/modules/syscons/fire/.. -I. -I@ -I@/../include 
-I/usr/obj/usr/src/i386/usr/include  /usr/src/sys/modules/syscons/fire/fire_saver.c
 /usr/src/sys/modules/syscons/fire/fire_saver.c:44: machine/random.h: No such file or 
directory
 mkdep: compile failed
 *** Error code 1

I've stepped on it too and fix is just committed.

--
Boris Popov



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: SMP changes and breaking kld object module compatibility

2000-04-24 Thread Boris Popov

On Tue, 25 Apr 2000, Bruce Evans wrote:

  Given that this is a change in splxxx() I suspect that it breaks
  most modules, but probably not all modules.  A quick grep -l spl * | wc
 
 Given that this is a change in the splxxx() implementation, it breaks
 zero modules.
 
 splxxx() was changed from an inline function to an ordinary function
 when SMP development started, to give the same ABI for the SMP case as
 for the non-SMP case.  This gives the same ABI for different SMP
 implementations as a side effect.

simple_lock* functions has breakage too. They defined as macros
for non-SMP case and as functions for SMP.

--
Boris Popov



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Recent commit changes extattr backing file format, users beware

2000-04-19 Thread Boris Popov

On Wed, 19 Apr 2000, Robert Watson wrote:

 I hope not to change the format any further.  I've been considering
 introducing a backing file header version number of some sort, but this is
 only necessary if we think the backing file format will change much more.

I'm vote for the version number at the begining of file header.
You may wish to change a header, change file layout etc., because extattr
support is just born and should reserve a way to grow.

In addition, it allows to write a simple 'extattrupgrade' utility
which will make above tasks more transparent to the end users.
(extattrdowngrade also may have some use :)

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: FreeBSD Build status

2000-04-18 Thread Boris Popov

On Tue, 18 Apr 2000, Poul-Henning Kamp wrote:

 In message [EMAIL PROTECTED], Peter Jeremy write
 s:
 
 IMHO, it's not such a bad idea.  freebsd-current _is_ the place to
 report problems with -current, why can't the report be produced by a
 daemon?  All the MUA's I've ever used allowed me to delete a mail
 before reading all of it, so I don't see that having detailed
 information (at the end) is a real issue (though it might be for
 someove paying by the byte).
 
 I agree.

As one of those who pays for an incoming traffic I'm prefer a
short letter with a list of directories where warning/errors happens and
an URL with full listing.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: [mount_nwfs] Got it!! But ...

2000-02-17 Thread Boris Popov

On Thu, 17 Feb 2000, The Hermit Hacker wrote:

 Great, finally figured out what I was missing for the mount_nwfs command

congrats...

 How do I get it to automount on reboot?  From what I can tell, you have to
 be root to do it ... but, you have to enter a passwd when you do it this
 way, so its not something you can add to /etc/fstab when a machine reboots

fstab(5) entries can be used to specify options for connection and
should be marked as 'noauto' (see man mount_nwfs(8)). Please take a look
at /usr/share/examples/nwclient/nwfs.sh.sample file. Line 14 of it sets
and exports HOME variable. Nothing prevents you to set this variable to
"/home/fred" and call mount_nwfs with "-O fred" argument. Of course, fred
has to specify NetWare password in his .nwfsrc file.

 So farr as I can tell, this is great for a single-user environemnt, but
 not multi-user, but it could just be a doc I'm missing ...

I've got reports where ncplib supports more than 10K users.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Mounting Netware drive onto 4.0-CURRENT ...

2000-02-17 Thread Boris Popov

On Thu, 17 Feb 2000, The Hermit Hacker wrote:

 Okay, tried that, still no go:
 
 athena:/home/kerri ncplogin -S admin -U .kerri.admin.acadia
 Warning: no cfg files found.
 Netware password:
 ncplogin: Could not login to server ADMIN: nwerr = 89f0
 athena:/home/kerri

NDS and NDS names are not supported by current implementation.
Thats why I'm told about bindery context before. If user "kerri" is in the
bindery context then "-U kerri" will work.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: [mount_nwfs] Got it!! But ...

2000-02-17 Thread Boris Popov

On Thu, 17 Feb 2000, Dan Nelson wrote:

  I've looked at the man page and the .nwfsrc file, but there is a
  'flaw' there, and that is what does one do in a multi-user
  environment, where I want to mount n users netware drives to the
  system on reboot? they have to give me their netware passwords?
 
 This is where Terry joins in, and talks about per-user credentials. 
 The problem is that the unix mount style (mount as root, and limit
 access on the client as users access files) doesn't mesh well with the
 Netware/SMB model (one independant mount per user).

Yeah, this problem exists. Someone with good design and
programming skills really should sit down and write session manager.

While this isn't done I've made some workarounds in the ncplib to
achieve same goals:

Connection to netware server have the same the same attributes as
file, eg. access mode, owner id, group id. This allows to make private
conections which is not visible to other users.

Since there is no way to ask user about password at boot time,
there is a 'password' variable which works as persistent password "cache".
There is also another way to do that, I'm calling it as "lazy mounts". If
mount point is marked as "lazy" then it mounted on boot as normal mount
but no netware login is performed and user sees typical SYS:LOGIN files.
After that, user can issue an "mount_nwfs /home/fred/nwmount" command and
enter password at promt. May be this method will be implemented in the
next version of ncplib.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Mounting Netware drive onto 4.0-CURRENT ...

2000-02-16 Thread Boris Popov

On Wed, 16 Feb 2000, The Hermit Hacker wrote:

 Okay, now I'm getting somewhere, but where I don't know :(  set the
 ifconfig, run IPXrouted, and netstat -nr tells me a bunch of stuff about
 IPX ... great, that appeasr to be up, but I get errors with ncplogin, so
 obviously I'm missing something (and wihtout the search of archives, this
 is the most embarressing and painful way of doing this *sigh*) ...
[skip]

 athena# ncplogin -S admin.acadiau.ca -U marc
 Warning: no cfg files found.

"admin.acadiau.ca" looks like a DNS record. If this server is a
netware 5.x one, then you can use "-S admin -A admin.acadiau.ca" options
and netware client will use UDP protocol. Otherwise, I'm suspect that
command line should look like this:

ncplogin -S admin -U marc

Please note, that user "marc" should be in the bindery context.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: kldload: can't load ncp: Exec format error

2000-02-11 Thread Boris Popov

On Fri, 11 Feb 2000, The Hermit Hacker wrote:

 atelier# kldload ncp
 kldload: can't load ncp: Exec format error
 atelier# ls -lt /modules/ncp.ko

ncp module compiled by default with IPX and UDP protocols support.
So, the possible cause of the above is the missing 'options IPX' line in
the kernel configuration file.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: NCP in 4.0-CURRENT ...

2000-02-11 Thread Boris Popov

On Fri, 11 Feb 2000, The Hermit Hacker wrote:

 Ignoring /modules/ncp.ko for now, I've enabled 'options NCP' in the
 kernela and recompiled ... is there anything else I have to do to get this
 to work?  I'd search the archives for this, but they are still down ... a

It depends. If you're need to mount volumes from netware server,
'options NWFS' line is also required. If netware server has only IPX
prtocol support (3.x, 4.x and possibly 5.x) then you're need 'options IPX'
line too. Don't forget to configure ipx protocol on the appropriate
ethernet interface (ifconfig ed0 ipx 0x37829BE for example) and enable
IPXrouted daemon.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: boot stops after Mounting root from ufs:/dev/ad0s2a

1999-12-08 Thread Boris Popov

On Mon, 6 Dec 1999, Kelvin Farmer wrote:

 Problem: Computer _sometimes_ stops after the "Mounting root from
 ufs:/dev/ad0s2a" line.
 Running Current, built world yesterday. (Problem appeared fairly
 recently (as in ~2 weeks?, but didn't have ddb in previous kernel)

I can confirm that behaviour of new ata driver. This happens one
time per 5-6 reboots. In addition, machines with VIA chipset work fine,
but all machines with i440BX chipset suffer from this problem:

pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard
pci0: PCI bus on pcib0
pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
vga-pci0: Rendition Verite V2000 SVGA controller irq 16 at device 0.0 on
pci1
isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
ata-pci0: Intel PIIX4 IDE controller at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
...
ad0: ST34321A/3.29 ATA-4 disk at ata0 as master
ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 1 depth queue, UDMA33
ad1: IBM-DJNA-371350/J76OA30K ATA-4 disk at ata1 as master
ad1: 12949MB (26520480 sectors), 26310 cyls, 16 heads, 63 S/T, 512 B/S
ad1: 16 secs/int, 32 depth queue, UDMA33

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: mount_nfs broken

1999-11-28 Thread Boris Popov

On Sun, 28 Nov 1999, Mark Murray wrote:

  Could you be more specific?  It seems to work for me (I removed 
  /var/db/mounttab and tried it with a new build and it did work).
 
 Damn. I screwed up the reporting bigtime.
 
 It is mount_nfs, and there is mention of mounttab.c in the Makefile,
 but no mounttab.c anywhere in the source tree.

this file located in the src/usr.sbin/rpc.umntall/ directory.
However common things should go in the library.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: loader.conf, ordering of loading of modules

1999-11-28 Thread Boris Popov

On Sun, 28 Nov 1999, Nick Hibma wrote:

 There are symbols in usb.ko that are needed by uhci.c . I know it is
 stupid, but that's the way it is, without a complete rewrite of the USB 
 stack.

You can define module dependency in the uhci module Makefile:
KMODDEPS=usb

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Texas Chainsaw Monday

1999-10-25 Thread Boris Popov

On Fri, 22 Oct 1999, Bill Paul wrote:

   install -c -s -o root -g wheel -m 555   mount_nwfs /vol2/release/sbin
   install: mount_nwfs: No such file or directory
  
  Ok, it seems that I found why mount_nwfs failed to build: I'm use
  'install' instead of ${INSTALL} in the libncp.
 
 Unfortunately, this has not fixed the problem: the build report for
 today (Oct 22) shows the same error.

Well, today (Oct 25) I've done my own 'make release' and it wents
fine (fix for netgraph.h sent to Julian). I think that the error message
that you saw, was caused by first 'installworld' - source tree was updated
but not rebuiled and 'make world' even didn't happens.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Texas Chainsaw Monday

1999-10-20 Thread Boris Popov

On Wed, 20 Oct 1999, Bill Paul wrote:

 install -c -s -o root -g wheel -m 555   mount_nwfs /vol2/release/sbin
 install: mount_nwfs: No such file or directory

Ok, it seems that I found why mount_nwfs failed to build: I'm use
'install' instead of ${INSTALL} in the libncp.

 Can somebody please explain this to me? The fact that mount_nwfs doesn't
 exist seems to indicate that compiling mount_nwfs failed. Yet if compiling
 mount_nwfs failed, why didn't it stop at the compilation failure?

Yep, that strange why build isn't failed.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: make buildworld break @ kdump

1999-10-14 Thread Boris Popov

On Thu, 14 Oct 1999, Marc van Woerkom wrote:

 It keeps interesting.
 
 /usr/obj/usr/src/tmp/usr/include/nwfs/nwfs_mount.h:61: `NCP_VOLNAME_LEN' 
undeclared here (not in a function)
 /usr/obj/usr/src/tmp/usr/include/nwfs/nwfs_mount.h:61: size of array 
`mounted_vol' has non-integer type

That was caused by my commits. Probably they should be done in one
transaction and you was 'lucky' enough to catch it :). Now it builds fine.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Bad reference to zname in vm_zone struct

1999-06-30 Thread Boris Popov

Hello,

Here is a 'little' problem with vm_zone structure and field
'zname' in it.

zinit() function takes a pointer to name of zone and assigns it to
field zname. Since nfs module defines this name in the static module
memory pointer to name becomes invalid when module unloaded via kldunload 
command. This will lead to trap in kernel or will produce junk in sysctl
output:

# kldload nfs
# kldunload nfs
# sysctl vm.zone

Last command will produce panic. This has been reported as
PR-kern/12464

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message