Re: keymaps
my vote: A version of the standard keymap with CapsLock and LeftCtl functio ns swapped so the control key is under my left finger like God intended! My vote is both of the above. I've never found a use for CapsLock, but LeftCtl is important enough that I wouldn't mind it duplicated. Most people I know are like this. (Yes of course there needs to be a way to get at capslock for those who really need it) I understand many of you prefer the Ctrl key sitting next to the 'A' key, as my own keymap swaps the Caps key and the Left Ctrl key too :-) But, this is a matter of personal taste and preference which you can easily obtain by editing a keymap. Gentlemen, I don't intend to add yet another keymap to /usr/share/syscons/keymaps. I am merely trying to define a reasonable set of common, consistent key binding for existing keymaps. National keyboards have different layout of regular keys. But function keys and special keys are placed identically. They should work in the same way, or at least similar way in all keyboards, unless there is a good reason to do otherwise. (I am not talking about non-AT keyboards which are totally different from either AT 84 or 101/102/104 keyboards.) What I want to avoid is that one key does one thing on one national keyboard and the same key on another national keyboard does a different thing. This is absurd, and hazardous when writing document or giving advises (you can cycle through vtys by hitting PrintScreen, um, well, on most keyboards, well, on your keyboard you may need to hit a different key, I don't know which...) In order to define a common set, I start from key assignments based on existing keymaps, which may not necessarily be your, or my, favorite. (Why on earth Ctrl-Alt-ESC yields debug? Because someone started it and documented in the handbook!) New functions and their assignments can be controversial and we shall hear various opinions about them. I expect that, and we should resolve this on technical merits. (The following is an example. In my previous post I removed the backscroll function from the Pause key because the ScrollLock key already has backscroll. My reasoning was wrong. A user reported that his notebook PC doesn't have the ScrollLock key and we have to let the Pause key have backscroll too.) I don't intend to enforce preference or taste, or particular usage of, or a particular way of working with the keyboard. (I certainly won't force mine on you) So, keymaps I am trying to define may look too plain, too boring, too uninteresting, and less appealing to you. But, I am not depriving you of liberty to modify your keymap. Be creative and write a keymap of your own. You are free to do that. But, don't expect your modification should instantly be the standard in all keymaps. It won't necessarily happen... Well, it might happen, if it has sound reason other than because I like it that way :-) Kazu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Booting from 2nd IDE [Re: Experiences with aout-to-elf and new bootblocks]
I wrote: Peter Jeremy wrote: Mark Blackman t...@rcru.rl.ac.uk wrote: FWIW, I've done it under 2.2.7 by 1) installing booteasy on both wd0 *AND* wd2 2) altering the boot.config to 1:wd(2,a)kernel This works for an a.out 3.0 kernel, but the old bootloader can't handle ELF kernels, so this isn't a usable solution. The new boot blocks, installed by disklabel -B $DRIVE do handle (both a.out and) ELF kernels, despite looking very similar to the old a.out-only ones. The idea is to provide a fallback means of booting a kernel in either format. So using a /boot.config statement like the above (or hitting any key before seeing the /boot/loader prompt, to get the old boot: prompt instead), is a recommended workaround for any temporary /boot/loader problems. I should have added that, where more than one version of FreeBSD is installed on the same machine, updating the default boot disk to the latest boot blocks is also suggested. A /boot.config like 1:wd(2,a) would then pass control directly to a non-default copy of /boot/loader. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: NFS v3 issue
Matthew Dillon schrieb: :With NFS v3 there seem still to be some open issues. :Im running the latest (4.0)-current with the new vm/NFS changes. :While I haven't found any problems with NFSv2 so far, v3 still seems to make :trouble. : :I noticed the error some months ago, while my /usr/obj was NFS mounted, and :a build failed while making termcap.db. Today, I gave it another try. :I copied /usr/src/share/termcap into an NFS mounted directory and did :a make. I compared the output of termcap.db with the one build on the local :drive. :While the NFS mounted one was only 1077760 bytes in size, the correct :size (from the local build) should be 1245184 bytes. I did the build :several times, everytime I got the same values. I then remounted the :direcory NFSv2. Now the build produced the right file (in size and content). : :The NFS Server is a Solaris 7 machine. : :Can anyone else confirm this error? : :Daniel I can't help you here, but I want to make sure: The problems you are having are the same problems you were having a few months ago? ( I want to make sure I haven't introduced new problems in -4.x, and if I have to fix them ASAP! ). I am not sure if they are the same, but it seems so: A make world with /usr/obj NFS mounted worked up to the point where the termcap was built. Now only the error is slightly different: A few months ago, cap_mkdb exited with SIG 11, now it succeeds but generates the wrong file. I think it's the same bug. The SEGV maybe have gone away because of some library reordering over the months. Daniel To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Splash screen and boot -s
Hi, booting into single user mode didn`t remove the splash screen at the enter path to shell... prompt. FreeBSD 4.0-CURRENT #0: Thu Jan 21 Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: readdir cd9660 direntp-d_type == bug (more)
Hi,
attached is the source of a test program.
With the CD of my ISDN card it produces:
{0} FreeBSD 4.0-CURRENT
(15) netch...@ttyp1 ./dirtest /cdrom
/cdrom:
.(type: unknown)
.. (type: unknown)
autorun.inf (type: unknown)
cardware (type: unknown)
doku (type: unknown)
fritz.ico(type: unknown)
fritz! (type: unknown)
intro.hlp(type: unknown)
online (type: unknown)
tools(type: unknown)
winport (type: unknown)
{0} FreeBSD 4.0-CURRENT
(16) netch...@ttyp1 ls -l /cdrom
total 173
-r-xr-xr-x 1 root wheel 54 22 Mai 1998 autorun.inf
dr-xr-xr-x 1 root wheel 2048 27 Mai 1998 cardware
dr-xr-xr-x 1 root wheel 2048 27 Mai 1998 doku
dr-xr-xr-x 1 root wheel 2048 27 Mai 1998 fritz!
-r-xr-xr-x 1 root wheel766 15 Mai 1998 fritz.ico
-r-xr-xr-x 1 root wheel 75833 22 Mai 1998 intro.hlp
dr-xr-xr-x 1 root wheel 2048 27 Mai 1998 online
dr-xr-xr-x 1 root wheel 2048 27 Mai 1998 tools
dr-xr-xr-x 1 root wheel 2048 27 Mai 1998 winport
Every other CD I tried shows similar results. With ufs or msdos it
displays the correct type (dir, reg, ...).
FreeBSD 4.0-CURRENT #0: Thu Jan 21
Bye,
Alexander.
--
http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de
binmYSTwHnzqq.bin
Description: dirtest.c
Re: Promise FastTrack PCI IDE controller
On Fri, 22 Jan 1999, Søren Schmidt wrote: [snip] Yep I know, the chipset on the Promise is not initialized to what the drives support then, its working in a slow (but always working though) mode. I did plan to change this, and even got the docs for the chips but it has sunken pretty low on the TODO list lately... [snip] Having one of these cards sitting in my desk after buying it mail-order and finding out afterwards that it wasn't supported, I for one would be exceedingly happy if support for the FastTrack was added. I'd be willing to test patches for people, but I'll have to bring the system up to date, which will probably take a day or two. mela...@yip.org - For external use only. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: KVA/KVM shortages
Previously on Thu, Jan 21, 1999 at 01:53:44PM -0800, Mike Smith wrote: : On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with : 768MB RAM) poking about in the code adding: : : options VM_KMEM_SIZE=(24*1024*1024) : options VM_KMEM_SIZE_MAX=(128*1024*1024) : : seems like a good way foward. Is it? : : From what I can see, you shouldn't need to set VM_KMEM_SIZE_MAX unless : you're also setting VM_KMEM_SIZE_SCALE. : My understanding was VM_KMEM_SIZE_SCALE picks up a default of value of 3 from vmparam.h, which if I understand the following from kern-malloc.c vm_kmem_size = VM_KMEM_SIZE; mem_size = cnt.v_page_count * PAGE_SIZE; #if defined(VM_KMEM_SIZE_SCALE) if ((mem_size / VM_KMEM_SIZE_SCALE) vm_kmem_size) vm_kmem_size = mem_size / VM_KMEM_SIZE_SCALE; #endif #if defined(VM_KMEM_SIZE_MAX) if (vm_kmem_size = VM_KMEM_SIZE_MAX) vm_kmem_size = VM_KMEM_SIZE_MAX; #endif combined with the apparent defaults of VM_KMEM_SIZE 12M VM_KMEM_SIZE_SCALE 3 VM_KMEM_SIZE_MAX 80M means vm_kmem_size never gets bigger than 80M without VM_KMEM_SIZE_MAX being defined 80M (This is all from a mid december 3.x box) : I just committed a tweak that allows you to say: : : set kern.vm.kmem.size=value : : at the loader prompt or in /boot/loader.rc to override the default : VM_KMEM_SIZE value. : Unless I am being too literal or miss-understanding the above do you not need to set VM_KMEM_SIZE_MAX or have thing moved on since december? -- GeoffB To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: PNP and new bootloader with ELF kernel
On Fri, 22 Jan 1999 12:22:26 +0800, Ying-Chieh Liao wrote: you can put this pnp information in /kernel.config and, in your /boot/boot.conf, put load /kernel load -t userconfig_script /kernel.config boot Hi chaps, Try to encourage current users to use /boot/loader.rc instead. We don't want kernel.config anymore, from what I've read on this list. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make world broken in /lib
me too -DNOSECURE seems to help but it hasn't completed yet. julian me too, but figured the longer strings with the crypt -DNOSECURE makes must be better :). Anyone know of an easy or possible way to turn a DES crypted passwd file into the normal libcrypt kind? --- E-Mail: Luke l...@aus.org Sent by XFMail -- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
world broken
having spent almost an hour trying to decode the complexities of the crypt making process I admit defeat.. can SOMEBODY please fix the build in -current and sent branson a nice pointy hat.. I think he committed and went on vacation (I haven't seen any commits that say they fixed this but I'm waiting for cvsup to connect just in case I missed it...) julian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
kvm_getswapinfo() function added to libkvm. top, pstat, systat updated
A new function, kvm_getswapinfo(), has been added to libkvm. pstat, systat, and top have been updated to use the new function. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
T/TCP in FreeBSD-3.x
Hi! Has FreeBSD-3.x a correct implementation of T/TCP? There is some bug mentioned in Squid FAQ (http://squid.nlanr.net/Squid/FAQ/FAQ-14.html#ss14.2), about brokenness of T/TCP in FreeBSD-2.2.2. Why I'm asking about this, is because I recently read an advice in one of the FreeBSD mailing lists, about Why my dial-up PPP connection from a FreeBSD box is so slow comparing with Windows NT (about ten times slower)? And the advice was (without explanations): Try to switch off the TCP_EXTENSIONS in /etc/rc.conf. So, is it safe to use T/TCP (at least for Squid) for RELENG_3? RELENG_2_2? And what about MBUF size (mentioned at the same page of the Squid FAQ)? Do I need to patch Squid as it shown at the page? Thanks. -- Konstantin V. Chuguev. System administrator of Southern http://www.urc.ac.ru/~joy/ Ural Regional Center of FREEnet, mailto:j...@urc.ac.ruChelyabinsk, Russia. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: readdir cd9660 direntp-d_type == bug (more)
attached is the source of a test program.
With the CD of my ISDN card it produces:
{0} FreeBSD 4.0-CURRENT
(15) netch...@ttyp1 ./dirtest /cdrom
/cdrom:
.(type: unknown)
.. (type: unknown)
autorun.inf (type: unknown)
This is because the cd9660 file system doesn't implement d_type.
{0} FreeBSD 4.0-CURRENT
(16) netch...@ttyp1 ls -l /cdrom
total 173
-r-xr-xr-x 1 root wheel 54 22 Mai 1998 autorun.inf
ls works because it stats the file.
#define _POSIX_SOURCE
#include sys/types.h
#include dirent.h
...
while((dent_p = readdir(dir_p)))
{
printf(%-40s (type: %s)\n, dent_p-d_name, types[dent_p-d_type]);
}
This probably shouldn't compile, since d_type isn't in POSIX.1. POSIX.1
only guarantees d_name in struct dirent. Names beginning with d_ are
reserved for use in dirent.h, but FreeBSD normally attempts to give
strict POSIX.1 if _POSIX_SOURCE is defined.
Bruce
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: mountd
On Thu, 21 Jan 1999, David E. Cross wrote: I posted this awhile ago to -questions, but never received a reply. We have a number of FreeBSD NFS servers here. Occasionally we need to change the exports list on the servers and send mountd a SIGHUP. This leads to a condition that in many ways is much worse than a server reboot. What happens is for the duration of mountd reading the exports file it denies all NFS requests. This has a number of bad effects; 1) any user home and system directories become unavailable, with the error 'permission denied' 2) (and this is far worse), any process with a mapped .text segment off of the NFS server, should it branch to code not in the cache gets immediately killed. This include user processes that are running from home directories, and system processes (such as ssh). If we were to reboot the machine it would just hang those connections until the machine came back, without killing anyone. Is there a solution to this problem? I know that none of HP-UX, IRIX, or Solaris have this problem. Please submit a PR for this (if there isn't one already) so at least it can be tracked. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
World broken in RELENG_3 when making aout-to-elf bulid
Hi folks, I have recent sources (cvsup'ed today) and make aout-to-elf broken with: === usr.bin/login cc -pipe -O2 -DCOMPAT_LINUX_THREADS -DVM_STACK -m486 -Wall -DLOGIN_ACCESS -DLOGALL?? -I/usr/obj/aout/usr/obj/src/tmp/usr/include -c /usr/obj/src/usr.bin/login/login.c /usr/obj/src/usr.bin/login/login.c: In function `main': /usr/obj/src/usr.bin/login/login.c:129: warning: argument `argv' might be clobbered by `longjmp' or `vfork' cc -pipe -O2 -DCOMPAT_LINUX_THREADS -DVM_STACK -m486 -Wall -DLOGIN_ACCESS -DLOGALL?? -I/usr/obj/aout/usr/obj/src/tmp/usr/include -c /usr/obj/src/usr.bin/login/login_access.c cc -pipe -O2 -DCOMPAT_LINUX_THREADS -DVM_STACK -m486 -Wall -DLOGIN_ACCESS -DLOGALL?? -I/usr/obj/aout/usr/obj/src/tmp/usr/include -c /usr/obj/src/usr.bin/login/login_fbtab.c cc -pipe -O2 -DCOMPAT_LINUX_THREADS -DVM_STACK -m486 -Wall -DLOGIN_ACCESS -DLOGALL?? -I/usr/obj/aout/usr/obj/src/tmp/usr/include? -o login login.o login_access.o login_fbtab.o? -lutil -lcrypt login.o: Undefined symbol `_pam_start' referenced from text segment login.o: Undefined symbol `_pam_strerror' referenced from text segment login.o: Undefined symbol `_pam_set_item' referenced from text segment login.o: Undefined symbol `_pam_strerror' referenced from text segment login.o: Undefined symbol `_pam_set_item' referenced from text segment login.o: Undefined symbol `_pam_strerror' referenced from text segment login.o: Undefined symbol `_pam_authenticate' referenced from text segment login.o: Undefined symbol `_pam_get_item' referenced from text segment login.o: Undefined symbol `_pam_strerror' referenced from text segment login.o: Undefined symbol `_pam_strerror' referenced from text segment login.o: Undefined symbol `_pam_end' referenced from text segment login.o: Undefined symbol `_pam_strerror' referenced from text segment login.o: Undefined symbol `_misc_conv' referenced from data segment *** Error code 1 Stop. Any glue??? Maxim To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Using LinuxThreads
On Thu, 21 Jan 1999, Julian Elischer wrote: On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote: And when are COMPAT_LINUX_THREADS and VM_STACK going away? I have no idea. I was hoping that at least COMPAT_LINUX_THREADS would go away before the branch. I don't have commit authority, so it isn't up to me. hmm did you send me the patches? I can certainly do it now..(given a patch set to apply) I just realised however, that if we make them go away we break SMP right? hmm I guess we only break it for programs that woudltry use it which should be none if you run SMP :-) It doesn't break SMP (I'm running an SMP kernel with COMPAT_LINUX_THREADS). All that happens is that linux_clone() returns an error. Surprisingly StarOffice still works fairly well. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
kldload of procfs panics
I'm having a bit of trouble with 4.0-CURRENT as of last night. After fully
updating my system, on reboot procfs (a KLD module) panics the system as
follows: (more explanation after bt)
#9 0xf01d9c1a in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -142545460,
tf_esi = -250596864, tf_ebp = -142545512, tf_isp = -142545640,
tf_ebx = 0, tf_edx = 0, tf_ecx = 0, tf_eax = 10, tf_trapno = 12,
tf_err = 0, tf_eip = -266759770, tf_cs = 8, tf_eflags = 66134,
tf_esp = 880, tf_ss = -147665856}) at ../../i386/i386/trap.c:437
#10 0xf01991a6 in ffs_read (ap=0xf780edb0) at ../../ufs/ufs/ufs_readwrite.c:97
#11 0xf0161bbd in vn_rdwr (rw=UIO_READ, vp=0xf732cc40, base=0xf1104000 ,
len=880, offset=0x4418, segflg=UIO_SYSSPACE, ioflg=8,
---Type return to continue, or q return to quit---
cred=0xf05a0280, aresid=0xf780ee90, p=0xf7333620) at vnode_if.h:331
#12 0xf012d11f in link_elf_load_file (filename=0xf10a8d90 procfs.ko,
result=0xf780ef2c) at ../../kern/link_elf.c:635
#13 0xf012cb76 in link_elf_load_module (filename=0xf10a8d90 procfs.ko,
result=0xf780ef2c) at ../../kern/link_elf.c:340
#14 0xf012afa3 in linker_load_file (filename=0xf1104c00 procfs,
result=0xf780ef4c) at ../../kern/kern_linker.c:263
#15 0xf012b782 in kldload (p=0xf7333620, uap=0xf780ef84)
at ../../kern/kern_linker.c:655
#16 0xf01da56f in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -272638612,
tf_esi = -1, tf_ebp = -272638580, tf_isp = -142544940,
tf_ebx = -272638324, tf_edx = 99, tf_ecx = 10, tf_eax = 304,
tf_trapno = 12, tf_err = 2, tf_eip = 134517080, tf_cs = 31,
tf_eflags = 662, tf_esp = -272638620, tf_ss = 39})
at ../../i386/i386/trap.c:1100
#17 0xf01ccf2c in Xint0x80_syscall ()
#18 0x8048245 in ?? ()
#19 0x80480e9 in ?? ()
(kgdb) frame 10
#10 0xf01991a6 in ffs_read (ap=0xf780edb0) at ../../ufs/ufs/ufs_readwrite.c:97
97 if ((u_int64_t)uio-uio_offset fs-fs_maxfilesize)
(kgdb) printf %p\n, fs
0x0
Now fs is part of strucct inode in the vnode, but struct inode seems to be
TOTALLY ZERO! After rebooting, a fsck fixes all filesystems and the system
boots fine, but on any _clean_ boot, procfs panics. I have absolutely no idea
what could be causing this, but that I know procfs is the first module loaded
and if I use the boot loader to load kernel+procfs first, nothing panics (e.g.
kernfs). Anyone have an idea?
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: Promise FastTrack PCI IDE controller
I've been playing with a Promise FastTrack RAID (IDE) controller with 3.0-current as of yesterday. Although it is recognised in the PCI bus probe as a Promise Ultra/33 (it has the same vendor/chip ID as the non-RAID card), the probes in i386/isa/wd.c fail. I added some debugging printfs to the code, and have found that wdreset() is failing. By changing the code to ignore that failure, it gets further, and correctly identifies the attached disks. I can even access the disks sufficiently to read the partition table with fdisk (but with timeouts). Errors in wdreset() for the Promise (at least for the Ultra/33) probably mean that du-dk_altport is not initialized properly. (Setting du-dk_altport is the only thing that is very special for the Promise, and wdreset() is the only function that uses du-dk_altport for anything except debugging.) The wrong setting of du-dk_altport may be caused by the section of code in pci/ide_pci.c described by /* This code below is mighty bogus. Bugs there may also break DMA capability. ... promise_status: port0: 0xeff0, port0_alt: 0xefe4, port1: 0xefa8, port1_alt: 0xefe0 ... wdc2: wdd_candma is set for ide_pci1 wdc2: I/O to 0xeff0 does work wdc2: reset failed If the main block of ports is really at 0xeff0, as it probably must be since something worked, the altport is probably at port 0xefe4 and initializing du-dk_altport to this manually should fix wdreset(). ide_pci: generic_dmainit eff0:0: warning, IDE controller timing not set wd4: wdsetmode() setting transfer mode to 22 I don't see how the Promise can work right if generic_dmainit() gets called. generic_dmainit() never sets UltraDMA mode. It only sets mode 22, which is twice as slow. There is no special support for seting the IDE controller timing for the Promise, so generic_dmainit() gets called unless the BIOS has already set the IDE controller timing. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
zip drive and parallel port in NIBBLE mode hang the machine
Hello! My system is too old to have anything other then Compatable and Bi-directional modes for the parallel port. Both of this are recognized as NIBBLE-only by ppc0. When I try to cp a big file (Wordperfect distribution) onto a Zip cartridge (with ufs with softupdates) the whole system becomes jerky and soon hangs -- I can still go from one virtual console to another, but can not do anything and need cold reboot. I used to be able to use the drive during Autumn (although I only used msdos-formatted cartridges). Any ideas? Thanks! -mi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 0112-SNAP system hangs w/ incessant disk activity - softupdates related?
Attached is a DDB trace that I obtained the next morning after I posted the original message. FWIW, I've been running without softupdates now since rebooting after that crash Monday morning, and everything is running beautifully (albeit a bit more slowly) :) mounted default. I hope this can help. I hear there are a lot of these traces floating around that maybe can be pieced together. I've since switched to 3.0-STABLE (though make world isn't quite done yet), so I don't follow -current anymore -- but I figured -current would be the best place to put this so that it can be fixed in -CURRENT and backported. Thanks. On Sun, 17 Jan 1999, Matt Behrens wrote: : The system becomes totally unresponsive (console driver still seems : to be running but the processes all seem to have hung) at some : random point. The second time, I noticed my second hard drive was : going totally crazy -- sounded like a `find /' or something. :) : In both cases, I couldn't Ctrl-Alt-Del, so I rebooted. : : The first time, I didn't know what to expect -- but the standard : fsck-if-not-clean took care of my problem on reboot. I didn't : get to see many of the messages, but I did catch quite a few (and : on the tail) clearing of unref files, many owned by me. They seemed : to (and indeed did) correspond to some files that I was unpacking. : Attributing it to just running into a random bug, I re-unpacked : the files and went on. - Matt Behrens m...@zigg.com Network Administrator, zigg.com http://www.zigg.com/ Engineer, Nameless IRC Network http://www.nameless.net/ Debugger(f021f865) at Debugger+0x37 sc_alloc_history_buffer(f025267c,2,0,f025267c,7011d) at sc_alloc_history_buffer+0xcd0 scdevtotty(f025267c,0,0,0,f0612c00) at scdevtotty+0x35c atkbd_attach_unit(f025267c,0,0,f32b7e24,f01effce) at atkbd_attach_unit+0x4e7 is_physical_memory(0,c0084040,f0610010,f0130010,7011d) at is_physical_memory+0x2cc Xintr1(0,0,f01a7188,c000,0) at Xintr1+0x5e wdintr(0,c000,f0610010,10,c000) at wdintr+0x5b8 Xintr14(8000,f32b0010,f01d0010,f32b7f88,f32a6200) at Xintr14+0x61 doreti_popl_es_fault(f32b7f88) at doreti_popl_es_fault+0x49 vn_syncer_add_to_worklist(f32abbf7,f02192a5,f0230588,f01f30fs,f01ef5c0) at vn_syncer_add_to_worklist+0x13c kproc_start(f0230588) at kproc_start+0x32 fork_trampoline(e4ec1589,c766f025,25e4ee05,88f0,25e4f025) at fork_trampoline+0x30
Re: -D_REENTRANT (Was: Using LinuxThreads)
Kurt D. Zeilenga k...@openldap.org wrote: Richard Seaman, Jr. wrote: [lost attribution] Also, the cc(1) says to use -D_THREADSAFE not -D_THREAD_SAFE. Hmm. Not on my machine. :) http://www.freebsd.org/cgi/man.cgi?query=ccapropos=0sektion=0manpath=FreeBSD+3.0-currentformat=html This was changed some time after 3.0.0. http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/gcc/gcc.1 Tony. -- f.a.n.finch d...@dotat.at f...@demon.net To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: PNP and new bootloader with ELF kernel
Sheldon Hearn wrote: On Fri, 22 Jan 1999 12:22:26 +0800, Ying-Chieh Liao wrote: you can put this pnp information in /kernel.config and, in your /boot/boot.conf, put load /kernel load -t userconfig_script /kernel.config boot Hi chaps, Try to encourage current users to use /boot/loader.rc instead. We don't want kernel.config anymore, from what I've read on this list. What should have changed up there is boot.conf. The /kernel.config is, as a matter of fact, correct. The commands you place in it are, as you can see, userconfig_script, not loader script. That's why you are placing them there, not in boot.rc. -- Daniel C. Sobral(8-DCS) d...@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
WARNING: Today's current breaks passwords
This may or may not affect you. Today's installworld broke passwords for me. By that, I mean that login, xdm, su and friends gave authentication failures on all passwords for all users that I tried. I suspect this has to do with a hashing algorithm that isn't backward compatible. I used Kerberos to get into the machine as root and change important passwords to exactly what they were before. This worked. The new encrypted passwords are happy. :) I don't want to cause hysteria, and I can't guarantee that my report is accurate. All the same, do yourself a favour on your next installworld: Make SURE you have an open root session somewhere. Do NOT hide it behind xlock, and do NOT use lock(1) to keep it safe. This will allow you to passwd(1) to create new encrypted passwords for your users. If you have shell accounts that need access to the box and you don't want to have to rehash all their passwords, hold off on installworld until someone calls me a liar, or a fix is committed. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Using LinuxThreads
On Thu, Jan 21, 1999 at 07:39:28PM -0700, Russell L. Carter wrote:
d...@tar.com said:
%libc_r could be modified so that is doesn't replace libc, but rather
%is an addon, comparable to the kernel threaded libc case. But, it
%would involve a bit of work.
I thought so at first, but then I had to look at wait4 today and
now I'm not so sure. At least some of libc_r is very closely
tied to the uthread scheduler:
Sure it is. But, I don't see why that prevents the possibility of leaving
libc in place and having libc_r just be an add on (not that I'm advocating
this). Taking your example, in libc the syscall is implemented as _wait4,
and wait4 is a weak alias to _wait4. If you replaced _thread_sys_wait4
below with _wait4 instead, and put the resulting code in a library separate
from libc (eg. in a new libc_r) along with the uthread scheduling code
and the rest of the uthread pthread code, you could leave libc alone.
Then, when you linked with libc and libc_r together, the wait4 in libc_r
would override the weak aliased wait4 in libc. If you didn't link with
libc_r, you'd have your plain old wait4.
The bigger problem is that the uthread code needs two layer aliasing
in order to implement pthread cancellation.
pid_t
wait4(pid_t pid, int *istat, int options, struct rusage * rusage)
{
pid_t ret;
/* Perform a non-blocking wait4 syscall: */
while ((ret = _thread_sys_wait4(pid, istat, options | WNOHANG,
rusage)) == 0 (options WNOHANG) == 0) {
/* Reset the interrupted operation flag: */
_thread_run-interrupted = 0;
/* Schedule the next thread while this one waits: */
_thread_kern_sched_state(PS_WAIT_WAIT, __FILE__, __LINE__);
/* Check if this call was interrupted by a signal: */
if (_thread_run-interrupted) {
errno = EINTR;
ret = -1;
break;
}
}
return (ret);
}
#endif
--
Richard Seamman, Jr. email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: WARNING: Today's current breaks passwords
Maybe your have switched between hashing modes (DES-MD5 or MD5-DES)? Because hashing algorithms doesn't changing without a wide notification has been made. Please check handbook on this subj. Maxim Sheldon Hearn wrote: This may or may not affect you. Today's installworld broke passwords for me. By that, I mean that login, xdm, su and friends gave authentication failures on all passwords for all users that I tried. I suspect this has to do with a hashing algorithm that isn't backward compatible. I used Kerberos to get into the machine as root and change important passwords to exactly what they were before. This worked. The new encrypted passwords are happy. :) I don't want to cause hysteria, and I can't guarantee that my report is accurate. All the same, do yourself a favour on your next installworld: ??? Make SURE you have an open root session somewhere. Do NOT hide ??? it behind xlock, and do NOT use lock(1) to keep it safe. ??? This will allow you to passwd(1) to create new encrypted ??? passwords for your users. ??? If you have shell accounts that need access to the box and you ??? don't want to have to rehash all their passwords, hold off on ??? installworld until someone calls me a liar, or a fix is ??? committed. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: WARNING: Today's current breaks passwords
hi, there! On Fri, 22 Jan 1999, Sheldon Hearn wrote: This may or may not affect you. Today's installworld broke passwords for me. By that, I mean that login, xdm, su and friends gave authentication failures on all passwords for all users that I tried. I suspect this has to do with a hashing algorithm that isn't backward compatible. is RELENG_3 affected too? /fjoe To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Using LinuxThreads
On Thu, Jan 21, 1999 at 12:38:14PM -0600, Richard Seaman, Jr. wrote: On Thu, Jan 21, 1999 at 06:12:29PM +0200, Jeremy Lea wrote: On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote: Actually, the new version, in FreeBSD ports form, doesn't require -DLINUXTHREADS anymore, but it does require -I/usr/local/include to pick up the right header, since it installs a pthread.h into /usr/local/include. This conflicts with the pthread.h in /usr/include. This is nagging at me. Having two headers of the same name, but importantly different content is asking for touble. There needs to be a way to ensure that only one or the other is picked up. The best way I can think of is to only include the contents of the user thread pthread.h if _THREAD_SAFE is defined (to force people to use the right defines...) and the contents of kernel thread pthread.h if _REENTRANT (and not _THREAD_SAFE) is defined. This has the added bonus of meaning that most linux apps wont have to be patched. Now, on the topic of conflicting pthread.h files, I agree this is a problem. One choice, which I originally implemented, is to fix pthread.h so it pulls in the right data based on a swtich (eg. if LINUXTHREADS is defined, pull in LT headers, else pull in user threads headers). I don't like using _THREAD_SAFE for this test, for the reason mentioned above. And I don't like using _REENTRANT because its so widely used and it could still confure people. The second choice, which is what the current version of the port does, is to put the conflicting headers in different directories, and require the application to define the order of the include files to get the right one in. There are proglems either way, and I don't really prefer one over the other. Upon further investigation, I'm not sure I agree with myself on this point anymore. I've been trying to get gimp compiled to look into the reported problem Brian Litzinger had. I notice that glib, gtk+ (both needed for gimp) and gimp itself generate include search paths that include /usr/local/include, which means that the linuxthreads pthread.h will get picked up even if the user wants the uthread version in /usr/include. Maybe having just one pthread.h that pulls in the required headers based on a switch (eg. -DLINUXTHREADS) is the way to go? -- Richard Seamman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: WARNING: Today's current breaks passwords
On Fri, 22 Jan 1999 16:51:40 +0200, Maxim Sobolev wrote: Maybe your have switched between hashing modes (DES-MD5 or MD5-DES)? Possibly that's what's happened, but it certainly isn't something I did deliberately. Because hashing algorithms doesn't changing without a wide notification has been made. Please check handbook on this subj. Really? You been watching your cvs commit mail? :) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: T/TCP in FreeBSD-3.x
Why I'm asking about this, is because I recently read an advice in one of the FreeBSD mailing lists, about Why my dial-up PPP connection from a FreeBSD box is so slow comparing with Windows NT (about ten times slower)? And the advice was (without explanations): Try to switch off the TCP_EXTENSIONS in /etc/rc.conf. This isn't something that can be fixed in FreeBSD's TCP. Rather, it is a general bug in how TCP Header Compression is defined for PPP and SLIP. Basically, TCP Header Compression will not compress any TCP segment that contains a TCP option. This means the use of ANY TCP option, whether T/TCP or RTTM, will cause your PPP links to not compress those packets and, thus, make your link slower. Unfortunately, just fixing FreeBSD isn't the answer, because you need to fix EVERY implementation of PPP to accept and generate TCP segments with options. The new IP Header Compression Internet Draft specifies how this is to be done. John To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
On Fri, 22 Jan 1999, Kazutaka YOKOTA wrote: Gentlemen, I don't intend to add yet another keymap to /usr/share/syscons/keymaps. I am merely trying to define a reasonable set of common, consistent key binding for existing keymaps. National keyboards have different layout of regular keys. But function keys and special keys are placed identically. They should work in the same way, or at least similar way in all keyboards, unless there is a good reason to do otherwise. (I am not talking about non-AT keyboards which are totally different from either AT 84 or 101/102/104 keyboards.) What would be useful here is the ability to compose keymaps. There would be basically two sets: one that defines the layout of the main keyboard and one that defines the layout of the other keys. That way I could pick my dvorak layout, then add on a layout that, say, swaps control and caps lock but leaves the main layout alone. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
make release, kernel.flp mfsroot.flp from Jan 21th doesn't work as well
Hi ho ! Someone recommended me a week or so ago, to use the 2 floppy install. Did so now with a FreeBSD 3.0-SNAP from Jan 21 1999. No success: my notebook 'sits' beneath me and tells me the following after inserting the 2nd floppy: zf_read: fill error [cpu register contents deleted] System halted JFYI -- Andreas Klemmhttp://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html NT = Not Today (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make release, kernel.flp mfsroot.flp from Jan 21th doesn't work as well
On Fri, Jan 22, 1999 at 05:00:52PM +0100, Andreas Klemm wrote: Hi ho ! Someone recommended me a week or so ago, to use the 2 floppy install. Did so now with a FreeBSD 3.0-SNAP from Jan 21 1999. No success: my notebook 'sits' beneath me and tells me the following after inserting the 2nd floppy: zf_read: fill error [cpu register contents deleted] System halted Sorry ! This was because of an read error on the floppy ! Please give me the hat ;-) -- Andreas Klemmhttp://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html NT = Not Today (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Using LinuxThreads
On Fri, 22 Jan 1999, Doug Rabson wrote: On Thu, 21 Jan 1999, Julian Elischer wrote: On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote: And when are COMPAT_LINUX_THREADS and VM_STACK going away? I have no idea. I was hoping that at least COMPAT_LINUX_THREADS would go away before the branch. I don't have commit authority, so it isn't up to me. hmm did you send me the patches? I can certainly do it now..(given a patch set to apply) I just realised however, that if we make them go away we break SMP right? hmm I guess we only break it for programs that woudltry use it which should be none if you run SMP :-) It doesn't break SMP (I'm running an SMP kernel with COMPAT_LINUX_THREADS). All that happens is that linux_clone() returns an error. Surprisingly StarOffice still works fairly well. StarOffice 5.0? Is this with Luoqi's shared process across SMP patches? -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd.Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
netd in free(): warning: junk pointer, too low to make sense.
Hi! I'm experiencing some strange errors with one of our workstations. I recently moved all of our workstations to 3.0 current as of 1998-12-18. Does any of this make any sense to anyone: trumpet:~rlogin balalaika netd in free(): warning: junk pointer, too low to make sense. trumpet:~telnet balalaika Trying 1.2.3.4... Connected to balalaika.partitur.se. Escape character is '^]'. inetd in free(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too low to make sense. FreeBSD/i386 (balalaika.partitur.se) (ttyp2) login: username Ok... I get in... If I'm lucky. Sometimes not at all. Besides, it acts a little strange. For example, here's what newsyslog told me recently: newsyslog: preposterous process number: 77243 newsyslog: log not compressed because daemon not notified Restarting inetd fixes the problem with rlogin/telnet, but it is bound to come back within a day or so. My guess is that this started when we started using samba on the machine, for sharing some simple stuff to windows machines. The samba has probably not been recompiled since our elf transition (our server uses the same binaries, and serves them via nfs to the troubled machine), so there shouldn't be a problem. Anyway, I fetched the brand new 2.0 port of samba, but still have problems. I haven't modified the smb.conf, though. It seems at first that it is the inetd that has some kind of memory leak, but I really don't like that idea. Well... Any ideas appreciated. Get back if you need more input. uname -a: FreeBSD balalaika.partitur.se 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Thu Jan 7 01:16:11 CET 1999 gir...@trumpet.partitur.se:/disk3/src/sys/compile/WORKSTATION i386 Oh, one more thing: There are five machines installed from the same build (built on the server, installed to all the boxes). The others work just fine. Regards, Palle To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: netd in free(): warning: junk pointer, too low to make sense.
On Fri, 22 Jan 1999, Palle Girgensohn wrote: Hi! I'm experiencing some strange errors with one of our workstations. I recently moved all of our workstations to 3.0 current as of 1998-12-18. Does any of this make any sense to anyone: trumpet:~rlogin balalaika netd in free(): warning: junk pointer, too low to make sense. check the archives of -current, i think this was fixed after the date of your build. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/4.0-current To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make release, kernel.flp mfsroot.flp from Jan 21th doesn't work as well
Andreas Klemm wrote: On Fri, Jan 22, 1999 at 05:00:52PM +0100, Andreas Klemm wrote: Hi ho ! Someone recommended me a week or so ago, to use the 2 floppy install. Did so now with a FreeBSD 3.0-SNAP from Jan 21 1999. No success: my notebook 'sits' beneath me and tells me the following after inserting the 2nd floppy: zf_read: fill error [cpu register contents deleted] System halted Sorry ! This was because of an read error on the floppy ! Please give me the hat ;-) No, you don't deserve it. :-) /boot/loader should *not* become so confused that it has to be killed by BTX, just because of an I/O error. Bad floppies are common and this is a reproducible bug that needs fixing. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
vinum read no longer works
I can no longer bring up my vinum volume with the vinum read command: vinum read /dev/wd0s1e /dev/wd2s1f vinum read /dev/wd0s1e vinum read /dev/wd2s1f all come back with vinum: no drives I understand that all slices belonging to a volume must now be passed to read, but that doesn't make any difference. I've modified /etc/rc to do a vinum create /etc/vinum.conf instead and that works, but I thought read was the correct commmand. 4.0-current as of yesterday, previously running 3.0-current as of the 19th. /etc/vinum.conf: drive drive1 device /dev/wd0s1e drive drive2 device /dev/wd2s1f volume usrc plex org striped 512b sd length 1g drive drive1 sd length 1g drive drive2 h24-64-221-247# vinum list Configuration summary Drives: 2 (4 configured) Volumes:1 (4 configured) Plexes: 1 (8 configured) Subdisks: 2 (16 configured) D drive1State: up Device /dev/wd0s1e D drive2State: up Device /dev/wd2s1f V usrc State: up Plexes: 1 Size: 2048 MB P usrc.p0 S State: up Subdisks: 2 Size: 2048 MB S usrc.p0.s0State: up PO:0 B Size: 1024 MB S usrc.p0.s1State: up PO: 256 kB Size: 1024 MB relevant changes to /etc/rc: if [ -f /etc/vinum.conf ]; then if [ -r /modules/vinum.ko ]; then # jkh paranoia kldload vinum vinum create /etc/vinum.conf 21 /dev/null else echo Can't find /modules/vinum.ko fi fi also, I suggest that something like the following patch be applied to /etc/rc once the read command works again, it allows the vinum on startup knob to function. rc.conf must be read in before vinum is started, or $vinum_slices is not initialized. --- rc.orig Wed Jan 20 04:30:13 1999 +++ rc Fri Jan 22 09:10:18 1999 @@ -22,11 +22,23 @@ PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin export PATH +# If there is a global system configuration file, suck it in. +if [ -f /etc/rc.conf ]; then +. /etc/rc.conf +fi + +# If old file exists, whine until they fix it. +if [ -f /etc/sysconfig ]; then +echo Warning: /etc/sysconfig has been replaced by /etc/rc.conf. +echo You should switch to /etc/rc.conf ASAP to eliminate this warning. +fi + # Configure ccd devices. if [ -f /etc/ccd.conf ]; then ccdconfig -C fi +# Configure vinum volumes. if [ -n $vinum_slices ]; then if [ -r /modules/vinum.ko ]; then # jkh paranoia kldload vinum @@ -88,17 +100,6 @@ if [ $? != 0 ]; then echo Filesystem mount failed, startup aborted exit 1 -fi - -# If there is a global system configuration file, suck it in. -if [ -f /etc/rc.conf ]; then - . /etc/rc.conf -fi - -# If old file exists, whine until they fix it. -if [ -f /etc/sysconfig ]; then - echo Warning: /etc/sysconfig has been replaced by /etc/rc.conf. - echo You should switch to /etc/rc.conf ASAP to eliminate this warning. fi adjkerntz -i To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: -D_REENTRANT (Was: Using LinuxThreads)
On Thu, Jan 21, 1999 at 02:00:53PM -0800, Kurt D. Zeilenga wrote: For kernel threading you just use libc. Whether or not libc generates thread safe (re-entrant) calls depends on whether its also linked with a library that 1) sets __isthreaded to a non-zero value, 2) has a _spinlock() implementationm, and 3) implements the functions flockfile, funlockfile, etc. There are also a few macros in header files that require _THREAD_SAFE to be defined to be thread safe. I was hoping to be able to produce one ldap library that could be safely linked with or without threads. However, if I must define _THREAD_SAFE to generate code to be linked with threads then I must produce two libraries (-lfoolib compiled with -U_THREAD_SAFE and -lfoolib_r with -D_THREAD_SAFE). _THREAD_SAFE is only used in stdio.h. Looking at what's there, it could be rewritten to eliminate _THREAD_SAFE entirely, at a (very slight) performance penalty. You'd have to check __isthreaded (could be done once, instead of twice, as in the code now) each time you call one of the functions defined within the _THREAD_SAFE switch. All _THREAD_SAFE does is let you avoid checking __isthreaded when you're not threaded. -- Richard Seamman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: -D_REENTRANT (Was: Using LinuxThreads)
Richard Seaman, Jr. wrote: On Thu, Jan 21, 1999 at 02:00:53PM -0800, Kurt D. Zeilenga wrote: For kernel threading you just use libc. Whether or not libc generates thread safe (re-entrant) calls depends on whether its also linked with a library that 1) sets __isthreaded to a non-zero value, 2) has a _spinlock() implementationm, and 3) implements the functions flockfile, funlockfile, etc. There are also a few macros in header files that require _THREAD_SAFE to be defined to be thread safe. I was hoping to be able to produce one ldap library that could be safely linked with or without threads. However, if I must define _THREAD_SAFE to generate code to be linked with threads then I must produce two libraries (-lfoolib compiled with -U_THREAD_SAFE and -lfoolib_r with -D_THREAD_SAFE). _THREAD_SAFE is only used in stdio.h. Looking at what's there, it could be rewritten to eliminate _THREAD_SAFE entirely, at a (very slight) performance penalty. You'd have to check __isthreaded (could be done once, instead of twice, as in the code now) each time you call one of the functions defined within the _THREAD_SAFE switch. All _THREAD_SAFE does is let you avoid checking __isthreaded when you're not threaded. So, if I want to produce a library which can be safely used by both threaded and non-threaded applications I should NOT define -D_THREAD_SAFE such that __isthreaded is always checked by the library. In effect, -D_THREAD_SAFE makes the generated code non-thread UNSAFE. - Kurt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: zip drive and parallel port in NIBBLE mode hang the machine
On Fri, 22 Jan 1999, Mikhail Teterin wrote: Hello! My system is too old to have anything other then Compatable and Bi-directional modes for the parallel port. Both of this are recognized as NIBBLE-only by ppc0. When I try to cp a big file (Wordperfect distribution) onto a Zip cartridge (with ufs with softupdates) the whole system becomes jerky and soon hangs -- I can still go from one virtual console to another, but can not do anything and need cold reboot. I used to be able to use the drive during Autumn (although I only used msdos-formatted cartridges). Any ideas? Thanks! try searching the lists, my suggestion is to compile like so: controller ppc0 at isa? disable port ? tty irq 7 change to: controller ppc0 at isa? disable port ? cam irq 7 -^^^ you may also want to try 'bio' it's been explained on the lists and i'm unsure. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/4.0-current To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Can't get 3.0 stable to build... :(
-BEGIN PGP SIGNED MESSAGE- I hope this is the right list... I'm having some problems building 3.0 stable on a 3.0-19990105-SNAP machine. I've tried blowing away /usr/src and checking it back out again to no avail. Buildworld always dies with this error: install -c -o root -g wheel -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.post.mk bsd.port.pre.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /usr/obj/usr/source/src/tmp/mk usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Note that my source tree is stored in /usr/source/src and that /usr/src is symlinked to /usr/source/src. I start the build by doing, cd /usr/src; make buildworld. The problem seems to be that /usr/obj/usr/source/src/tmp/mk does not exist, although /usr/source/src/tmp/make does. Does anyone have any suggestions, etc? - --- John Baldwin jobal...@vt.edu -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc -BEGIN PGP SIGNATURE- Version: 2.6.2 iQCVAwUBNqi8ILaE8XzBCodNAQHiUAP/QL1+SrFOFGbLnNuPxbwZrpnY83MVR0Sc lonWq1Mtv6SDe2y812fbZ7bHzAOoRqldMCNYHrllFae+6Vb/gj1v049ktTpFA1ow 2QloeArpjPMGHCP7NwlXmiwV5S2tP3og2MhJJb2wsaXTZsQ28XGXR0aEzK3LcmwI X0Q3Oke+vss= =3XMU -END PGP SIGNATURE- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Heads up! New swapper and VM changes being committed to -4.x tonight.
On Thu, 21 Jan 1999, Warner Losh wrote: In message pine.bsf.4.02a.9901211045530.26924-100...@korin.warman.org.pl Andrzej Bialecki writes: : I'm more than willing to test it in low memory conditions.. :-) I have : that special 386SX/4MB RAM machine in the corner to test things like : picobsd memory requirements... So how well does this work? I have a 4MB machine that I'd like to run FreeBSD on, including X on a low res screen... Hmmm.. Did I mention that I just left for a week to another country? Probably not :) I'll do the testing when I'm back. Andrzej Bialecki ++---++ - ab...@nask.pl ||PicoBSD|| FreeBSD in your pocket? Go and see: Research Academic |+---+| Small Embedded FreeBSD Network in Poland | |TT~~~| |http://www.freebsd.org/~picobsd/ ~-+==---+-+ - To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: -D_REENTRANT (Was: Using LinuxThreads)
On Fri, Jan 22, 1999 at 09:49:23AM -0800, Kurt D. Zeilenga wrote: Richard Seaman, Jr. wrote: _THREAD_SAFE is only used in stdio.h. Looking at what's there, it could be rewritten to eliminate _THREAD_SAFE entirely, at a (very slight) performance penalty. You'd have to check __isthreaded (could be done once, instead of twice, as in the code now) each time you call one of the functions defined within the _THREAD_SAFE switch. All _THREAD_SAFE does is let you avoid checking __isthreaded when you're not threaded. So, if I want to produce a library which can be safely used by both threaded and non-threaded applications I should NOT define -D_THREAD_SAFE such that __isthreaded is always checked by the library. I guess I was a little unclear. 1) I think you would have to rewrite a little bit of the header to use the __isthreaded test on a couple of more functions. 2) If you always define -D_THREAD_SAFE, __isthreaded will be checked whether you're threaded or not. If you're not threaded, __isthreaded should be false and you avoid the file locking code. If you're threaded, __isthreaded should be true and you get the file locking (if you're linked with a library that has actualy file locking code to override the libc file locking stub functions -- libc_r does this for you, you need something like a pthreads library linked in for libc). You could also just eliminate _THREAD_SAFE entirely by letting __isthreaded get checked on each relevant call. 3) If you're linking with FreeBSD user threads, you still have the problem that user threads needs libc_r and not libc, while everything else (no threads, or kernel threads) needs libc. The _THREAD_SAFE switch doesn't affect whether you link with libc or libc_r. As mentioned before, libc_r could be rewritten to look like a normal libpthread addon library, ie. it wouldn't duplicate libc, but it would require some work. 4) There are portions of libc that are only thread safe when they are compiled as part of libc_r (almost all of libc gets rolled into libc_r). This can be fixed. Indeed, I have patches that do this, but they need some testing. -- Richard Seamman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Changes to pam_kerberosIV broke ftpd
In article 199901211425.iaa33...@friley-184-92.res.iastate.edu, Patrick Hartling myst...@friley-184-92.res.iastate.edu wrote: It appears that revision 1.9 of lib/libpam/modules/pam_kerberosIV/klogin.c and revision 1.3 of lib/libpam/modules/pam_kerberosIV/pam_kerberosIV.c broke ftpd when compiling with MAKE_KERBEROS defined. Right. It's fixed now (yesterday, actually). John -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Nobody ever went broke underestimating the taste of the American public. -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: -D_REENTRANT (Was: Using LinuxThreads)
Richard Seaman, Jr. wrote: On Fri, Jan 22, 1999 at 09:49:23AM -0800, Kurt D. Zeilenga wrote: Richard Seaman, Jr. wrote: _THREAD_SAFE is only used in stdio.h. Looking at what's there, it could be rewritten to eliminate _THREAD_SAFE entirely, at a (very slight) performance penalty. You'd have to check __isthreaded (could be done once, instead of twice, as in the code now) each time you call one of the functions defined within the _THREAD_SAFE switch. All _THREAD_SAFE does is let you avoid checking __isthreaded when you're not threaded. So, if I want to produce a library which can be safely used by both threaded and non-threaded applications I should NOT define -D_THREAD_SAFE such that __isthreaded is always checked by the library. I guess I was a little unclear. 1) I think you would have to rewrite a little bit of the header to use the __isthreaded test on a couple of more functions. 2) If you always define -D_THREAD_SAFE, __isthreaded will be checked whether you're threaded or not. I would think that most third party libraries (from Ports) do not compile with -D_THREAD_SAFE. As such, __isthreaded won't be checked and the library cannot be safely used in a threaded environment. You could also just eliminate _THREAD_SAFE entirely by letting __isthreaded get checked on each relevant call. I would much prefer this. Then third party libraries compiled without -D_THREAD_SAFE can be used in threaded environments (though they might require external synchronization). Kurt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: netd in free(): warning: junk pointer, too low to make sense.
On Fri, 22 Jan 1999, Palle Girgensohn wrote: I'm experiencing some strange errors with one of our workstations. I recently moved all of our workstations to 3.0 current as of 1998-12-18. Does any of this make any sense to anyone: trumpet:~rlogin balalaika netd in free(): warning: junk pointer, too low to make sense. trumpet:~telnet balalaika Trying 1.2.3.4... Connected to balalaika.partitur.se. Escape character is '^]'. inetd in free(): warning: junk pointer, too low to make sense. There are two separate bugs that can cause this behavior, one in inetd and the other is the infamous dying daemons bug. Both have theoretically been fixed, recently. Sorry I don't have exact dates handy. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: World broken in RELENG_3 when making aout-to-elf bulid
In article 36a867ed.8adac...@altavista.net, Maxim Sobolev sobo...@altavista.net wrote: -o login login.o login_access.o login_fbtab.o -lutil -lcrypt login.o: Undefined symbol `_pam_start' referenced from text segment ... I merged the fix into RELENG_3 this morning. Sorry about that! John -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Nobody ever went broke underestimating the taste of the American public. -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: boot.flp versions
#define quoting(Jordan K. Hubbard) // All: Sorry the boot.flp has been broken for this long, but I've had // other distractions lately. I will make it work once more, somehow // or other, and just keep your eyes on current.freebsd.org over // the next few days. When it returns to 1.44MB in size again, give // it a try. :) Another problem I had with that snap here is that it does not install on a machine with 8M RAM. It started installing, but stopped in random places during file copy. It did work after I remade the kern.flp with only the devices I had (thus, using less memory). I noticed that swapping was disabled in the BOOTMFS kernel. Is this really necessary ? How hard is to add an option use this swap partition during install, or even a create and use a vn swap file in /usr/tmp during install ? Or should I just assume 8M RAM machines are not any more supported ? Jonny PS: Wow !!! The new loader made dealing with boot.flp a very easy task. :) -- Joao Carlos Mendes LuisM.Sc. Student jo...@jonny.eng.br Universidade Federal do Rio de Janeiro This .sig is not meant to be politically correct. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: boot.flp versions
OK, in retrospect, turning off swapping was a mistake. I should have thought about this a bit more before blindly accepting the suggestion from Andrzej. ;) Fixed. - Jordan #define quoting(Jordan K. Hubbard) // All: Sorry the boot.flp has been broken for this long, but I've had // other distractions lately. I will make it work once more, somehow // or other, and just keep your eyes on current.freebsd.org over // the next few days. When it returns to 1.44MB in size again, give // it a try. :) Another problem I had with that snap here is that it does not install on a machine with 8M RAM. It started installing, but stopped in random places during file copy. It did work after I remade the kern.flp with only the devices I had (thus, using less memory). I noticed that swapping was disabled in the BOOTMFS kernel. Is this really necessary ? How hard is to add an option use this swap partition during install, or even a create and use a vn swap file in /usr/tmp during install ? Or should I just assume 8M RAM machines are not any more supported ? Jonny PS: Wow !!! The new loader made dealing with boot.flp a very easy task. :) -- Joao Carlos Mendes LuisM.Sc. Student jo...@jonny.eng.br Universidade Federal do Rio de Janeiro This .sig is not meant to be politically correct. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Using LinuxThreads
|Maybe having just one pthread.h that pulls in the required headers |based on a switch (eg. -DLINUXTHREADS) is the way to go? Doing this makes linuxthread support more or less official, I would think. I am for it. Russell | |-- |Richard Seamman, Jr. email: d...@tar.com |5182 N. Maple Lanephone: 414-367-5450 |Chenequa WI 53058 fax: 414-367-5852 | |To Unsubscribe: send mail to majord...@freebsd.org |with unsubscribe freebsd-current in the body of the message | To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: WARNING: Today's current breaks passwords
-Original Message- From: Sheldon Hearn [mailto:a...@iafrica.com] Sent: Friday, January 22, 1999 3:17 PM To: Maxim Sobolev Cc: curr...@freebsd.org Subject: Re: WARNING: Today's current breaks passwords On Fri, 22 Jan 1999 16:51:40 +0200, Maxim Sobolev wrote: Maybe your have switched between hashing modes (DES-MD5 or MD5-DES)? Possibly that's what's happened, but it certainly isn't something I did deliberately. It happened to me too. Did a cvsupdate after the tag and Matt's code was commited, did a make world, built a new kernel, rebooted and couldn't log in! After changing root's password it went from being DES to SHA1 so I suspect it's failing to honour the existing hash algorithm and trying to use SHA1 regardless. Brandon looks like he's been around here recently, like yesterday when it happened :-). Paul. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: T/TCP in FreeBSD-3.x
In message 36a85ef1.444a...@urc.ac.ru you write: Why I'm asking about this, is because I recently read an advice in one of the FreeBSD mailing lists, about Why my dial-up PPP connection from a FreeBSD box is so slow comparing with Windows NT (about ten times slower)? And the advice was (without explanations): Try to switch off the TCP_EXTENSIONS in /etc/rc.conf. Some dialup terminal servers have problems with TCP options; turning off TCP_EXTENSIONS is the easiest way to handle these terminal servers. So, is it safe to use T/TCP (at least for Squid) for RELENG_3? RELENG_2_2? I asked for more info about the problems they were having with T/TCP and never got much of an answer; since they don't say what the problem they were having was it's hard to say whether or not it was resolved. And what about MBUF size (mentioned at the same page of the Squid FAQ)? Do I need to patch Squid as it shown at the page? Recent (as in the last day or so) RELENG_3's should not need this patch; the bug described has been fixed in another way. Bill To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Using LinuxThreads
On Fri, 22 Jan 1999, Russell L. Carter wrote: |Maybe having just one pthread.h that pulls in the required headers |based on a switch (eg. -DLINUXTHREADS) is the way to go? Doing this makes linuxthread support more or less official, I would think. I am for it. *confused look* somehow even though i've been trying to follow this thread i got lost. questions: 1) are 'linuxthreads' enabled by defualt now? 2) if not then 'make world -DLINUXTHREADS' ? 3) when it's decided can someone explain how to use this stuff nativly? thanks, -Alfred To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: keymaps
-Original Message- From: John Fieber [mailto:jfie...@indiana.edu] Sent: Friday, January 22, 1999 3:51 PM To: Kazutaka YOKOTA Cc: curr...@freebsd.org Subject: Re: keymaps On Fri, 22 Jan 1999, Kazutaka YOKOTA wrote: Gentlemen, I don't intend to add yet another keymap to /usr/share/syscons/keymaps. I am merely trying to define a reasonable set of common, consistent key binding for existing keymaps. National keyboards have different layout of regular keys. But function keys and special keys are placed identically. They should work in the same way, or at least similar way in all keyboards, unless there is a good reason to do otherwise. (I am not talking about non-AT keyboards which are totally different from either AT 84 or 101/102/104 keyboards.) What would be useful here is the ability to compose keymaps. There would be basically two sets: one that defines the layout of the main keyboard and one that defines the layout of the other keys. That way I could pick my dvorak layout, then add on a layout that, say, swaps control and caps lock but leaves the main layout alone. I was thinking something similar, a way to dynamically modify the map ala xmodmap would be useful so that users who have particular preferences can implement the changes in, say, .login That's exactly what I do with xmodmap and X. The standard maps can continue to reflect the actual layout of the keyboards then rather than having a number of variations according to popular user preference. Paul To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Using LinuxThreads
On Fri, Jan 22, 1999 at 02:47:53PM -0500, Alfred Perlstein wrote: *confused look* somehow even though i've been trying to follow this thread i got lost. questions: 1) are 'linuxthreads' enabled by defualt now? The terminology is a little confusing. There's linuxthreads for those running linux apps in FreeBSD using the linux emulation modules. Then, there's a port of linuxthreads to FreeBSD which runs natively, ie. no linux emulation, and gives 1-1 kernel threading to apps that link to it. Both require some options to be turned on for kernel/world builds that are not on by default. (see http://lt.tar.com) Julian Elischer has agreed to commit the patches to remove the options and make the code change permanent, when I send him the patches. I'll send him the patches as soon as I can test them after a make world, which I'll do as soon as the libcrypt build problems are fixed. 2) if not then 'make world -DLINUXTHREADS' ? See above. 3) when it's decided can someone explain how to use this stuff nativly? See http://lt.tar.com . I also have some patches for squid, glib and I'm working on gimp to compile using the FreeBSD port of linuxthreads. Others have had success in varying degress with NSPR (mozilla), ACE and others. -- Richard Seamman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: world broken
having spent almost an hour trying to decode the complexities of the crypt making process I admit defeat.. can SOMEBODY please fix the build in -current and sent branson a nice pointy hat.. I think he committed and went on vacation (I haven't seen any commits that say they fixed this but I'm waiting for cvsup to connect just in case I missed it...) julian I spend half night yesterday to sort this mess out. If no one objects, I'll commit my fixes. (anyone volunteers to make the hat?) -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Using LinuxThreads
On Fri, 22 Jan 1999, Richard Seaman, Jr. wrote: *confused look* somehow even though i've been trying to follow this thread i got lost. questions: 1) are 'linuxthreads' enabled by defualt now? The terminology is a little confusing. There's linuxthreads for those running linux apps in FreeBSD using the linux emulation modules. Then, there's a port of linuxthreads to FreeBSD which runs natively, ie. no linux emulation, and gives 1-1 kernel threading to apps that link to it. Both require some options to be turned on for kernel/world builds that are not on by default. (see http://lt.tar.com) Julian Elischer has agreed to commit the patches to remove the options and make the code change permanent, when I send him the patches. I'll send him the patches as soon as I can test them after a make world, which I'll do as soon as the libcrypt build problems are fixed. awesome, btw, it seems that make world is also broken on libkvm. 3) when it's decided can someone explain how to use this stuff nativly? See http://lt.tar.com . I also have some patches for squid, glib and I'm working on gimp to compile using the FreeBSD port of linuxthreads. Others have had success in varying degress with NSPR (mozilla), ACE and others. will do. -- Richard Seamman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/4.0-current To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: world broken
Luoqi Chen wrote: I spend half night yesterday to sort this mess out. If no one objects, I'll commit my fixes. (anyone volunteers to make the hat?) I know who gets the hat; please cool it on the fixes until the original committer has finished. I'm watching this one closely, and I need to track it on Internat as well. Not long now. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: PNP and new bootloader with ELF kernel
In message 1999012216.a2...@terry.dragon2.net, Ying-Chieh Liao ijl...@dragon2.net writes On Thu, Jan 21, 1999 at 23:03:45 +, Tim wrote: How do I set up the CSN now as I get CSN 1 disabled and CSN 2 disabled on boot. you can put this pnp information in /kernel.config and, in your /boot/boot.conf, put load /kernel load -t userconfig_script /kernel.config boot this works fine on my box Also I would like to remove the previous boot screen and boot straight into the new bootloader, so can a dos partition be configured to boot from the new bootloader just execute the following command : disklabel -B -b /boot/boot1 -s /boot/boot2 slice slice is which you boot from ex : disklabel -B -b /boot/boot1 -s /boot/boot2 wd0s1 Thanks for the info but unfortunately this has not worked, maybe this is the syntax I have used in the /kernel.config file pnp 1 enable os irq0 11 port0 0x3e8 used to work before else what permissions do the files need to be also, where did you find this load -t stuff Thanks -- Tim To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /etc/nsswitch.conf
On Wed, Jan 20, 1999 at 05:58:01PM +0100, Dag-Erling Smorgrav wrote: Mike Nguyen mikengu...@sprintmail.com writes: consolidating all that config information in one place, such as /etc/rc.conf, would be a good thing. Agreed, it really isn't such a good idea to clutter /etc/ with all those single line configuration files. How about having one file in /etc containing all the different configuration options, and have this file processed by a program to generate all the different configuration files. This would give us the benefits of a centralized configuration file, without the need of rewriting the many programs that really want to have their configuration in specific files. On the other hand, this would require a reprocessing of the file for each modification to the configuration. Maybe we could run the command at the beginning of /etc/rc, and allow a user with root privileges to rerun the command at any time to rescan the configuration? It would require a minimum of effort to implement this, so I hope this is not too simple for us. Regards --- Erik H. Bakke Habatech AS e...@habatech.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
vinum read no longer works
On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: I can no longer bring up my vinum volume with the vinum read command: vinum read /dev/wd0s1e /dev/wd2s1f vinum read /dev/wd0s1e vinum read /dev/wd2s1f all come back with vinum: no drives Correct. As I explained in detail in my HEADS UP message a couple of days ago, you must now specify drives, not partitions. The correct command might be vinum read /dev/wd0 /dev/wd2 To quote the message: One way you can shoot yourself in the foot: the `read' command has changed. In the previous version, you specified the name of exactly one device containing a vinum partition. This is suboptimal, because it doesn't allow you to read multiple configurations, and it doesn't allow you to move drives around. In the new version, you *must* specify the names of *all* disks containing Vinum partitions. For example, if you have Vinum partitions /dev/da1h /dev/da2h /dev/da3h /dev/da4h /dev/da5h and /dev/da6h, you might previously have written: vinum read /dev/da3h Now you *must* write: vinum read /dev/da1 /dev/da2 /dev/da3 /dev/da4 /dev/da5 /dev/da6 If you do this wrong, you have the potential to wipe out your on-disk configuration. You can avoid this by disabling saving the configuration. Do this with the `setdaemon' command: # vinum vinum - setdaemon 4 vinum - read /dev/da1 /dev/da2 /dev/da3 /dev/da4 /dev/da5 /dev/da6 I understand that all slices belonging to a volume must now be passed to read, but that doesn't make any difference. Yes it does. As a result of the incorrect read command, you have probably obliterated your configuration. I've modified /etc/rc to do a vinum create /etc/vinum.conf instead and that works, but I thought read was the correct commmand. `read' is the correct command. The arguments you supplied are wrong. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: boot.flp versions
As Joao Carlos Mendes Luis wrote... #define quoting(Jordan K. Hubbard) // All: Sorry the boot.flp has been broken for this long, but I've had // other distractions lately. I will make it work once more, somehow // or other, and just keep your eyes on current.freebsd.org over // the next few days. When it returns to 1.44MB in size again, give // it a try. :) Another problem I had with that snap here is that it does not install on a machine with 8M RAM. It started installing, but stopped in random places during file copy. It did work after I remade the kern.flp with only the devices I had (thus, using less memory). I noticed that swapping was disabled in the BOOTMFS kernel. Is this really necessary ? How hard is to add an option use this swap partition during install, or even a create and use a vn swap file in /usr/tmp during install ? Or should I just assume 8M RAM machines are not any more supported ? What grew so drastically that the memory requirements grew from 5 Mbytes minimum memory to 8Mb? (remember all those discussions when 4Mb became too small to run the install floppy?) Wilko _ __ | / o / / _ Bulteemail: wi...@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl __ Powered by FreeBSD __ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: vinum read no longer works
Greg Lehey wrote: On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: I can no longer bring up my vinum volume with the vinum read command: vinum read /dev/wd0s1e /dev/wd2s1f vinum read /dev/wd0s1e vinum read /dev/wd2s1f all come back with vinum: no drives Correct. As I explained in detail in my HEADS UP message a couple of days ago, you must now specify drives, not partitions. The correct command might be vinum read /dev/wd0 /dev/wd2 Does vinum scan the slices? What if there are two freebsd slices? From vinumhdr.h, it looks like it totally ignores slices. If somebody is working on a disk shared with something else (eg: DOS/windoze), then perhaps the examples should be: vinum read /dev/wd0s1 /dev/wd2s1 Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: vinum read no longer works
On Saturday, 23 January 1999 at 6:24:17 +0800, Peter Wemm wrote: Greg Lehey wrote: On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: I can no longer bring up my vinum volume with the vinum read command: vinum read /dev/wd0s1e /dev/wd2s1f vinum read /dev/wd0s1e vinum read /dev/wd2s1f all come back with vinum: no drives Correct. As I explained in detail in my HEADS UP message a couple of days ago, you must now specify drives, not partitions. The correct command might be vinum read /dev/wd0 /dev/wd2 Does vinum scan the slices? What if there are two freebsd slices? Currently it just scans the compatibility slice. I'll change that later. From vinumhdr.h, it looks like it totally ignores slices. Well, that's not the place I'd look. If somebody is working on a disk shared with something else (eg: DOS/windoze), then perhaps the examples should be: vinum read /dev/wd0s1 /dev/wd2s1 Interesting. Yes, I think this would work. The real problem here is that, as you know from private correspondence, I haven't found a good way to determine what partitions are on the system, so I go through with brute force and try to open each possible partition. This will change when I find a better way, but it shouldn't require incompatible changes to the command line syntax again. With any luck, I *will* be able to say `vinum start', and it will go out and find the partitions by itself. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
make world breakage
Hey guys! After all these commits for secure/lib/libcrypt it seems that make world doesn't work anymore. === csu/i386-elf === libcom_err === libcom_err/doc === ../secure/lib/libcrypt cc -nostdinc -O -pipe -I/usr/src/secure/lib/libcrypt/../../../lib/libmd -Wall -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/secure/lib/libcrypt/crypt.c -o crypt.o make: don't know how to make crypt-md5.c. Stop *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. burka# -- dima To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: vinum read no longer works
Greg Lehey wrote: On Saturday, 23 January 1999 at 6:24:17 +0800, Peter Wemm wrote: Greg Lehey wrote: On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: I can no longer bring up my vinum volume with the vinum read command: vinum read /dev/wd0s1e /dev/wd2s1f vinum read /dev/wd0s1e vinum read /dev/wd2s1f all come back with vinum: no drives Correct. As I explained in detail in my HEADS UP message a couple of days ago, you must now specify drives, not partitions. The correct command might be vinum read /dev/wd0 /dev/wd2 Does vinum scan the slices? What if there are two freebsd slices? Currently it just scans the compatibility slice. I'll change that later. What is worrying me was that wd0 is the whole disk, not a compatability slice... I'm not quite sure how this is dealt with, vinumio.c does a DIOCGPART into drive-partinfo.. Is this how it's finding the compatability slice info? As I understand it by looking at the unit numbers in /dev, and the subr_diskslice code: wd0c = whole compat slice (slice 0 = compat slice) wd0 = whole disk (this is slice 1 == whole disk != compat slice) wd0s1 == wd0s1c == whole of first slice (this is slice 2 in the major number). Now perhaps the DIOCGPART on slice 1 is being translated into the info for slice 0 (compat slice) but I don't quite see where. If somebody is working on a disk shared with something else (eg: DOS/windoze), then perhaps the examples should be: vinum read /dev/wd0s1 /dev/wd2s1 Interesting. Yes, I think this would work. The real problem here is that, as you know from private correspondence, I haven't found a good way to determine what partitions are on the system, so I go through with brute force and try to open each possible partition. This will change when I find a better way, but it shouldn't require incompatible changes to the command line syntax again. With any luck, I *will* be able to say `vinum start', and it will go out and find the partitions by itself. Well, we used to have a way, it was the #ifdef SLICE code. It used to actively probe the devices and went out and found all the disks, slices, labels etc. It would have been an ideal thing for vinum to hook into as it could notify vinum hey, I've just found something that looks like it belongs to vinum!. When vinum was told about all the components needed to make up a volume and attached that to the system, the SLICE code would have probed for disklabels etc inside. That would have taken us 99% of the way to booting from a drive array with a root partition. Greg Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: vinum read no longer works
On Saturday, 23 January 1999 at 7:10:08 +0800, Peter Wemm wrote: Greg Lehey wrote: On Saturday, 23 January 1999 at 6:24:17 +0800, Peter Wemm wrote: Greg Lehey wrote: On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: I can no longer bring up my vinum volume with the vinum read command: vinum read /dev/wd0s1e /dev/wd2s1f vinum read /dev/wd0s1e vinum read /dev/wd2s1f all come back with vinum: no drives Correct. As I explained in detail in my HEADS UP message a couple of days ago, you must now specify drives, not partitions. The correct command might be vinum read /dev/wd0 /dev/wd2 Does vinum scan the slices? What if there are two freebsd slices? Currently it just scans the compatibility slice. I'll change that later. What is worrying me was that wd0 is the whole disk, not a compatability slice... I'm not quite sure how this is dealt with, vinumio.c does a DIOCGPART into drive-partinfo.. Is this how it's finding the compatability slice info? As I understand it by looking at the unit numbers in /dev, and the subr_diskslice code: wd0c = whole compat slice (slice 0 = compat slice) wd0 = whole disk (this is slice 1 == whole disk != compat slice) wd0s1 == wd0s1c == whole of first slice (this is slice 2 in the major number). Now perhaps the DIOCGPART on slice 1 is being translated into the info for slice 0 (compat slice) but I don't quite see where. It's much more of a kludge than that. Remember, this is interim code while I look for the right way to do it. I take the name of the disk and append the letters a to h to them (omitting c), and try to open them. If somebody is working on a disk shared with something else (eg: DOS/windoze), then perhaps the examples should be: vinum read /dev/wd0s1 /dev/wd2s1 Interesting. Yes, I think this would work. The real problem here is that, as you know from private correspondence, I haven't found a good way to determine what partitions are on the system, so I go through with brute force and try to open each possible partition. This will change when I find a better way, but it shouldn't require incompatible changes to the command line syntax again. With any luck, I *will* be able to say `vinum start', and it will go out and find the partitions by itself. Well, we used to have a way, it was the #ifdef SLICE code. It used to actively probe the devices and went out and found all the disks, slices, labels etc. It would have been an ideal thing for vinum to hook into as it could notify vinum hey, I've just found something that looks like it belongs to vinum!. When vinum was told about all the components needed to make up a volume and attached that to the system, the SLICE code would have probed for disklabels etc inside. You mean Julian's SLICE code, right? Yes, I knew about that, and I'm agreed. But as you say, it's currently not there. I need a solution that works in all configurations. That would have taken us 99% of the way to booting from a drive array with a root partition. Maybe. There are a number of issues here, most of them minor but irritating. I haven't looked at it properly yet. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: world broken
Mark, can you announce when the fixes are in place? thanks, julian On Fri, 22 Jan 1999, Mark Murray wrote: Luoqi Chen wrote: I spend half night yesterday to sort this mess out. If no one objects, I'll commit my fixes. (anyone volunteers to make the hat?) I know who gets the hat; please cool it on the fixes until the original committer has finished. I'm watching this one closely, and I need to track it on Internat as well. Not long now. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make world breakage
make: don't know how to make crypt-md5.c. Stop Me three. I was looking forward to testing all the VM improvements, but have been stuck because of this. I've watched the cvs-all list and haven't seen a mention of this being fixed. -- Brian Litzinger br...@litzinger.com On Fri, Jan 22, 1999 at 02:54:08PM -0800, Dima Ruban wrote: After all these commits for secure/lib/libcrypt it seems that make world doesn't work anymore. === csu/i386-elf === libcom_err === libcom_err/doc === ../secure/lib/libcrypt cc -nostdinc -O -pipe -I/usr/src/secure/lib/libcrypt/../../../lib/libmd -Wall -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/secure/lib/libcrypt/crypt.c -o crypt.o make: don't know how to make crypt-md5.c. Stop *** Error code 2 ... Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: kvm_getswapinfo() function added to libkvm. top, pstat, systat updated
On Fri, 22 Jan 1999, Matthew Dillon wrote: A new function, kvm_getswapinfo(), has been added to libkvm. pstat, systat, and top have been updated to use the new function. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Where's struct kvm_swap and typedef struct kvm_swap *kvm_swap_t supposed to now be? Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: world broken
Luoqi Chen wrote:
I spend half night yesterday to sort this mess out. If no one objects,
I'll commit my fixes. (anyone volunteers to make the hat?)
I know who gets the hat; please cool it on the fixes until the original
committer has finished.
I'm watching this one closely, and I need to track it on Internat
as well. Not long now.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
Ok, I'll let the original committer do it. For those who can't wait to try
Matt's new VM system, the following diff will help you get by. After applied
the patch, mv/cp/ln secure/lib/libcrypt/crypt.c to crypt-des.c in the same
directory. (I hope this patch doesn't reveal any information that would
harm national security :-)
-lq
Index: lib/Makefile
===
RCS file: /home/ncvs/src/lib/Makefile,v
retrieving revision 1.87
diff -u -r1.87 Makefile
--- Makefile1998/12/17 23:02:11 1.87
+++ Makefile1999/01/21 20:22:54
@@ -39,9 +39,7 @@
# Build both libraries. They have different names, so no harm,
# and this avoids having stale libscrypt.*
-.if exists(${.CURDIR}/../secure) !defined(NOSECURE) !defined(NOCRYPT)
-_libcrypt= ../secure/lib/libcrypt libcrypt
-.else
+.if !defined(NOCRYPT)
_libcrypt= libcrypt
.endif
Index: secure/lib/libcrypt/crypt.c
===
RCS file: /home/ncvs/src/secure/lib/libcrypt/crypt.c,v
retrieving revision 1.9
diff -u -r1.9 crypt.c
--- crypt.c 1997/02/22 14:40:30 1.9
+++ crypt.c 1999/01/22 23:38:24
@@ -59,9 +59,8 @@
#include sys/param.h
#include pwd.h
#include string.h
+#include crypt.h
-char *crypt_md5(const char *pw, const char *salt);
-
/* We can't always assume gcc */
#ifdef __GNUC__
#define INLINE inline
@@ -578,20 +577,26 @@
return(retval);
}
-char *
-crypt(char *key, char *setting)
+char *
+crypt_des(pw, pl, sp, sl, passwd, token)
+ const unsigned char *pw;
+ const unsigned int pl;
+ const unsigned char *sp;
+ const unsigned int sl;
+ char * passwd;
+ char * token;
{
- int i;
- u_long count, salt, l, r0, r1, keybuf[2];
- u_char *p, *q;
- static u_char output[21];
+ int i;
+ u_long count, salt, l, r0, r1, keybuf[2];
+ u_char *p, *q;
+ u_char *key = pw, *setting = sp;
+ u_char *output = (u_char *)passwd;
- if (!strncmp(setting, $1$, 3))
- return crypt_md5(key, setting);
+ if (!*setting)
+ setting = key;
if (!des_initialised)
des_init();
-
/*
* Copy the key, shifting each character up by one bit
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: boot.flp versions
On Fri, 22 Jan 1999, Jordan K. Hubbard wrote: OK, in retrospect, turning off swapping was a mistake. I should have thought about this a bit more before blindly accepting the suggestion from Andrzej. ;) Fixed. Oh well.. It made sense for me, I just thought it might help to save some space. It was only a few bytes anyway, and we're short of a couple of kBs now, so it's irrelevant... Andrzej Bialecki ++---++ - ab...@nask.pl ||PicoBSD|| FreeBSD in your pocket? Go and see: Research Academic |+---+| Small Embedded FreeBSD Network in Poland | |TT~~~| |http://www.freebsd.org/~picobsd/ ~-+==---+-+ - To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: kvm_getswapinfo() function added to libkvm. top, pstat, systat updated
On Fri, 22 Jan 1999, Matthew Dillon wrote: A new function, kvm_getswapinfo(), has been added to libkvm. pstat, systat, and top have been updated to use the new function. Have you considered using sysctl(3) for this instead? If yes, could you explain why the libkvm seemed better to you? (I'm asking because with libkvm you need to use /dev/kmem _and_ you need to access symbol table - this doesn't work with stripped kernels). Andrzej Bialecki ++---++ - ab...@nask.pl ||PicoBSD|| FreeBSD in your pocket? Go and see: Research Academic |+---+| Small Embedded FreeBSD Network in Poland | |TT~~~| |http://www.freebsd.org/~picobsd/ ~-+==---+-+ - To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: world broken
so what happenned.. he checked in more stuff this morning and DIDN'T fix the build breakage from yesterday.. doesn't he know about it? On Fri, 22 Jan 1999, Mark Murray wrote: Luoqi Chen wrote: I spend half night yesterday to sort this mess out. If no one objects, I'll commit my fixes. (anyone volunteers to make the hat?) I know who gets the hat; please cool it on the fixes until the original committer has finished. I'm watching this one closely, and I need to track it on Internat as well. Not long now. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Using LinuxThreads
On Fri, 22 Jan 1999, Brian Feldman wrote: On Fri, 22 Jan 1999, Doug Rabson wrote: On Thu, 21 Jan 1999, Julian Elischer wrote: On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote: And when are COMPAT_LINUX_THREADS and VM_STACK going away? I have no idea. I was hoping that at least COMPAT_LINUX_THREADS would go away before the branch. I don't have commit authority, so it isn't up to me. hmm did you send me the patches? I can certainly do it now..(given a patch set to apply) I just realised however, that if we make them go away we break SMP right? hmm I guess we only break it for programs that woudltry use it which should be none if you run SMP :-) It doesn't break SMP (I'm running an SMP kernel with COMPAT_LINUX_THREADS). All that happens is that linux_clone() returns an error. Surprisingly StarOffice still works fairly well. StarOffice 5.0? Is this with Luoqi's shared process across SMP patches? I don't have Luoqi's patches. StarOffice seems to work even if there is no thread support. Wierd. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: kvm_getswapinfo() function added to libkvm. top, pstat, systat updated
On Fri, 22 Jan 1999 18:40:55 -0500 (EST), Brian Feldman gr...@unixhelp.org said: Where's struct kvm_swap and typedef struct kvm_swap *kvm_swap_t supposed to now be? Hopefully the latter isn't anywhere, since style(9) says very specifically that such typedefs are Not To Be Introduced. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same woll...@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: kvm_getswapinfo() function added to libkvm. top, pstat, systat updated
On Fri, 22 Jan 1999, Garrett Wollman wrote: On Fri, 22 Jan 1999 18:40:55 -0500 (EST), Brian Feldman gr...@unixhelp.org said: Where's struct kvm_swap and typedef struct kvm_swap *kvm_swap_t supposed to now be? Hopefully the latter isn't anywhere, since style(9) says very specifically that such typedefs are Not To Be Introduced. This doesn't change the fact that there seems to be them... Of course, without these definitions libkvm no longer will compile. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same woll...@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
panic: found dirty cache page 0xf046f1c0
Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got lost): panic: found dirty cache page 0xf046f1c0 mp_lock = 0101; cpuid = 1; lapic.id = 0100 Debugger(panic) Stopped at Debugger+0x37: movl$0,in_Debugger db trace Debugger(f01f1806) at Debugger+0x37 panic(f01fbb50,f046f1c0,0,80,f45cbb20) at panic+0xa4 vm_page_alloc(f45f6f68,80,3,0,80) at vm_page_alloc+0x114 vm_page_grab(f45f6f68,80,83,0,80) at vm_page_grab+0x8d _pmap_allocpte(f45cbb20,80,201df000,201df000,2a86000) at _pmap_allocpte+0x19 pmap_allocpte(f45cbb20,201df000,f02c4df4,201df000,f45cbac0) at pmap_allocpte+0x53 pmap_enter(f45cbb20,201df000,2a86000,5,0) at pmap_enter+0x3d vm_fault(f45cbac0,201df000,1,0,f4195180) at vm_fault+0x891 trap_pfault(f45f9fbc,1,201df236) at trap_pfault+0xf2 trap(27,27,,5,efbfad38) at trap+0x1c2 calltrap() at calltrap+0x3c --- trap 0xc, eip = 0x201df236, esp = 0xefbfac4c, ebp = 0xefbfad38 --- db c boot() called on cpu#1 syncing disks... 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 giving up 1: dev:, flags:20020034, blkno:1057008, lblkno:0 [..] This was compiled two houts ago from absolute latest -current: FreeBSD spinner.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #385: Sat Jan 23 08:38:42 WST 1999 pe...@spinner.netplex.com.au:/home/src/sys/compile/SPINNER i386 My other SMP machine (2xPPro200) seems to be running fine: FreeBSD beast.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #267: Thu Jan 21 21:39:45 WST 1999 pe...@beast.netplex.com.au:/home/src/sys/compile/BEAST i386 Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic: found dirty cache page 0xf046f1c0
At 10:34 AM 1/23/99 +0800, Peter Wemm wrote: Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got lost): panic: found dirty cache page 0xf046f1c0 mp_lock = 0101; cpuid = 1; lapic.id = 0100 Debugger(panic) Stopped at Debugger+0x37: movl$0,in_Debugger db trace Debugger(f01f1806) at Debugger+0x37 panic(f01fbb50,f046f1c0,0,80,f45cbb20) at panic+0xa4 vm_page_alloc(f45f6f68,80,3,0,80) at vm_page_alloc+0x114 vm_page_grab(f45f6f68,80,83,0,80) at vm_page_grab+0x8d _pmap_allocpte(f45cbb20,80,201df000,201df000,2a86000) at _pmap_allocpte+0x19 pmap_allocpte(f45cbb20,201df000,f02c4df4,201df000,f45cbac0) at pmap_allocpte+0x53 pmap_enter(f45cbb20,201df000,2a86000,5,0) at pmap_enter+0x3d vm_fault(f45cbac0,201df000,1,0,f4195180) at vm_fault+0x891 trap_pfault(f45f9fbc,1,201df236) at trap_pfault+0xf2 trap(27,27,,5,efbfad38) at trap+0x1c2 calltrap() at calltrap+0x3c --- trap 0xc, eip = 0x201df236, esp = 0xefbfac4c, ebp = 0xefbfad38 --- db c boot() called on cpu#1 syncing disks... 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 giving up 1: dev:, flags:20020034, blkno:1057008, lblkno:0 [..] This was compiled two houts ago from absolute latest -current: FreeBSD spinner.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #385: Sat Jan 23 08:38:42 WST 1999 pe...@spinner.netplex.com.au:/home/src/sys/compile/SPINNER i386 My other SMP machine (2xPPro200) seems to be running fine: FreeBSD beast.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #267: Thu Jan 21 21:39:45 WST 1999 pe...@beast.netplex.com.au:/home/src/sys/compile/BEAST i386 Cheers, -Peter I just got the same thing doing a make -j8 world Machine is a dual pentium pro Intel PR440FX This must be from the recent vm changes as I could make -j8 world continually a few days ago without problem. This is the second time it happened to me the first time I was running X so I couldn't see the debugger message . This time without X I got the : panic: found dirty cache page Manfred = ||man...@netcom.com|| ||p...@infinex.com || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: PNP and new bootloader with ELF kernel
Tim wrote: and, in your /boot/loader.rc, put load /kernel load -t userconfig_script /kernel.config Thanks for the info but unfortunately this has not worked, maybe this is the syntax I have used in the /kernel.config file pnp 1 enable os irq0 11 port0 0x3e8 used to work before else what permissions do the files need to be also, where did you find this load -t stuff load -t stuff is new stuff, currently undocumented, with the sole exception of help at loader's prompt (I assume you are using current from sometime this month, since the new loader was introduced in november/december). The load -t stuff is what will make /kernel.config get read. Your old contents for that file should be ok otherwise. Before modifying /boot/loader.rc, though, you might just *type* these commands at the loader's prompt (followed by boot), to test if they actually work. -- Daniel C. Sobral(8-DCS) d...@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic: found dirty cache page 0xf046f1c0
Peter Wemm wrote: Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got lost): panic: found dirty cache page 0xf046f1c0 mp_lock = 0101; cpuid = 1; lapic.id = 0100 Debugger(panic) Stopped at Debugger+0x37: movl$0,in_Debugger db trace This is possibly a false alarm.. Something wierd was happening. I cleaned out the kernel and reconfigured with NFS static (it was being loaded) and it seems to boot OK. At least, I'm not getting console corruption (random baud rate changes) and the SMP mutex being broken and both cpu's entering the kernel at once. I think I'll blame it on the 15 hour electrical storm. :-] Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic: found dirty cache page 0xf046f1c0
:Peter Wemm wrote: : Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got : lost): : : panic: found dirty cache page 0xf046f1c0 :... : :This is possibly a false alarm.. Something wierd was happening. I cleaned :out the kernel and reconfigured with NFS static (it was being loaded) and :it seems to boot OK. At least, I'm not getting console corruption (random :baud rate changes) and the SMP mutex being broken and both cpu's entering :the kernel at once. I think I'll blame it on the 15 hour electrical :storm. :-] : :Cheers, :-Peter An old nfs module would almost certainly not work with the new kernel without at least a recompile. I'd definitely recommend keeping the major modules compiled in rather then dynamically loaded, just on principle. In fact, in all my time at BEST and all my time playing with FreeBSD, I have *never* used any dynamic module except for the linux compatibility thingy, and even that was only a fluke. If you can compile it in, compile it in. But, keep a watch on it. I didn't have an SMP box to test the new VM stuff on so it's possible there's something going on there. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: kvm_getswapinfo() function added to libkvm. top, pstat, systat updated
:On Fri, 22 Jan 1999, Matthew Dillon wrote: : : A new function, kvm_getswapinfo(), has been added to libkvm. : : pstat, systat, and top have been updated to use the new function. : :Have you considered using sysctl(3) for this instead? If yes, could you :explain why the libkvm seemed better to you? That's easy. Look how much code kvm_getswapinfo() is and tell me that you want to waste that memory in the kernel. :(I'm asking because with libkvm you need to use /dev/kmem _and_ you need :to access symbol table - this doesn't work with stripped kernels). : :Andrzej Bialecki You can boot with a stripped kernel and then point the system's notion of the kernel binary to a non-stripped version. That doesn't handle permissions, but getting deep-down swap information is not something any standard utility ever needs to do. It isn't something like getting the load average, which utilities may legitimately need. For that reason, I see no problem leaving kvm_getswapinfo() in libkvm. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic: found dirty cache page 0xf046f1c0
:At 10:34 AM 1/23/99 +0800, Peter Wemm wrote: :Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got :lost): : :panic: found dirty cache page 0xf046f1c0 :mp_lock = 0101; cpuid = 1; lapic.id = 0100 :... :I just got the same thing doing a make -j8 world :Machine is a dual pentium pro Intel PR440FX :This must be from the recent vm changes as I could make -j8 world :continually a :few days ago without problem. This is the second time it happened to me :the first time I was running X so I couldn't see the debugger message . :This time without X I got the : : :panic: found dirty cache page : :Manfred Any dynamically loaded modules? e.g. nfs? Did you update /usr/src/contrib/sys (i.e. softupdates ) along with /usr/src/sys ? Are you using vinum? -Matt := :||man...@netcom.com|| :||p...@infinex.com || :||Ph. (415) 681-6235|| := Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic: found dirty cache page 0xf046f1c0
On Fri, 22 Jan 1999, Manfred Antar wrote: At 10:34 AM 1/23/99 +0800, Peter Wemm wrote: Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got lost): panic: found dirty cache page 0xf046f1c0 mp_lock = 0101; cpuid = 1; lapic.id = 0100 Debugger(panic) Stopped at Debugger+0x37: movl$0,in_Debugger db trace Debugger(f01f1806) at Debugger+0x37 panic(f01fbb50,f046f1c0,0,80,f45cbb20) at panic+0xa4 vm_page_alloc(f45f6f68,80,3,0,80) at vm_page_alloc+0x114 vm_page_grab(f45f6f68,80,83,0,80) at vm_page_grab+0x8d _pmap_allocpte(f45cbb20,80,201df000,201df000,2a86000) at _pmap_allocpte+0x19 pmap_allocpte(f45cbb20,201df000,f02c4df4,201df000,f45cbac0) at pmap_allocpte+0x53 pmap_enter(f45cbb20,201df000,2a86000,5,0) at pmap_enter+0x3d vm_fault(f45cbac0,201df000,1,0,f4195180) at vm_fault+0x891 trap_pfault(f45f9fbc,1,201df236) at trap_pfault+0xf2 trap(27,27,,5,efbfad38) at trap+0x1c2 calltrap() at calltrap+0x3c --- trap 0xc, eip = 0x201df236, esp = 0xefbfac4c, ebp = 0xefbfad38 --- db c boot() called on cpu#1 syncing disks... 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 giving up 1: dev:, flags:20020034, blkno:1057008, lblkno:0 [..] This was compiled two houts ago from absolute latest -current: FreeBSD spinner.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #385: Sat Jan 23 08:38:42 WST 1999 pe...@spinner.netplex.com.au:/home/src/sys/compile/SPINNER i386 My other SMP machine (2xPPro200) seems to be running fine: FreeBSD beast.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #267: Thu Jan 21 21:39:45 WST 1999 pe...@beast.netplex.com.au:/home/src/sys/compile/BEAST i386 Cheers, -Peter I just got the same thing doing a make -j8 world Machine is a dual pentium pro Intel PR440FX This must be from the recent vm changes as I could make -j8 world continually a few days ago without problem. This is the second time it happened to me the first time I was running X so I couldn't see the debugger message . This time without X I got the : panic: found dirty cache page You should definitely be using DDB_UNATTENDED, by the way, if you're going to be running X and want DDB but not to have DDB try to pop up on a panic. I did get DDB_UNATTENDED behavior finally working as well as it should, so there's no reason not to use it. Manfred = ||man...@netcom.com|| ||p...@infinex.com || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
-current now dead for over 24 hours.
All because of a makefile snaffoo.. luoqi has a patch to fix it, but if anyone knows what the author was trying to achieve, can they please try fixing it? julian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: some guidance on forked cvsup please
In article 199901210732.saa09...@lightning.itga.com.au, Gregory Bond g...@itga.com.au wrote: Now we've gone and got forked, can someone please give us examples of cvsup files for those that want to follow 4-current and those that want to follow 3-stable. To track -current, the cvsupfile should contain tag=. To track 3-stable, it should contain tag=RELENG_3. For the rest of the cvsupfile, see the examples in /usr/share/examples/cvsup. I haven't updated them with the new RELENG_3 tag yet, but I will do that soon. John -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Nobody ever went broke underestimating the taste of the American public. -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic: found dirty cache page 0xf046f1c0
Matthew Dillon wrote: :Peter Wemm wrote: : Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got : lost): : : panic: found dirty cache page 0xf046f1c0 :... : :This is possibly a false alarm.. Something wierd was happening. I cleaned :out the kernel and reconfigured with NFS static (it was being loaded) and :it seems to boot OK. At least, I'm not getting console corruption (random :baud rate changes) and the SMP mutex being broken and both cpu's entering :the kernel at once. I think I'll blame it on the 15 hour electrical :storm. :-] : :Cheers, :-Peter An old nfs module would almost certainly not work with the new kernel without at least a recompile. I'd definitely recommend keeping the major modules compiled in rather then dynamically loaded, just on principle. In fact, in all my time at BEST and all my time playing with FreeBSD, I have *never* used any dynamic module except for the linux compatibility thingy, and even that was only a fluke. If you can compile it in, compile it in. It's definately happening still, sorry. :-( I recompiled a 100% static kernel and have had three more explosions, usually after starting exmh. (exmh takes 10 to 15MB of ram on this system due to my mailbox folder sizes). But, keep a watch on it. I didn't have an SMP box to test the new VM stuff on so it's possible there's something going on there. However, a clue.. The SMP box that is doing fine is a P6, an NFS client and server (loading nfs.ko, it fsck's fast, so I use that box for making sure the modules work). The one that is crashing, is a P5, an NFS client and server (static kernel), and with a MFS /tmp. Both run softupdates (up to date src/contrib/sys). I suspect MFS is the key. There's the new VOP_FREEBLKS() stuff you added, and the corresponding calls to madvise to free the pages. Given madvise()'s murky history, I can't help but feel suspicious about it. I've unmounted /tmp and am about to thrash the machine. At the moment, it's sitting on: Swap: 120M Total, 376K Used, 120M Free Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
softupdates bug shows on zip drive and parallel port in NIBBLE mode
I tried both cam and bio -- no difference. It is not that it's slow -- I was prepared for that, it is that it totally hangs -- forever. I narrowed it down to softupdates. If I disable the softupdates on the cartridge's filesystem copying finishes successfully. Somehow the `cp' process takes 150% of the CPU time (purely single CPU system), but that's a different story, I guess. I hope, this sad experience of mine will help further improve softupdates. -mi - Forwarded message from Alfred Perlstein - On Fri, 22 Jan 1999, Mikhail Teterin wrote: When I try to cp a big file (Wordperfect distribution) onto a Zip cartridge (with ufs with softupdates) the whole system becomes jerky and soon hangs -- I can still go from one virtual console to another, but can not do anything and need cold reboot. [...] try searching the lists, my suggestion is to compile like so: controller ppc0 at isa? disable port ? tty irq 7 change to: controller ppc0 at isa? disable port ? cam irq 7 -^^^ you may also want to try 'bio' it's been explained on the lists and i'm unsure. - End of forwarded message from Alfred Perlstein - To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: -current now dead for over 24 hours.
Julian Elischer wrote: All because of a makefile snaffoo.. luoqi has a patch to fix it, but if anyone knows what the author was trying to achieve, can they please try fixing it? brandon and markm seem to have vanished. Please, commit luoqi's patch. You have commit privilege. -- Steve finger ka...@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
SOFTUPDATES code in 3.0-RELEASE
Is this code included, or must it be patched in? Is softupdates enabled by default or do I have to use a special mount flag? Thanks, Joe Joe McGuckin ViaNet Communications 1235 Pear Ave, Suite 107 Mountain View, CA 90403 Phone: 650-969-2203 Cell: 415-710-4894 Fax: 650-969-2124 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: SOFTUPDATES code in 3.0-RELEASE
On Fri, 22 Jan 1999, Joe McGuckin wrote: Is this code included, or must it be patched in? Because of licensing issues, you have to enable it yourself. See the instructions in /sys/ufs/ffs/README.softupdates for how to do this. Is softupdates enabled by default or do I have to use a special mount flag? Neither. :) Once you have a softupdates kernel, you use tunefs -n enable on the unmounted filesystem to enable softupdates. (You only have to do this once.) -- Brian Buchanan br...@csua.berkeley.edu -- FreeBSD - The Power to Serve! http://www.freebsd.org daemon(n): 1. an attendant power or spirit : GENIUS 2. the cute little mascot of the FreeBSD operating system To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: -current now dead for over 24 hours.
Steve Kargl wrote: Julian Elischer wrote: All because of a makefile snaffoo.. luoqi has a patch to fix it, but if anyone knows what the author was trying to achieve, can they please try fixing it? brandon and markm seem to have vanished. Please, commit luoqi's patch. You have commit privilege. I have not! Fix coming! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
kvm question
I ran into an interesting problem in the process of modifying netstat to understand the PF_NETGRAPH protocol family. netstat uses kvm_read(), etc. to read kernel symbols. However, this doesn't work when the symbols you're looking for are in an KLD module (eg, ng_socket.ko) -- the symbol will not be found. So I added some code/hackery to look for any loaded modules and if on named ng_socket.ko was found, try finding the symbol in there. My question is, should kvm_read() and friends be enhanced with this ability to find a symbol by searching through the loaded KLD modules? Seems a bit hackish, but then again so is the whole kvm() idea. I'd be willing to add this code if so.. it's not much. Unrelated question: SYSINIT() doesn't work from KLD modules. Is this problem being addressed? -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
