Re: Current in Production
Do you own a Harley? Do the Mosh Pit? You definitely like riding the edge of insanity... -current is always in a state of flux... I say you lucked out... FreeBSD is killer stuff, but, I personally wouldn't risk a job on the odds of getting a stable -current when I needed one... Chris Knight wrote: > Howdy, > > I'd just like to thank the FreeBSD team for an outstanding job. > I've got a FreeBSD-current system in production running an Intranet that has > just exceeded one year's uptime. Admittedly, the snapshot I built was > 30/10/2000, but it does go to show that current can indeed be used for > production systems. The system only ever had one reboot and that was when > the installation was migrated to a new box. > For those that are interested, the Intranet uses Apache, PHP, Firebird and > OpenLDAP for various Web-based management applications/tasks. > Again, thanks to everyone responsible for providing a reliable and > dependable distribution, even when it's considered unstable and for > development purposes only. > > Regards, > Chris Knight > Systems Administrator > AIMS Independent Computer Professionals > Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 > Web: http://www.aims.com.au jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel build breaks in bktr_i2c.c
last cvsup, less than an hour ago. cc -c -O -g -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I../../../../include -D_KERNEL -ffreestanding -include opt_global.h -fno-common -elf -mpreferred-stack-boundary=2 -Werror ../../../dev/bktr/bktr_i2c.c ../../../dev/bktr/bktr_i2c.c: In function `bt848_i2c_attach': ../../../dev/bktr/bktr_i2c.c:87: structure has no member named `i2c_sc' ../../../dev/bktr/bktr_i2c.c:92: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:93: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:95: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:95: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:101: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:103: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c: In function `bt848_i2c_detach': ../../../dev/bktr/bktr_i2c.c:113: structure has no member named `i2c_sc' ../../../dev/bktr/bktr_i2c.c:119: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:119: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:122: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:122: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c: In function `bti2c_smb_callback': ../../../dev/bktr/bktr_i2c.c:132: structure has no member named `i2c_sc' ../../../dev/bktr/bktr_i2c.c:141: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:142: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:149: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:150: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c: In function `bti2c_iic_callback': ../../../dev/bktr/bktr_i2c.c:165: structure has no member named `i2c_sc' ../../../dev/bktr/bktr_i2c.c:174: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:175: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:182: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:183: dereferencing pointer to incomplete type *** Error code 1 Stop in /usr/src/sys/i386/compile/WAHOO.UNIPROCESSOR. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Interesting syscons behaviour - [followup]
Yeah, I'm also using the SMP kernel. Dan Nelson wrote: > In the last episode (Jan 28), Jim Bryant said: > >>Oh yeah, I immediately did a shutdown with reboot, and the problem >>did not duplicate itself. >> >>Jim Bryant wrote: >> >> >>>After upgrading -current, then reverting back to the previous [more >>>stable] kernel, upon rebooting after reverting, I noticed the oddest >>>thing on ttyv0. Apparently, after /etc/rc took over in init all of the >>>text was still in the kernel color scheme. >>> >>>FreeBSD wahoo.kc.rr.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Fri Jan 18 >>>22:30:28 CST 2002 >>> >>>All I can say is that this is the first time I have seen this kinda >>>thing under FreeBSD, and I've been using it since version 1.1.5.1 >>> > > This happens to me about 50% of the time, but only with an SMP kernel, > and only with a verbose kernel boot. I just don't boot verbose anymore > :) I assume it's some sort of locking problem in the console driver. > > jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Interesting syscons behaviour - [followup]
Oh yeah, I immediately did a shutdown with reboot, and the problem did not duplicate itself. Jim Bryant wrote: > After upgrading -current, then reverting back to the previous [more > stable] kernel, upon rebooting after reverting, I noticed the oddest > thing on ttyv0. Apparently, after /etc/rc took over in init all of the > text was still in the kernel color scheme. > > FreeBSD wahoo.kc.rr.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Fri Jan 18 > 22:30:28 CST 2002 > > All I can say is that this is the first time I have seen this kinda > thing under FreeBSD, and I've been using it since version 1.1.5.1 > > jim jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Interesting syscons behaviour.
After upgrading -current, then reverting back to the previous [more stable] kernel, upon rebooting after reverting, I noticed the oddest thing on ttyv0. Apparently, after /etc/rc took over in init all of the text was still in the kernel color scheme. FreeBSD wahoo.kc.rr.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Fri Jan 18 22:30:28 CST 2002 All I can say is that this is the first time I have seen this kinda thing under FreeBSD, and I've been using it since version 1.1.5.1 jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Vinum issue with USB CompactFlash reader.
I know this is probably a minor issue, as it is only an annoyance, and doesn't impact operation or performance, but still.. Ever since I concatenated some old drives to make a more reasonable capacity out of them, I have been noticing the following whenever vinum is loaded at startup [Note: The dmesg output doesn't show it, but before the check condition errors, vinum is loaded. Also this occurs when no CF card is present in the reader, seems to do well when booted with a card in place.]: Could vinum not be detecting that this is a removable media device? Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 8) da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) da1 at ahc1 bus 0 target 15 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) Mounting root from ufs:/dev/ad0s1a cd1 at ahc0 bus 0 target 3 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim0 bus 0 target 0 lun 0 da3: Removable Direct Access SCSI-2 device da3: 150KB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present cd2 at ahc0 bus 0 target 4 lun 0 cd2: Removable CD-ROM SCSI-2 device cd2: 3.300MB/s transfers cd2: Attempt to query device size failed: NOT READY, Medium not present da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Cond
Re: Panic changing screen mode with vidcontrol
John Baldwin wrote: > On 27-Nov-01 Jim Bryant wrote: > >>VESA is broked. Remove VESA from your config. Been this way for months. >> >>It also will panic once in a VESA mode, such as my favorite and yours, >>132x60, when switching from vty to vty. >> > > Ouch, this is not good. This means vm86 is likely broke. Hmm, I wonder if the > TSS is broken somehow? Can you narrow this down to a particular commit? I think I wrote on this sometime in June or July. I went without internet access from about late-Feb/early-March through late-May/early-June. Once I was able to cvsup again, the problem was there. After writing to the list on this, I was responded to by the syscons maintainer [I forget his name, but I'll buy him a sake or Saporro to apologize for my memory lapse someday] who said that VESA is broken and should not be in my config. Sure enough, removing VESA fixed it. The closest answer I can give is the time-frame from about Feburary through June. My schedule is quite full right now, but I could do a little browsing through the attic as I can, and see what I can find related to both vm86 and syscons, as long as there are other eyes looking for it too. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic changing screen mode with vidcontrol
Andrew Kenneth Milton wrote > +---[ Peter Jeremy ]-- > | Having installed a new kernel and userland from sources about a day > | old, my vidcontrol command now causes a panic: > > [snip] > > | The command I used was "vidcontrol 132x60" after confirming that > | this was listed in "vidcontrol -i mode". I have previously been > | using VESA_132x60, but that also panics now. > > Was X running ? > > I get a panic on changing to VESA modes when X is already running. It will do this regardless if X is running. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic changing screen mode with vidcontrol
VESA is broked. Remove VESA from your config. Been this way for months. It also will panic once in a VESA mode, such as my favorite and yours, 132x60, when switching from vty to vty. Peter Jeremy wrote: > Having installed a new kernel and userland from sources about a day > old, my vidcontrol command now causes a panic: > > Fatal trap 12: page fault while in vm86 mode > fault virtual address = 0xc359b > fault code = user read, page not present > instruction pointer = 0xc000:0x359b > stack pointer = 0x0:0xf82 > frame pointer = 0x0:0xfdc > code segment= base 0x2, limit 0x5004f, type 0x0 > = DPL 0, pres 0, def32 0, gran 0 > processor eflags= interrupt enabled, resume, vm86, IOPL = 0 > current process = 57775 (vidcontrol) > > The backtrace shows nothing useful - gdb doesn't seem to handle > tracing through vm86 :-(. > > The command I used was "vidcontrol 132x60" after confirming that > this was listed in "vidcontrol -i mode". I have previously been > using VESA_132x60, but that also panics now. > > Any suggestions where to look? > > Peter > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: damaged file system despite unmounts
I recently [this week] had to revert to a tape backup of an out-of-sync /var because yet again, /var got mangled on 'shutdown -r now', this time, and I reported this to the list the first time this happened, is the second time I have had to do this, so this seems to be an ongoing issue. I have also receieved a lot of master superblock bad notices and had to manually fix those in between the two occurrances [the first was several months ago], anyhow, just like the first time, I got the master superblock bad warning, as well as the invalid label message. For some reason this always happens with /var, yet with no other filesystem. This time I newfs'ed without softupdates. We'll see what happens. David W. Chapman Jr. wrote: > On Wed, Nov 21, 2001 at 09:17:13AM -0500, Mikhail Teterin wrote: > >>For a while I was noticing my largest FS reported as not unmounted >>cleanly on boot. Today I decided to unmount it myself and check it with >>fsck. Here are the results. Notice, that the first fsck had to mark the >>FS clean. Notice that the second fsck found something else to do, and >>only the third one was happy. What's happening? Thanks, >> >> -mi >> >> > I noticed this a while ago on -current. I haven't checked recently, > but I do remember having this problem > > jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BTX issue, and general report on SMP issues...
John Baldwin wrote: > On 19-Nov-01 Jim Bryant wrote: > >>anyhow, now that this is working, i'm kinda pissed to have lost use of my >>mouse wheel. apparently the keyboard was made before >>wheels became popular. >> >>anyone know a good usb keyboard with a ps/2 mouse port built-in that will >>translate the wheel on the mouse? once ya get used to the >>wheels, it's amazing how much you use it... >> > > You can get USB mice with wheels I think. If the keyboard has a USB hub, then > it shouldn't care what the mouse is like. Does the keyboard have a PS/2 port > or some such? Yeah, this one is a belkin, and it lacks the hub, and instead has a ps/2 port on the side.. it's actually quite handy, as even now, it's not easy finding USB mice... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BTX issue, and general report on SMP issues...
John Baldwin wrote: > On 18-Nov-01 Jim Bryant wrote: > >>John Baldwin wrote: >> >> >>>On 16-Nov-01 Jim Bryant wrote: >>> >>> >>>>It's not the BIOS failing it... >>>> >>>>The BTX bootstrap loader V 1.00 detects the keyboard, and refuses to proceed >>>>without it. >>>> >>>> >>>Err, no. BTX cares zero, zilch, nada about keyboards. Can you please >>>provide >>>the error message you get? >>> >> >>It was no error message in particular, everything normally just froze. >> >>Anyhow, this is now a solved issue. >> >>Apparently, at one point in time a "-P" made itself into /boot.config, once >>/boot.config was rm'ed, everything sorted itself out. >> > > Oh, so it was booting over serial console, not quite frozen. It just looks > frozen. :) exactly... anyhow, now that this is working, i'm kinda pissed to have lost use of my mouse wheel. apparently the keyboard was made before wheels became popular. anyone know a good usb keyboard with a ps/2 mouse port built-in that will translate the wheel on the mouse? once ya get used to the wheels, it's amazing how much you use it... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BTX issue, and general report on SMP issues...
John Baldwin wrote: > On 16-Nov-01 Jim Bryant wrote: > >>It's not the BIOS failing it... >> >>The BTX bootstrap loader V 1.00 detects the keyboard, and refuses to proceed >>without it. >> > > Err, no. BTX cares zero, zilch, nada about keyboards. Can you please provide > the error message you get? It was no error message in particular, everything normally just froze. Anyhow, this is now a solved issue. Apparently, at one point in time a "-P" made itself into /boot.config, once /boot.config was rm'ed, everything sorted itself out. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BTX issue, and general report on SMP issues...
It's not the BIOS failing it... The BTX bootstrap loader V 1.00 detects the keyboard, and refuses to proceed without it. Chris Dempsey wrote: > Try changing the BIOS options regarding failing on all > errors. After changing my Tyan Thunder K7 to not fail > on keyboard failures, it was able to boot fine. > > Also, if you intend to use a USB keyboard permanently, > you may wish to comment out atkbdc from your kernel > configuration file. This will make it easier to set > up kbdcontrol with the USB keyboard. > > Let me know if you have further questions. > > Chris Dempsey jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
BTX issue, and general report on SMP issues...
I am in the process of switching to a USB keyboard with a PS/2 to USB mouse port on the KB [freeing IRQ 12]. The keyboard works, the mouse works. My problem here is in getting past the BTX loader WITHOUT the AT keyboard attached. How would I keep BTX from freezing when it can't see the AT keyboard? Also, after over a month of not being able to buildworld with SMP-current, I managed to build a kernel from the same sources that I built my last SMP kernel with [yesterday's -current], except this time it was in uniprocessor configuration, and now I don't get the random panics which were most obvious when attempting to buildworld over the past month or so [I have tried new kernels about every week for over a month, all have had the same issues]. I have read that others seem to be having problems in SMP, and I guess I am not alone. I saved the SMP kernel, so I can still boot into it, but these seem to be random, and I could sit for a minute or for an hour before I get to a point where I can even see the panic, but if any tracebacks are needed, I do have the debugger in, assuming this problem isn't already known. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB and SMP
PIIX4, and I do think it's running under uhci. Daniel O'Connor wrote: > On 10-Nov-2001 Jim Bryant wrote: > >> I have a [secondary] USB Keyboard with a mouse port on it's side installed, >> as well as a cameramate CompactFlash reader hooked up. >> Both work. >> > > What chipset though? > The OHCI stuff seems less reliable than UHCI. > Not sure if its the hardware, the driver or some combination :) > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > > jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel won't build - atomic.c/atomic.h errors...
I'll give it a try next time I build a kernel. Thanks for the info on the
optimization option info, adding -O was successful in
compiling atomic.c.
John Baldwin wrote:
> On 08-Nov-01 Bruce Evans wrote:
>
>>On Fri, 2 Nov 2001, Jim Bryant wrote:
>>
>>
>>>Is anyone else seeing this problem? I posted a message the other day to
>>>this list, and have yet to see a single response.
>>>
>>>This is from a completely fresh cvsup of everything.
>>>
>>>buildworld succeeds, but the kernel build fails on atomic.c with the
>>>following message about the ATOMIC_ASM macros in atomic.h.
>>>
>>>The archetecture is 5.0-really-current on an SMP P2-333 machine.
>>>
>>>the message seems to be: "inconsistent operand constraints in an `asm'"
>>>
>>Only people who have clobbered -O in CFLAGS in /etc/make.conf should see
>>this problem :-).
>>
>>The i386 still uses archaic constraints for some
>>input-output operands ("0" for the first operand). These never worked
>>right and if fact don't actually work for compiling this file without
>>optimization.
>>
>
> Hmm, would you prefer this diff then, I've had it floating around for a while
> now but wasn't sure it was right:
>
> --- //depot/vendor/freebsd/sys/i386/include/atomic.h2001/10/08 14:41:47
> +++ //depot/projects/smpng/sys/i386/include/atomic.h2001/10/08 22:37:17
> @@ -99,8 +99,8 @@
> atomic_##NAME##_##TYPE(volatile u_##TYPE *p, u_##TYPE v)\
> { \
> __asm __volatile(MPLOCKED OP\
> -: "=m" (*p)\
> -: "0" (*p), "ir" (V));\
> +: "+m" (*p)\
> +: "ir" (V)); \
> }
>
> /*
> @@ -211,25 +211,25 @@
> #endif /* KLD_MODULE */
>
> #if !defined(LOCORE)
> -ATOMIC_ASM(set, char, "orb %b2,%0", v)
> -ATOMIC_ASM(clear,char, "andb %b2,%0", ~v)
> -ATOMIC_ASM(add, char, "addb %b2,%0", v)
> -ATOMIC_ASM(subtract, char, "subb %b2,%0", v)
> +ATOMIC_ASM(set, char, "orb %b1,%0", v)
> +ATOMIC_ASM(clear,char, "andb %b1,%0", ~v)
> +ATOMIC_ASM(add, char, "addb %b1,%0", v)
> +ATOMIC_ASM(subtract, char, "subb %b1,%0", v)
>
> -ATOMIC_ASM(set, short, "orw %w2,%0", v)
> -ATOMIC_ASM(clear,short, "andw %w2,%0", ~v)
> -ATOMIC_ASM(add, short, "addw %w2,%0", v)
> -ATOMIC_ASM(subtract, short, "subw %w2,%0", v)
> +ATOMIC_ASM(set, short, "orw %w1,%0", v)
> +ATOMIC_ASM(clear,short, "andw %w1,%0", ~v)
> +ATOMIC_ASM(add, short, "addw %w1,%0", v)
> +ATOMIC_ASM(subtract, short, "subw %w1,%0", v)
>
> -ATOMIC_ASM(set, int, "orl %2,%0", v)
> -ATOMIC_ASM(clear,int, "andl %2,%0", ~v)
> -ATOMIC_ASM(add, int, "addl %2,%0", v)
> -ATOMIC_ASM(subtract, int, "subl %2,%0", v)
> +ATOMIC_ASM(set, int, "orl %1,%0", v)
> +ATOMIC_ASM(clear,int, "andl %1,%0", ~v)
> +ATOMIC_ASM(add, int, "addl %1,%0", v)
> +ATOMIC_ASM(subtract, int, "subl %1,%0", v)
>
> -ATOMIC_ASM(set, long, "orl %2,%0", v)
> -ATOMIC_ASM(clear,long, "andl %2,%0", ~v)
> -ATOMIC_ASM(add, long, "addl %2,%0", v)
> -ATOMIC_ASM(subtract, long, "subl %2,%0", v)
> +ATOMIC_ASM(set, long, "orl %1,%0", v)
> +ATOMIC_ASM(clear,long, "andl %1,%0", ~v)
> +ATOMIC_ASM(add, long, "addl %1,%0", v)
> +ATOMIC_ASM(subtract, long, "subl %1,%0", v)
>
> ATOMIC_STORE_LOAD(char,"cmpxchgb %b0,%1", "xchgb %b1,%0")
> ATOMIC_STORE_LOAD(short,"cmpxchgw %w0,%1", "xchgw %w1,%0")
>
>
jim
--
ET has one helluva sense of humor!
He's always anal-probing right-wing schizos!
-
POWER TO THE PEOPLE!
-
"Religious fundamentalism is the biggest threat to
international security that exists today."
United Nations Secretary General B.B.Ghali, 1995
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: USB and SMP
I have a [secondary] USB Keyboard with a mouse port on it's side installed, as well as a cameramate CompactFlash reader hooked up. Both work. Michael Class wrote: > Hello, > > just a question. Has anyone usb-devices working on a current-smp > (very recent current, but problem exists since I can remember) > system? On my Abit VP6 (Via-Chipset) a USB-Mouse and USB-Printer > do work fine if I boot a single-CPU kernel. With a SMP-Kernel > I am getting messages like: > > Nov 10 15:53:38 pc-micha /boot/kernel/kernel: uhub0: device problem, disabling p > ort 2 > Nov 10 15:53:56 pc-micha /boot/kernel/kernel: uhub1: device problem, disabling p > ort 2 > > and obviously the USB-Devices do not work. > > With a single CPU-Kernel usbdevs delivers > > pc-micha:/home/michaelc# usbdevs -v > Controller /dev/usb0: > addr 1: self powered, config 1, UHCI root hub(0x), VIA(0x), rev 0x0100 > port 1 powered > port 2 addr 2: self powered, config 1, DeskJet 990C(0x3304), >Hewlett-Packard(0x03f0), rev 0x0100 > Controller /dev/usb1: > addr 1: self powered, config 1, UHCI root hub(0x), VIA(0x), rev 0x0100 > port 1 addr 2: low speed, power 100 mA, config 1, Genius USB Wheel Mouse(0x0003), >KYE(0x0458), rev 0x > port 2 powered > > > This is the dmesg-frgment from a single CPU-Kernel for usb: > > uhci0: port 0xc400-0xc41f irq 10 at device 7.2 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhci1: port 0xc800-0xc81f irq 10 at device 7.3 on pci0 > usb1: on uhci1 > usb1: USB revision 1.0 > ums0: KYE Genius USB Wheel Mouse, rev 1.00/0.00, addr 2, iclass 3/1 > > Any Ideas? > > Michael > > > - > michael class, viktor-renner str. 39, 72074 tuebingen, frg > E-Mail: [EMAIL PROTECTED] > Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) > - > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel won't build - atomic.c/atomic.h errors...
Is anyone else seeing this problem? I posted a message the other day to this list, and have yet to see a single response. This is from a completely fresh cvsup of everything. buildworld succeeds, but the kernel build fails on atomic.c with the following message about the ATOMIC_ASM macros in atomic.h. The archetecture is 5.0-really-current on an SMP P2-333 machine. the message seems to be: "inconsistent operand constraints in an `asm'" I checked the CVS sebsite, and noticed a change three weeks ago in atomic.h, but atomic.c hasn't been changed in better than a year. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel build fails in atomic.c
I got the following eariler, and thinking I was out of sync, I cvsupped everything from scratch, and still got it. --- cc -c -g -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -f format-extensions -ansi -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I../../../ ../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 -fomit-frame-pointer ../../../i386/i386/atomic.c In file included from ../../../i386/i386/atomic.c:48: machine/atomic.h: In function `atomic_set_char': machine/atomic.h:214: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_char': machine/atomic.h:215: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_char': machine/atomic.h:216: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_char': machine/atomic.h:217: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_short': machine/atomic.h:219: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_short': machine/atomic.h:220: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_short': machine/atomic.h:221: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_short': machine/atomic.h:222: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_int': machine/atomic.h:224: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_int': machine/atomic.h:225: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_int': machine/atomic.h:226: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_int': machine/atomic.h:227: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_long': machine/atomic.h:229: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_long': machine/atomic.h:230: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_long': machine/atomic.h:231: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_long': machine/atomic.h:232: inconsistent operand constraints in an `asm' *** Error code 1 Stop in /usr/src/sys/i386/compile/WAHOO. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP kernel & burncd change..
Kris Kennaway wrote: > On Wed, Oct 03, 2001 at 01:56:11PM -0500, Jim Bryant wrote: > >>This may sounds strange, but as I don't actually recall seeing any actual changes to >burncd unless i missed something in my cvsup >>early this morning CDT... >> >>I just decided to give it another try before booting into the kernel built this >morning, and it seems that it was a "world" issue, >>and not a kernel issue, as I'm running the same kernel I reported below, but a world >from early THIS morning, and burncd DOES work now. >> > > There were changes recently..if your kernel is out of sync with your > world, you'll often get problems. > > Kris > actually, it was in sync, and it didn't work until i had made and installed a world and kernel from almost 24 hours ago, yet without rebooting. so i was using a kernel from around 48 hours ago and a world of about 24 hours ago before it would work. whatever it was was in the world stuff. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP kernel & burncd change..
This may sounds strange, but as I don't actually recall seeing any actual changes to burncd unless i missed something in my cvsup early this morning CDT... I just decided to give it another try before booting into the kernel built this morning, and it seems that it was a "world" issue, and not a kernel issue, as I'm running the same kernel I reported below, but a world from early THIS morning, and burncd DOES work now. Apparently, it wasn't a kernel issue, unless just leaving the machine up for a day released a lock that should never have been granted... 1:46:59pm wahoo(110): burncd -s 12 -f /dev/acd0c data StarOffice-x86.iso fixate next writeable LBA 0 addr = 0 size = 587956224 blocks = 287088 writing from file StarOffice-x86.iso size 574176 KB written this track 574176 KB (100%) total 574176 KB fixating CD, please wait.. Jim Bryant wrote: > Heheh... Just to clarify for some... my standard practice involves > following buildworld with installworld... > > Jim Bryant wrote: > >> Søren Schmidt wrote: >> >>> Kernel and burncd must be in sync again, a make kernel followed >>> by a make world should do it. >>> >>> -Søren >> >> >> >> >> acd0: CD-RW at ata1-master PIO4 >> >> This is from -current as of about 1am or so CDT today. I did a make >> buildworld instead of a make world, but I would assume that wouldn't >> be the cause of this. >> >> 2:51:10pm wahoo(112): burncd -s 12 -f /dev/acd0c data >> StarOffice52.iso fixate >> burncd: ioctl(CDIOCSTART): Device busy >> >> jim > > > -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP kernel & burncd change..
Heheh... Just to clarify for some... my standard practice involves following buildworld with installworld... Jim Bryant wrote: > Søren Schmidt wrote: > >> Kernel and burncd must be in sync again, a make kernel followed >> by a make world should do it. >> >> -Søren > > > > acd0: CD-RW at ata1-master PIO4 > > This is from -current as of about 1am or so CDT today. I did a make > buildworld instead of a make world, but I would assume that wouldn't be > the cause of this. > > 2:51:10pm wahoo(112): burncd -s 12 -f /dev/acd0c data StarOffice52.iso > fixate > burncd: ioctl(CDIOCSTART): Device busy > > jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP kernel & burncd change..
Søren Schmidt wrote: > Kernel and burncd must be in sync again, a make kernel followed > by a make world should do it. > > -Søren acd0: CD-RW at ata1-master PIO4 This is from -current as of about 1am or so CDT today. I did a make buildworld instead of a make world, but I would assume that wouldn't be the cause of this. 2:51:10pm wahoo(112): burncd -s 12 -f /dev/acd0c data StarOffice52.iso fixate burncd: ioctl(CDIOCSTART): Device busy jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
burncd issue
This is from -current as of about 1am or so CDT today. 2:51:10pm wahoo(112): burncd -s 12 -f /dev/acd0c data StarOffice52.iso fixate burncd: ioctl(CDIOCSTART): Device busy I was under the impression that if the kernel and world were in sync that this would work based on a message I read yesterday. acd0: CD-RW at ata1-master PIO4 jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB Multimedia Card (MMC) readers supported?
I believe at least one version of the SanDisk one is supported, and I recently helped test and get committed the Microtech CameraMate I personally recommend the CameraMate, as it has support for all known CompactFlash devices, including IBM Microdrives, as well as the fact that it also reads SmartMedia cards. Konstantin Chuguev wrote: > Hello, > > Are USB MMC Card Readers (such as SanDisk ImageMate) supported in > CURRENT? > I suppose they can be treated as generic SCSI-over-USB drives, just > want to be sure... > > Thanks, jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Post-KSE KDE Issues...
I am getting intermittant communications initialization errors involving DCOPSERVER upon starting KDE. The thing is that it seems to be random. So far it will happen 2 out of every 3 times you attempt to login via KDM... So far, the only cure is to keep logging in until it doesn't produce the message, with a maximum so far of 3 times before a successful login, minimum of getting in on the first attempt. I'm going to recompile KDE2 and see if this fixes anything, but if someone knows about this, please tell, as I really don't want to spend the next 24 hours recompiling... FreeBSD wahoo.kc.rr.com 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Fri Sep 14 08:13:08 CDT 2001 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/WAHOO i386 jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't write CD-Rs with or without new DAO mode
Jim Bryant wrote:
> Brian Fundakowski Feldman wrote:
>
>> After updating my system I can't burn CD-Rs successfully. Can anyone
>> else? What happens is pretty simple:
>>
>> {"/home/green/toxicity"}$ burncd -s 8 -d audio /dev/null $(ls |
>> trackclassify >
>> burncd: ioctl(CDRIOCINITWRITER): Input/output error
>> acd0: MODE_SELECT_BIG - ILLEGAL REQUEST asc=0x26 ascq=0x00 error=0x00
>>
>> The specific hardware is:
>>
>> atapci0: port 0xa000-0xa00f at device
>> 7.1 on pci0
>> acd0: CD-RW at ata0-master WDMA2
>>
>> I'd provide more info if I had it. Using atacontrol to stick the
>> CD-ROM drive in PIO mode doesn't help, nor does the "reinit" command.
>
>
>
> Although until I restore from tape, I am running -CURRENT world, but
> not-current kernel... based on -CURRENT breakage for me, I will have to
> regress world...
>
> Looks like the problem may be with the burncd program itself...
>
> 10:01:24pm wahoo(106): burncd -s 12 -f /dev/acd0c data
> pink-floyd-studio-albums-complete.iso fixate
> burncd: ioctl(CDRIOCINITWRITER): Inappropriate ioctl for device
> burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
> [ad nausium, spits 'em out fast]
using the world i'm about to regress to, and the kernel I did the above in, burncd
does work.
jim
--
ET has one helluva sense of humor!
He's always anal-probing right-wing schizos!
POWER TO THE PEOPLE!
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: can't write CD-Rs with or without new DAO mode
Brian Fundakowski Feldman wrote:
> After updating my system I can't burn CD-Rs successfully. Can anyone else?
> What happens is pretty simple:
>
> {"/home/green/toxicity"}$ burncd -s 8 -d audio /dev/null $(ls | trackclassify >
> burncd: ioctl(CDRIOCINITWRITER): Input/output error
> acd0: MODE_SELECT_BIG - ILLEGAL REQUEST asc=0x26 ascq=0x00 error=0x00
>
> The specific hardware is:
>
> atapci0: port 0xa000-0xa00f at device 7.1 on pci0
> acd0: CD-RW at ata0-master WDMA2
>
> I'd provide more info if I had it. Using atacontrol to stick the CD-ROM
> drive in PIO mode doesn't help, nor does the "reinit" command.
Although until I restore from tape, I am running -CURRENT world, but not-current
kernel... based on -CURRENT breakage for me, I
will have to regress world...
Looks like the problem may be with the burncd program itself...
10:01:24pm wahoo(106): burncd -s 12 -f /dev/acd0c data
pink-floyd-studio-albums-complete.iso fixate
burncd: ioctl(CDRIOCINITWRITER): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
burncd: ioctl(CDRIOCSETBLOCKSIZE): Inappropriate ioctl for device
[ad nausium, spits 'em out fast]
jim
--
ET has one helluva sense of humor!
He's always anal-probing right-wing schizos!
POWER TO THE PEOPLE!
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: KSE usage, and one forgotten item (PC98)
Okay, from -CURRENT fetched at approximately 1320 CDT today, buildworld/installworld were successful, building the kernel was successful, booting failed with the following [copied by hand]: trap 12: page fault in kernel mode cpuid = 1 lapic id = 0100 virt. addr = 0x0 code = supervisor read, page not present ip = 0x8:0xc0231aa6 sp = 0x10:0xd073db10 fp = 0x10:0xd073db48 cs = base = 0x0 limit = 0xf type = 1b dpl = 0x0 pres = 1 def32 = 1 gran = 1 eflags = interrupt enable, resume, IOPL = 0 proc = 156 (nfsd) trap 12 panic: page fault boot cpu#1 synching disks: panic: bdwrite: buffer not busy I am using a Tyan S1696-DLUA SMP Mobo with 512M RAM and dual Pent-II/333 CPUs Julian Elischer wrote: > I'm wondering how many people have tried running -current with the > KSE-2 changes in it. I've had only one minor bug report so far. > (which is either good or bad depending on wheterh it means > "it all works" or "No-one is using it") > > > Peter reminded me that we haven't changed the pc98 files for > netgraph. In nearly all cases the changes will be identical to those > in the i386 files but we have no way of testing them.. > > If a pc98 person can contect me I can help convert anything that is > required to make it work again. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: anonymous-ftp cracked
This doesn't indicate that you were cracked if it was anonymous FTP. You may have been scanned for open ports, and it appears that they took advantage of your FTP being open. Set up logging via the inetd.conf line (man ftpd for options). Then you can at least use ipf or ipfw to ban the domains that were involved. P. U. (Uli) Kruppa wrote: > Hi, > > sorry for cross-mailing two lists! > > I am running -CURRENT (ok - though I do not know anything > about computers) and just found about about 624 MB trash in > my /var/ftp - this is my anonymous-ftp -directory. > It was disposed in a sub-directory > ../incoming/tagged/byDj-krok . > > What can I do (besides deleting this stuff)? > > > Uli. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re:
Jonathan Love wrote: > > jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Raid Controller reconditioning
Faulty battery monitor? If it's a NiCad, consistant recharging when the cell isn't discharged to the recommended "discharged" voltage can cause what is known as "memory effect", where the battery will never charge above that partially-discharged state at which it been consistantly recharged from. Also, if a NiCad is allowed to discharge below a certain voltage, polarity reversal can happen. Most modern gear will use NiMH or Li-ion cells nowadays, because such cells do not have these problems. Some manufacturers using cheezy parts and other cut corners in quality do still use NiCad cells though [if they were shoddy there, where else were they shoddy?] Main question: is it under warranty? Tomas Palfi wrote: > i'm running stable4.3 on Dell poweredge 2500 with PERC 3/Di controller which > is causing a problem. the support battery on the controller is being > discharged on irregular basis and when fully discharged it freezes the > system. After rebooting the system the console displays: > > aac0: ** Battery charge is now OK > > this message is displayed on the console after approx. 2-3 mins of running. > there is no way the battery would be fully recharged after such a short > time. Being it a new system the battery has not been fully charged and > dischardged to gain full working capacity. > > come on guys, what's going on here?!, is anyone running 4.3 on Poweredge > 2500, has anyone got similar problems? i've checked it with 'stable guys' > and no messages no suggestion, nothing. perhaps it's me, overlooking > something, but the server goes down at least once a week > > thank you > -- > Tomas Palfi jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RAM cram!!! is this a -current issue? XF86/Netscape-6.10
I was just checking something out in top, and noticed a big discrepancy in the core usage for mozilla, and XF86 looks a bit heavier than normal... The "mozilla" in use is the linux netscape 6.10 dist direct from netscape [i avoided installing the -port, because it was using some kinda hacked version with missing menus and such]... Could this be a netscape memory leak issue, or a -current issue?? I have *NEVER* seen netscape using this much core. --- 5:57AM up 6 days, 9:33, 6 users, load averages: 0.99, 0.71, 0.49 FreeBSD wahoo.kc.rr.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Fri Aug 31 16:12:39 CDT 2001 --- last pid: 15303; load averages: 0.56, 0.61, 0.43 up 6+09:30:26 05:54:39 141 processes: 3 running, 117 sleeping, 21 waiting CPU states: 3.8% user, 0.0% nice, 3.5% system, 0.4% interrupt, 92.3% idle Mem: 404M Active, 39M Inact, 32M Wired, 13M Cache, 7488K Buf, 11M Free Swap: 1024M Total, 187M Used, 837M Free, 18% Inuse PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 11 root -160 0K 0K CPU0 0 117.0H 73.00% 73.00% idle: cpu0 10 root -160 0K 0K RUN1 115.7H 70.07% 70.07% idle: cpu1 558 jbryant 1000 332M 205M select 0 856:43 31.35% 31.35% mozilla-bin 285 root 990 124M 97664K select 0 48.7H 5.81% 5.81% XFree86 2 root -160 0K 0K psleep 0 0:24 0.88% 0.88% pagedaemon 525 jbryant960 25800K 6792K select 0 42:58 0.68% 0.68% kdeinit 596 jbryant960 86948K 26716K select 1 80:29 0.44% 0.44% communicator-linux- 487 jbryant960 16972K 3332K select 1 127:37 0.39% 0.39% kdeinit 527 jbryant960 17156K 2464K select 1 61:35 0.20% 0.20% kdeinit 13 root -48 -167 0K 0K WAIT 0 50:45 0.15% 0.15% swi6: tty:sio clock 505 jbryant960 17904K 3764K select 1 21:19 0.05% 0.05% kdeinit 28 root -60 -179 0K 0K WAIT 0 3:02 0.05% 0.05% irq12: psm0 15271 jbryant960 17228K 11384K select 1 0:11 0.05% 0.05% ksnapshot 15289 root -80 1636K 1184K physst 1 0:01 0.05% 0.05% dump 15290 root 200 1636K 1184K pause 0 0:01 0.05% 0.05% dump 15291 root 200 1636K 1184K pause 0 0:01 0.05% 0.05% dump 15253 jbryant960 2380K 1276K CPU1 1 0:05 0.00% 0.00% top jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
Jordan Hubbard wrote: > Are you guys on crack? Scheme is just a dialect of LISP, where "LISP" > could also just as easily be any one of MacLisp, InterLisp, Franz > Lisp, Common Lisp or one of many other possibilities. The very > acronym lacks specific meaning without an additional qualifier. > Scheme can also dynamically build and evaluate data as code just as > well as any other LISP dialect. Somebody needs to go back and take a > CS class or something. :-) > > - Jordan oops... mea culpa! not nuff caffine, i got my languages mixed there... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
FreeBSD Fanatic wrote: >>>Show us a suitable LISP interpreter, then. >>> >>$ cd ~/lang/Scheme/tinyscm-1.27 >>$ size scheme >> textdata bss dec hex filename >> 6134244763480 69298 10eb2 scheme >> > > Is that statically-linked? I'm curious to know the size of the bootloader > forth footprint. The loader is about 150k, so I'm sure you could probably > fit a nice Scheme interpreter in under that size... ?? > > >>Tinyscheme is a mostly complete R5RS Scheme (R5RS is the >> > > You can also conditionally-compile the components to make a smaller > footprint. I'm highly in favor of Scheme replacing 4th... It's a very > easy language to learn (only 11 special forms) yet still powerful (you > can't pass code as data in BASIC ;). If you replace the boot loader > interpreter, pick Scheme over LISP. There are lots of implementations: > siod, scm, mit-scheme, MzScheme, and tinyscheme are among the better ones. > > --Rick C. Petty, aka Snoopy [EMAIL PROTECTED] I still think that Scheme has far less proficient programmers than LISP. BTW: In LISP, *EVERYTHING* is data. LISP was executing data as code and writing self-replicating programs around 1951 or 1952. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
Bakul Shah wrote: >>>I doubt if the bootloader will ever change from FORTH, but if it >>>does, I suggest LISP as the preferred choice on a short-list of >>>potential replacements. >>> >>Show us a suitable LISP interpreter, then. >> > > I don't know what size constraints the bootloader has to have > but the smallest two lisp interpreters I have found are: > > $ cd /usr/ports/lang/slisp/work/slisp-1.2/src > $ size slisp >textdata bss dec hex filename > 17872 6163584 220725638 slisp > > $ wc *.h *.c > 67 3212266 extern.h > 69 3352053 slisp.h > 9272438 15990 funcs.c > 189 7304707 lexer.c > 147 4583232 main.c > 287 8326358 object.c > 136 4703370 parser.c > 18225584 37976 total > > slisp has most of the common lisp constructs. That would be a perfect candidate. Low source file count, compact in core [depending on dynamic requirements]. Easily modifiable for the task, and looks to have a usable base subset of the language. > $ cd ~/lang/Scheme/tinyscm-1.27 > $ size scheme >textdata bss dec hex filename > 6134244763480 69298 10eb2 scheme > $ wc *.h *.c > 12 33 247 dynload.h > 34411369221 scheme.h > 126 2922589 dynload.c > 4445 12353 125421 scheme.c > 4927 13814 137478 total > > Tinyscheme is a mostly complete R5RS Scheme (R5RS is the > closest thing to a Scheme standard) -- everything except > complex and rational number types, bignums, hygenic macros > and call-with-values and unwind-protect. You can probably > subset it quite a bit to make it far smaller (e.g. the real > number type and advanced math functions to avoid linking in > libm). If it matters to you, it has a BSD style licence. > > http://tinyscheme.sourceforge.net/home.html > http://tinyscheme.sourceforge.net/tinyscheme-1.27.tar.gz The problems of Scheme are much like the problems of FORTH. It's a niche language that has few proficient programmers. LISP may not be "mainstream", but it's far more so than Scheme [or FORTH for that matter], and is commonly taught in CompSci classes, meaning that most serious programmers have at least been familiarized with the language, in fact, your local drating tech may be quite proficient in it [AutoCAD uses LISP]... I personally don't care if FORTH stays, but if it's up for debate, LISP is a great choice. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
Kris Kennaway wrote: > On Wed, Sep 05, 2001 at 08:42:39PM -0500, Jim Bryant wrote: > > >>I doubt if the bootloader will ever change from FORTH, but if it >>does, I suggest LISP as the preferred choice on a short-list of >>potential replacements. >> > > Show us a suitable LISP interpreter, then. > > Kris Been a while since I looked around, and I do think that any suitable interpreter would have to be modified to suit the task of bootloading much better than a generic LISP can, even emacs had to modify LISP for their purposes, but sure, I'll do some looking around for candidates. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unpleasant ps output and possible related problems.
Dave Cornejo wrote: > I apologize for not having any idea where to start on this. I am not > whining for someone to fix something, merely reporting an odd behavior > that I have now seen on multiple machines in cae it means something to > anybody. > > I am tracking current almost daily on three machines. Starting > yesterday I managed to get one box that refused to go into multiuser > mode it would run the rc script and then hang somewhere executing the > scripts in /usr/local/etc/rc.d. If I Ctrl-C'ed it - it would come up > in the single-user mode shell. no login prompt, just the shell. I > could however telnet into the thing most things seemed to work. > > In this state it had hung without starting INN - so I su'ed and tried > to start it. INN starts, but I end up at a prompt with a uid of news! > If I exit that, INN dies. > > I do a ps -ax and I get some corrupt lines: > > 471 p0 Is 0:00.07 -csh (csh) > 473 p0 I 0:00.01 su -m > 474 p0 S 0:00.04 \M-[\M-!\^D\b\M-X\M-!\^D\b (csh) > 12673 p0 R+ 0:00.00 ps ax > 466 v0 Is+0:00.01 /usr/libexec/getty Pc ttyv0 > > In troubleshooting this I went back to an older kernel and the problem > persists. Change back to an old world and it's gone. Tried the > new kernel with old world and it also seems to work fine. So the > problem seems to be somewhere in the libs or userland. > > Now I went and looked at some other systems rebuilt yesterday evening > and today and while they still work I see the same sort of corruption > as above in the ps output - but no other apparent side effects. > > The corrupted line shows up in many different places and users, and > the exact contents vary, but there's always a "(csh)" at the end. When you rebuild and install a new kernel, are you also doing a `make buildworld` and a `make installworld` in /usr/src before you reboot? Sometimes changes to userland are trivial, and you may not need to rebuild userland, but utmp corruption is indicative of changes that require userland be rebuilt and installed. Ideally, you should buildworld/installworld *EVERY* time you build a -current kernel. Of course, if you have already done this, feel free to issue me a boot to the head. You note that you are running innd, please don't tell me that you are using -current in a production environment... -current is always subject to massive *FUNDAMENTAL* changes with only a moment's notice, and breakage without any notice at all... Using -current in a production environment, unless seriously justified [such as -current being more stable than -stable], is a fine way to put yourself in a position to commit hari-kari, and nobody wants that. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: none
John Polstra wrote: > In article <[EMAIL PROTECTED]>, > KSrinivasa Raghavan <[EMAIL PROTECTED]> wrote: > >>For some reasons I was unable to checkout sources from cvs server of >>FreeBSD sources. I have been using anoncvs.FreeBSD.org to fetch the >>files. >> > > I believe the administrators have been upgrading that system. I > don't know when it will be back up. > > >>I am getting "Operation timed out" errors. Are there any other cvs servers >>from which I can check out the sources ? >> > > Not as far as I know. > > By the way, more people would read your mail if you would type in a > subject. :-) > > John cvsup2.freebsd.org through cvsupn.freebsd.org seem to work just fine... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
Jim Bryant wrote: > Dave Cornejo wrote: > >> you wrote: >> >>> And just for the record: PERL is right out (of space) for this >>> purpose... >>> >> >> as I assume emacs would be too? :-( > > > > Hey now! Them's fightin' words! :^) > > Emacs makes the sun shine, > Emacs makes the birds sing, > Emacs makes the grass grow green! > > chsh -s /usr/local/bin/emacs root > > So what if FreeBSD can run on a 4 meg machine once it's booted, if it > can't use eight megs while booting, and do your laundry for you at the > same time! > > Emacs r0x! OF course, emacs would be a little large and bloated, no matter how much I like it, or you like it, but, you do bring up a viable alternative to FORTH [which is unlikely to be scrapped in the bootloader], and so far, it may be the only viable alternative discussed so far, and that is LISP. LISP can be implemented in a tiny form, it is the OLDEST high-level language in computing, it has a LARGE base of programmers, and it is easy to learn. Full Common-LISP wouldn't be necessary for a bootloader, only a reasonable subset. EMACS may be large, some will say bloated, but it is a tribute to the sheer flexibility of the LISP language. I doubt if the bootloader will ever change from FORTH, but if it does, I suggest LISP as the preferred choice on a short-list of potential replacements. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
Dave Cornejo wrote: > you wrote: > >>And just for the record: PERL is right out (of space) for this purpose... >> > > as I assume emacs would be too? :-( Hey now! Them's fightin' words! :^) Emacs makes the sun shine, Emacs makes the birds sing, Emacs makes the grass grow green! chsh -s /usr/local/bin/emacs root So what if FreeBSD can run on a 4 meg machine once it's booted, if it can't use eight megs while booting, and do your laundry for you at the same time! Emacs r0x! jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
Julian Elischer wrote: > > On Wed, 5 Sep 2001, Daniel C. Sobral wrote: > > >>David O'Brien wrote: >> >>>On Tue, Sep 04, 2001 at 09:48:24AM -0300, Daniel Capo Sobral wrote: >>> >>> When I first wrote the loader.conf thingy, I couldn't get the value of environment variables from the FICL environment. >>>... >>> >>> Anyway, I have been too busy lately to do anything with FreeBSD that is not directly related to things I have to do at work, and it doesn't look like slacking up so soon. So, unfortunately, I don't have time to do any of the little things that have been cropping up with loader. >>>A very good reason the loader should have used something other then a >>>language only 1% of the FreeBSD committers (and entire community) has >>>knowledge of. >>> >>/me shrugs >> >>I myself questioned the wisdom of using Forth at the time, and Jordan >>simply replied I was free to find a more popular language with a freely >>available interpreter that would fit in as small a space as FICL did. >> > > > there is a Basic interpeter that fits in 1024 bytes that could be used > if extended to know about files :-) > BASIC is evil incarnate! :^) jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
David O'Brien wrote: > On Wed, Sep 05, 2001 at 12:04:49PM -0700, Terry Lambert wrote: > >>Samuel Tardieu wrote: >> >>>Or why is BSD make used when the vast majority of Free Software developpers >>>use GNU make? >>> >>1)It actually works >> > > You forgot the syntax is nearly the same as GNU Make. > (or rather both accept nearly the same syntax as the original Bell Labs > make(1)). > > In the case of forth, the interpreter will accept nothing that looks even > vaguely simular to C/C++, FORTRAN, bourne shell, awk, or perl. FORTH is a pain in the ass, it's a bastardized and seldom-used language, but it does have one strong advantage in a boot-loader situation: it's tiny, and relatively easy to implement. It's been a very long time since FORTRAN fit in 4k, I don't think C ever did, bourne relies too much on external programs [/bin/test, etc], awk is too limited, and using perl would be akin to using winblowz as a bootloader [bLOAt] I haven't used FORTH since my VIC-20 days, but if you can use an HP calculator, you can probably pick up the basics of FORTH over a weekend. If you can do PostScript, then you can probably pick it up in an evening. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trying to play sound in -current
David W. Chapman Jr. wrote: >>I haven't looked at the code, but does a value of 0 for vchans mean >>infinite, I know this is a standard use for the value of zero in some >>instances... >> >> > What what I gather, 0 means none, only use how many channels the > sound card has. I'm assuming that John has multiple hardware > channels. Okay, that makes sense. I was wondering, because mine also shows a value of zero and works with multiple opens, but then I'm using a SB-Live!, and it has a lot of hardware channels, so if I switched to the Yamaha POS on the motherboard, I would have locks. This makes sense. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trying to play sound in -current
John Baldwin wrote: > On 04-Sep-01 David W. Chapman Jr. wrote: > >>On Tue, Sep 04, 2001 at 09:40:44AM -0700, John Baldwin wrote: >> >>>In fact, am doing so right now inside of KDE (with arts or whatever their >>>sound >>>daemon is called also running). Granted, it sounds rather weird. :-P >>> >>> 915 john -80 5236K 900K pcmwr0:01 1.66% 1.51% mpg123 >>> 914 john -80 4336K 912K pcmwr0:01 1.64% 1.51% mpg123 >>> >>> sysctl hw.snd >>>hw.snd.verbose: 0 >>>hw.snd.unit: 0 >>>hw.snd.autovchans: 0 >>>hw.snd.maxvchans: 0 >>>hw.snd.pcm0.vchans: 0 >>>hw.snd.pcm0.hwvol_step: 5 >>>hw.snd.pcm0.hwvol_mixer: vol >>> >>> >>If everything is using artsd then that may be the reason. My problem >>was I had apps using esound, artsd and them vmware directly talking >>to dsp. But this is only from what I gather, not from knowledge. >> > > Note the mpg123 processes. They are in pcmwr, i.e. writing to /dev/dsp > directly and not going through artsd. I haven't looked at the code, but does a value of 0 for vchans mean infinite, I know this is a standard use for the value of zero in some instances... The other guy's was set to 1, raising it fixed his problem. Yours works with multiple opens with a value of zero. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trying to play sound in -current
I recall reading the explanation somewhere on the KDE site on why artsd will hold a lock on the sound device, but as I recall the lock is like for 30 or 60 seconds... Reading the explanation I seem to recall thinking it was a lame hack solution to the problem of dealing with multiple opens on older sound hardware that can't handle multiple opens. I forget where this was but it was related to artsd. Julian Elischer wrote: > "David W. Chapman Jr." wrote: > >>I get this a lot recently when I try to play anything >> >> >>>echo test > /dev/dsp0 >>> >>/dev/dsp0: Device busy. >> >>even when it shouldn't be busy, after atbout 10 mins it usually >>becomes not busy >> > > sure your window manager isn't using it? > (e.g. 'enlighten' does, as does kde in some configurations) > > >>pcm0: port 0xd000-0xd03f irq 5 at device 14.0 on pci0 >>-- >>David W. Chapman Jr. >>[EMAIL PROTECTED] Raintree Network Services, Inc. >>[EMAIL PROTECTED] FreeBSD Committer >> >>To Unsubscribe: send mail to [EMAIL PROTECTED] >>with "unsubscribe freebsd-current" in the body of the message >> > -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
I sent it in a private message to you to keep from spamming the list with a 60k file... I was wondering why the address was so high, and it was still catching matches of anything... Mike Smith wrote: >>I have a question, does /dev/mem wrap lgoically back to address once >> it's reached the end of physical memory? >> > > Er, no, I wouldn't have thought so. > > >>110779f460 7c 7c 52 53 44 20 50 54 52 20 2e 54 62 56 7c 2e |||RSD PTR .TbV >>|.| >> >>Should this be far enough along for you to get what you need? If so, I'll ju >>st kill it, gzip the outfile, and send it to you. >> > > Definiely, thanks. > > jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
I have a question, does /dev/mem wrap lgoically back to address once it's reached the end of physical memory? I left the hexdump -C running all night and just checked and it's still running, and the output file shoes that it's somewhere past address: 110779f460 7c 7c 52 53 44 20 50 54 52 20 2e 54 62 56 7c 2e |||RSD PTR .TbV|.| Should this be far enough along for you to get what you need? If so, I'll just kill it, gzip the outfile, and send it to you. Mike Smith wrote: >>My motherboard is a Tyan S1696-DLUA dual P2-333. I am using the latest known >> bios updates. ACPI is enabled, and APM disabled in >>the BIOS. This happens regardless if PnP is on or off in the BIOS. >> >>[dmesg | grep -i acpi] >> >>ACPI debug layer 0x0 debug level 0x0 >> tbxface-0170: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TAB >>LES >> tbxface-0222: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_ >>TABLES >>ACPI: table load failed: AE_NO_ACPI_TABLES >> > > Your ACPI tables, assuming they exist, are somewhere we're not looking for > them yet. 8( > > Can you try: > > # hexdump /dev/mem | grep "RSD PTR" > > and if it finds anything (the string should be left-aligned on the line) > send me the line it outputs... (this will take a while). > > Thanks. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
I would have waited for the re-run of hexdump to finish, but checking right after I sent the last message produced: DING! wahoo(102): hexdump -C /dev/mem | grep "RSD PTR" 000716d0 67 72 65 70 20 22 52 53 44 20 50 54 52 22 27 00 |grep "RSD PTR"'.| 000719d0 67 72 65 70 20 22 52 53 44 20 50 54 52 22 27 00 |grep "RSD PTR"'.| 00369400 52 53 44 20 50 54 52 20 00 54 62 56 61 6c 69 64 |RSD PTR .TbValid| 0036ad00 44 53 44 54 00 52 53 44 20 50 54 52 20 00 52 53 |DSDT.RSD PTR .RS| You did say that what you are looking for would be left-aligned, could it be the bit at 00369400? Mike Smith wrote: >>My motherboard is a Tyan S1696-DLUA dual P2-333. I am using the latest known >> bios updates. ACPI is enabled, and APM disabled in >>the BIOS. This happens regardless if PnP is on or off in the BIOS. >> >>[dmesg | grep -i acpi] >> >>ACPI debug layer 0x0 debug level 0x0 >> tbxface-0170: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TAB >>LES >> tbxface-0222: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_ >>TABLES >>ACPI: table load failed: AE_NO_ACPI_TABLES >> > > Your ACPI tables, assuming they exist, are somewhere we're not looking for > them yet. 8( > > Can you try: > > # hexdump /dev/mem | grep "RSD PTR" > > and if it finds anything (the string should be left-aligned on the line) > send me the line it outputs... (this will take a while). > > Thanks. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
Duh!!! No wonder it was taking so long... Seems we both forgot that would have never come up with anything... doing a: hexdump -C /dev/mem | grep "RSD PTR" now... Mike Smith wrote: >>My motherboard is a Tyan S1696-DLUA dual P2-333. I am using the latest known >> bios updates. ACPI is enabled, and APM disabled in >>the BIOS. This happens regardless if PnP is on or off in the BIOS. >> >>[dmesg | grep -i acpi] >> >>ACPI debug layer 0x0 debug level 0x0 >> tbxface-0170: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TAB >>LES >> tbxface-0222: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_ >>TABLES >>ACPI: table load failed: AE_NO_ACPI_TABLES >> > > Your ACPI tables, assuming they exist, are somewhere we're not looking for > them yet. 8( > > Can you try: > > # hexdump /dev/mem | grep "RSD PTR" > > and if it finds anything (the string should be left-aligned on the line) > send me the line it outputs... (this will take a while). > > Thanks. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
In progress... You aren't joking about it taking a while... Been half an hour now... Mike Smith wrote: >>My motherboard is a Tyan S1696-DLUA dual P2-333. I am using the latest known >> bios updates. ACPI is enabled, and APM disabled in >>the BIOS. This happens regardless if PnP is on or off in the BIOS. >> >>[dmesg | grep -i acpi] >> >>ACPI debug layer 0x0 debug level 0x0 >> tbxface-0170: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TAB >>LES >> tbxface-0222: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_ >>TABLES >>ACPI: table load failed: AE_NO_ACPI_TABLES >> > > Your ACPI tables, assuming they exist, are somewhere we're not looking for > them yet. 8( > > Can you try: > > # hexdump /dev/mem | grep "RSD PTR" > > and if it finds anything (the string should be left-aligned on the line) > send me the line it outputs... (this will take a while). > > Thanks. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
I'm going to double-check my config against GENERIC, but I've been seeing this since
before the new changes.
Because of that one problem with the missing file the other day, I simply blasted and
re-synched my /usr/src/sys, so I am definitely
running the latest sources.
My motherboard is a Tyan S1696-DLUA dual P2-333. I am using the latest known bios
updates. ACPI is enabled, and APM disabled in
the BIOS. This happens regardless if PnP is on or off in the BIOS.
[dmesg | grep -i acpi]
ACPI debug layer 0x0 debug level 0x0
tbxface-0170: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES
tbxface-0222: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES
ACPI: table load failed: AE_NO_ACPI_TABLES
Andy Farkas wrote:
> On Thu, 30 Aug 2001, Bruce Evans wrote:
>
>
>>I've found acpica as useful as any other disk filling service and hope
>>it stays that way.
>>
>>Bruce
>>
>
> Can someone put this in fortunes.dat :)
>
> --
>
> :{ [EMAIL PROTECTED]
>
> Andy Farkas
> System Administrator
>Speednet Communications
> http://www.speednet.com.au/
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
>
jim
--
ET has one helluva sense of humor!
He's always anal-probing right-wing schizos!
POWER TO THE PEOPLE!
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: testing KSE
I'm in the process of getting set up for testing KSE too, but I was wondering, how are you capturing the panic dump? Do you run a serial console or something to do it? Carlo Dapor wrote: >>can you try the same with a "matching" -current? >>I heard that msdosfs is bombing there too. >>(just to confirm this.. if it works there but not with KSE >>then we have work to do :-) >> > > I build and run a kernel just before applying the patches, that was able to > mount the partition and 'accepted' reads/writes/deletes/create directories etc. > for a good three to four hours. > > As I stated earlier, the kse-patched kernel produced this: > > >>Fatal trap 12: page fault while in kernel mode >>fault virtual address = 0x4 >>fault code= supervisor read, page not present >>instruction pointer = 0x8:0xc11fa49a >>stack pointer = 0x10:0xca36aa70 >>frame pointer = 0x10:0xca36ae20 >>code segment = base 0x0, limit 0xf, type 0x1b >> = DPL 0, pres 1, def32 1, gran 1 >>processor eflags = interrupt enabled, resume, IOPL = 0 >>current process = 24854 (mount_msdosfs) >>trap number = 12 >>panic: page fault >>syncing disks... panic: bdwrite: buffer is not busy >>Uptime: 15h12m23s >>Automatic reboot in 15 seconds - press a key on the console to abort >>--> Press a key on the console to reboot <-- >> > > Right now, I am applying src-cur.4939.gz, after having reversed the KSE > patches. I am building a brand new kernel next. > > I'll post more on this in very soon. > > Ciao, derweil, > -- > Carlo > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Headsup! KSE Nay-sayers speak up!
Like I said... Count me in... Julian Elischer wrote: > Pleas guys, > cut it out... > > Take a copy, run it, beat on it.. > let me know if it fails.. > > thanks.. > > (p.s. I'll need to put a new patch up because -current has changed.. :-) jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Headsup! KSE Nay-sayers speak up!
David O'Brien wrote: > On Mon, Aug 27, 2001 at 03:13:19PM -0500, Jim Bryant wrote: > >>Count my vote as a go-for-it. >> > > Blah. You're vote doesn't mean jack in this. > Unless you are one actively working on the 5-CURRENT kernel (SMPng > specifically), or are funding 5-CURRENT kernel development; you really > don't have any right to say "go for it". > > "Don't write cheques your body can't cash." Quincy Jones's "The Dude". > > Committing KSE now could easily get in the way of the one person doing > SMPng work. Do you really want to jeopardize and slowdown that work? Actually, I'd like to see both projects proceed, but apparently what non-core contributers to FreeBSD think doesn't matter. Maybe all of the VOLUNTEER testers for -current should take your advice and go to NetBSD, OpenBSD, Linux, or open-Solaris... Maybe their opinions would be better received. As far as opinions are concerned, you have expressed yours, and I kinda hope it doesn't represent that of the entire core team. Opinions were asked for. Testers were asked for. I'm offering both. I don't think when Julian asked for opinions and testers that he was specifically asking core team members only. Julian, if this is not the case, please speak up, and accept my apology for butting in with my opinion, and my offer to take you up on your call for testers. All I did was write in support of getting some promised 5.0 items into 5.0, even offering to test them! Excuuse me! Shame on us peons for speaking our opinions! jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: KSE kernel comparissons
Garance A Drosihn wrote: > At 6:28 PM -0500 8/27/01, Jim Bryant wrote: > >> The patches seem relatively benign, and after some basic >> immediate testing, they should be committed to -current. >> That's all I'm trying to say. > > > Then shut up and help test it. That's what KSE needs, > some people who are willing to help out with the work. > > So far you've been blowing a lot of smoke in these KSE > threads, pretending that you support it. Most of that > support has been demanding that other people do stuff, > instead of any reasoned or intelligent input. Almost > everyone else in this thread is at least TRYING to be > professional about presenting the options, no matter > what their opinion might be. All of them "support" KSE > in the sense of wanting to see that work in FreeBSD. > They also have a number of other legitimate real-world > concerns. > > If you really supported KSE, then you would do something. > Something called 'work', which Julian is very familiar > with but which seems foreign to your vocabulary. Ahem... I believe I have said I'm going to be applying the patches. Did you miss that one? As far as the other's concerns, even I said it needs testing before inclusion. I have also offered to test it, is that not good enough for you, or do you just not read well? jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Headsup! KSE Nay-sayers speak up!
Garance A Drosihn wrote: > At 5:02 PM -0500 8/27/01, Jim Bryant wrote: > >> Garance A Drosihn wrote: >> >>> We can't just keep pushing back the release date because "some >>> very important enhancements" could be made. It will ALWAYS be >>> true that there are more "very important enhancements" on >>> the horizon, and you can't keep running after those. You have >>> to pick some point, and stick to that point, and "ship" at that >>> point. As long as current is known to be in rapid flux, most >> >> >> I'm glad you support integration of KSE then... As I recall such >> threading was in the original design specs for 5.0, as released >> when work on 5.0 began. > > > I'm disappointed that you completely misunderstood what I intended > to say in the above. My point is that sometimes you have to stick > to a "ship date" because you have to stick to that date, and not > because you stick to some list of features that you'd like to see. > The longer you let ship-dates slip, the longer you end up without > a release-quality product. I to this day still think that was the reasoning behind the Thanksgiving [An American Holiday] release of 2.0-R. What a disaster! I know for a fact that MickeySoft has had this philosophy since at least Win-95.. What a disaster! Marketing people screaming about ship-dates are the prime cause of unstable software, IMHO. Software should be shipped when design goals are met, not before. Last I heard, 4.4-R is RSN... Why should there be a mad rush to release 5.0-R practically right after 4.4-R, especially if it's not yet ready for prime-time? At the rate things are going, even WITH KSE integrated, 5.0-R should be close to the currently projected release date. I forget... Wasn't the *ORIGINAL* release date for 5.0-R slated for early-2002? What happened to that? Marketing types step in? > I think a lot of good work has gone into the current cut at KSE > support, and I certainly hope it goes in. However, there are a > number of other factors to consider. The right way to get KSE in > 5.0 is to help do the work which is necessary for that to happen, > and not to deliberately misquote people -- as you are pretty > clearly doing in the above. What I explicitly said in the above > message (and which you explicitly deleted) was that KSE should > wait for a later release if the remaining work is not done. If > you have some other opinion, that is fine, but do not reword *my* > opinion to claim that I agree completely with your opinion. It was an asinine reply to an asinine comment, not a deliberate misquotation. > Julian did a lot of good work, all he needs is a few more > developers to help test that work. None of us need a thread > arguing about release dates vs some goals set two years ago. Somehow I see the GOP using that same argument next year concerning the tax-scam... Medicare surplus wiped out, 9 billion into Social Security starting next week... oops, off topic... I agree with you to a point there. The design goals should be met. This isn't a commercial product, and thus I don't see that the argument that the release date should be set in stone is relevant, although it should be close to that which was originally specified. > I "support" the integration of KSE in the sense that I intend to > help test it (on a dual-CPU i386) sometime in the next week. I > do not support a delay of "5.0". I can not test on Alpha, as I > have no Alpha machines. Anyone who wants to prove their support > for KSE in 5.0 should step up and offer to do some of the testing, > etc. Actions will speak louder than any (misquoted) words. Again, I agree, except I still don't understand your dire need for a mad rush to have another "Thanksgiving release" a la 2.0-R. FreeBSD releases should be goal-oriented, not marketing-type oriented. 2.0-R left FreeBSD with reputation damage that took several years to clear up, I would have thought that some had learned from that "stick to the release date" experience. My first experience with -current sprang from that experience [for a while -current was more stable than -RELEASE, on freaking production systems]. It didn't take too long to get -RELEASE stable though, as I recall. Marketing types have a place: Selling RELEASED software and hardware... They should not be the end-all word on ship dates though. Hell, the Pentium 4 was a nice concept until... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: KSE kernel comparissons
Bosko Milekic wrote: > On Mon, Aug 27, 2001 at 03:09:53PM -0700, Julian Elischer wrote: > >>On Mon, 27 Aug 2001, Poul-Henning Kamp wrote: >> >> >>>In message <[EMAIL PROTECTED]>, Peter Wemm writes: >>> >>> My personal check list before committing it to -current is: - an honest shot at getting the Alpha working. Shouldn't be too hard. I'll work on this if nobody else will. - finish the userland build stuff. - carefully reread all of the key diffs for i386/i386/*, kern/*, vm/* etc. - take a look at ports impact and prepare them for the landing. >>>If you add: >>> >>> - Beat the shit out of it together with other developers for a couple of >>> weeks. >>> >>>Then I'm all for committing it when you have checked off those boxes. >>> >>I agree with this list. >> > > I think that realistically speaking, after having looked over the > diff, and after considering what was discussed here, that it would be > a good time to introduce the KSE work done thus far some time soon, > after said testing is done. The reason for this is that the KSE > changes to date are, as Julian and some others mentionned, > "infrastructural changes," and not _functional_ changes. Therefore, I > don't expect them to create additional logic issues (e.g. "I wonder if > it's KSE's semantics that are breaking this..." shouldn't come up with > these changes when debugging other code). > Thus, I agree with Peter and Julian on this issue and will be > applying the diff to both dual CPU machines I have here and testing > tonight. At the same time, I do hope that the actual _functional_ > changes come in a hopefully more orderly/slower manner so that it is > in fact possible to track down logic problems w.r.t. KSE should they > arise. > > On another (perhaps unrelated) note, I've noticed on the lists at > least one or two -CURRENT users/testers insist on having KSE > functionality but at the same time expecting to have production > material in early 5.0 "releases." I find this to be disturbing. While > I do agree that earlier "5.0 releases" should deffinately reach out to > the largest userbase possible, I am concerned that some users will > perhaps expect so much from the system that they will immediately go > ahead and pit it against more mature SMP OSes out there and then go on > to complain about everything under the Sun because "brand new > functionality (X) is not what I expected." The robustness and > performance of the work being done now will become more and more > apparent only as things progress and it should be noted that all of > these "nice things" resulting from all the work we're presently doing > will not just all magically surface when 5.0-RC1 (or whatever it's > going to be called) is "released." As I recall, *total* "functionality" of the subsystems wasn't promised for 5.0-R, but the infrastructure *was* promised. I expect you are reponding to my post in the other thread... Nobody is expecting a kick-butt implementation to just spring from the head of Zeus, but the infrastructure should be in place so that a kick-butt implementation can be made from it in the time that follows. With the infrastructure in place, we can probably expect a good implementation by 5.1-R, if it doesn't get committed at this stage, Julian will be lucky to get it in by 6.0-R, and I bet all the same arguments against will come up then as well. The patches seem relatively benign, and after some basic immediate testing, they should be committed to -current. That's all I'm trying to say. My response to the other gentleman were to address his comments that FreeBSD should not even hit the goals it had set initially for 5.0. I disagree with those arguments completely. I thought that Jordan and the core team had a good, even pessimistic estimate a couple of years ago for the future of 5.0 and even 6.0 as I recall... IMHO, I would tend to say that those estimates were pessimistic even. It definitely wasn't a "everything, including the kitchen sink" philosophy such as they had for 2.0-R [which was also influenced by legal matters], a lot of people may still remember that release, and the mad rush to fix the newly-introduced problems afterwards, I'm certain that David Greenman and some others do :^) Expecting to see the base infrastructure in place with at least some functionality of the new infrastructure is being realistic. Expecting a *PERFECT* implementation and *FULL* functionality of the new paradigms isn't. I want to see a functional SMPng for sure, but Julian is right, now is the time for the KSE infrastructure to be committed, it's at that stage. Just clarifying my "clarification" here. BTW: shouldn't this be in the other thread? jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @ya
Re: Headsup! KSE Nay-sayers speak up!
Jim Bryant wrote: > > > Garance A Drosihn wrote: > >> At 1:49 PM -0700 8/27/01, Sean Chittenden wrote: >> >>> > >If there are grave concerns about having KSE and SMPng in >>> > > 5.X, then why not push back the release date? The value far >>> > > outweighs the extra months needed to get it finished and out >>> > > the door, ...etc... >>> > >>> >>>> Good idea. >>> >>> >>> >>> Seriously, is there any reason to hold to a time line >>> at the expense of some very important and very fundamental >>> enhancements to FreeBSD? I suppose that's something for -core >>> to talk about/discuss, but I bet that if a poll was put on the >>> homepage of FreeBSD.org (hint hint) asking about this, you'd >>> get an overwhelming response to see KSE/SMPng in 5.X. With a >>> poll you might even pick up some more testers given the exposure >>> (hint hint). -sc >> >> >> >> We can't just keep pushing back the release date because "some >> very important enhancements" could be made. It will ALWAYS be >> true that there are more "very important enhancements" on >> the horizon, and you can't keep running after those. You have >> to pick some point, and stick to that point, and "ship" at that >> point. As long as current is known to be in rapid flux, most > > > > I'm glad you support integration of KSE then... As I recall such > threading was in the original design specs for 5.0, as released when > work on 5.0 began. Just to clarify things... Myself, and I am sure, many others signed on and committed to the testing of 5.0-current two years ago under the assumption that some of the stated goals of 5.0 were SMPng/fine-grained locking, and native threading. I'm not lowering my expectations. And please don't tell me that I put up with panics, filesystem corruption, and all of the other problems inherent with such testing just to come up with less than we expected to begin with. I agree that this needs to be committed, I also agree that a few small hurdles may need to be jumped before the integration [as is being discussed in the other thread]... The point is that it *SHOULD* be committed, the very moving target you speak of is the enemy to ever getting this finished. So long as it remains external, most of the work on it will merely be keeping it in sync with -current, rather than doing the real work of getting it implemented. Getting this internal, committed to -current, is the next step in it's development. Run that through your correctness checker... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Headsup! KSE Nay-sayers speak up!
Garance A Drosihn wrote: > At 1:49 PM -0700 8/27/01, Sean Chittenden wrote: > >> > >If there are grave concerns about having KSE and SMPng in >> > > 5.X, then why not push back the release date? The value far >> > > outweighs the extra months needed to get it finished and out >> > > the door, ...etc... >> > >> >>> Good idea. >> >> >> Seriously, is there any reason to hold to a time line >> at the expense of some very important and very fundamental >> enhancements to FreeBSD? I suppose that's something for -core >> to talk about/discuss, but I bet that if a poll was put on the >> homepage of FreeBSD.org (hint hint) asking about this, you'd >> get an overwhelming response to see KSE/SMPng in 5.X. With a >> poll you might even pick up some more testers given the exposure >> (hint hint). -sc > > > We can't just keep pushing back the release date because "some > very important enhancements" could be made. It will ALWAYS be > true that there are more "very important enhancements" on > the horizon, and you can't keep running after those. You have > to pick some point, and stick to that point, and "ship" at that > point. As long as current is known to be in rapid flux, most I'm glad you support integration of KSE then... As I recall such threading was in the original design specs for 5.0, as released when work on 5.0 began. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Headsup! KSE Nay-sayers speak up!
Matt Dillon wrote: > :> and preferably on more than the i386 platform. If we are going to > :> be serious about supporting more hardware platforms, then we have > :> to start treating them more seriously when major changes like this > :> come along. If we can't get some broader testing of this done in > :> the next few weeks, then the changes should probably wait until > :> after "5.0". > : > : > :I believe that I read in an earlier thread that the archetecture-specific changes >are minimal, and that majority of the changes are > :in high-level constructs in the kernel. Of course, I could be recalling this >incorrectly, but I don't think I am... > : > :jim > > Yes, this is correct. The assembly changes are just structural > indirections for things that were broken off from the proc structure. > The scheduler now messes with 'threads' rather then 'processes' for > the most part. That part of the diff set is involved but straight > forward. Julian also add KSTACK_PAGES to allow the kernel stack to > be specified in a more controlled manner. > > Here is an excerpt so you can see what I mean: > > ... > - > - movlP_VMSPACE(%ecx), %edx > + movlTD_PROC(%ecx), %eax > + movlP_VMSPACE(%eax), %edx > movlPCPU(CPUID), %eax > btrl%eax, VM_PMAP+PM_ACTIVE(%edx) > > - movlP_ADDR(%ecx),%edx > + movlTD_PCB(%ecx),%edx > ... > > See? not much too it. > > -Matt That's about what I thought it would be... If the other archetectures are so flaky right now under FreeBSD, then maybe some people are barking up the wrong tree when it comes to opposing KSE integration using the other archetectures as the crux of their argument. Sounds like they need to be kicking some butts to catch up with the pack! Testing should be across the board, but I don't see any reason why, if the maintainers of the other archetectures are so behind on other tasks that they can't have a seperate, later, 5.0-RELEASE for them. We shouldn't sacrifice intel functionality for timetable slippage on the other archetectures, and honestly, that's how I'm reading the arguments against... Again, I could be wrong, but... Of course, we could always end up like NetBSD, with a development cycle that makes FreeBSD's current cycle look fast, only because of support for all of the different archetectures. No offense to the NetBSD'ers out there, NetBSD is a fine OS, but my point is that FreeBSD is [or was] a different paradigm, primarily [but not exclusively] intel. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Headsup! KSE Nay-sayers speak up!
Sean Chittenden wrote: >>>I am ready to do my megga-commit to add the first stage of KSE-threading support >>>to >>>the kernel. If there is any argument as to the wisdom of this move, >>>then this is the time to speak up! >>> > > I have one system that I've been maintaining/updating since the > 2.X days and I feel it's time to nuke it and start over. +1 for a > non-smp system and SMP system. > > That said, I think the value of having both KSE and SMPng in 5.0 > is HUGE and I think there is probably a large number of people that > would be willing to endure kernel panics, dumps, etc. because the value > (in terms of technological accomplishment and saleability in the > corporate space) would be absolutely worth the bumpy road. -CURRENT > isn't worth tracking unless the dumps, bugs, etc are all going toward > both SMPng and KSE. Hey, anyone running -current without a tape drive attached with a daily dump schedule is either insane, a masochist, or both. Read my post from this morning about the mysterious filesystem corruption I had this morning... Kudos to Justin Gibbs for fixing EOM detection [let's get his scsi_sa.c patches committed ASAP]!!! > If there are grave concerns about having KSE and SMPng in 5.X, > then why not push back the release date? The value far outweighs the > extra months needed to get it finished and out the door, but what do I > know, I'm just a quiet kernel by standard making an observation. -sc Good idea. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Headsup! KSE Nay-sayers speak up!
Garance A Drosihn wrote: > "5.0" (or whatever name it will go by) is slated for November, right? > And the plan was that a new 6.0-current branch wouldn't even be STARTED > until sometime next year, because we'll be concentrating on the > reliability of 5.x. These kernel changes have to go in before anyone > can work on userland changes. My guess is that if we do not get the > KSE kernel stuff into 5.0, then we probably won't get to the desired > userland features until sometime WELL into 2003. Maybe that's better > than the gap between 4.0 and 5.0, but I think it's too long to have > these changes waiting around. I agree... I thought the idea of 5.0 was to kick Linux in the butt. It isn't as if they are just sitting around... FreeBSD is going to be left in the dust unless both the SMPng *AND* KSE projects are integrated into 5.0. > At the kernel summit meeting, Julian was given a green light with the > timetable of getting this set of changes done by August. Right now it > is pretty late in August, but (thanks partially to help from others) > that schedule has basically been kept to. It would be nice to reward > that effort by getting these changes in. [Looks at calandar] Yup! It's August! Good work Julian! > This does seem prudent to me. We should have at least a few more > people running these changes before they get committed to current, > and preferably on more than the i386 platform. If we are going to > be serious about supporting more hardware platforms, then we have > to start treating them more seriously when major changes like this > come along. If we can't get some broader testing of this done in > the next few weeks, then the changes should probably wait until > after "5.0". I believe that I read in an earlier thread that the archetecture-specific changes are minimal, and that majority of the changes are in high-level constructs in the kernel. Of course, I could be recalling this incorrectly, but I don't think I am... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Headsup! KSE Nay-sayers speak up!
Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Julian Elischer writes: > > >>I am ready to do my megga-commit to add the first stage of KSE-threading support >>to >>the kernel. If there is any argument as to the wisdom of this move, >>then this is the time to speak up! >> > > I say "No, not yet". > > Not yet, because in practice nobody has been running your patches yet. > > Not yet, because we have seen no quantified performance impact numbers > (yes, I'm trying to arrange to help you produce these but on a P5/133 > things are _S_L_O_W_! > > Not yet, because I seriously doubt if anybody has had any time to review > and reflect on the way you have gone around and done things. > > Not yet, because there are, as I understand it, unresolved issues with KAME. > > Not yet, because you are generalizing from only one platform, get at least > alpha working first. > > So I propose: > > Put up your patches in a highly visible place and advertise them on > -current, -arch and -smp. > > Once at least 5 developers have publically said "I'm running these > patches on my -current machine(s) and it doesn't totally hose me" > and at least 3 of those machines are SMP and one is non-i386 > architecture, then call for "last orders before commit". If Julian can guarantee it won't hose me completely from the get-go, count me as a tester. The box I would be testing this on is SMP, albeit, intel. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Headsup! KSE Nay-sayers speak up!
Julian Elischer wrote: > John Baldwin wrote: > >>On 27-Aug-01 Julian Elischer wrote: >> >>>I am ready to do my megga-commit to add the first stage of KSE-threading >>>support >>>to >>>the kernel. If there is any argument as to the wisdom of this move, >>>then this is the time to speak up! >>> >>>At this stage a commit would break alpha and ia64 until >>>they are patched. From experience I can say that it's not a horrific >>>change to the machine dependent code so patches PRE commit would be >>>welcome. >>> >>Just to get this out in the public: I for one think 5.x has enough changes in >>it and would like for KSE to be postponed to 6.0-current and 6.0-release. I >>know that I am in the minority on this, but wanted to say it anyways. It >>doesn't mean I don't like the KSE work or anything like that (I've even helped >>out on it some), I just think we have enough work in our basket. Also, I'll >>point out that p4's merging abilities make tracking current relatively easy, >>much more so than if Julian was maintaining a separate tree with this patch and >>having to keep updating current and manually merge it all the time. >> >> >> > > well I expected this to some extent.. > This is why I asked.. I want to get it out where it can be discussed. > the same could also be said for full pre-emption and SMP-NG. > > It is also interestingto note that KSE isn't the only game in town. > The new PTNG package looks interesting, using normal process rforking > to generate a pthreads environment. (It's a rewrite, not a port of > linux threads). > > All I have done is brought the kernel to a state where > it is READY for work to break the 1:1 barrier. It is basically > logically exactly the same kernel as in -current. I think it introduces > far fewer logical changes than, say, the pre-emption code, > or the locking code. I agree that we could wait. I don't however think we > should. I'd rather have ONE broken period than two. At USENIX we agreed that > if I got this done it would be committed and work could start to > provide the facilities that Dan and Chris need for the Userland > code to develop. Remember, that unless you turn this on, it's > a very complicated NOP. > > What P4 does is really irrelevent because there are only 4 people using it.. > (or is that 3?). It needs a distribution channel, and P4 isn't it. > (at least not at the moment.) > > What it DOES do however is make your locking code more challenging. > But that is going to have to be faced at some time Count my vote as a go-for-it. I agree that waiting for 6.0 would be too long indeed. I think that having the KSE framework in the kernel for 5.0 would be a good thing, along with SMPNG... I don't think this is going to turn into another 2.0-RELEASE fiasco [No offense, David, but 2.0-R was buggier than a bum's blanket], which, I may add, was quite quckly made stable after the initial -RELEASE. My one question is: If it does turn into another 2.0-R fiasco, are you ready to put in the hours needed to put out a QUICK bugfix -RELEASE [a la 5.0.5 or whatever?]. I would still prefer a stable -RELEASE. As far as intel goes, I say go for it! jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
UFS issue in -current? Plus good news for tape users...
FreeBSD wahoo.kc.rr.com 5.0-CURRENT FreeBSD 5.0-CURRENT #26: Sat Aug 25 02:25:41 CDT 2001 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/WAHOO i386 1). I shut down properly [shutdown -r now] about an hour ago to boot into winblowz [yeah, but it's the only thing morpheus works in]... 2). When I came up I had a message saying that I had to run fsck manualy... okay... 3). I found that /var [ad0s1f] had a mismatch between the superblock and the first alternate, and it also complained about an invalid label... As far as I know the shutdown went proper... Anyone else seeing this? /var is softupdates flagged... The good news is that Justin's scsi_sa.c patches DO WORK! Once I figured there was nothing that fsck could do for me, I did a newfs /dev/ad0s1f, then mounted it and did a restore of /var from tape. Outside of losing a day's worth of logs, I'm fine now, but the question is: why did it happen? jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: user/group "bind"
Okay, please don't say it... I'm blind... Boot to the head! I see it now, as GID 53... Jim Bryant wrote: > After being informed of the paragraph in UPDATING on this topic, I went > to /usr/src/etc to see what the settled-upon UID/GID of "bind" is... > > Ummm... Did someone forget to commit changes to the /usr/src/etc/group > and /usr/src/etc/passwd baseline files? > > What UID/GID should be used? > > jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
user/group "bind"
After being informed of the paragraph in UPDATING on this topic, I went to /usr/src/etc to see what the settled-upon UID/GID of "bind" is... Ummm... Did someone forget to commit changes to the /usr/src/etc/group and /usr/src/etc/passwd baseline files? What UID/GID should be used? jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why is csh tcsh? This can be a bad thing...
Terry Lambert wrote: > I was still grumpy about the change, but that at least was > enough to mollify me into not objecting loudly and persitantly > up to the import. > > Let me get this straight, though: _now_ you are saying that > the system wide defaults and account template defaults will > be whatever the tcsh maintainers say they are, and that any > changes that the tcsh maintainers make with instantly and > magically be imported into FreeBSD? > > I think there are a few logic flaws in your plan to have > people submit their gripes about the defaults to the tcsh > maintainers: > > 1)They set their defaults the way they like them, and > are unlikely to change. > 2)A lot of the people who shut up did so on the premise > that the defaults would cause tcsh to behave like csh > when invoked with that name, and that it was the tcsh > users, NOT the csh users, who would have to change > away from the system defaults to get their desired > behaviour. > 3)FreeBSD does not seem to track tcsh changes quickly > or religiously enough for a lobbying effort to really > be effective. > > While we may be stuck with this bait-and-switch "upgrade", I > think his complaints are not co easily addressed. Certainly, > the "exec" complaint remains valid, in any case: it's a bug > that csh didn't have. Terry, first things first, or is it last things first... I had issued myself a boot to the head because I had simply forgotten to background the startx and issue a logout [been so long since i've done things this way, blah blah blah, boot to the head], This was the second message in this thread, and I asked people to disregard my initial post because of this, shortly after sending the initial message. Since then, this has taken a life of it's own. After reading the ensuing posts, I do have to say that although I don't agree with a lot of the posts against adding more defacto-standard shells to the base distribution [remember the thread about a month ago], I at least now understand one of the base arguments behind the arguments against. I'm not trying to revive that topic, I'm just saying I see what was behind some of the arguments in that thread now. Anyhow, I have other things on my mind right now, such as why installworld is expecting a user named 'bind'... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: exec issue in tcsh?
Nate Williams wrote: >Wow. Why not use xdm? 8) > Too lazy? >>>Heh. You just uncomment one line in /etc/ttys and HUP init. It's not >>>compilicated. >>> >>Indeed. However, there are some differences in startup of which to be >>aware (.xinitrc vs. .xsession). >> > > I just hard-link the two files together. :) > > > Nate > > That only works in a single wm arena... What about: case $WMCHOICE in twm) xterm -bg black -fg cyan -sb -sl 5000 -geometry 132x60& twm ;; fvwm95) xterm -bg black -fg cyan -sb -sl 5000 -geometry 132x60& fvwm95 ;; olwm) xterm -bg black -fg cyan -sb -sl 5000 -geometry 132x60& olwm ;; olvwm) xterm -bg black -fg cyan -sb -sl 5000 -geometry 132x60& olvwm ;; wmaker) xscreensaver -timeout 10 -lock-mode -no-splash& wmaker ;; motif) xterm -bg black -fg cyan -sb -sl 5000 -geometry 132x60& mwm ;; gnome) xterm -bg black -fg cyan -sb -sl 5000 -geometry 132x60& gnome-session ;; kde2) startkde ;; esac jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: exec issue in tcsh?
David Wolfskill wrote: >>Date: Sun, 26 Aug 2001 02:43:56 -0400 (EDT) >>From: "Brandon D. Valentine" <[EMAIL PROTECTED]> >> > >>On Sat, 25 Aug 2001, Jim Bryant wrote: >> > >>>>Wow. Why not use xdm? 8) >>>> > >>>Too lazy? >>> > >>Heh. You just uncomment one line in /etc/ttys and HUP init. It's not >>compilicated. >> > > Indeed. However, there are some differences in startup of which to be > aware (.xinitrc vs. .xsession). > > Cheers, > david (who quit using xinit about a year ago) > You are missing the point. This is the way I choose to run X for the moment.. I have a quite nice multi-wm .xsession already in place that I like and works well. Yes, it would take only a moment to enable xdm... The point is that I'm using startx for now. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: exec issue in tcsh?
Mike Smith wrote: >>* Jim Bryant <[EMAIL PROTECTED]> [010823 01:33] wrote: >> >>>i noticed this after a build from -current of about 24 hours ago: >>> >>>due to problems getting kde-2.2 to compile under -current, I am >>>currently using windowmaker and doing a `exec startx >&/dev/null` >>>to get into X without leaving a console shell open... >>> > > Wow. Why not use xdm? 8) Too lazy? jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why is csh tcsh? This can be a bad thing...
Peter Wemm wrote: > Jordan Hubbard wrote: > >>>Because of certain differences, it cannot be used wholesale as a >>>replacement for csh. >>> >>Then please enumerate them so that they can be given due attention. >>This is exactly the sort of detailed feedback that was requested when >>we first raised the issue of switching over, and nobody could come up >>with any concrete differences that would cause harm, so the deed was >>done. >> > > We switched for several reasons: > 1: csh script interface sucks > 2: csh user interface sucks > 3: tcsh user interface is one of the better ones. > > csh is not a serious scripting language and hardly anybody ever uses it as > one in scripts that have sufficient complexity to notice the difference. > > As far as user interfaces go, tcsh is as close to a superset as you can > get. That was a step up for the majority of users who actually use it and > it is still "close enough" that built-in finger knowledge works as > expected. > > We made "genuine" csh available as a port in case somebody *has* to have > it for actual scripting that was impossible to tweak to run under tcsh. > (see ports/shells/44bsd-csh). > > Cheers, > -Peter Okay, at least this is the closest I've come to hearing an explaination... I was never arguing the utility of tcsh as an interactive shell, hell, like I said, I've ran it since it first appeared on comp.sources.unix.[misc?] many years ago, and use it as my shell of choice on any platform. My question was on the need to turn it into csh, when just including it in the /bin directory as tcsh was enough. I have been reading up on some of the old well-known diffs, and apparently many HAVE been fixed over the years, but as the gentleman who explained his experience earlier in this thread will attest, not all are fixed. For 4.4, the point is moot, if this is the way it is, this is the way it will ship [next week?]... For 5.0, I maybe the black sheep in saying this, but I'd like to see /bin/csh be the real thing for 5.0. By all means, leave tcsh in /bin, but for the sake of backwards compatability, IMHO `ln /bin/tcsh /bin/csh` was a bad idea. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why is csh tcsh? This can be a bad thing...
I'm aware of this, I have used tcsh since it first appeared on comp.sources.unix, many moons ago. Because of certain differences, it cannot be used wholesale as a replacement for csh. I'm all for tcsh being in /bin, but I don't think that it's a good idea to replace the industry-standard csh with tcsh as unexpected problems can occur when a csh script expecting csh behaviour ends up breaking due to the subtle differences between csh and tcsh... It's kinda late in the process to be complaining about this, but I just noticed this myself... To complete your sentance: "..., but it's not a drop-in replacement for csh." Kris Kennaway wrote: > On Thu, Aug 23, 2001 at 05:03:29PM -0500, Jim Bryant wrote: > >>Why is csh tcsh? >> >>There are differences... >> >> 4:52:48pm wahoo(6): cmp /bin/csh /bin/tcsh >> 4:59:12pm wahoo(7): >> > > tcsh is the newer version of csh. > > Kris jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Why is csh tcsh? This can be a bad thing...
Why is csh tcsh? There are differences... 4:52:48pm wahoo(6): cmp /bin/csh /bin/tcsh 4:59:12pm wahoo(7): jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
exec issue with tcsh?
Please DISREGARD my previous message on this topic... I have issued myself a severe boot to the head in the true tradition of tai-kwan-leap as a result of sending that, so if you must, please remember that I booted myself in the head first, and was enlightened by the experience. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
exec issue in tcsh?
i noticed this after a build from -current of about 24 hours ago: due to problems getting kde-2.2 to compile under -current, I am currently using windowmaker and doing a `exec startx >&/dev/null` to get into X without leaving a console shell open... the problem i have is that when i switched back to vty0 to test to see if removing VESA support solved the panic issue with syscons, i noticed that i still didn't have a login prompt over there, and pressing enter just gives a new line... i haven't tried a control-c, but i'd lay odds that it would kill the X session. i don't know if this is a tcsh issue or a getty issue i'll save my current session and do a conrol-c just to find out and post a followup message to this in a few minutes. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syscons VTY switch panic...
This seems to solve the problem. Thank you. How soon before VESA will be stable? I do prefer a 132x60 text-mode console... Kazutaka YOKOTA wrote: > Would you please remove the vesa driver from the kernel and > do not try loading the vesa module either, and see if things work? > > >>Actually, I have tried to get the VESA splash thing going, but never can get a >>nything to display... I can try removing that... I >>believe it is still set up this way... >> >>What are the limitations on image size and color-depth for the boot splash thi >>ng? >> > > The image must have 256 colors. Its size must be 1024x768 or smaller. > If you don't have the vesa support in the kernel, the maximum size is > 320x200. > > Kazu > > >>Kazutaka YOKOTA wrote: >> >> >>>Do you by any chance use a VESA mode in text vtys? >>> >>>The vesa module in -CURRENT has problems now. If you try to >>>set the VESA_800x600 mode in syscons, you will likely to >>>hang your machine. This is a known problem, and is somewhat >>>related to vm86 and context switching. I am afraid there is >>>no immediate fix for it. >>> >>>Kazu >>> >>> >>> I am getting this with regularity now. The one time I was available to see the panic, I forgot to go into the debug >>ge >> r and do a traceback, but it had something to do with a mwrite, and had a line concerning [maybe a buffer is?]... I know this isn't much to go on, but that's what I have. I'll get more info >>w >> hen I feel like wasting ten or fifteen minutes for a double-reboot... [is it necessary to do the `shutdown -r now` to write a ne >>w >> entropy, or can we just keep going if it boots without the proper entropy?]... I have pretty much isolated this to VTY switching via syscons. Occasionally >>, >> it will leave the system speaker in a constant tone until it reboots. This is very noticable then X exits. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Interrupt messages from usb0 on CURRENT
Same thing here, started with the build this morning... I know of one change that had been done in the past 36 hours to usb, but it should not have done this, as the patches I was using didn't produce this before the committer committed the patches. Maybe something else got changed as well? Vladimir B. Grebenschikov wrote: > Ollivier Robert writes: > > I just upgraded to the latest sources (two hours ago) on my VAIO laptop and > > I'm now getting dozens of messages: > > > > Aug 22 15:00:07 sidhe /boot/kernel/kernel: usb0: interrupt, but not for us > > Aug 22 15:00:51 sidhe last message repeated 8 times > > Aug 22 15:03:02 sidhe last message repeated 19 times > > Aug 22 15:12:59 sidhe last message repeated 92 times > > Have same problem on VAIO, on fresh sources. > > > Any idea? > > > > I also got an error where pccardd tried to attach my pcmcia card two times > > -- > TSB Russian Express, Moscow > Vladimir B. Grebenschikov, [EMAIL PROTECTED] jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syscons VTY switch panic...
Actually, I have tried to get the VESA splash thing going, but never can get anything to display... I can try removing that... I believe it is still set up this way... What are the limitations on image size and color-depth for the boot splash thing? Kazutaka YOKOTA wrote: > Do you by any chance use a VESA mode in text vtys? > > The vesa module in -CURRENT has problems now. If you try to > set the VESA_800x600 mode in syscons, you will likely to > hang your machine. This is a known problem, and is somewhat > related to vm86 and context switching. I am afraid there is > no immediate fix for it. > > Kazu > > >>I am getting this with regularity now. >> >>The one time I was available to see the panic, I forgot to go into the debugge >>r and do a traceback, but it had something to do with >>a mwrite, and had a line concerning [maybe a buffer is?]... >> >>I know this isn't much to go on, but that's what I have. I'll get more info w >>hen I feel like wasting ten or fifteen minutes for a >>double-reboot... [is it necessary to do the `shutdown -r now` to write a new >>entropy, or can we just keep going if it boots without >>the proper entropy?]... >> >>I have pretty much isolated this to VTY switching via syscons. Occasionally, >>it will leave the system speaker in a constant tone >>until it reboots. This is very noticable then X exits. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Disk I/O problems with -current.
Kris Kennaway wrote: > On Mon, Aug 20, 2001 at 11:52:07AM +0100, Josef Karthauser wrote: > >>I'm having strange problems with -current on a laptop with 64mb of >>memory. Periodically "things go strange" [tm]. >> >>Because of the lack of memory I'm using a fair amount of swap. >> >>Everything runs smoothly up until a point, which seems to depend upon >>not running too many large processes for too long. Then the file system >>grinds to a halt for seconds at a time. Some processes run, and others >>just hang. >> > > Yes, I see almost exactly the same thing (except that I haven't > noticed any processes which stay running during the freeze -- things > like keyboard and mouse activity in X or the console always freeze). > Mine could well be swap related too, though I have 128MB of memory. > > I really think developers should be made to run -current on an old, > slow, crippled machines so they notice this kind of thing which would > be lost in the noise on their fast machines :-) I've also noticed this... Sunday and yesterday, I deleted ALL installed -ports and -packages thinking that the meinproc issue with kde-2.2 was being caused by conflicts in libraries and/or include files [it's not either] on this system which has had about three years since a good clean scrubbing... While I was busy recompiling the basics, I noted that the disk activity would stop, and the console become non-responsive, yet there was no panic or other kernel message. This was happening consistantly for about 12 hours or so, and I had to back down from 5 or 6 parallel -ports compiles to one and two in parallel. I also have noted that when switching VTY [by hand, or when exiting X] the system would panic on mwrite and give message about the possibility of buffers being wierded out POSSIBLY [the message was a question]. I also noted on several instances that the "freezes" would occur when there is heavy disk and CPU activity combined with network access [this may or may not be a contributing factor, I don't know] such as fetching a distribution file. I have also noticed extreme slowness when disk activity occurs. top will show almost no CPU being used, but when there is something being copied or moved, everything becomes REALLY sluggish. This has only been noticed in kernels of the last month or so. Tyan S1696-DLUA MoBo, 2 ATAPI busses in use 20G-pri-master, 12G-pri-slave, HP burner sec-master, 2 SCSI-UW busses in use ST15150W dedicated bus, NEC CD-ROM and HP DDS2 on second bus, LinkSys [dc0] 10/100 ethernet, DEC DEFPA SAS UTP-PMD, SB-Live!/Value, Hauppauge WinTV/Theatre. dual P-II/333's, 512Megs SDRAM. Matrox MGA-G200 AGP. USB CompactFlash/SmartMedia reader. -CURRENT as of 3am CDT today. I noticed a lot of changes last night, especially in the vm code, and I'll wait and see if this fixes anything I've noted... Man them cvsup servers were slow this morning! jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
syscons VTY switch panic...
I am getting this with regularity now. The one time I was available to see the panic, I forgot to go into the debugger and do a traceback, but it had something to do with a mwrite, and had a line concerning [maybe a buffer is?]... I know this isn't much to go on, but that's what I have. I'll get more info when I feel like wasting ten or fifteen minutes for a double-reboot... [is it necessary to do the `shutdown -r now` to write a new entropy, or can we just keep going if it boots without the proper entropy?]... I have pretty much isolated this to VTY switching via syscons. Occasionally, it will leave the system speaker in a constant tone until it reboots. This is very noticable then X exits. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
Søren Schmidt wrote: > It seems Alexander Leidinger wrote: > >>On 19 Aug, Søren Schmidt wrote: >> >> >Yups, reverting this, even in a newer kernel makes sound work again, >well the VIA support is still not sounding proberly, but it didn't >before as well so thats not related to this bogon... > Perhaps the bug in the chipset^wPCI-spec? >>>I dont think so, before the latest changes it worked just fine... >>> >>What's the problem? I didn't noticed anything. >> > > It seems that there is either a slight pause, or random noise > between each DMA buffer played... > > -Søren Was this chipset or motherboard-dependant? Like I said, I had no problems running SMP and with a SB/Live!-Value... Current as of yesterday morning [6-7AMish CDT], Tyan S1696DLUA motherboard, 2 Pentium-II/333's, SB/Live! Value card. Did not produce thse issues. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound broken on -current again...
This is pretty wierd... I'm running -current as of 7am this morning, and am listening to Black in Black in XMMS at this moment. SB-Live! Value, I am running SMP. Richard Todd wrote: > In servalan.mailinglist.fbsd-current Daniel M. Kurry writes: > > >>On Wed, Aug 15, 2001 at 07:01:46PM +0200, some SMTP stream spewed forth: >> >>>One gets the first DMA buffer full, then the process hangs... >>> > >>Due to the lack of replies, I'll go ahead. >> > >>I am seeing sound breakage also. >>My card is a >>Creative Labs SoundBlaster Live!. >> > >>xmms will play a short (less than a second) spurt of audio and then stop >>responding. mpg123 will not play (any audio to the speakers) at all. >> > >>I ran a buildworld today which apparently broke it. >>That puts the breakage between today and sometime less than 2 months >>ago. >>(I really cannot be more specific.) >> > > I'm seeing much the same thing, on an SMP box with onboard sbc0 (Vibra16X) > sound chip. Attempting to play sound with madplay gets about 2 seconds of > sound and then silence, with the madplay process in an unkillable kernel > wait. Oddly enough, the sbc0 interrupt thread continues to occasionally gather > a tick of CPU time, but apparently not enough to do anything useful. > > I'm busy doing binary-search on the CVS tree, checking out source from > different times and seeing if I can localize the commit that broke it. > My current results are that a kernel built from source as of > 2001/08/10 00:00 CDT (i.e. 2001/08/09 22:00:00 PDT) works, one built > from source as of 2001/08/10 15:52 PDT does not, so the bug is > somewhere in between there. I'm now trying to narrow this down further, > to a specific commit somewhere in that region. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bash in /usr/local/bin?
Joseph Mallett wrote: > On Mon, Aug 13, 2001 at 07:23:26PM -0500, Jim Bryant wrote: > >>DOD/DFAS, as well as DOD/DISA. >> >>I find it amazing that the CIA has a more lax policy than DFAS and DISA. >> >> > > The only person I've ever talked to from the CIA was in charge of network > security to some degree, and according to him they can't even use FreeBSD, > OpenBSD, or NetBSD internally. Everything must come from a central vendor > and be supported by a real company, not by mailing lists. > > I'd call that less lax. Then, I'd call it about the same. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bash in /usr/local/bin?
DOD/DFAS, as well as DOD/DISA. I find it amazing that the CIA has a more lax policy than DFAS and DISA. David O'Brien wrote: > On Mon, Aug 13, 2001 at 04:13:52AM -0500, Jim Bryant wrote: > >>from what i've read here, not many undrestand the actual mindset of the >>military when it comes to computing. >> >>the closest would be the guy who mentioned that since ports are on the >>CD's that they should be acceptable, this is incorrect. >> > > You are making sweeping generalizations. Please stop and be specific > which parts of the military. It is correct for the CIA. > > The CIA[*] will not let you bring in any download bits off the net (or > floppies containing them) to compile locally and install. HOWEVER, if > the bits come on a CDROM from a commercial vendor, they are "OK". So in > the FreeBSD case, packages are on the commercial 4-disc set, and thus can > be installed. In older days for Solaris, one had to find a CD offering > from say Walnut Creek CDROM that contained precompiled versions of GNU > bits for Solaris. Again, if it was something their purchasing could buy > from a vendor an receive it was OK. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bash in /usr/local/bin?
Steve O'Hara-Smith wrote: > On Sun, 12 Aug 2001 17:04:01 -0500 > Jim Bryant <[EMAIL PROTECTED]> wrote: > > JB> I said I'd drop it, but apparently there are people that don't understand the >dinosaur mentality of certain organizations such as > JB> DOD, DISA/DECC, OSD, DARPA, USA, USN, USAF, and USMC. > JB> > JB> If it's not in the base setup, on a production box, you can't use it. >Everything must be kept in it's ORIGINAL install location, > > Th obvious solution to this is a 'Military' switch in sysinstall > that sets PREFIX to / for all ports. heheh... actually... i've seen military systems that do this... from what i've read here, not many undrestand the actual mindset of the military when it comes to computing. the closest would be the guy who mentioned that since ports are on the CD's that they should be acceptable, this is incorrect. it took me a while to figure out how backwards they really are. this is one of the many reasons that they cannot keep good unix talent around. remember, these are the same people that argued that C and C++ was evil and that only ADA was good for nearly 15 years, until they finally realized they were wrong. let's take a look at the failures of what was supposed to be ADA's swan-song project: the new FAA ATC system... you know... the one that keeps crashing everywhere it's installed. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bash in /usr/local/bin?
The Anarcat wrote: [Foul-mouthed anti-gummint drivel deleted] >>Actually, it is up to us to resolve this. I don't think you understand how >>DOD operates. The vendor makes the changes, not DOD. Not the admin. >> > > And FreeBSD is the *vendor*? I don't think so. At least I don't hope so. > If I'm mistaken, slap me Consider yourself slapped. The FreeBSD project is the only DOD-approved vendor of FreeBSD. Until the core team says otherwise. >>Moving the non-GPL shells to /bin is a trivial request that can solve >>problems that you obviously don't understand. >> > > Then we could also answer a trivial request such as making apache part > of the base system! If the DOD need a webserver, they're screwed? They > panic? What the heck is that? And why should we care about such > d**kheads? No, they aren't screwed. They don't panic. They simply say "screw FreeBSD" and just call Sun, which does have Apache in the base distribution, as well as the shells where the admin is allowed to use them, and doesn't give them a bunch of anti-gummint drivel. > Wasn't the DOD using NT? Not for anything serious. >>Key to this is an admin-friendly >>environment designed to get around the pre-cambrian attitudes that prevent >>DOD admins from using standard tools just because it's in the wrong place on >>the disk array or because it's considered a third-party option, or even >>worse: freeware [h! step away from the keyboard, son. you going to >>prison, boy!]. >> > > Bash standard? Funny. How many users of FreeBSD? How many users of Linux? How many people using csh? How many people using bash? Besides the fact that you don't reason well, you don't read too well. bash is GPL, it wouldn't qualify for the tree. zsh is open, and has the features of bash, and could probably be a good substitute. The proposition here doesn't involve any specific shell, it's a usability issue. > I had very good comments on the easiness (sp?) ppl have installing > third party apps in the install process. And the ports collection, and > the packages, etc... FreeBSD is very admin friendly, IMHO. Only when the admin has the ability to install third-party standard tools. >>Try thinking outside the box sometime. If you want a "traditional" unix, I >>think there is still a PDP-11 emulator and DL01 image of V7 at >>gatekeeper.dec.com. >> > > Yeah. Let's go with the New Technology: NT. All these buzzwords and > semantics are messing things up here. It's not a matter of tradition, > it's a matter of license (bash is GPL, FBSD is BSD-licensed), and > functionality (bash != sh). See also the comment about resistance to > have perl in the base system. perl is in the base system. and again, you don't read too well, i haven't said a nice word in this entire thread about bash, and others have noted the GPL. > Linux have bash in the base system simply because there's no other free close > relative to sh around. that was a rather inane statement... ever read the BSD license? >>I'm more for an evolutionary unix where the idea of what's standard changes >>to reflect the needs of it's admins and users in diverse environments. >> > > As much as I appreciate "evolution", I think this mentality is exactly > the thing that makes us pull away from support from old hardware. That's > a shame. how does moving defacto-standard userland items into the basic system effect the kernel? you lost me there. >>going nowhere due to outdated beliefs "oh, but that belongs in >>/usr/local/bin". >> > > Again, it's not a belief. It's a philosophy that is behind FreeBSD. a belief that keeps freebsd out of some hardcore, high-dollar markets. > Anyways, this has probably been burnt to death long time ago, I should > not get into this. Yes, and I think you should close and wipe your mouth after your foul-mouthed anti-gummint spewing. Flys are gathering around your tooth. >>My argument for the trivial move of the non-GPL shells to /bin, so long as >>they are statically linked, is based on experience in a market in which >>FreeBSD just got it's foot inside of the door. We have already done this >>with tcsh. I don't see what the problem is getting the rest of the non-GPL >>shells into /bin is. >> > > I missed something here. Is tcsh GPLed? I don't think so... A quick look > at /usr/src/contrib/tcsh gives me 2 matches for "GNU", config.guess and > config.sub. The rest looks like standard BSD license. Am I wrong? 2:19:01am wahoo(2): where tcsh /bin/tcsh Hey Jethro, who put that there? did you? wasn't me! Maybe it was one of dem damned gummint black heeleechoppers being piloted by ET and Bill Clinton... > Please, jim, do not take my comments too harsh. I have a very strong... > opinion of the military, and of "progress", "evolution" or whatever you > want to call that mad "fuite en avant" (I don't know the proper idiom in > english (this was french)). I'm not taking the comments too harsh. I w
Re: bash in /usr/local/bin?
Gordon Tetlow wrote: > As a preface to this whole thing, I find it higly amusing that you are > sending this mail from a Linux box. Of course, for that matter, so am I. > (I'm planning on changing that soon.) Excuse me? FreeBSD wahoo.kc.rr.com 5.0-CURRENT FreeBSD 5.0-CURRENT #18: Fri Aug 10 16:51:25 CDT 2001 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/WAHOO i386 When Netscape comes out with support for FreeBSD again, I'll run native, until then, I, like everyone else using freebsd am stuck using netscape in the COMPATLINUX construct. Please don't make assumptions about an operating environment without understanding the problems of living within that environment. > > On Sun, 12 Aug 2001, Jim Bryant wrote: > > >>I said I'd drop it, but apparently there are people that don't >>understand the dinosaur mentality of certain organizations such as >>DOD, DISA/DECC, OSD, DARPA, USA, USN, USAF, and USMC. >> >>If it's not in the base setup, on a production box, you can't use it. >>Everything must be kept in it's ORIGINAL install location, otherwise >>you MUST justify it and ask DISA/DECC for a waiver, which in itself, >>is a pain in the ass, and in many cases, not likely to happen due to >>dinosaur mentality. >> > > You said it yourself. They are a dinosaur. Why should be drag ourselves > back to the paleolithic and cater to a very specific problem in our base > tree? bash is a nice shell. I use it as my normal shell, but when I drop > to single user mode, I *always* end up using /bin/sh. I'm not a fan of csh > (tcsh isn't bad though) and I only write shell scripts in /bin/sh. > Besides, how often do you need to drop to single user mode and *really* > need bash? I'm not arguing for bash. I despise bash in fact. When I drop to single-user, I want to be in and out. That means I want the tools to do the job most efficiently so I can be in and out. I'm personally a tcsh fan, but shells are a matter of preference and proficiency. What can take ten minutes in the bourne shell may only take me five using the shell of my choice. IMHO, the real dinosaur mentality I see at this moment is opposition to a very trivial request, that even the real dinosaurs int he unix industry [the Suns, HPs, IBMs, SGIs, etc] are seeing must be done because of end-user complaints and requests. Also, dinosaurs or not, DOD is now an INVESTOR in the FreeBSD system. Name any other group besides maybe BSDI that has provided $1.4 million [USD] to the project. We should look towards making FreeBSD the open-source OS of choice in the DOD environment, in which Linux has already made major inroads where FreeBSD isn't even allowed to tread yet. >>I now refer you to the recent news concerning the TrustedBSD project. >> >>FreeBSD is getting military contracts now. We need to think ahead to >>the needs of a whole new class of admin and user, and they are in >>highly restrictive environments that preclude `mv /usr/local/bin/*sh >>/bin`. >> > > And those people that are working there are probably programming in COBOL > and Fortran. More likely C, C++, and Java. Maybe a bit of stuff ported to GNAT. > >>I'm sure there are equally restrictive environments for computers and >>operating systems in *EVERY* country, but I speak from my personal >>experience with the dinosaurs at DOD. At DOD, *EVERY* copy of FreeBSD >>will be subject to what I am saying. In the Sun environment in which >>I did my last DOD contract at, if tcsh wasn't in /bin, I wouldn't have >>been able to use it. That's how backwards they are. >> >>In answer to your statement, some admins can be fired, even arrested >>and brought up on charges for doing what you suggest. I'm certain >>that this happens in countries other than America as well. >> > > Again, this is a problem for you and the DOD to sort out. It should be of > no concern to the project. Actually, it is up to us to resolve this. I don't think you understand how DOD operates. The vendor makes the changes, not DOD. Not the admin. Another priority item should be making sure we are compatible with such things as the latest versions of Oracle, etc... This is an area in which we can compete head-to-head with the high-dollar stuff. Also, I havn't worked for DOD in a long time, but I have done recent contracts with them, and understand firsthand the BS involved in having to do without tools all unix people, including myself, consider standard, that are not allowed because it's not part of the base install. Moving the non-GPL shells to /bin is a trivial request that can solve problems that you obviously don't understand. DOD will is a
Re: bash in /usr/local/bin?
I said I'd drop it, but apparently there are people that don't understand the dinosaur mentality of certain organizations such as DOD, DISA/DECC, OSD, DARPA, USA, USN, USAF, and USMC. If it's not in the base setup, on a production box, you can't use it. Everything must be kept in it's ORIGINAL install location, otherwise you MUST justify it and ask DISA/DECC for a waiver, which in itself, is a pain in the ass, and in many cases, not likely to happen due to dinosaur mentality. I now refer you to the recent news concerning the TrustedBSD project. FreeBSD is getting military contracts now. We need to think ahead to the needs of a whole new class of admin and user, and they are in highly restrictive environments that preclude `mv /usr/local/bin/*sh /bin`. I'm sure there are equally restrictive environments for computers and operating systems in *EVERY* country, but I speak from my personal experience with the dinosaurs at DOD. At DOD, *EVERY* copy of FreeBSD will be subject to what I am saying. In the Sun environment in which I did my last DOD contract at, if tcsh wasn't in /bin, I wouldn't have been able to use it. That's how backwards they are. In answer to your statement, some admins can be fired, even arrested and brought up on charges for doing what you suggest. I'm certain that this happens in countries other than America as well. Joseph Mallett wrote: > If these admins can't figure out cp `which bash` /bin and then how to add it > to etc/shells and chsh root, then I really question if they should be the kind > of people that dictate the future of FreeBSD. > > 0n Sun, Aug 12, 2001 at 04:32:55AM -0500, Jim Bryant wrote: > >>IMHO, all widely accepted shells should be put in /bin jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USB Microtech CameraMate CF/CF+/CF+II/Microdrive/SmartMedia reader
I did an archive search of this list, and found a post from April from a guy who had some diffs to scsi_da.c and the umass driver to get this thing working. I sent him an email a couple of weeks ago, but haven't heard back yet. He said he had it working under -current. Does anyone have a copy of these diffs? There was at least one other subscriber to -current that asked him for these diffs... Also, I may be a little behind the times, as this is my first USB device to play with, so some tips on how to get it working with the drivers once patched would help too... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ahc fails to attach in -current (was: snapshot installation woes)
Andrew Kenneth Milton wrote: > > +---[ Gordon Tetlow ]-- > | On Sat, 4 Aug 2001, Gordon Tetlow wrote: > | > | > Sure enough, that fixed the kernel panic, but here's the next odd piece, > | > my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940 > | > dmesg reports that ahc0 is there. The lines from the dmesg are (hand > | > typed): > | > | ahc0: port 0x5000-0x50ff mem >0x5000-0x5fff irq 15 at device 15.0 on pci0 > | aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs > | > | Since -stable and -current are using the exact same driver, there is > | something more subtle (and sinister?) going on that I can't figure out. At > | this point, I'm throwing my hands up in the air unless someone can give me > | a better idea as to what the possible problem could be. I'd really like to > | try -current on this box as it's a dual proc PPro 200. > > You'll probably need to use DEVFS to get booted. I can't boot -current > from ahc using a standard /dev/ (or couldn't around the time DEVFS switched > from being default disabled, to default enabled, so I've been running DEVFS > ever since). This from either a 2940UW, or from dual onboard 7895's. So > if you can get it installed, try building a new kernel with DEVFS enabled. > > I can't run SMP with ahc either, the machine locks up and I get messages > about interrupts being off for too long (it was a while ago, but, I try > an SMP build every month or so, and it still locks up (don't get to see the > messages in X though)). > > Somtimes I do get more than 2-3 mins of uptime before it locks, and I can see > that /dev/smb0 is no longer 'configured' (lmmon et. al. stop working). > > So if you do get it booted, be prepared for some torrid times d8) As far as DEVFS goes, isn't that config option now depreciated, and everything is in devfs? By the way, I think I see his problem right now! Exactly as I said in my last message on this topic... What does his dmesg say for ata1? irq 15? Same shit I ran into... ata isn't reading if the controller is disabled in BIOS. Under -stable, this is being read, and no conflict exists. Could this actually be related to changes in ata? SMP and ahc0/1 work fine here... Tyan S1696-DLUA MoBo, 2 P2-333's, Linksys 10/100 on dc0, DEC DEFPA SAS UTP-PMD, SB Live!, and WinTV/Theatre. Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #12: Tue Jul 31 16:18:35 CDT 2001 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/WAHOO Timecounter "i8254" frequency 1192995 Hz CPU: Pentium II/Pentium II Xeon/Celeron (333.00-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping = 0 Features=0x183fbff real memory = 536870912 (524288K bytes) avail memory = 516796416 (504684K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 11 IOAPIC #0 intpin 17 -> irq 9 IOAPIC #0 intpin 18 -> irq 5 IOAPIC #0 intpin 19 -> irq 10 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 [...] ahc0: port 0xe000-0xe0ff mem 0xfebfd000-0xfebfdfff irq 10 at device 15.0 on pci0 ahc0: Using left over BIOS settings ahc1: port 0xec00-0xecff mem 0xfebff000-0xfebf irq 11 at device 15.1 on pci0 ahc1: Using left over BIOS settings jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ahc fails to attach in -current (was: snapshot installation woes)
Gordon Tetlow wrote: > > On Sat, 4 Aug 2001, Gordon Tetlow wrote: > > > Sure enough, that fixed the kernel panic, but here's the next odd piece, > > my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940 > > dmesg reports that ahc0 is there. The lines from the dmesg are (hand > > typed): > > > > ahc0: port 0x5000-0x50ff mem >0x5000-0x5fff irq 15 at device 15.0 on pci0 > > device_probe_and_attach: ahc0 attach returned 12 > > > > errno.h says ENOMEM is 12, so it seems that something in the ahc driver is > > unable to allocate memory. Dunno where or why, but something is fouling > > it up. By contrast 4.3-RELEASE doesn't have any issues (I'll try a recent > > snapshot if that would help). Sorry I can't help out any more, but the > > debugging tools in the installation disks seem to lacking > > (understandably). > > Okay, I tried with a 4.4-PRERELEASE bootdisk that was available on > current.jp.freebsd.org and dmesg came up with the following: > > ahc0: port 0x5000-0x50ff mem 0x5000-0x5fff >irq 15 at device 15.0 on pci0 > aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs > > Since -stable and -current are using the exact same driver, there is > something more subtle (and sinister?) going on that I can't figure out. At > this point, I'm throwing my hands up in the air unless someone can give me > a better idea as to what the possible problem could be. I'd really like to > try -current on this box as it's a dual proc PPro 200. I don't know if -current and -stable are using the same driver. Something *IS* different. Please see my post from about a month or so back in the aic7xxx group. Nobody responded to this. Where it would boot, with both controllers [3940UW on the MB] under -stable, it came up with the same message on ahc0 then after probing ahc1 and finding something there, reassigning ahc1 to ahc0. I ended up solving my own problem on this, although it did cause yet other problems. I had, because of IRQ issues, disabled the secondary IDE controller in the BIOS, to allow for both SCSI controller sides to have independant IRQs. This was causing the exact same message you note [see the dmesg output in the aic7xxx list]. Interesting to note that even with the secondary IDE controller disabled on the MB, -current failed to recognize this, and then in turn enabled it. Once I turned on the second IDE controller, this whole thing cleared up, albeit, with side-effects [now my Hauppauge WinTV/Theatre card is in conflict, and will cause a spontaneous reboot in both winblowz and fbsd when the TV is activated, although radio works fine]. Are you disabling motherboard IRQs in a similar fashion? Play with your IRQs, and have "Plug and Play" set in your BIOS. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /home: mount pending error: blocks 14 files 3
Am I desynched? I went to single-user, tried to do a fsck -s, and found there is no such option. Also, the /etc/fstab didn't need changed at all. It is already proper. Needless to say, going to single-user, running just `fsck -y /dev/ad0s1g` fixed the problem, although it noted no errors. Could there be a bug in softupdates again? Below is a copy of the top of the manpage for the version of fsck on my -current, and a copy of my [unmodified since ???] /etc/fstab. --- FSCK(8) FreeBSD System Manager's ManualFSCK(8) NAME fsck - file system consistency check and interactive repair SYNOPSIS fsck [-dvplfyn] [-B | -F] [-l maxparallel] [-t fstype] [-T fstype:fsoptions] [special | node ...] # DeviceMountpoint FStype Options Dump Pass# /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1e /usrufs rw 2 2 /dev/ad0s1f /varufs rw 2 2 /dev/ad0s1g /home ufs rw 2 2 /dev/ad0s1h /tmpufs rw 2 2 /dev/ad1s1e /misc ufs rw 2 2 /dev/da0s1 /ms-dog msdosfs rw 0 0 /dev/cd0c /cdrom cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 proc/usr/compat/linux/proc linprocfs rw 0 0 #argus:/misc/argus.misc nfs rw 0 0 --- In case you feel like asking, my cheetah died, and all I could afford was a big IDE at the time, the 'cuda winblowz is on is still alive tho... One of these days... Brian Somers wrote: > > The error means that your machine crashed with soft-updates enabled, > leaving 14 blocks and 3 files still allocated on disk (using up > blocks & inodes). > > If the error keeps turning up, I would guess that you have a 0 or > empty fsck field in /etc/fstab and fsck -s therefore not fixing the > problem. > > To fix it, correct fstab and run fsck -B. > > > I've never had this before, and I have traced the message to ufs/ffs/ffs_vnops.c >on line 634. > > > > I have recently noticed [since my last svsup] that this is happening on boot and >shutdown [in which case, the messasge is also in > > the same file, but for umount conditions]. > > > > I am not a filesystem expert.. How concerned should I be? > > > > This is -current a week or two old [before all the lockup threads began]... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /home: mount pending error: blocks 14 files 3 [correction]
Jim Bryant wrote: > > I've never had this before, and I have traced the message to ufs/ffs/ffs_vnops.c on >line 634. > > I have recently noticed [since my last svsup] that this is happening on boot and >shutdown [in which case, the messasge is also in > the same file, but for umount conditions]. > > I am not a filesystem expert.. How concerned should I be? > > This is -current a week or two old [before all the lockup threads began]... correction: s/ffs_vnops.c/ffs_vfsops.c hun -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/home: mount pending error: blocks 14 files 3
I've never had this before, and I have traced the message to ufs/ffs/ffs_vnops.c on line 634. I have recently noticed [since my last svsup] that this is happening on boot and shutdown [in which case, the messasge is also in the same file, but for umount conditions]. I am not a filesystem expert.. How concerned should I be? This is -current a week or two old [before all the lockup threads began]... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Looks like I solved my own problem... Sorry...
Okay, AFTER rebuilding linuxthreads with the most recent port, IT DID make it past gen_lex_hash. Word to the wise, if you haven't rebuilt linuxthreads, I suggest you do to avoid the problems I have had. Again, I am running -current of the early hours [CDT] of Sunday morning. Jim Bryant wrote: > > Okay, I just built it successfully without "WITH_LINUXTHREADS=yes". > > I also noticed that my linuxthreads lib was linuxthreads-2.1.2, and I'm rebuilding >it with the linuxthreads-2.2.3_1 sources. > Afterwards, I'll try the compile again. > > Jim Bryant wrote: > > > > I forgot to add: > > > > I am using the make option: `make WITH_LINUXTHREADS=yes` > > > > Jim Bryant wrote: > > > > > > I don't know if this belongs here, in the database list, or in the ports list... > > > > > > Under -current from early Sunday morning [CDT], a build of mysql-server-3.23.39 >hangs forever at: > > > > > > --- > > > ===> Building for mysql-server-3.23.39 > > > . > > > . [snip] > > > . > > > ./gen_lex_hash > lex_hash.h > > > --- > > > > > > It was there since about the time I went to bed, and it's still there now. > > > > > > I'll try to `make clean ; make`, just to be sure that something wierd didn't >happen. > > > > > > Is this a -current issue, or should I post this problem in one of the other >lists? jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gen_lex_hash in mysql-server-3.23.39 build hangs forever under -current
Okay, I just built it successfully without "WITH_LINUXTHREADS=yes". I also noticed that my linuxthreads lib was linuxthreads-2.1.2, and I'm rebuilding it with the linuxthreads-2.2.3_1 sources. Afterwards, I'll try the compile again. Jim Bryant wrote: > > I forgot to add: > > I am using the make option: `make WITH_LINUXTHREADS=yes` > > Jim Bryant wrote: > > > > I don't know if this belongs here, in the database list, or in the ports list... > > > > Under -current from early Sunday morning [CDT], a build of mysql-server-3.23.39 >hangs forever at: > > > > --- > > ===> Building for mysql-server-3.23.39 > > . > > . [snip] > > . > > ./gen_lex_hash > lex_hash.h > > --- > > > > It was there since about the time I went to bed, and it's still there now. > > > > I'll try to `make clean ; make`, just to be sure that something wierd didn't >happen. > > > > Is this a -current issue, or should I post this problem in one of the other lists? jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gen_lex_hash in mysql-server-3.23.39 build hangs forever under -current
I forgot to add: I am using the make option: `make WITH_LINUXTHREADS=yes` Jim Bryant wrote: > > I don't know if this belongs here, in the database list, or in the ports list... > > Under -current from early Sunday morning [CDT], a build of mysql-server-3.23.39 >hangs forever at: > > --- > ===> Building for mysql-server-3.23.39 > . > . [snip] > . > ./gen_lex_hash > lex_hash.h > --- > > It was there since about the time I went to bed, and it's still there now. > > I'll try to `make clean ; make`, just to be sure that something wierd didn't happen. > > Is this a -current issue, or should I post this problem in one of the other lists? jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
