Boatload of patche...
I have a boatload of patches I'd like to have reviewed. They are fixes for most of the current batch of compiler warnings in make buildworld. Any takers? I did fine one bug, I think. Warner To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Code Crusader 2.0.x on FreeBSD
Replying to both Scott Michel and Russell L. Carter: Scott. According to man pthread, libc_r is pulled in automatically by the -pthread switch.
Re: does login.conf limitations work ?
On Fri, 23 Apr 1999, Luigi Rizzo wrote: > Hi, > > i was wondering if the limitations that are supposed to be enforced via > the login.conf mechanism do really work... > > In particular, i have tried (on 3.1 something, but don't think that > current is much different in this respect) to enforce the daily etc. > login times but the system seems to ignore them. > > I think /etc/login.conf is properly parsed, because if i assign a user > to a class that is not defined in login.conf i get complaints, but > other than that i am unable to limit login time... > > Any hints ? That's also my impression. I glipmsed the whole source tree and I couldn't find any place where the limits are enforced. BTW. what entity should enforce login time limits? Kernel? Some user-space daemon? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
singed short to unsigned long conversion problem in isa.c
The type of the member id_port in isa_device structure is signed short
and a value is converted int unsigned long to allocate I/O port
resource via bus_alloc_resources. If an I/O port >= 0x8000,
conversion from signed short to unsigned long causes unexpected result
and nexus_alloc_resouce cannot allocate resouce.
Fix is:
-- BEGIN --
*** isa.c.orig Sat Apr 24 20:55:32 1999
--- isa.c Sat Apr 24 20:55:24 1999
***
*** 75,81
* The structure used to attach devices to the isa bus.
*/
struct isa_device {
! short id_port[ISA_NPORT_IVARS];
u_short id_portsize[ISA_NPORT_IVARS];
vm_offset_t id_maddr[ISA_NMEM_IVARS];
vm_size_t id_msize[ISA_NMEM_IVARS];
--- 75,81
* The structure used to attach devices to the isa bus.
*/
struct isa_device {
! u_short id_port[ISA_NPORT_IVARS];
u_short id_portsize[ISA_NPORT_IVARS];
vm_offset_t id_maddr[ISA_NMEM_IVARS];
vm_size_t id_msize[ISA_NMEM_IVARS];
-- END --
If this should not be in sys/i386/isa, I will copy this file into
sys/pc98/pc98. Comment please.
---+--+
KATO Takenori |FreeBSD |
Dept. Earth Planet. Sci, Nagoya Univ. |The power to serve! |
Nagoya, 464-8602, Japan| http://www.FreeBSD.org/ |
FreeBSD(98) 3.1: Rev. 01 available! |http://www.jp.FreeBSD.org/|
FreeBSD(98) 2.2.8: Rev. 01 available! +==+
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: does login.conf limitations work ?
Andrzej Bialecki writes: > On Fri, 23 Apr 1999, Luigi Rizzo wrote: > > > Hi, > > > > i was wondering if the limitations that are supposed to be enforced via > > the login.conf mechanism do really work... > > > > In particular, i have tried (on 3.1 something, but don't think that > > current is much different in this respect) to enforce the daily etc. > > login times but the system seems to ignore them. > > > > I think /etc/login.conf is properly parsed, because if i assign a user > > to a class that is not defined in login.conf i get complaints, but > > other than that i am unable to limit login time... > > > > Any hints ? > > That's also my impression. I glipmsed the whole source tree and I couldn't > find any place where the limits are enforced. BTW. what entity should > enforce login time limits? Kernel? Some user-space daemon? > To report a login.conf success, i've used on a 2.2.8 system the "cputime" ressource limit. I set it to zero and that worked very well. So may be only some limits are implemented ? Stephane Legrand. -- stephane.legr...@wanadoo.fr : http://perso.wanadoo.fr/stephane.legrand/ FreeBSD Francophone : http://www.freebsd-fr.org/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
make world error with source upto src-cur.3843
Hello, Is there anyone know how to fix the problem. I cannot make world with source src-cur.3843 and the error is as followings. Thanks. Clarence === Error === cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -DPREFIX=\"/usr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:423: `GPLUSPLUS_INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:423: initializer element for `include_defaults_array[0].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:424: `OLD_GPLUSPLUS_INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:424: initializer element for `include_defaults_array[1].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:449: `GCC_INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:449: initializer element for `include_defaults_array[2].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c: In function `main': /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: `GCC_INCLUDE_DIR' undeclared (first use in this function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: for each function it appears in.) *** Error code 1 Stop. === Error === To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: singed short to unsigned long conversion problem in isa.c
On Sat, 24 Apr 1999, KATO Takenori wrote:
> The type of the member id_port in isa_device structure is signed short
> and a value is converted int unsigned long to allocate I/O port
> resource via bus_alloc_resources. If an I/O port >= 0x8000,
> conversion from signed short to unsigned long causes unexpected result
> and nexus_alloc_resouce cannot allocate resouce.
>
> Fix is:
>
> -- BEGIN --
> *** isa.c.origSat Apr 24 20:55:32 1999
> --- isa.c Sat Apr 24 20:55:24 1999
> ***
> *** 75,81
>* The structure used to attach devices to the isa bus.
>*/
> struct isa_device {
> ! short id_port[ISA_NPORT_IVARS];
> u_short id_portsize[ISA_NPORT_IVARS];
> vm_offset_t id_maddr[ISA_NMEM_IVARS];
> vm_size_t id_msize[ISA_NMEM_IVARS];
> --- 75,81
>* The structure used to attach devices to the isa bus.
>*/
> struct isa_device {
> ! u_short id_port[ISA_NPORT_IVARS];
> u_short id_portsize[ISA_NPORT_IVARS];
> vm_offset_t id_maddr[ISA_NMEM_IVARS];
> vm_size_t id_msize[ISA_NMEM_IVARS];
> -- END --
>
> If this should not be in sys/i386/isa, I will copy this file into
> sys/pc98/pc98. Comment please.
It needs to be signed since the value -1 is used to indicate no port
resources. Perhaps it would be better to change it to 'int' instead of
'u_short'.
--
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: does login.conf limitations work ?
On Sat, 24 Apr 1999, Stephane Legrand wrote: > > That's also my impression. I glipmsed the whole source tree and I couldn't > > find any place where the limits are enforced. BTW. what entity should > > enforce login time limits? Kernel? Some user-space daemon? > > > > To report a login.conf success, i've used on a 2.2.8 system the > "cputime" ressource limit. I set it to zero and that worked very > well. So may be only some limits are implemented ? You're right, this part works. However, I was talking about login time (which is how long can user be logged on to the system), which isn't checked anywhere. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
New ATA hangs my machine
Hi, I'd love to play with the new IDE drivers, especially that I got an LS-120 drive, but... I can't mount my filesystems with it. I'm using today's sources (kernel config file attached), and it fsck's them just ok, and then just hangs. Keyboard works, though. If I boot with -v, it reports: ad0: invalid primary partition table: no magic and of course it just sits there... The issue is, however, that old kernel booted just fine. I attached relevant parts of dmesg with old drivers, and disklabel and fdisk output. Any clues? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ pci0: on pcib0 chip0: at device 0.0 on pci0 isab0: at device 7.0 on pci0 isa0: on isab0 ide_pci0: at device 7.1 on pci0 intel_piix_status: primary master sample = 3, master 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 slave sample = 3, slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled ide_pci: busmaster 0 status: 04 from port: 9002 intel_piix_status: secondary master sample = 3, master 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 slave sample = 3, slave recovery = 1 intel_piix_status: secondary slave fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled ide_pci: busmaster 1 status: 04 from port: 900a fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 intel_piix_dmainit: setting multiword DMA mode 2 wd0: wdsetmode() setting transfer mode to 22 intel_piix_status: primary master sample = 3, master recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = intel_piix_dmainit: setting multiword DMA mode 2 wd1: wdsetmode() setting transfer mode to 22 intel_piix_status: primary slave sample = 3, slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled wdc0: unit 1 (wd1): , DMA, 32-bit, multi-block-16 wd1: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wd1: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc0: interrupting at irq 14 wdc1 at port 0x170-0x177 irq 15 flags 0x80ff80ff on isa0 wdc1: unit 0 (atapi): , removable, dma, iordy wdc1: ATAPI Floppies not configured wdc1: unit 1 (atapi): , removable, accel, dma, iordis wcd0: drive speed 171 - 5500KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA, packet track wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked, lock protected wdc1: interrupting at irq 15 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d atkbd0: interrupting at irq 1 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status: kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status: psm0: failed to reset the aux device. vga0: on isa0 [...] BIOS Geometries: 0: 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1: 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2: 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3: 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4: 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5: 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6: 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7: 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. Considering FFS root f/s. changing root device to wd1s1a wd1s1: type 0xa5, start 63, end = 6291431, size 6291369 wd1s1: C/H/S end 391/158/63 (3926663) != end 6291431: invalid wd1s2: type 0xa5, start 6291432, end = 8418815, size 2127384 wd1s2: C/H/S start 39
Re: does login.conf limitations work ?
On Sat, 24 Apr 1999, Stephane Legrand wrote: > Andrzej Bialecki writes: > > On Fri, 23 Apr 1999, Luigi Rizzo wrote: > > > > > Hi, > > > > > > i was wondering if the limitations that are supposed to be enforced via > > > the login.conf mechanism do really work... > > > > > > In particular, i have tried (on 3.1 something, but don't think that > > > current is much different in this respect) to enforce the daily etc. > > > login times but the system seems to ignore them. > > > > > > I think /etc/login.conf is properly parsed, because if i assign a user > > > to a class that is not defined in login.conf i get complaints, but > > > other than that i am unable to limit login time... > > > > > > Any hints ? > > > > That's also my impression. I glipmsed the whole source tree and I couldn't > > find any place where the limits are enforced. BTW. what entity should > > enforce login time limits? Kernel? Some user-space daemon? > > > > To report a login.conf success, i've used on a 2.2.8 system the > "cputime" ressource limit. I set it to zero and that worked very > well. So may be only some limits are implemented ? > If you'd like to see where the ones which are implemented are implemented, look at the process context-switch routines in the kernel. Not having checked, but guessing, I bet login reads login.conf as a db and uses the values to set rlimits, which is where they would be set. > Stephane Legrand. > > -- > stephane.legr...@wanadoo.fr : http://perso.wanadoo.fr/stephane.legrand/ > FreeBSD Francophone : http://www.freebsd-fr.org/ > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: 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: New ATA hangs my machine
On Sat, 24 Apr 1999, Andrzej Bialecki wrote: > Hi, > > I'd love to play with the new IDE drivers, especially that I got an LS-120 Note that wfd is here for those drives.. I'm currently in a sticky situation: wd: works with all drives, does no manner of DMA on my 6.4G Medalist ATA: works with all but LS-120 (for me), does UDMA2 great on my Medalist, but has no dump routine > drive, but... I can't mount my filesystems with it. I'm using today's > sources (kernel config file attached), and it fsck's them just ok, and > then just hangs. Keyboard works, though. If I boot with -v, it reports: > > ad0: invalid primary partition table: no magic > > and of course it just sits there... > > The issue is, however, that old kernel booted just fine. I attached > relevant parts of dmesg with old drivers, and disklabel and fdisk output. > > Any clues? LBA? > > Andrzej Bialecki > > // WebGiro AB, Sweden (http://www.webgiro.com) > // --- > // -- FreeBSD: The Power to Serve. http://www.freebsd.org > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: 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: does login.conf limitations work ?
On Sat, 24 Apr 1999, Brian Feldman wrote: > On Sat, 24 Apr 1999, Stephane Legrand wrote: > > > Andrzej Bialecki writes: > > > On Fri, 23 Apr 1999, Luigi Rizzo wrote: > > > > > > > Hi, > > > > > > > > i was wondering if the limitations that are supposed to be enforced via > > > > the login.conf mechanism do really work... > > > > > > > > In particular, i have tried (on 3.1 something, but don't think that > > > > current is much different in this respect) to enforce the daily etc. > > > > login times but the system seems to ignore them. > > > > > > > > I think /etc/login.conf is properly parsed, because if i assign a user > > > > to a class that is not defined in login.conf i get complaints, but > > > > other than that i am unable to limit login time... > > > > > > > > Any hints ? > > > > > > That's also my impression. I glipmsed the whole source tree and I > > couldn't > > > find any place where the limits are enforced. BTW. what entity should > > > enforce login time limits? Kernel? Some user-space daemon? > > > > > > > To report a login.conf success, i've used on a 2.2.8 system the > > "cputime" ressource limit. I set it to zero and that worked very > > well. So may be only some limits are implemented ? > > > > If you'd like to see where the ones which are implemented are implemented, > look at the process > context-switch routines in the kernel. Not having checked, but guessing, I > bet login reads > login.conf as a db and uses the values to set rlimits, which is where they > would be set. > > > Stephane Legrand. > > > > -- > > stephane.legr...@wanadoo.fr : http://perso.wanadoo.fr/stephane.legrand/ > > FreeBSD Francophone : http://www.freebsd-fr.org/ > > > > > > To Unsubscribe: send mail to majord...@freebsd.org > > with "unsubscribe freebsd-current" in the body of the message > > Some of it works, and some doesn't some is implemented in login, other parts are in init.. rob To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: singed short to unsigned long conversion problem in isa.c
Doug Rabson wrote: > It needs to be signed since the value -1 is used to indicate no port > resources. Perhaps it would be better to change it to 'int' instead of > 'u_short'. Oops, I didn't realize this case. The assumption that an I/O port address is lower than 0x8000 is OK for IBM-PC's ISA-bus, but PC98 can use hiher addresses for ISA-bus like bus. ---+--+ KATO Takenori |FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. |The power to serve! | Nagoya, 464-8602, Japan| http://www.FreeBSD.org/ | FreeBSD(98) 3.1: Rev. 01 available! |http://www.jp.FreeBSD.org/| FreeBSD(98) 2.2.8: Rev. 01 available! +==+ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: does login.conf limitations work ?
> > "cputime" ressource limit. I set it to zero and that worked very > > well. So may be only some limits are implemented ? > > You're right, this part works. However, I was talking about login time > (which is how long can user be logged on to the system), which isn't > checked anywhere. too bad... this is something isp's would love to have! cheers luigi ---+- Luigi RIZZO . EMAIL: lu...@iet.unipi.it. Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) ---+- To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: singed short to unsigned long conversion problem in isa.c
Singed shorts are often the result of sitting on a stove during the summer. We also recently saw a "hanging root device to..." in a boot on one of our machines. :-) Robert N Watson rob...@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 Carnegie Mellon Universityhttp://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: does login.conf limitations work ?
Andrzej Bialecki wrote: > > On Sat, 24 Apr 1999, Stephane Legrand wrote: > > > > That's also my impression. I glipmsed the whole source tree and I > > couldn't > > > find any place where the limits are enforced. BTW. what entity should > > > enforce login time limits? Kernel? Some user-space daemon? > > > > To report a login.conf success, i've used on a 2.2.8 system the > > "cputime" ressource limit. I set it to zero and that worked very > > well. So may be only some limits are implemented ? > > You're right, this part works. However, I was talking about login time > (which is how long can user be logged on to the system), which isn't > checked anywhere. It isn't. Login.conf, just like, now, pam, is one of those cases of a wonderful clean, orthogonal solution which is only partially implemented. I personally think login time should be enforced through tty revocation. The main problem is that no solution exists which will do the right thing regarding processes to kill for all processes. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: singed short to unsigned long conversion problem in isa.c
On Sun, 25 Apr 1999, KATO Takenori wrote: > Doug Rabson wrote: > > > It needs to be signed since the value -1 is used to indicate no port > > resources. Perhaps it would be better to change it to 'int' instead of > > 'u_short'. > > Oops, I didn't realize this case. > > The assumption that an I/O port address is lower than 0x8000 is OK for > IBM-PC's ISA-bus, but PC98 can use hiher addresses for ISA-bus like > bus. I understand. I think the best thing is to store the port address as an int. I don't think there is a need to fork the file into a pc98 version. -- 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: singed short to unsigned long conversion problem in isa.c
> > Singed shorts are often the result of sitting on a stove during the > summer. > > We also recently saw a "hanging root device to..." in a boot on one of our > machines. You'll see the 'c' up above all of the SCSI device probe messages. Not sure how we go about making that one tidy. -- \\ 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
Heads up! config(8) changes..
This shouldn't cause much in the way of trouble, but it will complain about old lint in your config files. That includes 'net/tty/bio/cam' mask indicators, and 'vector xxxintr' as well as some of the wierder workarounds for the poor 'options' parsing. So: things like: device sio1 at isa? tty port "IO_COM2" tty irq 3 become: device sio1 at isa? port IO_COM2 irq3 options "VM86"-> options VM86 options "_KPOSIX_FOO=12345L" -> options _KPOSIX_FOO=12345L etc. These are warnings about things that have been silently ignored for a while, or I've just (hopefully) fixed. However, I don't know lex/yacc too well, so I could well have stuffed something up. If there isn't too much trouble (ha ha! I should know better than to touch config), I'll commit a set of cleaned up GENERIC / LINT files. You do not need to build a new config(8), the version numbers have not been bumped (and don't need to). Cheers, -Peter --- Forwarded Message peter 1999/04/24 11:59:20 PDT Modified files: usr.sbin/config config.h config.y lang.l main.c mkioconf.c mkmakefile.c mkoptions.c mkswapconf.c Log: More cleanups, tweaks and features. - make this work: options FOO123=456 *without quotes* - grumble (but accept) vector xxxintr, and tty/net/bio/cam flags. - complain if a device is specified twice (eg: 2 x psm0) - don't require quotes around: port IO_COM2 - recognize negative numbers. (ie: options CAM_DEBUG_UNIT=-1) - GC some more unused stuff (we don't have composite disks from config(8)). - various other nits (snprintf paranoia etc) Revision ChangesPath 1.24 +2 -12 src/usr.sbin/config/config.h 1.30 +58 -181 src/usr.sbin/config/config.y 1.19 +7 -7 src/usr.sbin/config/lang.l 1.32 +2 -2 src/usr.sbin/config/main.c 1.54 +4 -4 src/usr.sbin/config/mkioconf.c 1.41 +4 -4 src/usr.sbin/config/mkmakefile.c 1.11 +2 -2 src/usr.sbin/config/mkoptions.c 1.19 +6 -6 src/usr.sbin/config/mkswapconf.c --- End of Forwarded Message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Heads up! config(8) changes..
On Sat, Apr 24, 1999, Peter Wemm wrote: > This shouldn't cause much in the way of trouble, but it will complain > about old lint in your config files. That includes 'net/tty/bio/cam' > mask indicators, and 'vector xxxintr' as well as some of the wierder > workarounds for the poor 'options' parsing. > > So: things like: > device sio1 at isa? tty port "IO_COM2" tty irq 3 > become: > device sio1 at isa? port IO_COM2 irq3 > > options "VM86"-> options VM86 > options "_KPOSIX_FOO=12345L" -> options _KPOSIX_FOO=12345L > etc. Excellent! Why wasn't this done before? -- Chris Costello And on the seventh day, He exited from append mode. pgpGhVciU4sm2.pgp Description: PGP signature
Re: Heads up! config(8) changes..
Chris Costello wrote: > On Sat, Apr 24, 1999, Peter Wemm wrote: > > This shouldn't cause much in the way of trouble, but it will complain > > about old lint in your config files. That includes 'net/tty/bio/cam' > > mask indicators, and 'vector xxxintr' as well as some of the wierder > > workarounds for the poor 'options' parsing. > > > > So: things like: > > device sio1 at isa? tty port "IO_COM2" tty irq 3 > > become: > > device sio1 at isa? port IO_COM2 irq3 > > > > options "VM86"-> options VM86 > > options "_KPOSIX_FOO=12345L" -> options _KPOSIX_FOO=12345L > > etc. > >Excellent! Why wasn't this done before? Probably because the code was a nightmare.. :-) Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: does login.conf limitations work ?
In article , Andrzej Bialecki wrote: > On Fri, 23 Apr 1999, Luigi Rizzo wrote: > > That's also my impression. I glipmsed the whole source tree and I couldn't > find any place where the limits are enforced. BTW. what entity should > enforce login time limits? Kernel? Some user-space daemon? Pre-PAM, it would have been done in login itself, I believe. That's where other things such as password expiration are checked. With PAM, it should go into the "account management" modules. Somebody has submitted such a module to me, and they're currently making some post-review revisions I requested. After that I will commit it. Note, it doesn't handle login time restrictions either -- it does only what login does now. However, once the module exists, we'll at least have a place to put the changes into. 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: new-bus, pcm, and matcd (was Re: new-bus breaks both sound drivers)
>> >mp3s aren't playing quite right with x11amp though, little >> >skips here and there, they work fine with the old kernel. >> >mpg123 seems fine, as does the sound in FXTV. >> >I'll try making the world again. >> >> Was there ever any resolution/further inspection of this? > >Not as far I know; its still happening here. cmp3 (mpg123) also skips >in the same way, but its much less noticeable. >I've been updating and recompiling almost daily. Ugh. This also has the same effect on captured audio using fxtv. It seems that everything audio related is messed up now. (Or perhaps real time?) I will try to find the exact day where things broke I guses. I don't have much time right now though.. Chris To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: does login.conf limitations work ?
Luigi Rizzo once stated: => > "cputime" ressource limit. I set it to zero and that worked very => > well. So may be only some limits are implemented ? => => You're right, this part works. However, I was talking about login time => (which is how long can user be logged on to the system), which isn't => checked anywhere. = =too bad... this is something isp's would love to have! idled from ports? -mi To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: singed short to unsigned long conversion problem in isa.c
Doug Rabson once stated: => If this should not be in sys/i386/isa, I will copy this file into => sys/pc98/pc98. Comment please. = =It needs to be signed since the value -1 is used to indicate no port =resources. Perhaps it would be better to change it to 'int' instead of ='u_short'. Uff, waisting additional 24 physical bits for one bit of information... -mi To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
sound still broken
I was just wondering when and if sound was going to be fixed anytime soon, I'm still getting the same error as the last time I mailed. I just cvsupped about an hour ago, so I'm pretty up to date. Kenneth Culver To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: singed short to unsigned long conversion problem in isa.c
:> The assumption that an I/O port address is lower than 0x8000 is OK for :> IBM-PC's ISA-bus, but PC98 can use hiher addresses for ISA-bus like :> bus. : :I understand. I think the best thing is to store the port address as an :int. I don't think there is a need to fork the file into a pc98 version. : :-- :Doug RabsonMail: d...@nlsystems.com :Nonlinear Systems Ltd. Phone: +44 181 442 9037 I would recommend making it an unsigned short, and representing the -1 case with a '#define BAD_PORT ((unsigned short)-1)'. All representations and tests for this special case would be required to use the #define rather then a constant. -Matt Matthew Dillon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
