Linux-Setup Digest #199, Volume #21              Thu, 10 May 01 03:13:07 EDT

Contents:
  Re: Dual boot on already setup machine. ("Earth")
  Re: PCI modem 3COM/USR 2977 (Nader)
  Re: PCI modem 3COM/USR 2977 (Nader)
  HELP! Kamakazi Shell Script Whacks System To Death! /etc/rc.d/rc.sysinit function 
("Brian Wildasinn")
  Re: anyone have solution install RH7.1 on 16M RAM (J Sloan)
  How to route email locally and externally? (Mark Johnson)
  /etc/profile problem (Warren Parker)
  Moonlighter needed - Orange County California (Dan Fraser)
  problem with Gcombust as normal user  (Yves Leung-Tack)
  Re: Shutdown for non root users (michael james obrien)
  Re: How to route email locally and externally? ("michael.fengler")
  how to allow shutdown for a user ?? :) (Yves Leung-Tack)

----------------------------------------------------------------------------

From: "Earth" <[EMAIL PROTECTED]>
Subject: Re: Dual boot on already setup machine.
Date: Thu, 10 May 2001 04:44:53 GMT

Thank you very much.

"David Efflandt" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> On Thu, 10 May 2001 02:38:01 GMT, Earth <[EMAIL PROTECTED]> wrote:
> >
> > I currently run win98se, and would like to learn Linux.  I will need to
keep
> > win98 until I know how to use Linux, so I will need a dual boot.  How
can I
> > setup a dual boot without reformatting, or losing any win98 data ect?
>
> Make sure that you have a Win98 rescue disk.
>
> If you need to resize your Win partition to make room for Linux, make sure
> that you back up anything essential.  Temporarily turn off virtual memory
> in Win98 (to minimize hidden files at the far end) and fully defrag your
> hard drive.
>
> Linux comes with a boot loader (LILO) that can install in the MBR (master
> boot record at beginning of drive) to boot Windows or Linux.  If your
> installation offers to make a Linux boot floppy do it (a perfectly DOS
> formatted floppy with NO bad sectors).  If not, learn how to make one
> after installing Linux.  You will need it if (when) Windows overwrites
> your MBR.
>
> http://www.linux.org/docs/ldp/howto/mini/Linux+Win95/index.html
> Gives more info that applies equally to Win98.
>
> --
> David Efflandt  (Reply-To is valid)  http://www.de-srv.com/
> http://www.autox.chicago.il.us/  http://www.berniesfloral.net/
> http://cgi-help.virtualave.net/  http://hammer.prohosting.com/~cgi-wiz/



------------------------------

From: Nader <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Re: PCI modem 3COM/USR 2977
Date: Wed, 09 May 2001 21:49:11 -0700

I've been where you are now.

1) First, try upgrading your serial driver (see
http://serial.sourceforge.net/) to at least 5.05.

2) If that doesn't work, search http://groups.google.com for your modem and
linux issues.

3) If those don't work, try upgrading your kernel to 2.4.

My issue was compounded by a PCI IRQ conflict between my modem and my UDMA66
controller.  I could either patch my 2.2.16 kernel or upgrade to 2.4 to resolve
that.  If you have ATA-66 or ATA-100, this may also be a problem for you.

Let me know if you need more assistance.

Nader



Mark Slagell wrote:

> I've been surfing around for the world's collected wisdom on making this
> modem work but am coming up empty so far.  Possibly relevant info is
> below.  Can anybody shed light?
>
> TIA
>
>   -- Mark
>
> ---------------------------
> >uname -a
> Linux pc5053 2.2.18 #4 Mon Apr 9 14:58:16 CDT 2001 i686 unknown
> ---------------------------
> >lspci -v
> [...]
> 01:0b.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610
> (rev 01) (prog-if 02 [16550])
>         Subsystem: US Robotics/3Com USR 56k Internal FAX Modem
> (Model 2977)
>         Flags: medium devsel, IRQ 3
>         I/O ports at dff0
>         Capabilities: [dc] Power Management version 2
>
> ---------------------------
> >cat /proc/pci
> [...]
>   Bus  1, device  11, function  0:
>     Serial controller: Unknown vendor Unknown device (rev 1).
>       Vendor id=12b9. Device id=1008.
>       Medium devsel.  IRQ 3.
>       I/O at 0xdff0 [0xdff1].
> ---------------------------
> >cat /proc/interrupts
>            CPU0
>   0:     247814          XT-PIC  timer
>   1:       4923          XT-PIC  keyboard
>   2:          0          XT-PIC  cascade
>   3:      32587          XT-PIC  eth0
>   9:      12746          XT-PIC  Intel ICH 82801AA
>  12:      69297          XT-PIC  PS/2 Mouse
>  13:          1          XT-PIC  fpu
>  14:     961293          XT-PIC  ide0
>  15:          7          XT-PIC  ide1
> NMI:          0
> ---------------------------
> >setserial /dev/ttyS3 port 0xdff0 autoconfig auto_irq
> >setserial -g /dev/ttyS3
> /dev/ttyS3, UART: unknown, Port: 0xdff0, IRQ: 3
> >minicom
> [unresponsive on /dev/ttyS3]
> ---------------------------
> >[tried setserial with uart as 16550A, 16450, etc, no difference]
> >[tried setserial options: ^fourport, skip_test. no difference]
> >[tried changing IRQ with setpci, managed to lock up the machine a few times]


------------------------------

From: Nader <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Re: PCI modem 3COM/USR 2977
Date: Wed, 09 May 2001 21:57:25 -0700

And since your /proc/interrupts doesn't show "serial" next to IRQ 3 like it
should, it seems that you have IRQ sharing problems.  Try the serial driver
upgrade and if that doesn't do it, try the kernel upgrade.


Nader wrote:

> I've been where you are now.
>
> 1) First, try upgrading your serial driver (see
> http://serial.sourceforge.net/) to at least 5.05.
>
> 2) If that doesn't work, search http://groups.google.com for your modem and
> linux issues.
>
> 3) If those don't work, try upgrading your kernel to 2.4.
>
> My issue was compounded by a PCI IRQ conflict between my modem and my UDMA66
> controller.  I could either patch my 2.2.16 kernel or upgrade to 2.4 to resolve
> that.  If you have ATA-66 or ATA-100, this may also be a problem for you.
>
> Let me know if you need more assistance.
>
> Nader
>
> Mark Slagell wrote:
>
> > I've been surfing around for the world's collected wisdom on making this
> > modem work but am coming up empty so far.  Possibly relevant info is
> > below.  Can anybody shed light?
> >
> > TIA
> >
> >   -- Mark
> >
> > ---------------------------
> > >uname -a
> > Linux pc5053 2.2.18 #4 Mon Apr 9 14:58:16 CDT 2001 i686 unknown
> > ---------------------------
> > >lspci -v
> > [...]
> > 01:0b.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610
> > (rev 01) (prog-if 02 [16550])
> >         Subsystem: US Robotics/3Com USR 56k Internal FAX Modem
> > (Model 2977)
> >         Flags: medium devsel, IRQ 3
> >         I/O ports at dff0
> >         Capabilities: [dc] Power Management version 2
> >
> > ---------------------------
> > >cat /proc/pci
> > [...]
> >   Bus  1, device  11, function  0:
> >     Serial controller: Unknown vendor Unknown device (rev 1).
> >       Vendor id=12b9. Device id=1008.
> >       Medium devsel.  IRQ 3.
> >       I/O at 0xdff0 [0xdff1].
> > ---------------------------
> > >cat /proc/interrupts
> >            CPU0
> >   0:     247814          XT-PIC  timer
> >   1:       4923          XT-PIC  keyboard
> >   2:          0          XT-PIC  cascade
> >   3:      32587          XT-PIC  eth0
> >   9:      12746          XT-PIC  Intel ICH 82801AA
> >  12:      69297          XT-PIC  PS/2 Mouse
> >  13:          1          XT-PIC  fpu
> >  14:     961293          XT-PIC  ide0
> >  15:          7          XT-PIC  ide1
> > NMI:          0
> > ---------------------------
> > >setserial /dev/ttyS3 port 0xdff0 autoconfig auto_irq
> > >setserial -g /dev/ttyS3
> > /dev/ttyS3, UART: unknown, Port: 0xdff0, IRQ: 3
> > >minicom
> > [unresponsive on /dev/ttyS3]
> > ---------------------------
> > >[tried setserial with uart as 16550A, 16450, etc, no difference]
> > >[tried setserial options: ^fourport, skip_test. no difference]
> > >[tried changing IRQ with setpci, managed to lock up the machine a few times]


------------------------------

From: "Brian Wildasinn" <[EMAIL PROTECTED]>
Crossposted-To: comp.unix.shell
Subject: HELP! Kamakazi Shell Script Whacks System To Death! /etc/rc.d/rc.sysinit 
function
Date: Wed, 9 May 2001 21:25:28 -0700

[ reposted from compos.linux.setup ]

Hi all,

I'm looking for help with what maybe is a broken shell function, called
"action", listed below.  I can manually run its input "STRING" command and
see a full /proc directory by typing,
     `mount -n -t proc /proc /proc && ls`
but  the same command fails when the shell script, /etc/rc.d/rc.sysinit
runs:

     `action "Mounting proc filesystem" mount -n -t proc /proc /proc.

I tested this shell script manually again by loading the shell script
"action()" listed in /etc/rc.d/init.d/functions, which reads as:

# BOOTUP=color   on this RedHat 6.9~7.0 system
# for setting [SUCCESS], [FAILURE], etc. to pretty colors
if [ "$BOOTUP" != "verbose" ]; then
    INITLOG_ARGS="-q"
else
    INITLOG_ARGS=
fi

    # Run some action. Log its output.
    action() {
    STRING=$1
    echo -n "$STRING "
    shift
    initlog $INITLOG_ARGS -c "$*" && success "$STRING" || failure "$STRING"
    rc=$?
    echo
    return $rc
}

Nothing fancy. Just returns the error which I am trying to fix:

    Mounting pro filesystem dup2: Bad file descriptor
                                [FAILED]

Anyone have any ideas how to fix this shell script "action()" function?
See original post in comp.os.linux.setup for system setup info, which
mentions my debugging efforts so far.

I hazard to guess that the system bootup scripts are failing due to a
non-fscked, >>> non-mounted /proc read-only filesystem <<<. dup2 errors
result
because rc.sysinit finds that the  /proc directory is empty. The system will
not proceed to multiuser unless it has a clean (fsck'ed) filesystem. Running
top and df fails as well since these programs depend on pulling information
from the /proc directory, stating "Error: /proc must be mounted      To
mount /proc at boot you need an /etc/fstab line like:   /proc  /proc   proc
defaults     In the meantime, mount /proc /proc -t proc


Looking at the dup2 error, "Bad file descriptor", it seems that since proc
wasn't mouted there are no virtual files to get a valid file description.
And thus, the error, "Bad file descriptor".

I'm not sure of the booting sequence of programs other than what the rhl
guide mentions 1) Lilo 2) Kernel 3) Init 4) rc.sysinit.  But since the
filesystem remains "Read-only" it may be that there is a broken script
between Init and rc.sysinit. I think maybe that this has to do with mounting
the system read-only first for auto-fscking and then remounting the as
writable so that rc.sysinit can mount and get file descriptors from the
/proc directory.

What scripts are run between Init and rc.sysinit? Before rc.sysinit mounts
/proc it does:

1) # Rerun ourselves through initlog
        if [ -z "$IN_INITLOG"]; then
       [ -f /sbin/initlog ] && exec /sbin/initlog &INITLOG_ARGS -r
/etc/rc.sysint
       fi

2) # If we're using devfs, start devfsd now -- we need the old device names
      [ -e /dev/.devfsd -a -x /sbin/devfsd ] && /sbin/devfsd /dev

3) # Set the path
    PATH=/bin:/sbin:/usr/bin:/usr/sbin
    export PATH
4) # Read in config data.
    if [ -f /etc/sysconifg/network ]; then
    .  /etc/sysconfig/network
    else
    NETWORKING=no
    HOSTNAME=localhost
    fi

5) # Source functions
    .   /etc/init.d/functions

6) # Print a banner. ;)
    echo -en "\t\t\tWelcome to "
   [ "$BOOTUP" != "serial" ] && echo -en \\033[1;31m"
    echo -en "Red Hat"
   [ "$BOOTUP" != "serial" ] && echo -en \\033[0;39m"
   echo " Linux"
    if [ "$PROMPT" != "no" ]; then
    echo -en "\t\tPress 'I' to enter interactive startup."
    echo
    sleep 1
   fi

7) # Fix console loglevel
/bin/dmesg -n $LOGLEVEL

# Mount /proc (done here so volume labels can work with fsck)
action "Mounting proc filesystem" mount -n -t proc /proc /proc

And here's where the dup2 errors occur.  The only place dup2 occurs in /etc
is in /etc/ltrace.conf:  ; unistd.h ... int dup2(int, int);  The comment
occurs in /usr/include/unistd.h: /* Duplicate FD to FD2, closing FD2 and
making it open on the same file. */  extern int dup2(int __fd, int __fd2)
__THROW;



Any help is appreciated!

Brian
[root@(none) /proc]#



> "Brian Wildasinn" <[EMAIL PROTECTED]> wrote in message
> news:9dc66r$bud$[EMAIL PROTECTED]...
> > Remounting read-write the root file system, the /proc filesystem is able
> to
> > be mounted.
> > However, upon rebooting the proc file system is added to /etc/mtab as
> >
> > none /proc /proc
> >
>
>
>
>





------------------------------

From: J Sloan <[EMAIL PROTECTED]>
Crossposted-To: 
alt.comp.linux,comp.os.linux.admin,comp.os.linux.networking,comp.os.linux.questions,comp.os.linux.redhat,comp.os.linux.security
Subject: Re: anyone have solution install RH7.1 on 16M RAM
Date: Thu, 10 May 2001 05:15:31 GMT

Have you tried a "text" install?

jjs

tin wrote:

> not the swap partitions problem
> is redhat will popup "not enought RAM to install "
> before install process
>
> anyway thank you very much
>
> "James Richard Tyrer" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> > tin wrote:
> >
> > > anyone have solution install RH7.1 on 16M RAM
> > > Intel p100 box
> >
> > I had RH 5.2 running on a 486 with 8 MB of RAM and 127MB+ Swap; it did
> > work.  X was a bit slow and I didn't use a desktop -- NO KDE or GNOME --
> > just fvwm or twm to run applications.
> >
> > You could probably install RH7.1.  You can make a standard install if
> > you have a large enough disk.  But you will probably find KDE or GNOME
> > too slow and if you want to try them you would need 256MB of Swap.
> > There is a theory that two 127MB Swap partitions are faster than one
> > large one.  As I said above, you will probably want to use fvwm or twm
> > to run X applications.  GUI applications will not be very fast.
> >
> > On the other hand if you want it for Console only, it should be OK.
> >
> > But, I would add memory if you have room for it on the Mother Board.
> >
> > If it is an old type of memory, try picking it up used at Computer
> > Renaissance.
> >
> > JRT
> >
> >


------------------------------

Subject: How to route email locally and externally?
From: [EMAIL PROTECTED] (Mark Johnson)
Date: Thu, 10 May 2001 04:59:51 GMT

Is it possible to configure our linux box such that it can determine 
whether to route an email locally or out to the relay host?  

For example, our company is provided by our ISP a domain name 
"foobarco.com" and 15 email address: [EMAIL PROTECTED], [EMAIL PROTECTED], 
etc...  All the employees run Win98 and Mac9 but we want to run linux as a 
file server and web server and possibly an email host.

What we would like to do is when joe emails mary we would like that email 
to not out out to the ISP and then right back in, instead it should just 
realize that Joe and Mary are local users and deposit the email in there 
linux home account which they can access using their regular SMTP/POP3 
email client.  However, if Joe emails [EMAIL PROTECTED] then linux will 
relay the email to the ISP and everything continues as regular.

I know that I could this easily by just having an internal and external 
email accounts (i.e. [EMAIL PROTECTED], and [EMAIL PROTECTED]) but the 
users won't like this.  Instead it needs to be transparent from the user, 
however, they will have to understand that they can't access the "office" 
email from home.

Anyway, any suggestions here?  I'm kind of newbie with all this...

thanks for your time!


NOTE: we do not have any window's domain controllers.  I was thinking of 
using SAMBA for authentication and etc.., currently, everyone is on a plain 
old Win98 workgroup.


------------------------------

From: Warren Parker <[EMAIL PROTECTED]>
Subject: /etc/profile problem
Date: Thu, 10 May 2001 15:32:24 +1000
Reply-To: [EMAIL PROTECTED]

I have Linux RedHat 7.0 installed on a PC. The pc loads xdm
automatically. If I logon through X my env does not reflect the
variables in the /etc/profile. If I do the Ctrl-Alt-F1 to logon, then
the env reflects the contents of the /etc/profile. Does this make sense?
If so what is the xdm equivalent of /etc/profiles.
Any help would be greatly appreciated.


------------------------------

From: Dan Fraser <[EMAIL PROTECTED]>
Subject: Moonlighter needed - Orange County California
Date: Wed, 09 May 2001 22:41:01 -0700

We are looking for a Linux moonlighter in the Orange County area to help
us transfer a DOS batch file based industrial system to a Linux based
system. This is NOT a regular position and is not suitable for someone
who needs something to pay the rent. Payment will be in the form of very
low priced stock options in a public company that will be profitable by
August . Estimated time required to do the job is 50 hours depending on
your experience. Can lead to more contract work in future. 
I don't care about qualifications or how old you are. Students and
"hackers" welcome. If you know lot about setting up Linux machines,
specially script based units and can write the Linux equivalent of DOS
batch files, I can use your help.  Experience with Linmodem software 
(using a Winmodem under Linux) and getting PCI sound cards to work under
Linux will be helpful. We will supply dedicated machines for you to use.
We prefer to deal with someone who lives in Orange County, California or
nearby (LA or RIverside county) as there will be times personal contact
will be needed.
Call Dan at 714-420-7535 or after 5:30 in the evening at 714-637-5366.
-- 
Dan Fraser

>From the City of Orange in sunny California
714-637-5966 Cell 714-420-7535

Check out my electronic schematics site at: http://nav.to/techman10
If you are into cars check out www.roadsters.com

------------------------------

From: Yves Leung-Tack <[EMAIL PROTECTED]>
Subject: problem with Gcombust as normal user 
Date: Thu, 10 May 2001 02:56:50 -0400

Hi,


 When I try to run the gcombust I got these messages :

/usr/bin/cdrecord: Operation not permitted. WARNING: Cannot do
mlockall(2).
/usr/bin/cdrecord: WARNING: This causes a high risk for buffer
underruns.
/usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set
RR-scheduler
/usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using
setpriority().
/usr/bin/cdrecord: WARNING: This causes a high risk for buffer
underruns.
/usr/bin/cdrecord: Operation not permitted. shmctl failed to lock shared
memory segment


Does someone known how to fix this ?
As root, it works just fine. And I check that user is part of the
cdrom/cdwriter group ...


Merci !

------------------------------

From: [EMAIL PROTECTED] (michael james obrien)
Crossposted-To: alt.os.linux,comp.os.linux.misc
Subject: Re: Shutdown for non root users
Date: 9 May 2001 21:18:30 GMT

Harald Schneider ([EMAIL PROTECTED]) wrote:
: HI,

: how can I allow shutdown for non root users via remote (telnet) access?

: I know, this is VERY insecure, but in my special case (not connected to
: internet, admin user
: must not know the root pwd)  I need this feature.

: All the best,
: Harald

Have you tried changing the permissions of /sbin/halt to a+x  ?


------------------------------

From: "michael.fengler" <[EMAIL PROTECTED]>
Subject: Re: How to route email locally and externally?
Date: Thu, 10 May 2001 08:14:04 +0200
Reply-To: Michael Fengler <[EMAIL PROTECTED]>

On Thu, 10 May 2001, Mark Johnson wrote:

>Is it possible to configure our linux box such that it can determine
>whether to route an email locally or out to the relay host?
>
>For example, our company is provided by our ISP a domain name
>"foobarco.com" and 15 email address: [EMAIL PROTECTED], [EMAIL PROTECTED],
>etc...  All the employees run Win98 and Mac9 but we want to run linux as a
>file server and web server and possibly an email host.
>
>What we would like to do is when joe emails mary we would like that email
>to not out out to the ISP and then right back in, instead it should just
>realize that Joe and Mary are local users and deposit the email in there
>linux home account which they can access using their regular SMTP/POP3
>email client.  However, if Joe emails [EMAIL PROTECTED] then linux will
>relay the email to the ISP and everything continues as regular.

Sure thing. Using Postfix, I have the following in /etc/postfix/main.cf:
mydomain = my.domain.de
mydestination = $mydomain
masquerade = $mydomain
relayhost = smtp.my.provider.com
and a regular account for all (mail)users. This accepts all mails to
[EMAIL PROTECTED], rewrites From: lines to [EMAIL PROTECTED] for outgoing
mails and relais everything _not_ addressed to my.domain.de via my ISP.

- Mike


------------------------------

From: Yves Leung-Tack <[EMAIL PROTECTED]>
Subject: how to allow shutdown for a user ?? :)
Date: Thu, 10 May 2001 03:11:03 -0400

Hi, 


  I used Linux Mandrake 7.2 at HOME.
And I login as a normal user. But to shutdown I have to be root
I wonder how can I allow user to shutdown ???
It is "really" painful to type sum,  pwd, and finally shutdown !

I found nothing in man page ...except about a file shutdown.allow
But as user I cannot even use the command shutdown :((

Thanks a lot !

------------------------------


** 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.setup.

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-Setup Digest
******************************

Reply via email to