Linux-Misc Digest #399, Volume #20 Sat, 29 May 99 10:13:31 EDT
Contents:
fcntl(..,F_SETLK,..) over (NEWS)
kernel error messages (NEWS)
Re: SCSI error (aic7xxx.c (NEWS)
Re: [rxvt] numeric keyboa (NEWS)
Re: Iomega products and L (NEWS)
Re: ls colors... not reco (NEWS)
Re: RH6, Gnome & RealPlay (NEWS)
Re: Warning! [object] may (NEWS)
Re: 3 buttom mouse emulation ("D. Vrabel")
Application/PDF in Netsca (NEWS)
----------------------------------------------------------------------------
From: NEWS <[EMAIL PROTECTED]>
Subject: fcntl(..,F_SETLK,..) over
Date: 27 May 1999 22:17 GMT
Hi,
I am not sure how/why, but fcntl() locks of files on NFS mounted
file systems fails with 2.2.5-15. It works on 2.0.34 (and other
OSs such as freeBSD, so I suspect this is something to do with
the 2.2 version. Here's a small sample program, (originally from
nmh-0.27-* (sbr/lock_file.c)), to illustrate the problem.
The machine runs stock redhat 6.0, and is
kannanvpc snippets$ uname -a
Linux kv 2.2.5-15 #3 Tue May 25 10:56:10 EDT 1999 i686 unknown
Has anyone else seen this before?
I wonder if this is a bug in the 2.2 kernels, my configuration
(I am also appending my kernel .config file at the bottom), or
something with the redhat 6.0 configuration.
Hopefully, someone can spot what I am missing in this?
Thanks,
Kannan
PS: Is there an appropriate place to posit kernel related bugs/issues?
The small test program:
/*
* lock.c -- routines to lock/unlock files
*
* $Id$
*/
#include <stdio.h>
#include <sys/types.h>
#include <stdlib.h>
#include <unistd.h>
#include <string.h>
# include <errno.h>
# include <fcntl.h>
static void testLock(char*, int);
int
main(int argc, char* argv[])
{
int fd;
char* file = (argc >= 2 ? argv[1] : "./test");
/* create the file */
fd = open(file, O_RDWR|O_CREAT, 0644);
if (fd < 0) {
perror("write");
return EXIT_FAILURE;
}
(void) write(fd, "TEST", 5);
(void) close(fd);
testLock(file, O_RDONLY);
testLock(file, O_RDWR);
(void) unlink(file);
return EXIT_SUCCESS;
}
static void
testLock(char *file, int access)
{
int fd, j;
struct flock buf;
/* make sure we open at the beginning */
access &= ~O_APPEND;
if ((fd = open (file, access | O_NDELAY)) == -1) {
fprintf(stderr, "open(%s): %s", file, strerror(errno));
return;
}
buf.l_type = (((access & O_WRONLY) || (access & O_RDWR)) ?
F_WRLCK : F_RDLCK);
buf.l_whence = SEEK_SET;
buf.l_start = 0;
buf.l_len = 0;
j = fcntl (fd, F_SETLK, &buf);
if (j < 0) {
fprintf(stderr,
"fcntl(%s(fd = %d), F_SETLK, {%s, SEEK_SET, 0, 0}) = %s\n",
file, fd,
(buf.l_type == F_RDLCK ? "F_RDLCK" : "F_WRLCK"),
strerror(errno));
} else {
fprintf(stderr,
"fcntl(%s(fd = %d), F_SETLK, {%s, SEEK_SET, 0, 0}) = %s\n",
file, fd,
(buf.l_type == F_RDLCK ? "F_RDLCK" : "F_WRLCK"),
"success");
buf.l_type = F_UNLCK;
buf.l_whence = SEEK_SET;
buf.l_start = 0;
buf.l_len = 0;
fcntl(fd, F_SETLK, &buf);
}
close (fd);
return;
}
======================================================================
my kernel config is:
#
# Automatically generated make config: don't edit
#
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
#
# Processor type and features
#
CONFIG_M386=y
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M686 is not set
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
# CONFIG_SMP is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y
#
# General setup
#
CONFIG_NET=y
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_QUIRKS is not set
CONFIG_PCI_OLD_PROC=y
# CONFIG_MCA is not set
# CONFIG_VISWS is not set
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_BINFMT_JAVA=m
# CONFIG_PARPORT is not set
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
CONFIG_APM_POWER_OFF=y
# CONFIG_APM_IGNORE_MULTIPLE_SUSPEND is not set
# CONFIG_APM_IGNORE_SUSPEND_BOUNCE is not set
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
#
# Plug and Play support
#
CONFIG_PNP=y
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_BLK_DEV_IDEPCI is not set
# CONFIG_IDE_CHIPSETS is not set
#
# Additional Block Devices
#
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_INITRD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_CPQ_DA is not set
CONFIG_PARIDE_PARPORT=y
CONFIG_PARIDE=m
#
# Parallel IDE high-level drivers
#
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m
CONFIG_PARIDE_PG=m
#
# Parallel IDE protocol modules
#
CONFIG_PARIDE_ATEN=m
CONFIG_PARIDE_BPCK=m
CONFIG_PARIDE_COMM=m
CONFIG_PARIDE_DSTR=m
CONFIG_PARIDE_FIT2=m
CONFIG_PARIDE_FIT3=m
CONFIG_PARIDE_EPAT=m
CONFIG_PARIDE_EPIA=m
CONFIG_PARIDE_FRIQ=m
CONFIG_PARIDE_FRPW=m
CONFIG_PARIDE_KBIC=m
CONFIG_PARIDE_KTTI=m
CONFIG_PARIDE_ON20=m
CONFIG_PARIDE_ON26=m
# CONFIG_BLK_DEV_HD is not set
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK_DEV=y
# CONFIG_FIREWALL is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_IP_ROUTER is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
# CONFIG_IP_MROUTE is not set
CONFIG_IP_ALIAS=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
#
# (it is safe to leave these untouched)
#
CONFIG_INET_RARP=m
CONFIG_SKB_LARGE=y
# CONFIG_IPV6 is not set
#
#
#
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_BRIDGE is not set
# CONFIG_LLC is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
# CONFIG_CPU_IS_SLOW is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
#
# SCSI support
#
CONFIG_SCSI=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
#
# SCSI low-level drivers
#
CONFIG_SCSI_7000FASST=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AHA152X=m
CONFIG_SCSI_AHA1542=m
CONFIG_SCSI_AHA1740=m
CONFIG_SCSI_AIC7XXX=m
# CONFIG_AIC7XXX_TCQ_ON_BY_DEFAULT is not set
CONFIG_AIC7XXX_CMDS_PER_DEVICE=8
CONFIG_AIC7XXX_PROC_STATS=y
CONFIG_AIC7XXX_RESET_DELAY=5
CONFIG_SCSI_ADVANSYS=m
CONFIG_SCSI_IN2000=m
CONFIG_SCSI_AM53C974=m
CONFIG_SCSI_MEGARAID=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
CONFIG_SCSI_DTC3280=m
CONFIG_SCSI_EATA=m
CONFIG_SCSI_EATA_TAGGED_QUEUE=y
# CONFIG_SCSI_EATA_LINKED_COMMANDS is not set
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_EATA_DMA=m
CONFIG_SCSI_EATA_PIO=m
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
CONFIG_SCSI_GENERIC_NCR5380=m
# CONFIG_SCSI_GENERIC_NCR53C400 is not set
CONFIG_SCSI_G_NCR5380_PORT=y
# CONFIG_SCSI_G_NCR5380_MEM is not set
CONFIG_SCSI_INITIO=m
CONFIG_SCSI_INIA100=m
CONFIG_SCSI_NCR53C406A=m
CONFIG_SCSI_SYM53C416=m
CONFIG_SCSI_NCR53C7xx=m
# CONFIG_SCSI_NCR53C7xx_sync is not set
CONFIG_SCSI_NCR53C7xx_FAST=y
CONFIG_SCSI_NCR53C7xx_DISCONNECT=y
CONFIG_SCSI_NCR53C8XX=m
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
CONFIG_SCSI_NCR53C8XX_PROFILE=y
# CONFIG_SCSI_NCR53C8XX_IOMAPPED is not set
# CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT is not set
CONFIG_SCSI_PAS16=m
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
CONFIG_SCSI_PSI240I=m
CONFIG_SCSI_QLOGIC_FAS=m
CONFIG_SCSI_QLOGIC_ISP=m
CONFIG_SCSI_QLOGIC_FC=m
CONFIG_SCSI_SEAGATE=m
CONFIG_SCSI_DC390T=m
# CONFIG_SCSI_DC390T_NOGENSUPP is not set
CONFIG_SCSI_T128=m
CONFIG_SCSI_U14_34F=m
# CONFIG_SCSI_U14_34F_LINKED_COMMANDS is not set
CONFIG_SCSI_U14_34F_MAX_TAGS=8
CONFIG_SCSI_ULTRASTOR=m
CONFIG_SCSI_DEBUG=m
#
# Network device support
#
CONFIG_NETDEVICES=y
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_EQUALIZER is not set
CONFIG_ETHERTAP=m
CONFIG_NET_ETHERNET=y
CONFIG_NET_VENDOR_3COM=y
CONFIG_EL1=m
CONFIG_EL2=m
CONFIG_ELPLUS=m
CONFIG_EL16=m
CONFIG_EL3=m
CONFIG_3C515=m
CONFIG_VORTEX=m
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_RTL8139 is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_ACENIC is not set
# CONFIG_NET_ISA is not set
# CONFIG_NET_EISA is not set
# CONFIG_NET_POCKET is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_DLCI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_RADIO is not set
# CONFIG_TR is not set
# CONFIG_SHAPER is not set
# CONFIG_HOSTESS_SV11 is not set
# CONFIG_COSA is not set
# CONFIG_RCPCI is not set
#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set
#
# IrDA subsystem support
#
# CONFIG_IRDA is not set
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
CONFIG_SERIAL_EXTENDED=y
# CONFIG_SERIAL_MANY_PORTS is not set
CONFIG_SERIAL_SHARE_IRQ=y
# CONFIG_SERIAL_DETECT_IRQ is not set
# CONFIG_SERIAL_MULTIPORT is not set
# CONFIG_HUB6 is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_MOUSE=y
#
# Mice
#
CONFIG_ATIXL_BUSMOUSE=m
CONFIG_BUSMOUSE=m
CONFIG_MS_BUSMOUSE=m
CONFIG_PSMOUSE=y
CONFIG_82C710_MOUSE=m
CONFIG_PC110_PAD=m
# CONFIG_QIC02_TAPE is not set
CONFIG_WATCHDOG=y
#
# Watchdog Cards
#
# CONFIG_WATCHDOG_NOWAYOUT is not set
CONFIG_WDT=m
# CONFIG_WDT_501 is not set
CONFIG_SOFT_WATCHDOG=m
CONFIG_PCWATCHDOG=m
CONFIG_ACQUIRE_WDT=m
CONFIG_NVRAM=m
CONFIG_RTC=y
#
# Video For Linux
#
# CONFIG_VIDEO_DEV is not set
#
# Joystick support
#
# CONFIG_JOYSTICK is not set
CONFIG_DTLK=m
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_FT_NORMAL_DEBUG=y
# CONFIG_FT_FULL_DEBUG is not set
# CONFIG_FT_NO_TRACE is not set
# CONFIG_FT_NO_TRACE_AT_ALL is not set
CONFIG_FT_STD_FDC=y
# CONFIG_FT_MACH2 is not set
# CONFIG_FT_PROBE_FC10 is not set
# CONFIG_FT_ALT_FDC is not set
#
# Filesystems
#
# CONFIG_QUOTA is not set
CONFIG_AUTOFS_FS=m
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_UMSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_MINIX_FS is not set
CONFIG_NTFS_FS=m
CONFIG_NTFS_RW=y
CONFIG_HPFS_FS=m
CONFIG_PROC_FS=y
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
CONFIG_ROMFS_FS=m
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
CONFIG_UFS_FS=m
CONFIG_UFS_FS_WRITE=y
#
# Network File Systems
#
# CONFIG_CODA_FS is not set
CONFIG_NFS_FS=m
CONFIG_NFSD=m
CONFIG_NFSD_SUN=y
CONFIG_SUNRPC=m
CONFIG_LOCKD=m
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
#
# Partition Types
#
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MAC_PARTITION is not set
# CONFIG_SMD_DISKLABEL is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
CONFIG_NLS=y
#
# Native Language Support
#
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
CONFIG_MDA_CONSOLE=m
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
# CONFIG_FB_PM2 is not set
# CONFIG_FB_VESA is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_MATROX is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FBCON_ADVANCED is not set
# CONFIG_FBCON_FONTWIDTH8_ONLY is not set
# CONFIG_FBCON_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Sound
#
CONFIG_SOUND=m
CONFIG_SOUND_ES1370=m
CONFIG_SOUND_ES1371=m
CONFIG_SOUND_SONICVIBES=m
CONFIG_SOUND_MSNDCLAS=m
# CONFIG_MSNDCLAS_HAVE_BOOT is not set
CONFIG_MSNDCLAS_INIT_FILE="/etc/sound/msndinit.bin"
CONFIG_MSNDCLAS_PERM_FILE="/etc/sound/msndperm.bin"
CONFIG_SOUND_MSNDPIN=m
# CONFIG_MSNDPIN_HAVE_BOOT is not set
CONFIG_MSNDPIN_INIT_FILE="/etc/sound/pndspini.bin"
CONFIG_MSNDPIN_PERM_FILE="/etc/sound/pndsperm.bin"
CONFIG_SOUND_OSS=m
CONFIG_SOUND_PAS=m
CONFIG_SOUND_SB=m
CONFIG_SOUND_ADLIB=m
CONFIG_SOUND_GUS=m
CONFIG_GUS16=y
CONFIG_GUSMAX=y
CONFIG_SOUND_MPU401=m
CONFIG_SOUND_PSS=m
# CONFIG_PSS_MIXER is not set
CONFIG_SOUND_MSS=m
CONFIG_SOUND_SSCAPE=m
CONFIG_SOUND_TRIX=m
CONFIG_SOUND_MAD16=m
CONFIG_MAD16_OLDCARD=y
CONFIG_SOUND_WAVEFRONT=m
CONFIG_SOUND_CS4232=m
CONFIG_SOUND_OPL3SA2=m
CONFIG_SOUND_MAUI=m
CONFIG_SOUND_SGALAXY=m
CONFIG_SOUND_AD1816=m
CONFIG_SOUND_OPL3SA1=m
CONFIG_SOUND_SOFTOSS=m
CONFIG_SOUND_YM3812=m
CONFIG_SOUND_VMIDI=m
CONFIG_SOUND_UART6850=m
#
# Additional low level sound drivers
#
CONFIG_LOWLEVEL_SOUND=y
CONFIG_ACI_MIXER=m
CONFIG_AWE32_SYNTH=m
CONFIG_AEDSP16=m
CONFIG_AEDSP16_BASE=220
CONFIG_MPU_BASE=330
#
# SC-6600 Audio Cards have no jumper switches at all
#
CONFIG_SC6600=y
#
# SC-6600 specific configuration
#
CONFIG_SC6600_JOY=y
CONFIG_SC6600_CDROM=4
CONFIG_SC6600_CDROMBASE=0
CONFIG_AEDSP16_SBPRO=y
#
# Audio Excel DSP 16 [Sound Blaster Pro]
#
CONFIG_AEDSP16_BASE=220
CONFIG_AEDSP16_SB_IRQ=5
CONFIG_AEDSP16_SB_DMA=0
CONFIG_AEDSP16_MPU401=y
#
# Audio Excel DSP 16 [MPU-401]
#
CONFIG_AEDSP16_MPU_IRQ=5
#
# Kernel hacking
#
CONFIG_MAGIC_SYSRQ=y
------------------------------
From: NEWS <[EMAIL PROTECTED]>
Subject: kernel error messages
Date: 27 May 1999 09:32 GMT
Hi,
I am getting a strange error from the kernel (hostname kernel: khm).
Does anyone know what that means, or where I can find a document
explaining kernel error messages?
thanks a lot,
Stefano
--
Stefano Ghirlanda, Zoologiska Institutionen, Stockholms Universitet
Office: D554, Arrheniusv. 14, S-106 91 Stockholm, Sweden
Phone: +46 8 164055, Fax: +46 8 167715, Email: [EMAIL PROTECTED]
------------------------------
From: NEWS <[EMAIL PROTECTED]>
Subject: Re: SCSI error (aic7xxx.c
Date: 27 May 1999 02:47 GMT
On 25 May 1999 09:06:43 GMT,
Takashi Ichihara <[EMAIL PROTECTED]> wrote:
> Hi
>
> We have installed 8 nodes of Linux cluster and frequently
>encountered with SCSI errors for 4 nodes. So far we have tested
>following 3 sets of kernels and SCSI drivers. In all case, we
>have encountered the similar errors.
>
> Linux 2.0.36 (aic7xxx.c version 5.1.2)
> Linux 2.2.4 (aic7xxx.c version 5.1.10)
> Linux 2.2.7-ac1 (aic7xxx.c version 5.1.13)
>
>A sample error log is attached in this text. Following is our
>configuration information.
>
> Motherboard: ASUS P2B-DS
> CPU/memory Dual Pentium II 450 MHz, 256 MB Memory
> SCSI Adapter: Adaptec AIC-7890/1 Ultra2 SCSI host adapter
> SCSI Disk: SEAGATE Model: ST39173LW
> Linux kernel: linux-2.2.4 and Linux 2.2.7-ac1
> SCSI driver : aic7xxx.c version 5.1.10 and 5.1.13(by Alan's patch)
>
> Does anyone know how to fix this problem ? Is there any newer
>drivers for aic7xxx.c ? Thanks for the information.
Hey, I dont think this is in the aic7xxx.c, I think its higher up, maybe
in the scsi disk code. Maybe. This is a guess. I was having similar
odd problems with a cdrom on my one scsi chain. My system spec's are
similar:
Motherboard: ASUS P2B-LS
CPU/Memory: Pentium II 400 Mhz, 256 MB Memory
SCSI Adapter: Adaptec AIC-7890/1 Ultra2 SCSI host adapter
SCSI Disk: SEAGATE Model: Cheetah 9LP
Linux Kernel: 2.2.9
Anyways, here's my suggestion. Recompile the kernel and turn off
' Probe all LUNs on each SCSI device ' in the kernel config.
It solved my SCB timeout problem with my Sony CD-R.
Good luck,
--
Mental
When I grow up, I wanna be more like me.
I had a clue. I didn't like it. I took it back and exchanged it for an
attitude.
_______________________________________________________________________
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
------------------------------
From: NEWS <[EMAIL PROTECTED]>
Subject: Re: [rxvt] numeric keyboa
Date: 27 May 1999 14:17 GMT
In message <[EMAIL PROTECTED]>,
Bernhard Dobbels wrote:
>
> i'm using rxvt in X (xfree/fvwm2) on linux and when i start-up a
> terminal, i can't use the numeric keys on my keyboard (it beeps),
> even non the /*-+ on that part of the keyboard.
> If i do the command reset (=tset), the rxvt gets resetted or so and
> i can use the numeric keys. What is changed and how can i do this
> automaticaly when i open a terminal?
I assume that rxvt is emulating a DEC VT100.
Please keep in mind that the numeric keypad in a DEC terminal has 2
different modes: numeric and application. The application mode
generates specified Escape sequences (and seems to be the default);
the numeric mode makes digits. Your Linux machine's terminfo entry
(for whatever terminal type you have specified) must have a "reset"
sequence that sets numeric mode.
This sort of thing is discussed in the "DEC keyboards" and "using
terminals with Unix" links from
http://www.cs.utk.edu/~shuford/terminal_index.html
The O'Reilly book "termcap and terminfo" (by John Strang, Linda Mui,
and Tim O'Reilly, 0-937175-22-6) discusses these concepts in depth.
http://www.ora.com/catalog/term/noframes.html
...Richard S. Shuford
Stratus Computer
Maynard, Massachusetts
--
Stratus Computer http://www.stratus.com/
Redundant-hardware fault-tolerant computer systems running VOS or HP-UX.
The above opinions are not those of Stratus.
------------------------------
From: NEWS <[EMAIL PROTECTED]>
Subject: Re: Iomega products and L
Date: 26 May 1999 23:17 GMT
Hi Sylvia,
I believe the support I had from the Iomega Linux users had some
impact to fix my problem with Iomega. When I called them back after
I sent my message all over the net, the technician knew I was the
Linux guy just as I mentioned my name :-).
Anyway I was at friend place and had the unit installed on his
machine running Dos. The technician had us do very simple test ---
nothing more then what I had done under Linux. He immediately offered to
replace the unit.
Next time I am buying hardware for my computers, I will make sure
that the companies do not have that attitude toward Linux users.
They won't force me into an OS I do not want.
Thanks for your support,
Dominic.
>>>>> "sw" == Sylvia Wong <[EMAIL PROTECTED]> writes:
sw> On 24 May 1999 22:04:09 -0400, Dominic Mitchell <[EMAIL PROTECTED]> wrote:
>> to Iomega ([EMAIL PROTECTED]) that if this is the policy
>> they want to adopt then the Linux community will have to consider
>> products from a friendlier company.
sw> I totally agreed with you. I recently bought a zip drive. I knew at that
sw> time that they're supported under linux (we've them at uni). I read the
sw> manual and was suprised that other minority OSes are supported (incl os/2
sw> and mac) but not linux, not even any unixes. I rang the company to tell
sw> them that this is not good enough and the only respond I get is "we do not
sw> support unix". I now wonder what would happen if the drive failed while
sw> it's still under warranty.
sw> --
sw> Auckland research student, an endangered species.
sw> [EMAIL PROTECTED]
sw> http://linux.ele.auckland.ac.nz/~swon074
--
==============================================================
Dominic Mitchell Email: [EMAIL PROTECTED]
Department of Economics mailto:[EMAIL PROTECTED]
Queen's University
Kingston, Ontario
Canada, K7L 3N6 Running Linux Redhat 5.2
==============================================================
------------------------------
From: NEWS <[EMAIL PROTECTED]>
Subject: Re: ls colors... not reco
Date: 27 May 1999 02:47 GMT
On Tue, 25 May 1999 09:10:01 -0500, Daniel Beckham <[EMAIL PROTECTED]> wrote:
<comment snipped>
>> John Strange <[EMAIL PROTECTED]> wrote in message
>> news:7icgfp$ppa$[EMAIL PROTECTED]...
>> > I added
>> >
>> > alias ls="ls --color=tty"
>> > to /etc/bashrc
>>
>> Oh, you mean such that other users, who don't want that color trash, have to
<more crap snipped>
Ok, here's the deal. You want neat ls colors. This is how I did it, I
think there's also a howto but I'm not into reading directions. :)
Firstly, you need to decide no what colors you want to use for what
files. Its been ages since I've looked at ansi's and I forget most
of the color combos. Do a websearch, you'll find it. Fortunately most
distro's come with a default set of colors.
Try running 'dircolors -p', hopefully you'll get output like this:
_______________________________________________________________________
# Configuration file for dircolors, a utility to help you set the
# LS_COLORS environment variable used by GNU ls with the --color option.
# The keywords COLOR, OPTIONS, and EIGHTBIT (honored by the
# slackware version of dircolors) are recognized but ignored.
# Below, there should be one TERM entry for each termtype that is colorizable
TERM linux
TERM console
TERM con132x25
TERM con132x30
TERM con132x43
TERM con132x60
TERM con80x25
TERM con80x28
TERM con80x30
TERM con80x43
TERM con80x50
TERM con80x60
TERM xterm
TERM vt100
# Below are the color init strings for the basic file types. A color init
# string consists of one or more of the following numeric codes:
# Attribute codes:
# 00=none 01=bold 04=underscore 05=blink 07=reverse 08=concealed
# Text color codes:
# 30=black 31=red 32=green 33=yellow 34=blue 35=magenta 36=cyan 37=white
# Background color codes:
# 40=black 41=red 42=green 43=yellow 44=blue 45=magenta 46=cyan 47=white
NORMAL 00 # global default, although everything should be something.
FILE 00 # normal file
DIR 01;34 # directory
LINK 01;36 # symbolic link
FIFO 40;33 # pipe
SOCK 01;35 # socket
BLK 40;33;01 # block device driver
CHR 40;33;01 # character device driver
ORPHAN 40;31;01 # symlink to nonexistent file
# This is for files with execute permission:
EXEC 01;32
# List any file extensions like '.gz' or '.tar' that you would like ls
# to colorize below. Put the extension, a space, and the color init string.
# (and any comments you want to add after a '#')
# If you use DOS-style suffixes, you may want to uncomment the following:
#.cmd 01;32 # executables (bright green)
#.exe 01;32
#.com 01;32
#.btm 01;32
#.bat 01;32
..tar 01;31 # archives or compressed (bright red)
..tgz 01;31
..arj 01;31
..taz 01;31
..lzh 01;31
..zip 01;31
..z 01;31
..Z 01;31
..gz 01;31
..deb 01;31
..jpg 01;35 # image formats
..gif 01;35
..bmp 01;35
..ppm 01;35
..tga 01;35
..xbm 01;35
..xpm 01;35
..tif 01;35
..mpg 01;37
..avi 01;37
..gl 01;37
..dl 01;37
________________________________________________________________________
Ok, lets make this less painful. Redirect the output of "dircolors -p"
to a file (I hide mine) in your homedir. This way you can edit it and
make it 'neat' (Anyone know any blinking ansi codes I could use for
mp3's?).
Do this:
dircolors -p > ~/.colourrc
Now edit your .profile or .bashrc or whatever and add these lines:
alias ls="ls --color"
eval `dircolors $HOME/.colourrc`
And you're done. The manpages for dircolors and ls are good starting
points. As to observations about whats good practice and not good
practice to do from an administrative perspective, it will become
evident in time. Most linux users are on 'single user' systems and
tend to not think as an admin would who had to keep many users happy.
Which is right or wrong depends on the situation. There are no hard
and fast rules.
I hope this helps.
--
Mental
When I grow up, I wanna be more like me.
I had a clue. I didn't like it. I took it back and exchanged it for an
attitude.
_______________________________________________________________________
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
------------------------------
From: NEWS <[EMAIL PROTECTED]>
Subject: Re: RH6, Gnome & RealPlay
Date: 27 May 1999 01:02 GMT
Tim Ryan at [EMAIL PROTECTED] says...
> Gnome uses esd for all sound. This is the Enlightenment Sound Daemon
> and it does take over /dev/dsp completely. To use a program that
> uses /dev/dsp use the esddsp wrapper. This redirects /dev/dsp through
> esd. The only time I have trouble with this is when the libc versions
> don't match.
Ahh, thank you. I was determined to figure out the strange
weirdness with the sound device in my RH6.0 boxen. I stumbled
around a little, but your post helped alot. Here's some info:
The esp demon is used with Enlightnment, here is where you can find
some info on it in your dist:
/usr/doc/esound-0.2.12
and here on the web:
http://www.tux.org/~ricdude/EsounD.html
With my system, when I shutdown X to go to command line, I couldn't
figure out why my /dev/dsp was always busy. Apparently, the esd
doesn't let go, even after Gnome/E is shutdown. I think this is a
bug err feature, something. :)
Anyway, it's easy to kill, the user owns the process. If you want
to use a sound program in Gnome/E and they don't recognize the esd,
then you have to user the wrapper, which is "esddsp".
How, it's easy, like :
esddsp ./lxdoom
This would start lxdoom from an xterm. It works, but here's the
catch: The wrapper introduces a ton of lag to games, about 1-2
seconds on my ole P133, which is not good. At least Doom works,
Quake2 just says something like "Your soundcard can't do that" and
disables sound.
The lag shouldn't be a problem if you just want to play a sound file
or something, though.
I just read a post mentioning about a newer version of Gnome/E not
hogging the /dev/dsp so much. I'll check that out and see if things
can be improved.
--
Douglas Bollinger
Mt. Holly Springs, PA 17065
My other computer runs Linux.
------------------------------
From: NEWS <[EMAIL PROTECTED]>
Subject: Re: Warning! [object] may
Date: 27 May 1999 16:17 GMT
Followups set to comp.lang.c++ for topicality.
Dragos STOICHITA <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hi,
Greetings.
> I am compiling KDE 1.1.1 on a HPPA 1.1 platform running HPUX.
> I know I am posting in a linux forum, but I also have linux at home,
> and I think my problem is related to the compiler, and not to the
> platform.
That's right. Related more to C++, even.
> The compilation finishes successfully, but GCC outputs at a ton of
> warnings, of the same type. For nearly every line in the source it says:
>
> Warning! [object] may be crobbled by longjmp or vfork
>
> I have been looking for the explanation in the info page and on the net
> at least for 4 hours, but I didn't find anything.
If longjmp or setjmp are used in a C++ program,
the result is very likely to be that some destructors
are not run against objects that were constructed
in stack frames that longjmp strips back, and that
destructors are run against pseudo-objects that
were not constructed (or which have already been
destructed) in the stack frame containing the
setjmp call. This latter possiblity best fits the
"object may be crobbled" warning.
All things considered, setjmp/longjmp should
really not appear in C++ programs except when
used by the most disciplined programmers who
know C++ well but are still willing to write long
stretches of strictly C code in the region between
the setjmp and longjmp. (Those are rare folks.)
The fix is to either get rid of the setjmp/longjmp
calls, or compile the code as C.
--
--
Larry Brasfield
Above opinions may be mine alone.
(Humans may reply at unundered [EMAIL PROTECTED] )
------------------------------
From: "D. Vrabel" <[EMAIL PROTECTED]>
Subject: Re: 3 buttom mouse emulation
Date: Sat, 29 May 1999 13:08:52 +0100
On 28 May 1999 krishan.purahoo@#jet.uk wrote:
> Hi,
> How do I configure my 2 button mouse to emulate a 3 button mouse. Using
> the mouseconfig utility in slackware 4.0 there is no option to let me
> do that (the mouseconfig utility in redhat does have that option). I am
> using the KDE desktop - Can I set this within KDE?
If it's more the console using gpm read the gpm man pages. You'll have to
edit a config. file.
For X use XF86Setup (run from console as root). Or read the XF86Config man
page for the required setting.
David
--
David Vrabel
Engineering Undergraduate at University of Cambridge, UK.
------------------------------
From: NEWS <[EMAIL PROTECTED]>
Subject: Application/PDF in Netsca
Date: 27 May 1999 19:32 GMT
I downloaded and installed Acrobat4 and set it as an
application to Netscape4.51. When I call a pdf file
the acroread comes up but it cannot find the downloaded
pdf file. If I search the cache directory and find it
in a subdirectory there the I can read it fine.
How could I do this automatically?
-TIA
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.misc) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Misc Digest
******************************
