Linux-Networking Digest #361, Volume #11 Tue, 1 Jun 99 05:13:43 EDT
Contents:
Re: Wingate and Linux (Steve Davidson)
Re: Unwanted DNS lookup (Gary Helbig)
Re: IPCHAINS (Bob G)
Re: Is Linux Slower than Windows??(ppp) (Paul D. Smith)
Re: How do you set up 2 network cards? (Gary Helbig)
Re: autofs or am-utils, which one? (Stefan Boresch)
Dec VT220 Terminal Configuration (Steve Davidson)
Problems with GPM, Serial-Ports and Squid!!! (Thomas =?iso-8859-1?Q?H=E4rtel?=)
Re: A question about collisions (Gary Helbig)
Samba wierdness with mounted filesystem (Alastair Mayer)
Re: DIALD building problems with RH5.2 (Gilford Wimbley)
Re: MARS_EMU for administrators (Alexei Kakhno)
Re: sane and networks (Rage-DCA)
----------------------------------------------------------------------------
From: Steve Davidson <[EMAIL PROTECTED]>
Subject: Re: Wingate and Linux
Date: Mon, 31 May 1999 22:53:48 -0400
George Georgakis wrote:
> You don't you just use the Linux box as the gateway???
>
> George--
> ---------------------------------------------------------------------------
> I never reply by email as a) I don't give out my real email address freely,
> and b) it stops other NG users from reading the solutions to problems
> I can be contacted thru geegee(a)linuxstart.com
> ---------------------------------------------------------------------------
I have dumped WinGate and am using WinNat lite (freeware!) on my dedicated
win9x box, browsing NGs as we speak on my new RH 6.0 installation thru a
dial-up connection on the Win98 box (over WinNAT). Took some poking around to
get it configured, but all is well now.
In my case, my SOs computer (win98) is always up and running, she needs access
to the web and email all the time. I'm constantly futzing around with my
machine (boot between Win9x, NT, BeOS, and RH - develop apps for all
platforms) - made more sense to make her machine the gateway.
Check out http://www.ivasion.com/winnat.htm. WinNAT seems to provide all of
the services of WinGate without the annoying client configuration issues
(WinNAT does not require an app to be running on the client machine), plus the
2-machine version is freeware. I have not yet run into any major limitations
with the product.
{ I am not affiliated in any way with WinNAT - I just found it last week and
have been impressed by its capabilities. }
Hope this helps
Steve
------------------------------
From: Gary Helbig <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Unwanted DNS lookup
Date: Mon, 31 May 1999 23:14:31 -0700
Tim,
I could be as simple as setting the order for name resolution.
You want: order hosts bind dns (or order hosts dns bind)
(This is in /etc/resolv.conf, or via linuxconfig)
This should make it look at /etc/hosts for the name first.
Obviously, all of your systems have to be defined there.
Or, you could build a DNS server inside your proxy server. It's a
bit of work (I had to get help), but there are a bunch of benefits.
I'll let you know on the other one as soon as I get sendmail
working!
Gary.
Adecs BV wrote:
>
> Dear reader,
>
> At the moment I got a small network here at our company with some Win9x
> machine's, and a Linux machine. One of the win95 machines runs Wingate and
> has an internal ISDN modem that allows other machines to use the internet.
> Now I want to replace the Win95 proxy server with a good and secure Linux
> proxy server, but because the ISDN modem we've got is supported under Linux,
> I'm first configuring the Linux machine as a mail server.
>
> At the moment the Linux machine runs oke, but I got two problems. When I
> send an internal mail, let's say to [EMAIL PROTECTED], everything goes oke,
> except that the proxy server is asked for a DNS lookup. This is something I
> don't want because for a DNS lookup the proxy server makes a connection to
> our ISP. How can I fix this problem?
>
> The second problem is that mails to outside the domain aren't delivered.
> Any suggestions why and how this can be fixed.
>
> Thanks in advance,
> Tim Blommerde
------------------------------
From: Bob G <[EMAIL PROTECTED]>
Subject: Re: IPCHAINS
Date: Tue, 01 Jun 1999 06:00:37 GMT
Ken wrote:
>
> I am running RedHat 6.0 and have ipchains working but I can not get ipchains
> to allow NetMeeting inbound, outbound works fine. Does anyone have a
> successful set of rules for ipchains/NetMeeting? I have been to several how
> to's and have tried several configs but still no luck.
> Please Help if you have the answer
I spent a LOT of time trying to get netmeeting working via masq about a
year ago using netmeeting 2.1. Sadly, I don't have any particularly good
news. Search for articles Q158623 and Q174611 on support.microsoft.com.
To sum up, to get inbound audio to work, UDP connections must be allowed
on ports 1025-65535. Not a particulary practical approach.
In fairness to Microsoft, this is a limitation of the H.323 protocols,
not a MS screwup.
Did you get two-way audio to work outbound? I'd be delighted if my info
is simply out of date!
- Bob
------------------------------
From: [EMAIL PROTECTED] (Paul D. Smith)
Subject: Re: Is Linux Slower than Windows??(ppp)
Date: 01 Jun 1999 00:52:14 -0400
Reply-To: [EMAIL PROTECTED]
%% [EMAIL PROTECTED] (Ray) writes:
r> On 27 May 1999 01:35:42 -0400, Paul D. Smith <[EMAIL PROTECTED]> wrote:
>> My belief is that my phone lines just have really, really crappy
>> quality. When I had the second line put in they had to come back
>> twice, muttering something about "being at the end of the line" and
>> "not having enough circuits available" or some such thing. Sigh.
>> Doesn't work any better with my original phone line, though.
r> Sometimes when they run out of lines they will use a mux to
r> essentially turn 1 line into 2. Needless to say, this isn't so
r> good for modem communications.
:(
Would there be any interference between the lines, doing this? I must
say I've not seen any change in quality when someone's using the other
line (or not).
>> I do get some strange error at boot time that _seems_ to indicate some
>> IRQ conflict, although I don't think there is one based on what I know
>> about my cards. I have an internal Zoom V90, and I'm using isapnp to
>> set it up. The error doesn't appear in my /var/log/messages log or from
>> dmesg, though, and it scrolls off the screen so I'm not quite sure how
>> to capture it :-/.
r> That's really odd, dmesg is usually pretty good job of grabing this stuff.
r> Could you just scroll up the screen (using <Shift PgUp>) right after you
r> boot and have a look?
I boot into XDM, but I've used ctrl-alt-F1 to get back to the initial
terminal and shift-pgup, etc. keys don't work: nothing happens when I
press them. Maybe I don't have something set up, or maybe xdm is
whacking my keyboard. I'll turn off XDM and try again.
r> 1. Try running a phone cable right from the telco box outside your
r> house. If the connect speed is about the same then the interior
r> wiring is probably ok.
I thought of this one a while ago, since I wired the second line myself
(from the telco box to my study) :). My telco box is actually just
inside the house, in the basement, but I've run cord from my modem
directly to both the original and the secondary line-in ports in the
telco box: no difference :(.
r> 2. Since you have 2 lines, borrow a second modem (preferably an
r> external) and try calling yourself. If you still can't do at least
r> 31.2 then you probably have a mux on one or both lines and you're
r> SOL.
Ooh. Tricky. Didn't think of that. Too bad; I actually had an extra
modem around until 2 weeks ago :(. I'll see if I can get another one.
I wonder if I can call up Bell Atlantic and get them to tell me whether
they're muxing my lines... Boy, I hate Bell Atlantic.
r> One last thing is to check and see if there is a firmware upgrade
r> available for your modem.
Good idea, but I bought it (from a reputable local PC store) in January
so it's probably pretty up-to-date.
--
===============================================================================
Paul D. Smith <[EMAIL PROTECTED]> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
===============================================================================
These are my opinions---Nortel Networks takes no responsibility for them.
------------------------------
From: Gary Helbig <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.setup
Subject: Re: How do you set up 2 network cards?
Date: Mon, 31 May 1999 23:23:23 -0700
Matthew,
There should be no problem with them on the same interrupt, but on
the same port is a problem.
The BIOS _should_ set up the cards before Linux has a chance to look
at them.
First thing I would try is turning OFF all attempts to control the
IRQ & I/O. Then look in /var/log/messages to see what the kernel found
on the way up.
Try the cards one at a time. You may have one dead card. Or one
dead slot; I have found motherboards where interrupts worked in only 3
of the 4 PCI slots. The slot ordering can have an impact too; try
swapping all the PCI cards around.
3COM has some pretty good diagnostics on their web site. Download
those, and see what they think of your hardware.
Gary.
Matthew Hanselman wrote:
>
> Anybody know how to get 2 3Com Etherlink XL cards to work in the same box?
> I can't seem to force Linux to put the 2 cards on different IRQ/ports.
> The cards come up on IRQ 9 base 0xb800; This append does nothing:
> append="ether=5,0xb800,eth0" (eth0 will still be on irq 9)
>
> Or, if I put this into conf.modules, eth0 will never come up:
> options 3c59x irq=5
>
> Playing around with the BIOS to force a PCI slot to a particular IRQ has
> yielded nothing...
>
> Any ideas?
>
> - Matt
------------------------------
From: Stefan Boresch <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.development.system
Subject: Re: autofs or am-utils, which one?
Date: 01 Jun 1999 08:41:26 +0200
Hm, I guess it would help if you described what exactly you
wanted to do. I have switched to autofs from amd starting with
RH 5.2. Under 5.2, I had problems with local auto.master files
reading NIS maps, so I had to hack the /etc/rc.d/init.d/autofs
script. Under RH 6.0, this works flawlessly. (For RH 5.2 I
use autofs on both the alpha and i386, RH 6.0 tested on i386
only (so far))
Stefan
--
Institute for Theoretical Chemistry phone: -43-1-427752715
University of Vienna FAX: -43-1-427752790
Waehringerstr. 17 -43-1-4028525
A-1090 Vienna, Austria
------------------------------
From: Steve Davidson <[EMAIL PROTECTED]>
Subject: Dec VT220 Terminal Configuration
Date: Mon, 31 May 1999 23:26:09 -0400
I have an old Dec VT220 terminal that I would like to use for access to
my RH box. Where can I find information regarding setting this up?
------------------------------
From: Thomas =?iso-8859-1?Q?H=E4rtel?= <[EMAIL PROTECTED]>
Subject: Problems with GPM, Serial-Ports and Squid!!!
Date: Tue, 01 Jun 1999 08:15:34 +0200
I can't use my mouse on linux, when start yast, choose the mousetype and
start gpm with ttyS0 then nothing happens, but when i restart my system
with a DOS bootdisk and use a DOS mouse driver everything is correct.
My second Problem is I want to use a modem on ttyS1, but when I
configure the /sbin/init.d/serial script (manuell configuration f�r COM
2) my squid server won't start when I restart my system. Squid starts
only when everything is disabled in the serial script.
Does anyone know why linux does so?
thanx
------------------------------
From: Gary Helbig <[EMAIL PROTECTED]>
Subject: Re: A question about collisions
Date: Mon, 31 May 1999 23:41:18 -0700
CF,
At 100%, every other packet is getting stomped on by somebody else;
your 100Mbit network is delivering 50Mbits. Which is still very
useable.
My _opinion_ would be to ignore it when under 5%, concider
segmenting the network at about 25%, and try a new topology if it hit
50%.
BTW, I have found that the new "dual-speed" hubs are actually
switching hubs. A simple/cheap way of segmenting a network.
Gary.
CF wrote:
>
> I have been wondering the same thing, and wondering about buying a switch.
>
> We have 1/2% to 1.5% collisions. One reply here says under 5% is ok,
> another says "nearly 100%" is ok.
>
> Is there any consensus on this?
>
> CaryF
>
> Chris Jackson <[EMAIL PROTECTED]> wrote in message
> news:3752cd8b.8509433@news...
> > ok, I have been living with this problem up till now thinking there
> > was something wrong with my setup or maybe my connection to the
> > internet wasn't so hot, but this is the problem I have....
> >
> > eth0 Link encap:Ethernet HWaddr 00:10:5A:15:35:C8
> > inet addr:24.3.254.64 Bcast:24.3.254.255
> > Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:1174178 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:625644 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:6823 txqueuelen:100
> > Interrupt:11 Base address:0x6100
> >
> > eth1 Link encap:Ethernet HWaddr 00:20:78:15:67:20
> > inet addr:192.168.1.1 Bcast:192.168.1.255
> > Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:629369 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:1063614 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:3232 txqueuelen:100
> > Interrupt:9 Base address:0x6200
> >
> > my eth0 has an extremely large amount of collisions on it, or is this
> > normal?
> > I am running RedHat 6.0 and this is the network cards lines from dmesg
> >
> > 3c59x.c:v0.99Kb 5/7/99 Donald Becker
> > http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
> > eth0: 3Com 3c905B Cyclone 100baseTx at 0x6100, 00:10:5a:15:35:c8,
> > IRQ 11 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate
> > interface.
> > MII transceiver found at address 24, status 786d.
> > MII transceiver found at address 0, status 786d.
> > Enabling bus-master transmits and whole-frame receives.
> > ne2k-pci.c:v0.99L 2/7/98 D. Becker/P. Gortmaker
> > http://cesdis.gsfc.nasa.gov/linux/drivers/ne2k-pci.html
> > ne2k-pci.c: PCI NE2000 clone 'Winbond 89C940' at I/O 0x6200, IRQ 9.
> > eth1: PCI NE2000 found at 0x6200, IRQ 9, 00:20:78:15:67:20.
> >
> > any help with this would be greatly appreciated thanks
> >
------------------------------
From: Alastair Mayer <[EMAIL PROTECTED]>
Subject: Samba wierdness with mounted filesystem
Date: Wed, 19 May 1999 17:43:08 -0600
Hi,
I'm in the process of upgrading an NT server to Linux. The box
basically serves as a static file server to a small cluster of special
purpose workstations, hosting an array of large (20+ GB) SCSI drives.
Under NT, these drives were shared as pcserv1, pcserv2, etc, and
I'm basically duplicating that (or trying to) with samba. I created
mount points /pcserv1, /pcserv2, etc, and set up my smb.conf file.
Here's the problem: If I don't mount the drives, and say just have
a couple of dummy files in the /pcserv1 dir, I can see them fine from
the client (W95 for testing at the moment, the real clients are NTW).
But when I mount the drives, I get a "not accessible, access denied"
error.
One possible (?) gotcha -- the mounted drives are NTFS, but I'm
running 2.2.5 and can see the files just fine locally. Howcome
samba won't share? (The files are only ever read, so I don't
have to worry about writing to NTFS.)
(Oh, I'm running samba 2.0.3, if that makes a difference)
Help?
-- Alastair Mayer
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Gilford Wimbley)
Subject: Re: DIALD building problems with RH5.2
Date: Tue, 01 Jun 1999 07:31:33 GMT
On 31 May 1999 10:05:46 +0200, [EMAIL PROTECTED]
(Villy Kruse) wrote:
>In article
><[EMAIL PROTECTED]>,
>Mike Bartman <[EMAIL PROTECTED]> wrote:
>
>
>
>>
>>There is no "__errno_location" field in icmp.h, just an "errno" field
>>in a structure. I'm assuming that the __errno_location symbol is
>>being generated by the compiler, right? Why? And how to I get past
>>this problem? I'm familiar with OpenVMS, but as I said, unix
>>development is new to me so this may be trivial for some of you, but
>>it's got me stumped at the moment! :^)
>
>
>
>That errno field in a structure should be renamed to something else
>as there is a #define errno somewhere in the headers.
>
>
>Also, version 0.16 needs up to patch level 5 before it compiles on redhat
>system. You'll run into other problems, too if you don't.
>
>Look at the contrib.redhat.com see if there is a rpm version you can
>download. It has been there fore ages, including patch level 5.
>
>
>Also check http://diald.unix.ch for the current (I thing) home page for diald.
>
>
>
>Villy
Yeah, I downloaded a clean version of 0.16 and a patch to 0.16.5 and
it compiled with one warning. It was a pointer type mismatch but it
was in a comparison. I decided to leave it alone and try to run diald
without worrying about the error, and it seems to be working fine.
It took me like three days to figure out what do with the patch, but
hey, learning is fun. Let me know if you can't find the patch, and
I'll email it to you or something.
regards,
GW
ps, the patch has to be applied to a pristine copy of 0.16, so if you
don't have a pristine version of the source, still, you might need to
download it again.
------------------------------
From: [EMAIL PROTECTED] (Alexei Kakhno)
Subject: Re: MARS_EMU for administrators
Date: Tue, 01 Jun 1999 07:32:55 GMT
I see many questions in the newsgroup about MarsNWE server
and decide to help because my server works for a long time
without any problems and never turned off as Unix server,
IP router, PPP for remote Windows95 users to access to Internet,
NFS AIX <--> Linux.
Hardware: Motherboard HX chipset, CPU P166,
Netcards: ISS 3c509, 3 of PCI 3c590. Linux 5.0 with kernel 2.0.36.
First, IPX must be in your kernel for NCP package and
MarsNWE Server,
do:
cd /usr/src/linux
make config # assign Y for CONFIG_IPX
# or check .config if CONFIG_IPX=Y all ok!!!
re-compile kernel and install it.
then unzip , untar... MarsNWE sources and edit config.h of the MarsNWE
for your needs, read README, etc Be attention!!! read, read ...
create novell group
add users they must be belong to the novell group
===========================================================
each user has the same home directory i.e /home/novell
.bash_profile:
# add exit 1 --- user can't use telnet
exit 1
==========================================================
add names of the novell users into /etc/ftpusers
# user can't use ftp
==========================================================
chmod +t /usr1/SYS # each user can control own files, delete, etc
============================================================
Here's my /etc/nwserv.conf :
# This is the configuration-file for "mars_nwe", a free
# netware-emulator
# for Linux.
#
#
# !! section 4 : automatic creation of ipx-interfaces changed in
# 0.98.pl9 !!
#
# since version 0.98.pl11:
# the most important options in config.h can now be altered in
# this file begin at section 60.
#
# This file specifies which Linux-resources (printers, users,
# directories)
# should be accessible to the DOS-clients via "mars_nwe". Furthermore
# some general parameters are configured here.
# Some options of "mars_nwe" can only be altered by editing the the
# file
# `config.h' and re-compiling "mars_nwe", please see there for more
# information.
#
=========================================================================
# Section 1: volumes (required)
#
1 SYS /usr1/SYS k
1 SYS1 /usr2/SYS k
#
=========================================================================
# Section 2: servername (optional)
#
2 ROF
#
=========================================================================
# Section 3: Number of the internal network (required)
#
3 auto
#
=========================================================================
# Section 4: IPX-devices (strongly recommended)
4 0x1 eth2 802.2 1
4 0x3 eth3 802.2 1
4 0x4 eth1 802.2 1
# Section 5: special device flags
#
=========================================================================
# Flags
5 0x1
#
=========================================================================
# Section 6: version-"spoofing"
6 1 0x0
#
=========================================================================
# Section 7: password handling of DOS-clients (required)
7 0
# Section 8: special login/logout/security and other flags.
8 0x0
# Section 9: Standard creat mode for creating directories and files.
#
#=========================================================================
9 0770 0770
#=========================================================================
# Section 10: UID and GID with minimal rights
10 200
11 65534
#
=========================================================================
# Section 12: supervisor-login (required)
12 SUPERVISOR root
#
=========================================================================
# Section 13: user-logins (optional)
#
13 ALEX alex baba 0x1
13 director director 0x1
# Section 14: currently not used
#
=========================================================================
# Section 15: automatic mapping of logins (decision required)
15 0 top-secret
#
=========================================================================
# Section 16: Tests on startup
16 1
# Section 17-20: currently not used
#
=========================================================================
# Section 21: print queues (optional)
#
=========================================================================
# Section 22: print server entries (optional)
#
=========================================================================
# Section 30: Burst mode values (optional)
#
=========================================================================
# Section 40ff: Some pathes (optional)
#
=========================================================================
# 40 = path for vol/dev/inode->path cache, needed for
client-32,namespace
40 /var/spool/nwserv/.volcache
# 41 = path for share/lock files
41 /var/spool/nwserv/.locks
# 42 = path for spool dir
42 /var/spool/nwserv
#
#
# 45 = path for bindery file's
45 /var/mars_nwe/bindery
#
=========================================================================
# Section 50: Conversion tables by Victor Khimenko <[EMAIL PROTECTED]>
# Tables for DOS->Unix names translation & upper/lowercase
translations
# For more information see doc/README.NLS
# some examples files exist in the examples directory.
# Conversation file must include 4 tables a 256 byte.
# 0 = dos2unix
# 1 = unix2dos
# 2 = down2up 'dosname'
# 3 = up2down 'dosname'
#
=========================================================================
# Syntax:
# 50 Filename of conversation file.
#
# Examples:
# 50 /etc/nwserv.cnv
# Changing defaults from config.h
# more information in config.h
# 60 10 # MAX_CONNECTIONS
# 61 10 # MAX_NW_VOLS
# 68 1 # USE_MMAP (use mmap=1, no mmap=0)
# 69 0 # HANDLE_ALL_SAP_TYPS (all sap typs=1, only typ 4=0)
# 70 0x44444444 # NETWORK_SERIAL_NMBR (4 byte)
# 71 0x2222 # NETWORK_APPL_NMBR (2 byte)
# --------------------------------------------------------
# You usally don't want to change anything below this line
# --------------------------------------------------------
# Sections 100-106: amount of debug-information
#
# FLAG:
# 0 no debug messages
# 1 errors and notes are reported
# 99 maximum debug levels
100 0 # debug IPX KERNEL (0 | 1)
101 1 # debug NWSERV
102 0 # debug NCPSERV
103 0 # debug NWCONN
104 0 # debug (start) NWCLIENT, should *always* be
'0' !
105 0 # debug NWBIND
106 1 # debug NWROUTED
# Sections 200-202: logging of "nwserv"
#
200 1 # 0 = no logfile and dont daemonize
nwserv/nwrouted
# 1 = daemonize nwserv/nwrouted and use
logfile
201 /var/mars_nwe/nw.log # filename of logfile
#201 syslog # if filename == syslog then syslogd will be
used for
# all messages
202 0x0 # flag in hex notation
# 0x0=append all messages to logfile.
# & 0x1=creat new logfile instead of
appending.
#202 0x3 # & 0x2=use syslogd for error messages instead
of logfile.
# Sections 210,211: timing
210 10 # 1 .. 600 (default 10) seconds after server
# really goes down after a down command
211 60 # 10 .. 600 (default 60) broadcasts every x
seconds
# Sections 300-302: loging of routing-information
300 1 # > 0 print routing info to file every x
broadcasts.
# ( normally minutes )
301 /var/mars_nwe/nw.routes # filename of logfile
302 0x0 # flags will be interpreted as hex value.
# 0 = append to this file
# & 0x1 = creat new routing info file
# & 0x2 = split info into several files
# (extensions = .1, .2, .3 ... )
# Section 310: watchdogs
310 7 # send wdog's only to device net < x ticks.
# 0 = always send wdogs. < 0 = never send
# wdogs
# Section 400:
# station file for special handling of stations.
400 /etc/nwserv.stations # for syntax see file in the examples
# Section 401: nearest server
#
# for special handling of the 'get nearest server request'.
401 0 # 0 = ignore entry 400, get nearest response always
# enabled.
# Section 402: station connect restrictions
#
# for special handling of the 'creat connection' (attach) call.
402 0 # 0 = ignore entry 400, create connection always
# enabled.
# *************************************************************
i'll be glad if this information usefull
Best wishes, Alexei
mailto: [EMAIL PROTECTED]
------------------------------
From: Rage-DCA <[EMAIL PROTECTED]>
Subject: Re: sane and networks
Date: Tue, 01 Jun 1999 06:56:44 GMT
Rage-DCA wrote:
> i'm not sure if this is the right newsgroup to ask this in, but i was
> wondering if someone could give me some pointers about my scanner. i'm
> using sane which is the best i've found so far (let me know if there is
> something better). ok, here goes my questions.
>
> a) sometimes the scanner is not on when i reboot my computer meaning
> that when linux initalizes my scsi card it does not detect the scanner.
> is there a way to still be able to turn it on and then have the scsi
> card find it. right now if i turn it on, it still says there are no
> scanners connected. only way i know how to fix it is reboot and i can't
> do that often.
>
> b) also, i had a question about the umax scanner drivers. they give a
> list of enhancement arguments for the command line, but i can't seem to
> get any of them to work (i.e. --brightness). does anyone know how i
> might fix this since my scanner scans to dark?
>
> thx for the help, peace.
>
> --
>
> Jason Osborne (Rage-DCA)
> - [EMAIL PROTECTED]
> - http://rage.dynip.com
> - LinuxInside - I run it, do you?
well, i guess noone knew about this one, but i was able to solve it
myself. if you wanted to know what i've found for part a, here goes. you
can reinitalize devices by the following command:
echo "scsi remove-single-device 0 0 5 0" > /proc/scsi/scsi
echo "scsi add-single-device 0 0 5 0" > /proc/scsi/scsi
a == hostadapter id (first one being 0)
b == SCSI channel on hostadapter (first one being 0)
c == ID
d == LUN (first one being 0)
all this does is first delete the device with the id you specify then when
you add it back, its scans the id you specify. pretty kewl, thanks to
#linux on undernet for the help. hope this is useful for a few ppl. btw, b
still remains unsolved so if you have any ideas, please feel free to
respond
--
Jason Osborne (Rage-DCA)
- [EMAIL PROTECTED]
- http://rage.dynip.com
- LinuxInside - I run it, do 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 (and comp.os.linux.networking) 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-Networking Digest
******************************
