Recent KVA increase allows maxusers64 ?
Hi folks, I've gotten myself confused. Am I correct in thinking that dg's recent hike on KVA size allows for MAXUSERS 64 without odd lock-ups? Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
sio, dca
i have problems with sio and i read in the man something about dca(4), is it a replacement ? does it work well ? is it included with 4.0-CURRENT ? please reply
Re: Postfix
On Sun, 14 Mar 1999 17:22:42 +0100, Blaz Zupan wrote: We don't even have a Postfix port. Has anybody created a port or should I go ahead and have a look at it? Hi Blaz, Have a look at the PR database, specifically at ports/10710. I haven't checked it out myself. Perhaps you'd like to try it out and send feedback to the freebsd-ports mailing list, which is a much more appropriate list through which to address this sort of issue. http://www.freebsd.org/cgi/query-pr.cgi?pr=10710 Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RealTek driver woes
I'm running a RealTek ethernet card in a 486dx4-100 machine and am having some problems. Firstly, doing an ls on a nfs mounted directory exported from the RealTek machine hangs. According to tcpdump it is receiving the readdir packets. Secondly, it will hange solidly when acting as the receiver (haven't tried it as the sender) running the netpipe tests (NPtcp -s -r receiving, the sender runs NP -t -h host_rl -s) - no DDB, just a solid hang. An ISA SMC card in the same machine is fine. I've tried it with RL_USEIOSPACE defined and undefined. This is running a very current system, with the id string $Id: if_rl.c,v 1.12 1999/02/23 15:38:25 wpaul Exp$ Here's the dmesg output. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Thu Mar 25 21:37:03 WST 1999 t...@bloop.craftncomp.com:/data/src/sys/compile/bleep Timecounter i8254 frequency 1193182 Hz CPU: AMD Enhanced Am486DX4 Write-Through (486-class CPU) Origin = AuthenticAMD Id = 0x484 Stepping=4 Features=0x1FPU real memory = 16777216 (16384K bytes) avail memory = 13750272 (13428K bytes) Preloaded elf kernel kernel at 0xc02c3000. Preloaded elf module linux.ko at 0xc02c309c. Probing for devices on PCI bus 0: chip0: Host to PCI bridge (vendor=10b9 device=1445) rev 0x00 on pci0.0.0 rl0: RealTek 8139 10/100BaseTX rev 0x10 int a irq 9 on pci0.4.0 rl0: Ethernet address: 00:00:e8:53:a2:3e rl0: autoneg complete, link status good (half-duplex, 10Mbps) Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:d2:b2:72, type SMC8216T (16 bit) atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pca0 on motherboard pca0: PC speaker audio driver ata0 at 0x1f0-0x1f7 irq 14 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled ad0: ST34321A/3.11 ATA-4 disk at ata0 as master ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue changing root device to ad0s2a Stephen -- The views expressed above are not those of PGS Tensor. People often think of research as a form of development -- that it's about doing exactly what you planned, doing it on time, and doing it with resources that you said you'd use. But if you're going to do that, you have to know what you are doing, and if you know what you are doing, it isn't really research. --Dave Liddle, The New Yorker, Feb. 23/Mar.2, 1998, p 84 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Postfix
Have a look at the PR database, specifically at ports/10710. I haven't checked it out myself. Perhaps you'd like to try it out and send feedback to the freebsd-ports mailing list, which is a much more appropriate list through which to address this sort of issue. If you had taken at look at the PR yourself, you'd notice that it was ME, who submited that PR :) Blaz Zupan, b...@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
rc.conf issues: host identity vs host config
The current rc.conf system doesn't seem to allow for separating out host identity from host configuration. As a result I'm not able to create a site-wide rc.conf file and rdist it to multiple machines, configured identically except for having distinct own host names. I think some very basic information identifying a host should be kept in its own place: host name and ip address for each network interface And I like the way SunOS does it: The file hostname.if contains the machine's host name, where if is the name of the network interface. E.g., if the only network interface is le0, the file hostname.le0 contains the host name. With multiple network interfaces you would have a distinct hostname.if file for each one. Now you can rdist /etc/hosts containing all host names and IP addresses. At boot time we get the host name from hostname.if, look up the host name in /etc/hosts, and get our IP address. And non-default netmasks are listed in /etc/netmasks, which can also be propagated via rdist. To reassign IP addresses, simply rdist a new copy of /etc/hosts and reboot all machines. Rahul To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Postfix
On Thu, 25 Mar 1999 17:30:18 +0100, Blaz Zupan wrote: If you had taken at look at the PR yourself, you'd notice that it was ME, who submited that PR :) I did take a look at it, that's how I know about it. You don't seriously expect me to notice the name of each originator for each PR I look at, do you? :-) Anyway, this is going to get silly soon. Everyone knows about the PR now, so it's really just a case of someone spending time on a commit. I'll bet you a noddy badge that it won't be jmb. ;-) Later, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: rc.conf issues: host identity vs host config
On Thu, 25 Mar 1999 08:41:22 PST, Rahul Dhesi wrote: The current rc.conf system doesn't seem to allow for separating out host identity from host configuration. Use /etc/rc.conf for host configuration and /etc/rc.conf.local for host identity. Or whatever. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Spontaneous reboots
Kris Kennaway wrote: Has anyone else been seeing this? What kind of information would help to narrow the problem down? This has happened a few times on my -stable box, though not very often. It just happened a few minutes ago, I wasn't doing anything on the machine, I wasn't even logged in. No core dump or anything. :-( I'd think nothing of it on a -current box, but it seems a bit worrying that this sort of thing happens on a supposedly stable version. Mind you, it could be a hardware problem I suppose. Karl Pielorz wrote: The sort of thing we're looking for is, Which version of FreeBSD (I'd assume something -current because you posted to the -current mailing list, but how current?), what hardware (i.e. CPU type [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? FreeBSD 3.1-STABLE, Cyrix 6x86 133MHz, 48MB RAM. I don't think I've got any hardware I'd class as weird. Disk info, $ mount /dev/wd0s2a on / (local, noatime, writes: sync 5 async 17) /dev/wd0s3c on /home (local, soft-updates, writes: sync 2 async 61) /dev/wd2s1c on /tmp (local, soft-updates, writes: sync 2 async 31) /dev/wd2s2e on /usr (local, soft-updates, writes: sync 2 async 86) /dev/wd2s3e on /var (local, nosuid, soft-updates, writes: sync 318 async 470) procfs on /proc (local) $ swapinfo Device 1K-blocks UsedAvail Capacity Type /dev/wd2s4b1606500 160522 0%Interleaved I'm not sure how recent, the machine had been up for nearly 22 days, and I think I rebuilt the world soon before that, so it's as of around the beginning of March. Brian Feldman wrote: He should proviide a full dmesg from bootverbose mode. OK, I wonder if anyone can spot the problem in this (if indeed there is something I've broken)... Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-STABLE #104: Tue Mar 2 18:29:08 GMT 1999 b...@scientia.demon.co.uk:/usr/src/sys/compile/SCIENTIA Calibrating clock(s) ... i8254 clock: 1193483 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CPU: Cyrix 6x86 (486-class CPU) Origin = CyrixInstead DIR=0x2231 Stepping=2 Revision=2 real memory = 50331648 (49152K bytes) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x0020 - 0x02ffdfff, 48226304 bytes (11774 pages) avail memory = 47013888 (45912K bytes) Found BIOS32 Service Directory header at 0xf00fad20 Entry = 0xfb1a0 (0xf00fb1a0) Rev = 0 Len = 1 PCI BIOS entry at 0xb1d0 Other BIOS signatures found: ACPI: $PnP: 000fbf50 pci_open(1):mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=70308086) Probing for devices on PCI bus 0: found- vendor=0x8086, dev=0x7030, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 chip0: Intel 82437VX PCI cache memory controller rev 0x02 on pci0.0.0 PCI Concurrency: enabled Cache: 256K pipelined-burst secondary; L1 enabled DRAM: no memory hole, 66 MHz refresh Read burst timing: x-2-2-2/x-3-3-3 Write burst timing: x-3-3-3 RAS-CAS delay: 3 clocks found- vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 chip1: Intel 82371SB PCI to ISA bridge rev 0x01 on pci0.7.0 I/O Recovery Timing: 8-bit 2 clocks, 16-bit 1 clocks Extended BIOS: disabled Lower BIOS: disabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: disabled, B: disabled, C: IRQ11, D: disabled MB0: IRQ15, MB1: found- vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[0]: type 4, range 32, base f000, size 4 ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 04 from port: f002 intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1
Re: Problems with ELF Emacs
Peter Jeremy peter.jer...@auss2.alcatel.com.au writes: I'm running -current from a couple of weeks ago. I recently re-compiled XFree86 to ELF - which works, and re-compiled emacs-19.34b - which won't work with X11, though it does work inside an Xterm. My old aout emacs still works (with old aout libraries - the re-compiled aout libraries seem to be missing a symbol). I run an Elf build of Emacs 19.34b daily on a completely Elf, very up-to-date 4.0-CURRENT box with Elf XFree86 3.3.3.1. No trouble at all. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: latest -current doesn't execute BSDI-binary bladeenc
In article 199903170258.saa01...@implode.root.com, David Greenman d...@root.com wrote: A much better solution would be for someone to spend the time to implement the needed VM frobbing of modifying, at BSDI binary exec-time, the ps_strings address constant in the binary's crt0 that is causing the problem. Is that the only issue as far as the kernel is concerned? If so, there's an easy solution. If %ebx is nonzero on entry to a BSD/OS executable, it is taken to be the ps_strings constant. Otherwise a hard-coded value is used. So all we have to do is arrange for %ebx to have the right value on entry to the program. It looks easy to fix. Add a new member to struct image_params for the ps_strings value, and set it in the various image activators. It should be PS_STRINGS (from sys/exec.h) for a BSD/OS binary (a_midmag == 0314), and 0 for all others. Then in kern_exec.c:execve(), pass the value to setregs() as a new parameter. Stuff it into %ebx in i386/machdep.c:setregs(), and ignore it for the other architectures. That should do it. John -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Spontaneous reboots
There was another report of a similar problem on -hackers. Removing the 'pseudo-device splash' seemed to fix things. You might also try the patches in this thread. http://www.freebsd.org/cgi/getmsg.cgi?fetch=715663+0+archive/1999/freebsd-hackers/19990307.freebsd-hackers Nathan Ben Smithurst b...@scientia.demon.co.uk wrote: Kris Kennaway wrote: Has anyone else been seeing this? What kind of information would help to narrow the problem down? This has happened a few times on my -stable box, though not very often. It just happened a few minutes ago, I wasn't doing anything on the machine, I wasn't even logged in. No core dump or anything. :-( I'd think nothing of it on a -current box, but it seems a bit worrying that this sort of thing happens on a supposedly stable version. Mind you, it could be a hardware problem I suppose. Karl Pielorz wrote: The sort of thing we're looking for is, Which version of FreeBSD (I'd assume something -current because you posted to the -current mailing list, but how current?), what hardware (i.e. CPU type [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? FreeBSD 3.1-STABLE, Cyrix 6x86 133MHz, 48MB RAM. I don't think I've got any hardware I'd class as weird. Disk info, $ mount /dev/wd0s2a on / (local, noatime, writes: sync 5 async 17) /dev/wd0s3c on /home (local, soft-updates, writes: sync 2 async 61) /dev/wd2s1c on /tmp (local, soft-updates, writes: sync 2 async 31) /dev/wd2s2e on /usr (local, soft-updates, writes: sync 2 async 86) /dev/wd2s3e on /var (local, nosuid, soft-updates, writes: sync 318 async 470) procfs on /proc (local) $ swapinfo Device 1K-blocks UsedAvail Capacity Type /dev/wd2s4b1606500 160522 0%Interleaved I'm not sure how recent, the machine had been up for nearly 22 days, and I think I rebuilt the world soon before that, so it's as of around the beginning of March. Brian Feldman wrote: He should proviide a full dmesg from bootverbose mode. OK, I wonder if anyone can spot the problem in this (if indeed there is something I've broken)... Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-STABLE #104: Tue Mar 2 18:29:08 GMT 1999 b...@scientia.demon.co.uk:/usr/src/sys/compile/SCIENTIA Calibrating clock(s) ... i8254 clock: 1193483 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CPU: Cyrix 6x86 (486-class CPU) Origin = CyrixInstead DIR=0x2231 Stepping=2 Revision=2 real memory = 50331648 (49152K bytes) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x0020 - 0x02ffdfff, 48226304 bytes (11774 pages) avail memory = 47013888 (45912K bytes) Found BIOS32 Service Directory header at 0xf00fad20 Entry = 0xfb1a0 (0xf00fb1a0) Rev = 0 Len = 1 PCI BIOS entry at 0xb1d0 Other BIOS signatures found: ACPI: $PnP: 000fbf50 pci_open(1): mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=70308086) Probing for devices on PCI bus 0: found- vendor=0x8086, dev=0x7030, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 chip0: Intel 82437VX PCI cache memory controller rev 0x02 on pci0.0.0 PCI Concurrency: enabled Cache: 256K pipelined-burst secondary; L1 enabled DRAM: no memory hole, 66 MHz refresh Read burst timing: x-2-2-2/x-3-3-3 Write burst timing: x-3-3-3 RAS-CAS delay: 3 clocks found- vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 chip1: Intel 82371SB PCI to ISA bridge rev 0x01 on pci0.7.0 I/O Recovery Timing: 8-bit 2 clocks, 16-bit 1 clocks Extended BIOS: disabled Lower BIOS: disabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: disabled, B: disabled, C: IRQ11, D: disabled MB0: IRQ15, MB1: found- vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[0]: type 4, range 32, base f000, size 4 ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled,
Re: rc.conf issues: host identity vs host config
I think some very basic information identifying a host should be kept
in its own place:
host name and ip address for each network interface
And I like the way SunOS does it: The file hostname.if contains the
machine's host name, where if is the name of the network interface.
In /etc/rc.conf have the typical
network_interfaces=lo0 fxp0
line, but don't have a
ifconfig_fxp0=
this will cause ``/etc/rc.network'' to run this code:
# Set up all the network interfaces, calling startup scripts if needed
for ifn in ${network_interfaces}; do
if [ -e /etc/start_if.${ifn} ]; then
. /etc/start_if.${ifn}
fi
This is how DHCP users run ``/sbin/dhclient''. So in
``/etc/start_if.fxp0'' you can place ``hostname foo.bar.com'' along with
a ``ifconfig fxp0'' line.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: rc.conf issues: host identity vs host config
Sorry to reply to my own email, but there is an error. On Thu, Mar 25, 1999 at 11:00:28AM -0800, David O'Brien wrote: In /etc/rc.conf have the typical network_interfaces=lo0 fxp0 line, but don't have a ifconfig_fxp0= this will cause ``/etc/rc.network'' to run this code: The error is, reguardless of any ``ifconfig_fxp0=.'' lines in /etc/rc.conf, ``/etc/start_if.fxp0'' will be run (if it exists). Thus all you would need to do is put the ``hostname foo.bar.com'' in there. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: rc.conf issues: host identity vs host config
On 25-Mar-99 Rahul Dhesi wrote: The current rc.conf system doesn't seem to allow for separating out host identity from host configuration. As a result I'm not able to create a site-wide rc.conf file and rdist it to multiple machines, configured identically except for having distinct own host names. I think some very basic information identifying a host should be kept in its own place: host name and ip address for each network interface Have you looked at DHCP? You don't even have to rdist a file for that to work. We use PicoBSD to clone 80 machines by dd'ing the drives over the network and then have each machine's IP assigned to its ether address and use DHCP to distribute hostnames and IPs to each computer. Works like a charm. --- John Baldwin jobal...@vt.edu -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc Power Users Use the Power to Serve! - http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: JAIL code headed for -current.
add my vote for 3.1 chroot() has always been a little less than JAIL if the user so constrained expects/requires access to virtually anything. __ go not unto usenet for advice, for the inhabitants thereof will say: yes, and no, and maybe, and I don't know, and fuck-off. _ attila__ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: rc.conf issues: host identity vs host config
The current rc.conf system doesn't seem to allow for separating out host identity from host configuration. Just to squash this; yes, it does. As a result I'm not able to create a site-wide rc.conf file and rdist it to multiple machines, configured identically except for having distinct own host names. I think some very basic information identifying a host should be kept in its own place: You can do this trivially. Put the data in /etc/rc.conf.site, and include it at the end of /etc/rc.conf. rc.conf then contains per-system configuration information, and rc.conf.site can be rdist'ed around. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: rc.conf issues: host identity vs host config
Mike Smith wrote: As a result I'm not able to create a site-wide rc.conf file and rdist it to multiple machines, configured identically except for having distinct own host names. I think some very basic information identifying a host should be kept in its own place: You can do this trivially. Put the data in /etc/rc.conf.site, and include it at the end of /etc/rc.conf. rc.conf then contains per-system configuration information, and rc.conf.site can be rdist'ed around. Last I checked, rc.conf.site was referenced in defaults/rc.conf. Has this changed? -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org What kind of psychologist laughs at her patients? I don't laugh at all of them. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: rc.conf issues: host identity vs host config
On Fri, 26 Mar 1999 09:06:06 +0900, Daniel C. Sobral wrote: Last I checked, rc.conf.site was referenced in defaults/rc.conf. Has this changed? Check again. :-) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: JAIL code headed for -current.
I just noticed the date on this discussion was two months ago;
so I referenced the code in kern_prot.c which indicates no
decision was made on this item
was another solution implemented?
actually, in a more deliberate consideration of the implications
of changing the suser() call, I agree with Eric, but the concept,
including assigning an exclusive internal IP number is important
enough to warrant implementation, but maybe not with a revision
to the suser() arguments.
perhaps consider implementing a structure which each suser()
call, and any function in the chroot() space, can reference
which would contain the value of NOJAIL, the IP number, and
whatever other parameters are discovered to be needed later.
the structure can be added to any number of the sys/ group
includes (all though it must be individually static to each
icidence of chroot().
Eric's suggestion of the macro solves two problems: finding
all incidents of suser(), and ancilliary code added later which
might fail to notice the additional argument for which they
would receive the expected response...
int new_suser(chroot, cred, acflag)
struct uchroot *chroot;
struct ucred *cred;
u_short *acflag;
{
if (chroot-nojail)
return (EPERM); /* I presume this is the check */
if (cred-cr_uid == 0) {
if (acflag)
*acflag |= ASU;
return (0);
}
return (EPERM);
}
I always have a preference to structures despite the extra
reference --you can always add variables of any type as required.
with the CPU speeds approaching nirvana, every new project is
coded with a single stucture passed to each procedure; in many
cases passing an element or two is more efficient, but it breaks
the model.
in general it is no more expensive on cpu time than unravelling
a string of variables or structure elements being passed in
the call since each has a backward reference.
On Wed, 27 Jan 1999, Sean Eric Fagan wrote:
*In article 199901271944.laa15317.kithrup.freebsd.curr...@kithrup.com you
write:
*all over the kernel:
*
* suser(NOJAIL, bla, bla);
*or
* suser(0, bla, bla);
*Oh, goody, more gratuitious incomaptibilities with everyone else.
*
*And to followup to my own message, since nobody else has:
*
*This is stupid. While I don't object to the concept (and even know people who
*have requested it), that particular implementation sucks. It breaks an
*existing API *and* ABI.
*
*I would suggest using a different routine name than suser(); suser() can be
*made into a macro or stub routine that calls the new routine with a first
*argument of 0 (or, of course, both a macro *and* a stub routine).
*
*Any time there's a change, all over the kernel, THIS SHOULD RAISE WARNING
*FLAGS, PEOPLE!
*
*
*To Unsubscribe: send mail to majord...@freebsd.org
*with unsubscribe freebsd-current in the body of the message
*
__
go not unto usenet for advice, for the inhabitants thereof will say:
yes, and no, and maybe, and I don't know, and fuck-off.
_ attila__
The more things change, the more they stay insane.
To be a ruler of men, you need at least 12 inches
There is no safety this side of the grave. Never was; never will be.
__
Microsoft isn't evil, they just make really crappy Operating Systems
-Linus Torvalds
__
Windows 98: n.
useless extension to a minor patch release for 32-bit extensions and
a graphical shell for a 16-bit patch to an 8-bit operating system
originally coded for a 4-bit microprocessor, written by a 2-bit
company that can't stand for 1 bit of competition.
-
(c) 1999 Stan Brown. Redistribution via the Microsoft Network is prohibited.
__
(ASP) Microsoft Corporation (MSFT) announced today that the release of its
productivity suite, Office 2000, will be delayed until the first quarter
of 1901.
__
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
LZS (STAC) compression in i4b?
Hello, Does current i4b support LZS/STAC compression? My ISP just enabled it on their ISDN ports, I'd like to use it. Or is compression not necessary in the kernel driver, but in the userspace programs (ppp, pppd). When I grep through ppp sources I do see STAC mentioned somewhere. -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know p...@xs4all.nl | the Netherlands| what I'm doing. ---+-+-- Running FreeBSD-current UNIX. See http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Spontaneous reboots
On Thu, 25 Mar 1999, Ben Smithurst wrote: Kris Kennaway wrote: Has anyone else been seeing this? What kind of information would help to narrow the problem down? This has happened a few times on my -stable box, though not very often. It just happened a few minutes ago, I wasn't doing anything on the machine, I wasn't even logged in. No core dump or anything. :-( I'd think nothing of it on a -current box, but it seems a bit worrying that this sort of thing happens on a supposedly stable version. Mind you, it could be a hardware problem I suppose. It could. Ahem... are you absolutely certain there are no messages in /var/log/messages that happen before the reboot? Karl Pielorz wrote: The sort of thing we're looking for is, Which version of FreeBSD (I'd assume something -current because you posted to the -current mailing list, but how current?), what hardware (i.e. CPU type [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? FreeBSD 3.1-STABLE, Cyrix 6x86 133MHz, 48MB RAM. I don't think I've got any hardware I'd class as weird. Disk info, $ mount /dev/wd0s2a on / (local, noatime, writes: sync 5 async 17) /dev/wd0s3c on /home (local, soft-updates, writes: sync 2 async 61) /dev/wd2s1c on /tmp (local, soft-updates, writes: sync 2 async 31) /dev/wd2s2e on /usr (local, soft-updates, writes: sync 2 async 86) /dev/wd2s3e on /var (local, nosuid, soft-updates, writes: sync 318 async 470) procfs on /proc (local) $ swapinfo Device 1K-blocks UsedAvail Capacity Type /dev/wd2s4b1606500 160522 0%Interleaved I'm not sure how recent, the machine had been up for nearly 22 days, and I think I rebuilt the world soon before that, so it's as of around the beginning of March. Brian Feldman wrote: He should proviide a full dmesg from bootverbose mode. OK, I wonder if anyone can spot the problem in this (if indeed there is something I've broken)... Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-STABLE #104: Tue Mar 2 18:29:08 GMT 1999 b...@scientia.demon.co.uk:/usr/src/sys/compile/SCIENTIA Calibrating clock(s) ... i8254 clock: 1193483 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CPU: Cyrix 6x86 (486-class CPU) Origin = CyrixInstead DIR=0x2231 Stepping=2 Revision=2 real memory = 50331648 (49152K bytes) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x0020 - 0x02ffdfff, 48226304 bytes (11774 pages) avail memory = 47013888 (45912K bytes) Found BIOS32 Service Directory header at 0xf00fad20 Entry = 0xfb1a0 (0xf00fb1a0) Rev = 0 Len = 1 PCI BIOS entry at 0xb1d0 Other BIOS signatures found: ACPI: $PnP: 000fbf50 pci_open(1): mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=70308086) Probing for devices on PCI bus 0: found- vendor=0x8086, dev=0x7030, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 chip0: Intel 82437VX PCI cache memory controller rev 0x02 on pci0.0.0 PCI Concurrency: enabled Cache: 256K pipelined-burst secondary; L1 enabled DRAM: no memory hole, 66 MHz refresh Read burst timing: x-2-2-2/x-3-3-3 Write burst timing: x-3-3-3 RAS-CAS delay: 3 clocks found- vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 chip1: Intel 82371SB PCI to ISA bridge rev 0x01 on pci0.7.0 I/O Recovery Timing: 8-bit 2 clocks, 16-bit 1 clocks Extended BIOS: disabled Lower BIOS: disabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: disabled, B: disabled, C: IRQ11, D: disabled MB0: IRQ15, MB1: found- vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[0]: type 4, range 32, base f000, size 4 ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 04 from port: f002 intel_piix_status: secondary master/slave sample = 3, master/slave recovery =
Testers wanted: misc/10566
Hi folks, Can anyone using /etc/pccard_ether with a DHCP implementation _other_ than the one we have in the base system (isc-dhcp2) feed back on the diffs supplied in PR 10566, viewable at http://www.freebsd.org/cgi-bin/query-pr.cgi?pr=10566 Thanks, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: JAIL code headed for -current.
In message pine.bsf.4.05.9903252311150.22565-100...@hun.org, attila writes: I just noticed the date on this discussion was two months ago; so I referenced the code in kern_prot.c which indicates no decision was made on this item was another solution implemented? It is on my machine here, It has just been preempted by things related to the real world ( life). Just be patient it is on the way. -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
