Linux-Setup Digest #941, Volume #20              Thu, 29 Mar 01 10:13:09 EST

Contents:
  Re: Bellsouth ADSL (Randy Switt)
  ANNOUNCE: loopslack (Kent Robotti)
  Re: RH7.* -- downgrading to gcc/g++ 2.95.3 (Carlos Moreno)
  Re: RH7.* -- downgrading to gcc/g++ 2.95.3 (Carlos Moreno)
  Re: Bellsouth ADSL (Eggert Ehmke)
  boot floppy corrupted - how to login now? ("Bill Jones")
  Re: RH7.* -- downgrading to gcc/g++ 2.95.3 (Steve Bradley)
  Re: Adaptec 19160 SCSI card support? (Joshua Baker-LePain)
  Re: Bellsouth ADSL (Rod Smith)
  fsck stops me booting ([EMAIL PROTECTED])
  console problem ([EMAIL PROTECTED])
  Re: RH7.* -- downgrading to gcc/g++ 2.95.3 ("ne...")
  looking for an FAQ ("SpiderFly")
  Re: boot floppy corrupted - how to login now? (Kevin Croxen)
  Re: NTP HowTo ("KW")
  SB Live! 1024 no midi emulation (Andy Collinson)
  Re: looking for an FAQ ("Davide Bianchi")

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

From: Randy Switt <[EMAIL PROTECTED]>
Crossposted-To: 
poster,ahn.tech.linux,alt.os.linux.mandrake,bellsouth.net.support.adsl,bellsouth.net.support.linux
Subject: Re: Bellsouth ADSL
Date: Thu, 29 Mar 2001 07:28:01 -0500

News Mail wrote:

> Help!!!
>
> We just got this ADSL and set up Linux Mandrake 7.2 but we can't get it
> connected. I did the "adsl-setup". Then "adsl-start" and get a "time-out"
> message. We are not sure but we may have an IRQ problem. What command can we
> use to see the list of IRQs?
>
> meesh32

What ADSL modem are you using?

Randy S.



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

From: Kent Robotti <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.slackware,comp.os.linux.misc
Subject: ANNOUNCE: loopslack
Date: Thu, 29 Mar 2001 12:32:30 -0000


=======================================================================
There's no linux packages or distribution at the site below, you
need to have or get a slackware linux distribution on cdrom.

There's a number of places you can get a slackware linux 
distribution on cdrom for as little as $2.

What you'll find here is the means to install a slackware
linux distribution from cdrom or hard drive (see installing
linux below).

The rootdisk "loopslak.bin" below, is based on the rootdisk 
"color.gz" from slackware 7.2 current.

The rootdisk now has ext3 and reiserfs (kernel 2.2 and 2.4) 
filesystem support.

The rootdisk also has umsdos and loop linux support, you can 
create a linux system with a ext2, ext3, or reiserfs filesystem 
on a dos/win9x partition, and boot it from there.

The loop linux system can't be larger than 2000mb, you can
enlarge or reduce the size of the system after you create it.

# loop_resize "From the rootdisk!"

The rootdisk can also be used as a rescue system, it has been 
updated and changed, but should work with any existing slackware 
bootdisks.

Read CHANGES below for more changes.

The present slackware bootdisks don't have ext3 or reiserfs support.
If you want a bootdisk with support for either of them, you would 
have to create it yourself.

This is an example of how to write a slackware boot and root 
disk to a 1.44mb formatted floppy, under dos and linux.

Create boot floppy!
C:\ rawrite2 bare.i a:
# dd if=bare.i of=/dev/fd0

Create root floppy!
C:\ rawrite2 loopslak.bin a: 
# dd if=loopslak.bin of=/dev/fd0

You can get slackware bootdisks at the slackware site or
on the slackware cdrom in the bootdsks.144 directory.

ftp://ftp.freesoftware.com/pub/linux/slackware/slackware/bootdsks.144

Read README.TXT at the above site!

You can get kernels "bzImage" here or on the slackware cdrom in
the kernels directory.

ftp://ftp.freesoftware.com/pub/linux/slackware/slackware/kernels

Read README.NOW at the above site!

You can create a bootdisk with the kernel of your choice.

The kernel must have "ram disk and initrd support", all slackware 
kernels have this.

The kernel should also have "loop device support" if you want to 
create a loop linux system, all slackware kernels have this.

Get "makedisk.zip" and unzip it.

Under dos/win9x you would do it this way.

C:\ pkunzip -d makedisk.zip
C:\makedisk> makedisk kernel "Create bootdisk!"

Under linux you would do it this way.

# unzip makedisk.zip
makedisk# chmod 755 makedisk.sh 
makedisk# makedisk.sh kernel "Create bootdisk!"

####################### Installing Linux! ##########################

Q. How do i install a slackware linux system?
A. Put the cd with the slackware distribution in the drive.

Use the boot and root floppies you created.

Put the boot floppy in the drive and restart your computer, 
at the boot prompt press enter, you'll be told when to INSERT 
the root floppy. 

If you don't want to use floppies you can boot "loopslak.bin"
from your dos/win9x system, using loadlin.exe.

C:\ loadlin kernel initrd=loopslak.bin root=/dev/ram0 rw

ftp://ftp.freesoftware.com/pub/linux/slackware/slackware/kernels/LOADLIN.EXE

After you boot the rootdisk you should run setup.

# setup

If you want to create a umsdos or loop linux system on a 
dos/win9x system, choose "Umsdos_loop" from the menu.

If you want to create a linux system on it's own partition, 
choose "Linux_native" from the menu.

Umsdos_loop   Install linux on a dos/win partition
Linux_native  Install linux on it's own partition

Chose LOOP_HELP or LINUX_HELP from the menu for help!.

When you run 'setup' you'll have the option of installing 
the slackware linux system, from cdrom or a directory on 
your dos/win9x system.

1 Install from a slackware CD-ROM   
etc.
3 Install from a pre-mounted directory "Read below!"

If you have a directory on you're dos/win9x system with the 
slackware packages (at least the a1 series), you could chose 
option 3 above and answer /mnt/slakware below.

Which would mean that you have \slakware\a1 \slakware\a2 
etc., on your dos/win9x system.
 
Which directory would you like to install from?
/mnt/slakware

########################### CHANGES! ##################################

These are some of the changes to the installation setup.

The addition of "menu express" and "expert express" modes.

"menu" mode puts up a menu at the start of each series of
packages, from which you can install systems such as
the GNU C/C++ compiler, or the Linux source code.  It's
easy to use, and makes installation go much faster than 
"newbie" mode.

"menu express" mode is the same as "menu", except it puts 
the menu for each package series up front, then installs 
your choices non-stop.  You can also go back over selected 
menus, if you want to make changes. 

"expert" mode is similar, but allows the toggling of every
individual package.  This offers the greatest control over
what gets installed on the machine, but can be tricky for
beginners.  

"expert express" mode is the same as "expert", except it puts 
the menu for each package series up front, then installs your
choices non-stop.  You can also go back over selected menus, 
if you want to make changes. 

The "cpkgtool" script from the slackware 7.2 current "hdsetup.tgz" 
package has been changed, it now has four new options, that's the 
only change.

# pkgtool

Convert  rpm or deb package to slackware tgz format
List     contents of rpm, deb, tar.gz, tgz, or tar.bz2 package
Monitor  make install and create record of install
Create   slackware package from /var/log/packages/package_name

You can convert x.rpm or x.deb packages to slackware x.tgz format.

Yow can monitor a command like "make install" and create a record 
of the install. 

The record will be put in /var/log/packages/package_name 
and can be removed like any installed package.

# removepkg package_name

You'll also have the option of creating a slackware tgz package 
of the install, after the install or later using /var/log/packages/
package_name as the guide.

Usually when you compile a package you do this, more or less.

# ./configure --prefix=/usr
# make
# make install

Instead of the "make install" step do 'pkgtool', and
chose monitor from the menu.

# ./configure --prefix=/usr
# make
# pkgtool

Do this to install it.

# installpkg cpkgtool.tgz
#######################################################################

You can get loopslak.bin, cpkgtool.tgz, makedisk.zip, and 
rawrite2.exe here.

http://www.tux.org/pub/people/kent-robotti/looplinux
ftp://ftp.tux.org/pub/people/kent-robotti/looplinux

loopslak.bin 1320kb
cpkgtool.tgz 23kb
makedisk.zip 14kb
rawrite2.exe 16kb

The license for the above is GPL.

Kent Robotti <[EMAIL PROTECTED]> (3-29-2001)

End!
=======================================================================

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

From: Carlos Moreno <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: Re: RH7.* -- downgrading to gcc/g++ 2.95.3
Date: Thu, 29 Mar 2001 08:27:05 -0500

Jacob Williams wrote:
> 
> couldn't you just use rpm -ivh --force gcc.whatever_version.rpm and not
> worry about uninstalling the old one... it should overwrite all the relevant
> files.... ( i believe )

Ok!  I didn't know about this option  (I was familiar 
with the --upgrade option, but I assume that it wouldn't 
work for downgrading...).  Ok, I'll experiment with 
that method...  Although according to a message that 
I received directly by e-mail, it is suggested that 
if the make bootstrap succeeds, then I should sleep 
in peace, since apparently the bootstrap procedure 
does perform a strict checking on the generated 
executables...  So maybe I should just compile it 
with gcc 2.96 and have some piece of mind?

Thanks a bunch!

Carlos
--

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

From: Carlos Moreno <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: Re: RH7.* -- downgrading to gcc/g++ 2.95.3
Date: Thu, 29 Mar 2001 08:31:18 -0500

Harald Arnesen wrote:
> 
> You have, of course, no guarantee that _any_ compiler will produce
> correct code.

:-)  (of course...  I'm aware of that -- it's just a matter of 
assumptions:  a compiler tag as experimental may or may not be 
stable, so we might as well assume that it is not.  And one 
tagged as official release may or may not, but we are better 
off assuming that it is stable, otherwise we would have to 
just hang our keyboards and retire  :-)   Or even worse, we 
would have to switch to Windows and MS products, but then, 
there we DO KNOW that things tagged as *official release* 
DO NOT work  :-))

> Compiling GCC goes as follows:
> 
> Stage 1: Compile the source with your current compiler.
> Stage 2: Compile the source with the compiler made in stage 1.
> Stage 3: Compile the source with the compiler made in stage 2.
> 
> The last two compilers are compared, and if they differ, something is
> wrong.

Woaw!  This is impressive -- well, pretty obvious, once you're 
told that this is what they do  :-) 

Ok, so I'll stop worrying about my paradox-like arguments 
and compile normally and sleep in peace  :-) 

Thanks!

Carlos
--

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

From: Eggert Ehmke <[EMAIL PROTECTED]>
Subject: Re: Bellsouth ADSL
Date: Thu, 29 Mar 2001 15:34:24 +0200
Reply-To: [EMAIL PROTECTED]

On Thu, 29 Mar 2001 03:38:32 -0600, "News Mail" <[EMAIL PROTECTED]> wrote:

>We just got this ADSL and set up Linux Mandrake 7.2 but we can't get it
>connected. I did the "adsl-setup". Then "adsl-start" and get a "time-out"
>message. We are not sure but we may have an IRQ problem. What command can we
>use to see the list of IRQs?

cat /proc/interrupts
cat /proc/iomem
cat /proc/ioports

--
Eggert Ehmke
Email: [EMAIL PROTECTED]

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

From: "Bill Jones" <[EMAIL PROTECTED]>
Subject: boot floppy corrupted - how to login now?
Date: Thu, 29 Mar 2001 08:37:16 -0500

I did not install lilo with my install of Redhat 7.0.  Been using it for
months successfully, and now all of a sudden, booting with the floppy no
longer works.  It gets to the boot: prompt, and then just says something
like "Error 0x0" (not sure if that's the exact msg).

I had installed linux on my previous PC about 5 years ago, and always used a
boot floppy, and it never failed.  So I never wanted to use lilo.

I'm sure if I could get logged in, I could make another boot floppy using
mkbootdisk, but how can I boot linux now?  When I try the Redhat boot
floppy, it always goes into Installation Mode, no matter what parameters I
use.  I've tried stuff like "linux single root=/dev/hda1" and "linux
rescue", but nothing works.



--
<remove 7of9 for e-mail replies>

--
Bill Jones                 e-mail addresses:
Computer Sciences Corp.         (work)  [EMAIL PROTECTED]
Norwich, Connecticut            (play)  [EMAIL PROTECTED]
(860) 701-1201     WWW:  http://pages.cthome.net/billj




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

From: Steve Bradley <[EMAIL PROTECTED]>
Subject: Re: RH7.* -- downgrading to gcc/g++ 2.95.3
Crossposted-To: comp.os.linux.development.apps
Date: Thu, 29 Mar 2001 13:38:03 GMT

FWIW,  I've compiled almost everything that I've put on my system beyond the 
base RH7 install, and my own creations, with 2.96 and haven't had any 
problems. The code executes fine, the system is stable.

Steve

Carlos Moreno wrote:

> 
> The chicken or the egg??  (or chasing my own tail??)
> 
> I'm wondering what would be the correct procedure to downgrade
> from gcc/g++ 2.96 to the latest *official* release, 2.95.3

-- 
Steve Bradley
[EMAIL PROTECTED]

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

From: Joshua Baker-LePain <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Re: Adaptec 19160 SCSI card support?
Date: 29 Mar 2001 13:44:09 GMT

In comp.os.linux.hardware Melvin Gators <[EMAIL PROTECTED]> wrote:
> Do these SCSI cards work well under linux?

I don't have any *direct* experience with 19160s, but I've got about 4
boxes with onboard AIC-7899 based U160 controllers.  That should be
the same chip the 19160 uses.  They work great with the standard aic7xxx
module.  The one caveat is that there seems to be an issue with Quantum
drives which causes them to negotiate at 80MB/s rather than 160.  That's
not really a concern unless you've got a bunch of them on the chain.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

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

From: [EMAIL PROTECTED] (Rod Smith)
Crossposted-To: bellsouth.net.support.linux
Subject: Re: Bellsouth ADSL
Date: Thu, 29 Mar 2001 13:48:16 -0000
Reply-To: [EMAIL PROTECTED]

[Posted and mailed]

In article <6uDw6.2219$[EMAIL PROTECTED]>,
        "News Mail" <[EMAIL PROTECTED]> writes:
> Help!!!
> 
> We just got this ADSL and set up Linux Mandrake 7.2 but we can't get it
> connected. I did the "adsl-setup". Then "adsl-start" and get a "time-out"
> message. We are not sure but we may have an IRQ problem. What command can we
> use to see the list of IRQs?

You may or may not even be going at this in the right way. There are two
factors that are critically important for deciding how to configure
Linux to use a DSL connection, or even if it's possible:

1) The type of modem. To use Linux, it's best to have an external
   Ethernet-interfaced modem. I've heard of drivers for one internal
   modem (the Diamond 1MM; links are on my Web page at
   http://www.rodsbooks.com/network/network-dsl.html), and I believe
   drivers are now available for one USB model (try doing a Web search
   or a search on http://groups.google.com using keywords like "Linux",
   "DSL", and "USB"). If you've got some non-supported internal or USB
   modem, forget it. You *MUST* replace the modem or write your own
   drivers.
2) The IP address assignment method. Common options are static IP
   addresses, DHCP, and PPPoE. The first two use standard Linux
   networking configuration methods. PPPoE requires special software.
   Again, links are on my Web page; but it sounds like you've already
   installed one (probably Roaring Penguin). This may or may not be
   necessary, depending upon your ISP.

*AFTER* you've determined that your hardware is supported and that you
really should be using PPPoE, consider looking for hardware conflicts or
the like. As a general rule, though, when you run into problems like
this you should check your log file -- usually /var/log/messages. This
should contain some clues as to why the connect command failed.

-- 
Rod Smith, [EMAIL PROTECTED]
http://www.rodsbooks.com
Author of books on Linux & multi-OS configuration

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

From: [EMAIL PROTECTED]
Subject: fsck stops me booting
Date: 29 Mar 2001 13:54:25 GMT

hi there

I recently installed redhat gnu/linux 7.0 and after getting a corrupted 
filesystem, my machine wouldn't boot.
i got a prompt saying:

Control-D for normal bootup or root password to run fsck

this is ok if the problem is on a desktop machine, but on a 
server it's not good.

how can i get linux to automatically run fsck if it find problems 
without me having to be at the server and give the root password
 or type Control-D?

any help greatly appreciated

thanks

Amanda


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

From: [EMAIL PROTECTED]
Subject: console problem
Date: 29 Mar 2001 13:59:35 GMT

hi there

I have tried to get a console working on a linux server (serial port) and have 
almost got there.

I can see the bootup messages from the kernal until it gets to

freeing up memory ...etc

then is stops until it finishes booting up and I get the login prompt.

what I'd like to see at the console is /everything/ between freeing up
kernel mem to the login prompt

here is my lilo.conf

serial=0,9600n8
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=300
default=linux
password=********
vga=normal

image=/boot/vmlinuz-2.2.18
        label=linux
        read-only
        root=/dev/hda4
        restricted
        append="console=ttyS0 console=tty0"


what am i doing wrong here?

thanks

amanda







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

Crossposted-To: comp.os.linux.development.apps
From: "ne..." <[EMAIL PROTECTED]>
Subject: Re: RH7.* -- downgrading to gcc/g++ 2.95.3
Date: Thu, 29 Mar 2001 13:59:39 GMT

On Mar 29, 2001 at 08:31, Carlos Moreno eloquently wrote:

>Harald Arnesen wrote:
[...]
>> Compiling GCC goes as follows:
>>
>> Stage 1: Compile the source with your current compiler.
>> Stage 2: Compile the source with the compiler made in stage 1.
>> Stage 3: Compile the source with the compiler made in stage 2.
>>
>> The last two compilers are compared, and if they differ, something is
>> wrong.
>
>Woaw!  This is impressive -- well, pretty obvious, once you're
>told that this is what they do  :-)
You do know that this is in the documentation which we
expect you read?

-- 
Registered Linux User # 125653 (http://counter.li.org)
Flame on!
                -- Johnny Storm
  8:55am  up 12 days,  9:54,  9 users,  load average: 0.00, 0.00, 0.00


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

From: "SpiderFly" <[EMAIL PROTECTED]>
Subject: looking for an FAQ
Date: Thu, 29 Mar 2001 14:26:25 GMT

Is there an FAQ for this News Group?

    I have just completed building my 7th Windows machine and want to
install Linux onto machine number 5. to try it out and may be converted. I'm
looking for answers to the normal, where can I get it, how do I install it,
what do I need to know, how can I get to the internet through and Win98
Internet sharing server machine, what hardware problems could I have. I'm
hoping to use my K6-500Mhz 128Mb 30Gb machine will this be ok?

Thanks for the help,
    Ad.



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

From: [EMAIL PROTECTED] (Kevin Croxen)
Subject: Re: boot floppy corrupted - how to login now?
Date: 29 Mar 2001 14:02:28 GMT

The short answer is to make yourself a new boot floppy to access
your partition. Now I don't use RedHat, so whether there's a simple
way to do this from RedHat's media is a complete mystery to me.

However, one very simple way to make a disk to recover with would be
to use your favorite DOS/Win box to download and rawrite a single
Slackware bootdisk which you can use to boot your Linux partition from
as normal, and then you may create a proper RedHat floppy or install
LILO, as you prefer.

>From ftp.freesoftware.com, download the single Slackware bootdisk image
"bare.i" :     

ftp.freesoftware.com/pub/linux/slackware/slackware-current/bootdsks.144/bare.i

Use the DOS utility rawrite (available online from the same directory) to 
write this boot image to a floppy.   (rawrite boot.i  a:)

Boot from this floppy. At the point where the floppy asks for boot
parameters, point it toward your RedHat partition.

mount root=/dev/hda1

And away you go. After RedHat is booted, make your usual floppy or 
whatever. 

Mandatory installation routine when booting from RedHat media? Yet
another reason I'm glad I don't use the distro.

Cheers,

--Kevin




In article <xTGw6.6227$[EMAIL PROTECTED]>, Bill Jones wrote:
>I did not install lilo with my install of Redhat 7.0.  Been using it for
>months successfully, and now all of a sudden, booting with the floppy no
>longer works.  It gets to the boot: prompt, and then just says something
>like "Error 0x0" (not sure if that's the exact msg).
>
>I had installed linux on my previous PC about 5 years ago, and always used a
>boot floppy, and it never failed.  So I never wanted to use lilo.
>
>I'm sure if I could get logged in, I could make another boot floppy using
>mkbootdisk, but how can I boot linux now?  When I try the Redhat boot
>floppy, it always goes into Installation Mode, no matter what parameters I
>use.  I've tried stuff like "linux single root=/dev/hda1" and "linux
>rescue", but nothing works.
>
>
>
>--
><remove 7of9 for e-mail replies>
>
>--
>Bill Jones                 e-mail addresses:
>Computer Sciences Corp.         (work)  [EMAIL PROTECTED]
>Norwich, Connecticut            (play)  [EMAIL PROTECTED]
>(860) 701-1201     WWW:  http://pages.cthome.net/billj
>
>
>

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

From: "KW" <[EMAIL PROTECTED]>
Subject: Re: NTP HowTo
Crossposted-To: alt.os.linux,linux.redhat,redhat.kernel.general
Date: Thu, 29 Mar 2001 08:34:58 -0600

My fault,  there is another line you have to run, but for the life of me
I can't remember it...  A quick search reveals the answer is....


hwclock   --synctohc   

add that as well ;) and all should be well....




In article <[EMAIL PROTECTED]>, "Zorc"
<[EMAIL PROTECTED]> wrote:

> Look at http://www.eecis.udel.edu/~ntp/. There you'll get what you want.
> 
> Never use just ntpdate, ntpdate sets the time 'hard' and doesn't set the
> hwclock.
> 
> zorc
> 
> SS wrote:
> 
>> Ok..  I got a really silly question.  I'm trying to setup my Linux box
>> to automatically synth with one of those atomic clock.  But I'm not
>> able to find any HowTo doc on this subject.
>>
>> Can someone tell me how I can setup this automatic time synth?  Let
>> say, the system will check the time every hour or 15 minutes...
>>
>> Thanx
>>
>> Sam
>

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

From: Andy Collinson <[EMAIL PROTECTED]>
Subject: SB Live! 1024 no midi emulation
Date: Thu, 29 Mar 2001 16:06:32 +0100


Im using SuSe 7.1 kernal 2-4-0 and running KDE 2.0.1  MY sound blaster Live 
PCI card will play wave files, CD audio and emulate midi using kmidi.
However when i look at kde control center it tells me that my sound card is 
using ALSA drivers 0.5.1a and that SYNTH devices are NOT enabled in CONFIG.
If this is the problem please can someone point me in the right direction 
or refer to a doc source. Thanks in advance

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

From: "Davide Bianchi" <[EMAIL PROTECTED]>
Subject: Re: looking for an FAQ
Date: Thu, 29 Mar 2001 10:05:22 -0800

"SpiderFly" <[EMAIL PROTECTED]> wrote in message
news:lCHw6.22187$[EMAIL PROTECTED]...
> Is there an FAQ for this News Group?

You can found a lot of Faqs and other info at
www.linuxdoc.org

Davide




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


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