Linux-Misc Digest #42, Volume #27 Tue, 6 Feb 01 18:13:02 EST
Contents:
Re: Stumped by random X freezes,slow system (Chet Vora)
Re: Lilo (Sven Heinecke)
Re: mounting bloc device (Mark Bratcher)
Re: Where to find a RH 7.1 beta CD? (milanuk)
Re: Cloning Linux Drives (* Tong *)
Re: Not using Lilo with Mandrake 7.2 (Chris Gordon-Smith)
Re: From an ex Microsoft devotee ("pascal gauthier")
Re: Question about Zsh (Bruce Stephens)
Re: SB Live! Software and Redhat 7 (.)
----------------------------------------------------------------------------
From: Chet Vora <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x,comp.os.linux.setup
Subject: Re: Stumped by random X freezes,slow system
Date: Tue, 06 Feb 2001 17:07:27 -0500
This is a multi-part message in MIME format.
==============AC0BA371238EF24EED5670F0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Oops...forgot the XF86Config.
Chet Vora wrote:
> Hi,
>
> I recently installed RH6.2 on a HP Kayak XA workstation which used to host a
> Win9X system before(removed). After having lots of problems with the display
> (because of incorrect resolution settings) and the mouse (cursor would position
> itself on the LH corner and not move from there. Cured by choosing the right
> driver for it), I was able to get XFree86 running on it. But I've been
> experiencing sudden random freezes while in Gnome. Also, things seem to be very
> slow, though that observation might also hold true when in console mode (without
> X). There doesn't seem to be any pattern to the freezes. The one thing worth
> mentioning is that the system seems to be using the SCSI driver for the PCI bus.
>
> Relevant o/p of dmesg:
> -------------------------
> VFS: Mounted root (ext2 filesystem).
> ncr53c8xx: at PCI bus 2, device 0, function 0
> ncr53c8xx: 53c875 detected with Symbios NVRAM
> ncr53c875-0: rev=0x04, base=0xfbfff800, io_port=0xe800, irq=10
> ncr53c875-0: Symbios format NVRAM, ID 7, Fast-20, Parity Checking
> ncr53c875-0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 05/4e/80/01/00/24
> ncr53c875-0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 05/46/a0/00/08/24
> ncr53c875-0: on-chip RAM at 0xfbffe000
> ncr53c875-0: resetting, command processing suspended for 2 seconds
> ncr53c875-0: restart (scsi reset).
> ncr53c875-0: enabling clock multiplier
> ncr53c875-0: Downloading SCSI SCRIPTS.
> scsi0 : ncr53c8xx - version 3.2a-2
> scsi : 1 host.
>
> I am also attaching the XF86Config file.
>
> Would appreciate any help.
>
> TIA,
> Chet
==============AC0BA371238EF24EED5670F0
Content-Type: text/plain; charset=us-ascii;
name="XF86Config.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="XF86Config.txt"
# File generated by XConfigurator.
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
FontPath "/usr/X11R6/lib/X11/fonts/TrueType"
FontPath "unix/:-1"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
#NoTrapSignals
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
#DontZap
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
#DontZoom
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Keyboard section
# **********************************************************************
Section "Keyboard"
Protocol "Standard"
# when using XQUEUE, comment out the above line, and uncomment the
# following line
#Protocol "Xqueue"
AutoRepeat 500 5
# Let the server do the NumLock processing. This should only be
# required when using pre-R6 clients
#ServerNumLock
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#Xleds 1 2 3
#To set the LeftAlt to Meta, RightAlt key to ModeShift,
#RightCtl key to Compose, and ScrollLock key to ModeLock:
LeftAlt Meta
RightAlt Meta
ScrollLock Compose
RightCtl Control
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# XkbDisable
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# XkbModel "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# XkbModel "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# XkbLayout "de"
# or:
# XkbLayout "de"
# XkbVariant "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# XkbOptions "ctrl:swapcaps"
# These are the default XKB settings for XFree86
# XkbRules "xfree86"
# XkbModel "pc101"
# XkbLayout "us"
# XkbVariant ""
# XkbOptions ""
XkbKeycodes "xfree86"
XkbTypes "default"
XkbCompat "default"
XkbSymbols "us(pc101)"
XkbGeometry "pc"
XkbRules "xfree86"
XkbModel "pc101"
XkbLayout "us"
EndSection
# **********************************************************************
# Pointer section
# **********************************************************************
Section "Pointer"
Protocol "IMPS/2"
Device "/dev/mouse"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Protocol "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice
# BaudRate 9600
# SampleRate 150
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Emulate3Buttons
# Emulate3Timeout 50
ZAxisMapping 4 5
Buttons 3
# ChordMiddle is an option for some 3-button Logitech mice
# ChordMiddle
EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "Hitachi CM1711M"
VendorName "Unknown"
ModelName "Unknown"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 24.8-82.0
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50.0-120.0
# Modes can be specified in two formats. A compact one-line format, or
# a multi-line format.
# These two are equivalent
# ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Interlace
# Mode "1024x768i"
# DotClock 45
# HTimings 1024 1048 1208 1264
# VTimings 768 776 784 817
# Flags "Interlace"
# EndMode
# This is a set of standard mode timings. Modes that are out of monitor spec
# are automatically deleted by the server (provided the HorizSync and
# VertRefresh lines are correct), so there's no immediate need to
# delete mode timings (unless particular mode timings don't work on your
# monitor). With these modes, the best standard mode that your monitor
# and video card can support for a given resolution is automatically
# used.
# 640x400 @ 70 Hz, 31.5 kHz hsync
Modeline "640x400" 25.175 640 664 760 800 400 409 411 450
# 640x480 @ 60 Hz, 31.5 kHz hsync
Modeline "640x480" 25.175 640 664 760 800 480 491 493 525
# 800x600 @ 56 Hz, 35.15 kHz hsync
ModeLine "800x600" 36 800 824 896 1024 600 601 603 625
# 1024x768 @ 87 Hz interlaced, 35.5 kHz hsync
Modeline "1024x768" 44.9 1024 1048 1208 1264 768 776 784 817 Interlace
# 640x400 @ 85 Hz, 37.86 kHz hsync
Modeline "640x400" 31.5 640 672 736 832 400 401 404 445 -HSync +VSync
# 640x480 @ 72 Hz, 36.5 kHz hsync
Modeline "640x480" 31.5 640 680 720 864 480 488 491 521
# 640x480 @ 75 Hz, 37.50 kHz hsync
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -HSync -VSync
# 800x600 @ 60 Hz, 37.8 kHz hsync
Modeline "800x600" 40 800 840 968 1056 600 601 605 628 +hsync +vsync
# 640x480 @ 85 Hz, 43.27 kHz hsync
Modeline "640x480" 36 640 696 752 832 480 481 484 509 -HSync -VSync
# 1152x864 @ 89 Hz interlaced, 44 kHz hsync
ModeLine "1152x864" 65 1152 1168 1384 1480 864 865 875 985 Interlace
# 800x600 @ 72 Hz, 48.0 kHz hsync
Modeline "800x600" 50 800 856 976 1040 600 637 643 666 +hsync +vsync
# 1024x768 @ 60 Hz, 48.4 kHz hsync
Modeline "1024x768" 65 1024 1032 1176 1344 768 771 777 806 -hsync -vsync
# 640x480 @ 100 Hz, 53.01 kHz hsync
Modeline "640x480" 45.8 640 672 768 864 480 488 494 530 -HSync -VSync
# 1152x864 @ 60 Hz, 53.5 kHz hsync
Modeline "1152x864" 89.9 1152 1216 1472 1680 864 868 876 892 -HSync -VSync
# 800x600 @ 85 Hz, 55.84 kHz hsync
Modeline "800x600" 60.75 800 864 928 1088 600 616 621 657 -HSync -VSync
# 1024x768 @ 70 Hz, 56.5 kHz hsync
Modeline "1024x768" 75 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
# 1280x1024 @ 87 Hz interlaced, 51 kHz hsync
Modeline "1280x1024" 80 1280 1296 1512 1568 1024 1025 1037 1165 Interlace
# 800x600 @ 100 Hz, 64.02 kHz hsync
Modeline "800x600" 69.65 800 864 928 1088 600 604 610 640 -HSync -VSync
# 1024x768 @ 76 Hz, 62.5 kHz hsync
Modeline "1024x768" 85 1024 1032 1152 1360 768 784 787 823
# 1152x864 @ 70 Hz, 62.4 kHz hsync
Modeline "1152x864" 92 1152 1208 1368 1474 864 865 875 895
# 1280x1024 @ 61 Hz, 64.2 kHz hsync
Modeline "1280x1024" 110 1280 1328 1512 1712 1024 1025 1028 1054
# 1024x768 @ 85 Hz, 70.24 kHz hsync
Modeline "1024x768" 98.9 1024 1056 1216 1408 768 782 788 822 -HSync -VSync
# 1152x864 @ 78 Hz, 70.8 kHz hsync
Modeline "1152x864" 110 1152 1240 1324 1552 864 864 876 908
# 1280x1024 @ 70 Hz, 74.59 kHz hsync
Modeline "1280x1024" 126.5 1280 1312 1472 1696 1024 1032 1040 1068 -HSync -VSync
# 1600x1200 @ 60Hz, 75.00 kHz hsync
Modeline "1600x1200" 162 1600 1664 1856 2160 1200 1201 1204 1250 +HSync +VSync
# 1152x864 @ 84 Hz, 76.0 kHz hsync
Modeline "1152x864" 135 1152 1464 1592 1776 864 864 876 908
# 1280x1024 @ 74 Hz, 78.85 kHz hsync
Modeline "1280x1024" 135 1280 1312 1456 1712 1024 1027 1030 1064
# 1024x768 @ 100Hz, 80.21 kHz hsync
Modeline "1024x768" 115.5 1024 1056 1248 1440 768 771 781 802 -HSync -VSync
# 1280x1024 @ 76 Hz, 81.13 kHz hsync
Modeline "1280x1024" 135 1280 1312 1416 1664 1024 1027 1030 1064
# 1600x1200 @ 70 Hz, 87.50 kHz hsync
Modeline "1600x1200" 189 1600 1664 1856 2160 1200 1201 1204 1250 -HSync -VSync
# 1152x864 @ 100 Hz, 89.62 kHz hsync
Modeline "1152x864" 137.65 1152 1184 1312 1536 864 866 885 902 -HSync -VSync
# 1280x1024 @ 85 Hz, 91.15 kHz hsync
Modeline "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +HSync +VSync
# 1600x1200 @ 75 Hz, 93.75 kHz hsync
Modeline "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +HSync +VSync
# 1600x1200 @ 85 Hz, 105.77 kHz hsync
Modeline "1600x1200" 220 1600 1616 1808 2080 1200 1204 1207 1244 +HSync +VSync
# 1280x1024 @ 100 Hz, 107.16 kHz hsync
Modeline "1280x1024" 181.75 1280 1312 1440 1696 1024 1031 1046 1072 -HSync -VSync
# 1800x1440 @ 64Hz, 96.15 kHz hsync
ModeLine "1800X1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
# 1800x1440 @ 70Hz, 104.52 kHz hsync
ModeLine "1800X1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
# 512x384 @ 78 Hz, 31.50 kHz hsync
Modeline "512x384" 20.160 512 528 592 640 384 385 388 404 -HSync -VSync
# 512x384 @ 85 Hz, 34.38 kHz hsync
Modeline "512x384" 22 512 528 592 640 384 385 388 404 -HSync -VSync
# Low-res Doublescan modes
# If your chipset does not support doublescan, you get a 'squashed'
# resolution like 320x400.
# 320x200 @ 70 Hz, 31.5 kHz hsync, 8:5 aspect ratio
Modeline "320x200" 12.588 320 336 384 400 200 204 205 225 Doublescan
# 320x240 @ 60 Hz, 31.5 kHz hsync, 4:3 aspect ratio
Modeline "320x240" 12.588 320 336 384 400 240 245 246 262 Doublescan
# 320x240 @ 72 Hz, 36.5 kHz hsync
Modeline "320x240" 15.750 320 336 384 400 240 244 246 262 Doublescan
# 400x300 @ 56 Hz, 35.2 kHz hsync, 4:3 aspect ratio
ModeLine "400x300" 18 400 416 448 512 300 301 302 312 Doublescan
# 400x300 @ 60 Hz, 37.8 kHz hsync
Modeline "400x300" 20 400 416 480 528 300 301 303 314 Doublescan
# 400x300 @ 72 Hz, 48.0 kHz hsync
Modeline "400x300" 25 400 424 488 520 300 319 322 333 Doublescan
# 480x300 @ 56 Hz, 35.2 kHz hsync, 8:5 aspect ratio
ModeLine "480x300" 21.656 480 496 536 616 300 301 302 312 Doublescan
# 480x300 @ 60 Hz, 37.8 kHz hsync
Modeline "480x300" 23.890 480 496 576 632 300 301 303 314 Doublescan
# 480x300 @ 63 Hz, 39.6 kHz hsync
Modeline "480x300" 25 480 496 576 632 300 301 303 314 Doublescan
# 480x300 @ 72 Hz, 48.0 kHz hsync
Modeline "480x300" 29.952 480 504 584 624 300 319 322 333 Doublescan
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
Section "Device"
Identifier "Generic VGA"
VendorName "Unknown"
BoardName "Unknown"
Chipset "generic"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by Xconfigurator:
Section "Device"
Identifier "Cirrus Logic|GD 5465 [Laguna]"
VendorName "Unknown"
BoardName "Unknown"
#VideoRam 4096
#Option "fifo_conservative"
# Use Option "no_bitblt" if you have graphics problems. If that fails
# try Option "noaccel".
# Refer to /usr/X11R6/lib/doc/README.cirrus.
# To allow linear addressing, uncomment the Option line and the
# address that the card maps the framebuffer to.
# Insert Clocks lines here if appropriate
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# The Colour SVGA server
Section "Screen"
Driver "svga"
# Use Device "Generic VGA" for Standard VGA 320x200x256
#Device "Generic VGA"
Device "Cirrus Logic|GD 5465 [Laguna]"
Monitor "Hitachi CM1711M"
Subsection "Display"
Depth 32
Modes "1024x768"
ViewPort 0 0
EndSubsection
EndSection
# The 16-color VGA server
Section "Screen"
Driver "vga16"
Device "Generic VGA"
Monitor "Hitachi CM1711M"
Subsection "Display"
Modes "640x480" "800x600"
ViewPort 0 0
EndSubsection
EndSection
# The Mono server
Section "Screen"
Driver "vga2"
Device "Generic VGA"
Monitor "Hitachi CM1711M"
Subsection "Display"
Modes "640x480" "800x600"
ViewPort 0 0
EndSubsection
EndSection
# The accelerated servers (S3, Mach32, Mach8, 8514, P9000, AGX, W32, Mach64
# I128, and S3V)
Section "Screen"
Driver "accel"
Device "Cirrus Logic|GD 5465 [Laguna]"
Monitor "Hitachi CM1711M"
Subsection "Display"
Depth 32
Modes "1024x768"
ViewPort 0 0
EndSubsection
EndSection
==============AC0BA371238EF24EED5670F0==
------------------------------
From: Sven Heinecke <[EMAIL PROTECTED]>
Subject: Re: Lilo
Date: 6 Feb 2001 22:21:12 GMT
Neil West <[EMAIL PROTECTED]> wrote:
> When trying to run lilo -v -t I get the error "device 0x0304 exceeds 1024
> cylinder limit". After running the "df" command I get the following output:
>
> Filesystem 1k-blocks Used Available Use% Mounted on
> /dev/hda5 3534096 1672048 1682524 50% /
> /dev/hda2 15554 2464 12287 17% /boot
> /dev/hda6 3534096 1779860 1574712 54% /home
> /dev/fd0 1412 1084 256 81% /mnt/floppy
>
>
> The /boot partition is clearly under the 16 meg limit. My theory is that
> because it does not occurr first on the drive, it crosses over the 1024
> cylinder limit.
I think lilo v. 21.4.4. works if /boot is over cylinder 1024. Have a
look at http://judi.greens.org/lilo/
so far
Sven
------------------------------
From: [EMAIL PROTECTED] (Mark Bratcher)
Subject: Re: mounting bloc device
Date: Tue, 06 Feb 2001 22:22:35 GMT
In article <95pqnh$abf$[EMAIL PROTECTED]>, Fr�d�ric Hoerni wrote:
>is it possible to mount /dev/sga (cd writer) which is in bloc mode, as a
>filesystem ?
>i get an error.
>thanks
>
Yes, it's possible.
What format is the CD? Is it a "normal" data CD (like a program disk),
or is it a music CD?
What is the error message?
Is your CD-RW drive SCSI or IDE?
--
Mark Bratcher
To reply, remove both underscores (_) from my email address
===========================================================
Escape from Microsoft's proprietary tentacles: use Linux!
------------------------------
From: milanuk <[EMAIL PROTECTED]>
Subject: Re: Where to find a RH 7.1 beta CD?
Date: Tue, 06 Feb 2001 22:31:28 GMT
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
>
> Thanks for the reply, but LSL *just today* put up a 7.1 RH beta CD
> for US$3.78 (it wasn't there yesterday when I looked)
>
Well, you have my sincere apologies. And condolences. ;) Good luck w/
the Fisher beta. Someday, when I get my LAN nailed down the way I
want, I may w/ a RH beta, but at this rate, it'll be about 9.2 or so :)
Monte
--
There are basically three kinds of men. There
are the ones who learn by reading. Then there are
the few who learn by observation. The rest just
have to pee on the electric fence for themselves.
Sent via Deja.com
http://www.deja.com/
------------------------------
From: * Tong * <[EMAIL PROTECTED]>
Subject: Re: Cloning Linux Drives
Date: 06 Feb 2001 18:44:31 -0400
"OpenMind" <**Mail Free America**> writes:
> Naturally, my 1000 page Linux book does not appear to mention a solution
> anywhere in the index. :-)
>
> I'm bringing up a number of identical systems... the only difference MIGHT
> be size of the hard drive.
[...]
I just hope that Linux newbies won't be treated so badly in the future:
> cp /dev/hda dev/hdb
Apart from that this one line reply didn't help too much, it is just
not right!
I know sometimes people want to show off that how simple it is to do
things in *nix world, but this simple cp just can't do a good
job. People ask questions here are serious about their questions and
are hoping to get serious answers. If you want to illustrate the
using of the "cp", at least you should use the flag -dpR.
I'm also a Linux newbie, my knowledge ends here. But I want to give
what I know in a helpful way. The moral is that I wish that people
can give the answer really helps, and better yet, be complete. So
that when the similar question show up again in this NG, people can
refer to your complete answer via deja-news url.
To make the knowledge complete regarding this problem, mkkickstart
is an option (which is my first choice), and dd is another. But the
problem of dd is that fragmented file get duplicated into fragmented
file, from generation to generation, and get more fragmented when
using. The solution is cpio (?). And for your particular problem,
the best solution is that you keep a centralized zipped version of
the disk image and deploy from there (using NFS of smbar). But
again, I'm still a *nix newbie and my knowledge ends here. I wish I
can show you how to do it. Hopefully somebody can stand out and
help us.
--
Tong (remove underscore(s) to reply)
http://members.xoom.com/suntong001/
- All free contribution & collection & music from the heavens
------------------------------
From: Chris Gordon-Smith <[EMAIL PROTECTED]>
Subject: Re: Not using Lilo with Mandrake 7.2
Date: Tue, 6 Feb 2001 22:51:22 +0000
mike wrote:
> Hi,
>
> A friend of mine seemed to indicate that in Mandrake 7.0 that he
> was not able to go through the install without installing Lilo. He did
> not want to do this as it messed up his system. The only way
> that he was able to install that version was to do a
> control-alternate-delete
> out of the installation right before the Lilo section.
> I would like to know if I can choose not to use Lilo on the
> hard drive in the new install of Mandrake 7.2
> and only make a boot floppy?
>
The answer is yes. I have done exactly this (with Mandrake 7.2) within the
last 2 - 3 weeks.
You just run through the normal installation, but when you get to the part
that installs the bootloader (LILO) you simply press cancel. The
installation process then skips installing LILO and carries on to the next
stage. You go ahead and create the boot floppy. There is no problem using
the boot floppy; it just takes a few seconds longer at boot time.
By the way, the reason I skipped the LILO installation on my last install
was that on previous installs, the LILO installation was messing up the
master boot record (I don't know why - yet). I could restore the master
boot record with fdisk /mbr, but this left me without LILO, and screwed up
access to my second disc from Windows.
Sooner or later I may have another go with LILO, but for the present
booting from floppy is fine.
Chris Gordon-Smith
London UK
------------------------------
From: "pascal gauthier" <[EMAIL PROTECTED]>
Subject: Re: From an ex Microsoft devotee
Date: Tue, 06 Feb 2001 22:53:49 GMT
In article <[EMAIL PROTECTED]>, "alan simes"
<[EMAIL PROTECTED]> wrote:
If you don't code GUI, think of Visual SlickEdit (www.slickedit.com), it is
a clone a Visual Studio, without the GUI developpement. Altought, you
have a class browser and a good editor in X window.
But after 2 years of developement, I prefer vim and ddd + bash/make.
The learning curve might be high, but the word productivity take it's
sence !
> Dear all
>
> I have developed software for Windows (all flavours) for years. Would I
> listen to the calls to consider Linux from my trainee programmers? Would
> I buggery !
>
> And then I decided to install it for myself on a twin Pentium pro I
> happened to have lying around.
>
> All I can say is that I have fallen in love.
>
> Silky smooth tasking, X is simply magnificent, long file names,
> fantastic networking etc.
>
> As soon as there are real productivity tools available ie. Visual Studio
> for Linux, Microsoft is a whole heap a trouble !!!
>
> Enough of my ranting.
>
> Just wanted to share my new found adoration for
> Linux....................
>
>
>
> simes
>
>
------------------------------
From: Bruce Stephens <[EMAIL PROTECTED]>
Subject: Re: Question about Zsh
Date: 06 Feb 2001 23:04:46 +0000
[EMAIL PROTECTED] writes:
> >>>>> "VANTASSLE" == VANTASSLE CRAIG R <[EMAIL PROTECTED]>
> >>>>> writes:
> VANTASSLE> I was wondering if there was any documentation on the ZSH
> VANTASSLE> of Red Hat 7.0. I want to get some in-depth knowledge on
> VANTASSLE> this shell. If anyone knows any ideas please let me
> VANTASSLE> know.
>
> You might take a look at <http://www.zsh.org/>.
>
> You might also want to look in /usr/doc/zsh [or look for other
> directories starting with "zsh" there].
>
> You might try the command:
> "info zsh"
> or
> "pinfo zsh"
> which may pop up the Info-based documentation
Depends on how it's been packaged, but there's info documentation and
manpages, and these contain the same information (since they're
derived from the same source). "man zsh" should tell you the other
manpages available, and "man zshall" should give you everything.
------------------------------
From: [EMAIL PROTECTED] (.)
Crossposted-To: comp.os.linux.hardware,alt.os.linux,comp.os.linux
Subject: Re: SB Live! Software and Redhat 7
Date: 6 Feb 2001 23:06:37 GMT
In comp.os.linux.misc Tomi Kinnunen <[EMAIL PROTECTED]> wrote:
> Hello to all Linuxists,
> I'm a newbie to Linux, just installed Redhat 7. I have few questions about the use
>of Sound Blaster
> Live! 1024 on this system:
> 1. Is there available SAME KIND of DRIVERS for Linux than the Live!Ware package in
>Windows?
> ( The ability to control all DSP-effects available in the card real-time,
>applied e.g. to guitar
> "multi-effects processor" ? )
> 2. I apologize that I have to use "Windowz terminology" :-), but I'd also need the
>'corresponding' audio
> software:
> * "FastTracker / MadTracker"
> - Some good tracker to build music from samples & instruments.
> * "SoundForge"
> (btw., THE BEST audio editing software ever made, IMO !!)
> - Adding all possible effects with software to audio files,
> ( including Compression,Reverb,Delay,Bending,Fading,Tapping,
> EQ,Flanger,Chorus, etc. etc. etc. )
> * "MultiQuence", "DDClip", "Vegas Audio", etc.
> - Multitrack editor/recorder.
> Any useful help is very welcome !!! With best regards,
You did pay for all of thats software, didnt you? :)
=====.
------------------------------
** 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 by posting to comp.os.linux.misc.
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
******************************
