Linux-Setup Digest #461, Volume #20              Sat, 20 Jan 01 21:13:09 EST

Contents:
  Re: Very New to Linux (Dave Wegher)
  Re: Help supported NIC cards don't work on Red Hat 7.0 (David)
  RH7 not recognizing NIC (Carlos Moreno)
  Re: Kernel 2.4-long-post-caution ("Sri Panyam")
  Re: Kernel 2.4 (Steve Martin)
  Re: Help supported NIC cards don't work on Red Hat 7.0 ([EMAIL PROTECTED])
  Re: Kernel 2.4 (Steve Martin)
  Re: Kernel 2.4 PPP Support (Steve Martin)
  Re: Kernel 2.4-long-post-caution (olgnuby)
  Re: Killed my CDROM - Help! (Steve Martin)
  Help installing KDE 2.0 (Arctic Storm)
  Re: Why no real-support for ext2fs by DriveImage et al. ? (Frederic Faure)
  Re: HELP!!Only the L appears in LILO ("Coral J. Cook Jr.")
  Re: Kernel 2.4 ("Sri Panyam")
  Re: HELP!!Only the L appears in LILO (Correction) ("Coral J. Cook Jr.")
  Re: HELP!!Only the L appears in LILO ("Aaron")
  why can't modprobe find the module? (Dave Brondsema)
  RPM supports only package rev <= 3 (Swapnajit Mittra)
  Re: SAMBA not working on RH7 on peer to peer win2k network using DHCP from maxgate 
switch/router ("Cameron Kerr")
  Re: PPPSETUP (Harry)

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

From: [EMAIL PROTECTED] (Dave Wegher)
Subject: Re: Very New to Linux
Date: 21 Jan 2001 00:10:10 GMT

[EMAIL PROTECTED] wrote:

> Ok what i want to do is very simple i bet but i cannot figure it out
> for the life of me, Im running Redhat 6.2

> I have a compaq deskpro 6000
> 1 IDE and 1 SCSI drive
> A built in Netflex NIC and a 3com NIC
> A matrox Millenium video card 4MB

> What i want to do is the following

> I want to know how to change video resolution?
> change it from 800x600 to 1024x768 i cang figure it out
> also where are the network card settings so i can see if the cards are
> there?

I'm probably as new to Linux as as you, but this worked for me using Corel
Linux and the KDE desktop.  From your xwindows desktop, click the program
start icon, then control center, then desktop, then video settings. This
let me change resolutions and refresh rates.  Good luck.

I haven't a clue about the network stuff.

Good Luck.




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

From: David <[EMAIL PROTECTED]>
Subject: Re: Help supported NIC cards don't work on Red Hat 7.0
Date: Sun, 21 Jan 2001 00:14:13 GMT

Brian Donaldson wrote:
> 
> I have installed Red hat 7.0 about 5 times now and it still doesn't detect
> ethier of my nic cards.  The cards are 3com 3c905b-tx or D-Link - 538TX.  Is
> there alway to probe for them after installing my OS?


Check to see if there is a line like this in /etc/modules.conf

 alias eth0 3c59x  # this is for the 3com 905b

If it isn't there then look in /lib/modules/x.x.xx/net I think and see
if the module exists. If it does then add the line above to modules.conf
and configure and restart the network.

 /etc/rc.d/init.d/network restart

You can use "netcfg" to configure the network if you are running X or
"ifconfig" from a text console or X.

-- 
Confucius say: He who play in root, eventually kill tree.
Registered with the Linux Counter.  http://counter.li.org
ID # 123538
Completed more W/U's than 99.005% of seti users. +/- 0.01%

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

From: Carlos Moreno <[EMAIL PROTECTED]>
Subject: RH7 not recognizing NIC
Date: Sat, 20 Jan 2001 19:09:34 -0500


Hi there,

I'm upgrading from RH6.2 to RH7, and the NIC is not recognized 
by the RH7 installation program.  Given that I know that the 
card is a NE2K clone (it was recognized by RH6.2 as a ne2k-pci), 
is there anything I can do to force the configuration to include
a ne2k-pci network card?   (BTW, the card is a D-Link DE-528CT)

I tried with linuxconf, but it didn't work;  I also tried with 
the insmod command, but I am clueless about how to use it, or if 
it is the right thing to do -- it only gives me error messages 
when I attempt it.

Any help/ideas/pointers greatly appreciated!

Thanks,

Carlos
--

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

From: "Sri Panyam" <[EMAIL PROTECTED]>
Subject: Re: Kernel 2.4-long-post-caution
Date: Sun, 21 Jan 2001 11:34:30 +1100

Hi


    Aah but by copying the System.map to /boot (which already has a 'sym
link'ed System.map to System.map-old-version), i would loose my old map.
Which means that at the lilo prompt, I would not be able to revert to my
"old" kernel in case something goes wrong.  Is there  a way I could have
both the map files and be able to use each one as i need.  I mean can is
there a way of telling lilo to use the old System.map file for the old
kernel and System.map.new file for the new kernel?

Thanks
Sri
olgnuby <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]...
> Sri Panyam wrote:
> >
> > Hi
> >
> >   I just compiled version 2.4 of the kernel and was able to create a
boot
> > iamge successfully :- bzImage.
>
> Looks like the thread has accumulated a lot of advice and similar
> problems, and I guess like the thread the other day on where to unpack
> the new kernel and the new README that is included with the new 2.4.0
> kernel, which to me is like so much of the documentation written by
> coders and programers who forget they aren't writing machine language
> for instructions to a machine, but a set of steps to follow for ordinary
> human beings to understand and follow, and supposedly a remark by Linus
> some place has a few people confused.
>
> So I may as well add to the confusion...
>
> So, I'll do my disclaimer. I don't know if this the right way or not,
> but it's the way that has worked for me for about three or four years on
> a number of different Linux distributions.
>
> Put your kernel package, be it .tgz or .bz2 in the top level directory
> you plan to use it from and unpack it. If you do it in the conventional
> /usr/src director, be aware that there is probably already a symbolic
> link /usr/src/linux that points to the directory that your distribution
> placed your original kernel headers and sources, or headers as the case
> may be and that regardless where you put it and unpack it, unless you do
> some major gymnastics, it is by default going to unpack into a sub
> directory called /linux if the directory or a link is already there, or
> create the /linux directory. To preclude it from unpacking into and
> getting mixed in with the old headers or from wiping out your original
> kernel sources, examine your /usr/src directory and if the link is there
> and if you choose to compile and install from /usr/src/linux, first
> remove the old link. If your /usr/src/linux is not a link, but an actual
> directory, rename it temporarily to /linux.old or something and then
> unpack your kernel. You will wind up with a /usr/src/linux directory
> that contains your new kernel.
>
> Okay, here is where some of this stuff is Bill Ball from a number of
> years back and some is Charlie from experience.
>
>
> I change the name of the new /linux directory to /linux-2.4.0, then
> create a new symbolic link, by (cd /usr/src or
> /home/me/bathroom/stall_2/ or whatever was your choice of compile and
> install place) and execute (ln -s /linux-2.4.0 linux) For me this gives
> the ppp-2.4, modutils and other stuff that I'll probably need to use the
> new kernel directions on how to find it if need be.
>
> I then just su to root privileges and do:
>
> cd /usr/src/linux
>
> Read every readme and doc file you can find in the to level and all the
> sub directories. ;-)
>
> make mrproper
>
> make xconfig
>
> After configuring my kernel for what I want in it and tailoring it to my
> own needs, I save it and exit xconfig and do
>
> make dep
>
> Here rather than fart around with all the other methods, because rarely
> are you going to come up with a kernel that will fit by making zImage, I
> simply always use:
>
> make bzImage
>
> Instructions from past say at this point to do a:
> make clean
> but recent instructions seem to have omitted this. I haven't used it
> lately and haven't had any problems "yet" <YMMV> then:
>
> make modules
>
> At this point, (why? because it works for me every time ;-)), I do a:
>
> cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.4.0
>
> cp /usr/src/linux/System.map /boot/System.map-2.4.0
>
> cd /boot
>
> examine your /boot directory and determine if the file /boot/System.map
> is a symbolic link to /boot/map or
> /boot/System.map-old-shit-or-what-ever and if it is, do a
>
> rm System.map
>
> ln -s System.map-2.4.0 System.map
>
> cd /usr/src/linux
>
> make modules_install
>
> If you have upgraded to the new, latest and greatest modutils, the make
> modules_install will do all the gymnastics of creating the dependency
> files in the /lib/modules/2.4.0 or whatever and in you modules directory
> it will place a link back to your build directory and all that shit in
> addition to all your new module directories.
>
> Edit the /etc/lilo.conf file depending on your system and point your map
> to /boot/System.map and set your image to /boot/vmlinuz-2.4.0 then run
>
> /sbin/lilo
>
> and if all went well, you should get the message that all your boot
> options have been added and written.
>
> At this point, you should, I reiterate should, because like the old
> chief in "Little Big Man" "Some days the magic works, some days it
> don't" be able to do a
>
> shutdown -r now
>
> and you should reboot with the roar of a 2.4.0 in all it's glory or
> gory, and you may get lucky and even get a petite lil penguin and not
> have to go through the shit of watching forty miles of Modules not found
> or other shit kind
> of errors on boot up.
>
> Then unless you're a programmer or developer...
>
> If it all works, do a http://www.freebsd.org and do something that is a
> real challenge and do like I do, run Linux Netscape 4.76 and StarOffice
> 5.2 and all that good stuff under FreeBSD 4.2 and have DOSEMU and Wine
> and ??? What the hell am I doing using NotePad to edit this with. Isn't
> that what I was trying to get away from in the first place... ;-)
>
> 'cause that's all there is. Nothing more.
>
> nuther disclaimer... I'm not really a linux lover, not a geek, just a 60
> year old fart goat roper who found a RedHat 5.0 cd in a library book a
> few years ago and got curious, and if I can compile a kernel than damn
> it, any body ought.
>
> Charlie
>
> --
> "Laughter is the best laxative there is for a constipated mind. Humor is
> an ideal spoon to dose it."
>  --Chronocidal Charlie, 1995-2000, RIP.--
>



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

From: Steve Martin <[EMAIL PROTECTED]>
Subject: Re: Kernel 2.4
Date: Sun, 21 Jan 2001 00:32:16 GMT

Sri Panyam wrote:
> 
> Hi
> 
>     I copied the new boot image with along with the new System.map files to
> /bootnew/ (instead of / ) and in lilo.conf, i changed the image from
> /boot/bzImage.myker to /bootnew/bzImage.myker.  However, I am still having
> the same problem.  Is there anything else i need to do?

I believe in asking the stupid questions first to get them out of the
way.
You *did* re-run lilo after changing lilo.conf to activate the changes,
didn't you?

One other thing occurs to me. This may be a problem depending on which
version of Lilo you have. Is the kernel located within the first
1024 cylinders of the hard drive? The latest version of Lilo works okay
without this restriction, but it can cause problems if your boot-up
partition (in your case, /bootnew/) is located outside the 1024-cylinder
limit.

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

From: [EMAIL PROTECTED]
Subject: Re: Help supported NIC cards don't work on Red Hat 7.0
Date: Sun, 21 Jan 2001 00:29:17 GMT

I'm having that EXACT same problem.  I cannot get RH 7 to recognize my
905b!  I have tried downloading the driver from 3com's website here:
http://support.3com.com/infodeli/tools/nic/3c905b.htm but it says that
the driver was not designed for my Kernel version and that I need to
compile it myself.  I'm not sure how to do this.


Sent via Deja.com
http://www.deja.com/

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

From: Steve Martin <[EMAIL PROTECTED]>
Subject: Re: Kernel 2.4
Date: Sun, 21 Jan 2001 00:40:39 GMT

"ne..." wrote:

> >the same problem.  Is there anything else i need to do?

> Yes, rename the kernel. It should be vmlinuz-2.4.0.

Nope, this is not necessary. As long as the entry in
lilo.conf is the same as the name of the kernel file,
it can be anything. I'm booting from a 2.4 kernel
contained in a file called "/vmlinuz". In fact, there
is code in /usr/src/linux/arch/i386/boot/Makefile to
copy the new kernel to $(INSTALL_PATH)/vmlinuz
upon successful build. INSTALL_PATH is set in the
top-level Makefile; it's normally commented out,
with the notation to un-comment it if it is desired
to install the new kernel in a directory other than
the root directory.

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

From: Steve Martin <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,alt.os.linux.suse,comp.os.linux
Subject: Re: Kernel 2.4 PPP Support
Date: Sun, 21 Jan 2001 00:44:31 GMT

Costas Gavardinas wrote:
> 
> I have installed and compiled the new 2.4 kernel. Although I selected ppp
> support from the appropritate menus, I get an error: ppp support not
> installed in kernel, or something similar. Is there something I am doing
> wrong?? Thanks for any clues!
> Costas

Ran into the same problem here, almost drove me nuts. Turned out
to be a bad case of RTFM.

In /usr/src/linux/Documentation/Changes, it mentions that the new
PPP works differently. You must (a) upgrade pppd to at least
version 2.4.0b1, and (b) either be using devfs, or else you must
manually create a device file /dev/ppp with the command

  mknod /dev/ppp c 108 0

as the superuser.

Once I made the /dev/ppp special file, ppp miraculously began
working like a charm.

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

From: olgnuby <[EMAIL PROTECTED]>
Subject: Re: Kernel 2.4-long-post-caution
Date: Sun, 21 Jan 2001 00:47:51 GMT

Sri Panyam wrote:
> 
> Hi
> 
>     Aah but by copying the System.map to /boot (which already has a 'sym
> link'ed System.map to System.map-old-version), i would loose my old map.
> Which means that at the lilo prompt, I would not be able to revert to my
> "old" kernel in case something goes wrong.  Is there  a way I could have
> both the map files and be able to use each one as i need.  I mean can is
> there a way of telling lilo to use the old System.map file for the old
> kernel and System.map.new file for the new kernel?


What I said ;-)

> > At this point, (why? because it works for me every time ;-)), I do a:
> >
> > cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.4.0
> >
> > cp /usr/src/linux/System.map /boot/System.map-2.4.0
> >
> > cd /boot
> >
> > examine your /boot directory and determine if the file /boot/System.map
> > is a symbolic link to /boot/map or
> > /boot/System.map-old-shit-or-what-ever and if it is, do a
> >
> > rm System.map
> >
> > ln -s System.map-2.4.0 System.map
> >
> > cd /usr/src/linux
> >
> > make modules_install

and I repeat ;-)

> > cp /usr/src/linux/System.map /boot/System.map-2.4.0
> >
> > cd /boot
> >
> > examine your /boot directory and determine if the file /boot/System.map
> > is a symbolic link to /boot/map or
> > /boot/System.map-old-shit-or-what-ever and if it is, do a
> >
> > rm System.map
> >
> > ln -s System.map-2.4.0 System.map

If it doesn't work, you can rm the sym link /boot/System.map and make a
new sym link to your old map or System.map-old-what-ever that will still
be in /boot intact.

To be completely safe do;

mkbootdisk -dev /dev/fd0(or what ever your floppy is) (old kernel in
format 2.2.12-1) for example mkbootdisk -device /dev/fd0 2.2.12-1 to
boot to your old kernel and map if necessary.

Of course, you will need a formatted floppy in your floppy drive for
best results.

G'nite

Charlie

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

From: Steve Martin <[EMAIL PROTECTED]>
Subject: Re: Killed my CDROM - Help!
Date: Sun, 21 Jan 2001 00:48:41 GMT

"Mark R. Holbrook" wrote:

> 
> So I checked to see if /dev/cdrom was linked to the CD:   ls -lga
> /dev/cdrom:
> 
> lrwxrwxrwx    1 root     root            3 Jan 16 03:41 /dev/cdrom ->
> hdc

Nope. Remove this link and create a new one linking /dev/cdrom to
/dev/scd0.
Your IDE CD-ROM drive shows up as /dev/scd0 under SCSI emulation.

When you recompiled your kernel, did you include SCSI CD-ROM support?

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

From: Arctic Storm <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Help installing KDE 2.0
Date: Sun, 21 Jan 2001 00:53:08 GMT

I just downloaded KDE 2.0 RPM's.
It's approximately 26 files; all RPM's.
I issued the following commands.
rpm -Uvh qt*
rpm -Uvh lib*
rpm -Uvh htdig*
So far so good.
And then I tried issuing the following command.
rpm -Uvh kde*
I got tons of failed dependencies errors.
Any help?

----


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

From: [EMAIL PROTECTED] (Frederic Faure)
Subject: Re: Why no real-support for ext2fs by DriveImage et al. ?
Date: Sun, 21 Jan 2001 00:45:58 GMT

On Fri, 19 Jan 2001 10:28:59 +0100, media factory
<[EMAIL PROTECTED]> wrote:
>Could you please explain what TomsRtBt is?

        It's one of of those stand-alone Linux floppies with a bunch
of drivers. Don't remember the URL, so google.com -> tomsrtbt

>As far as I understand, diskimages cannot include more than one partition.
>That means, that restoring a disk image does not touch the MBR and partition
>table. Partitioning has to be setup before. And MBR must reflect where your
>kernel (in case of Linux) can be found.

        In that case, how come restoring an image on a brand new HD
still works? How maybe disk cloners save the MBR without telling the
user? Or maybe the MBR is overwritten only if restoring an image that
was on the first partition?

To get back to the topic of this thread :-) What is so special about
ext2fs that cloning SW have a hard time handling it while they work
fine with FAT16, FAT32, NTFS?

FF.

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

From: "Coral J. Cook Jr." <[EMAIL PROTECTED]>
Crossposted-To: 
comp.os.linux,comp.os.linux.hardware,comp.os.linux.help,comp.os.linux.misc
Subject: Re: HELP!!Only the L appears in LILO
Date: Sun, 21 Jan 2001 00:58:28 GMT

Bindou,

I don't know how you can have a primary "slave" disk without having a
primary "master" disk...I think this is problem. In any case, it sounds like
your master boot record is hosed. to correct and be able to boot up into
Windows, boot to a dos/windows floppy, or a windows CD, then exit out of
system. You should then be able to enter the command:

fdisk/mbr

This should fix your master boot record. Now reboot the computer and you
should come up into Windows.

Coral




"bindou" <[EMAIL PROTECTED]> wrote in message
news:94ctuh$6t1$[EMAIL PROTECTED]...
> Help!.
> I have installed linux redhat 7.0 on a computer running windows me an i
get
> the following problem when i restart the computer:
> only L appears when booting and the screen freeze.
> i have installed it on a primary slave disk.
> Note that the computer does not have a primary master disk
> Also i have tried to modify the lilo.conf found in by removing linear and
> putting lba32,but when i type lilo it gives the following warning:
> /dev/hdb is not the first disk.
> I have also tried to copy the boot.b and map file from the linux boot
floppy
> but without results.
>
> Any help please as i cannot even boot on the Windows System
>
> Rgds
>
> Jbk
>
>



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

From: "Sri Panyam" <[EMAIL PROTECTED]>
Subject: Re: Kernel 2.4
Date: Sun, 21 Jan 2001 12:16:30 +1100

Hi

    Yep i ran lilo each time after the change was made to lilo.conf.  How
can i find out the cylinder at which the kernel is located?

Sri
Steve Martin <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Sri Panyam wrote:
> >
> > Hi
> >
> >     I copied the new boot image with along with the new System.map files
to
> > /bootnew/ (instead of / ) and in lilo.conf, i changed the image from
> > /boot/bzImage.myker to /bootnew/bzImage.myker.  However, I am still
having
> > the same problem.  Is there anything else i need to do?
>
> I believe in asking the stupid questions first to get them out of the
> way.
> You *did* re-run lilo after changing lilo.conf to activate the changes,
> didn't you?
>
> One other thing occurs to me. This may be a problem depending on which
> version of Lilo you have. Is the kernel located within the first
> 1024 cylinders of the hard drive? The latest version of Lilo works okay
> without this restriction, but it can cause problems if your boot-up
> partition (in your case, /bootnew/) is located outside the 1024-cylinder
> limit.



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

From: "Coral J. Cook Jr." <[EMAIL PROTECTED]>
Crossposted-To: 
comp.os.linux,comp.os.linux.hardware,comp.os.linux.help,comp.os.linux.misc
Subject: Re: HELP!!Only the L appears in LILO (Correction)
Date: Sun, 21 Jan 2001 01:22:17 GMT

Correction!!! The command to run is:

fdisk /mbr

fdisk (space) /mbr ...I omitted the space between "fdisk" and "/mbr" in the
original post.

Coral


"Coral J. Cook Jr." <[EMAIL PROTECTED]> wrote in message
news:Uuqa6.12114$[EMAIL PROTECTED]...
> Bindou,
>
> I don't know how you can have a primary "slave" disk without having a
> primary "master" disk...I think this is problem. In any case, it sounds
like
> your master boot record is hosed. to correct and be able to boot up into
> Windows, boot to a dos/windows floppy, or a windows CD, then exit out of
> system. You should then be able to enter the command:
>
> fdisk/mbr
>
> This should fix your master boot record. Now reboot the computer and you
> should come up into Windows.
>
> Coral
>
>
>
>
> "bindou" <[EMAIL PROTECTED]> wrote in message
> news:94ctuh$6t1$[EMAIL PROTECTED]...
> > Help!.
> > I have installed linux redhat 7.0 on a computer running windows me an i
> get
> > the following problem when i restart the computer:
> > only L appears when booting and the screen freeze.
> > i have installed it on a primary slave disk.
> > Note that the computer does not have a primary master disk
> > Also i have tried to modify the lilo.conf found in by removing linear
and
> > putting lba32,but when i type lilo it gives the following warning:
> > /dev/hdb is not the first disk.
> > I have also tried to copy the boot.b and map file from the linux boot
> floppy
> > but without results.
> >
> > Any help please as i cannot even boot on the Windows System
> >
> > Rgds
> >
> > Jbk
> >
> >
>
>



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

From: "Aaron" <bombarumba@hot*SpamMeNot*mail.com>
Crossposted-To: 
comp.os.linux,comp.os.linux.hardware,comp.os.linux.help,comp.os.linux.misc
Subject: Re: HELP!!Only the L appears in LILO
Date: Sat, 20 Jan 2001 20:30:06 -0500

also, make sure your linux boot partition is within the starting 1024
cylinders (1024? i'm not sure... keep it somewhere in the beginning) of your
hard disk.

you can only boot from a primary partition, and it has to be within the
first 1024 cylinders of your disk.

:)


==================


"Coral J. Cook Jr." <[EMAIL PROTECTED]> wrote in message
news:Uuqa6.12114$[EMAIL PROTECTED]...
> Bindou,
>
> I don't know how you can have a primary "slave" disk without having a
> primary "master" disk...I think this is problem. In any case, it sounds
like
> your master boot record is hosed. to correct and be able to boot up into
> Windows, boot to a dos/windows floppy, or a windows CD, then exit out of
> system. You should then be able to enter the command:
>
> fdisk/mbr
>
> This should fix your master boot record. Now reboot the computer and you
> should come up into Windows.
>
> Coral
>
>
>
>
> "bindou" <[EMAIL PROTECTED]> wrote in message
> news:94ctuh$6t1$[EMAIL PROTECTED]...
> > Help!.
> > I have installed linux redhat 7.0 on a computer running windows me an i
> get
> > the following problem when i restart the computer:
> > only L appears when booting and the screen freeze.
> > i have installed it on a primary slave disk.
> > Note that the computer does not have a primary master disk
> > Also i have tried to modify the lilo.conf found in by removing linear
and
> > putting lba32,but when i type lilo it gives the following warning:
> > /dev/hdb is not the first disk.
> > I have also tried to copy the boot.b and map file from the linux boot
> floppy
> > but without results.
> >
> > Any help please as i cannot even boot on the Windows System
> >
> > Rgds
> >
> > Jbk
> >
> >
>
>



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

From: Dave Brondsema <[EMAIL PROTECTED]>
Subject: why can't modprobe find the module?
Date: Sun, 21 Jan 2001 01:15:06 GMT




I'm trying to install the tulip module on RH6.2.  I have tulip.o and
pci-scan.o in /lib/modules/`uname -r`/net/.

But if I do "modprobe tulip.o", it says that it cannot find module
tulip.o

This seems pretty simple, but I'm obviously doing something wrong.  Can
anyone help?

Thanks,

--
Dave Brondsema


Sent via Deja.com
http://www.deja.com/

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

From: Swapnajit Mittra <[EMAIL PROTECTED]>
Subject: RPM supports only package rev <= 3
Date: Sun, 21 Jan 2001 01:19:51 GMT



   Hello,

   I have official RH6.1 installed on a pentium m/c. Now
   whenever I try to install a new version of an
   rpm, I get the following message:

[root@bhalobasa mittra]# rpm -i netscape-common-4.75-2.i386.rpm
only packages with major numbers <= 3 are supported by this version of
RPM

   This is not specific to just netscape installation.
   It has come up in almost all new installations,
   including a new version of rpm.

   What is wrong ?
   Thanks.

--
=-=-= 100% pure Verilog PLI - go, get it ! =-=-=
 Principles of Verilog PLI -By- Swapnajit Mittra
 Kluwer Academic Publishers. ISBN: 0-7923-8477-6
 http://www.angelfire.com/ca/verilog/


Sent via Deja.com
http://www.deja.com/

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

From: "Cameron Kerr" <[EMAIL PROTECTED]>
Subject: Re: SAMBA not working on RH7 on peer to peer win2k network using DHCP from 
maxgate switch/router
Date: Sun, 21 Jan 2001 14:30:24 +1300

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

> I have a small peer to peer network, consisting of 2 win2k machines and
> a linux box. The linux box is running RH7.0. I've downloaded the various
> updates and loaded them. But, I cannot get any of the win2k computers to
> see the linux box. If I do a network neighborhood on the win2k boxes,
> they see each other by machine name. They do not see the machine name
> for the linux box, or any of its drives. I cannot ping any of the
> machines in the network without using their ip address, which is
> assigned by the Maxgate ugate 3200 switch/router. (It is connecting my
> network to a comcast cable modem.) I can ping all of the machines,
> including the linux box, if I ping the ip addresses. The ugate 3200 has
> a table that contains the machine names and dynamically assigned ip
> addresses, and it is correct.

> I think the problem is that there is, and can be (as I understand it) no
> DNS for the network, because it is being assigned ip addresses
> dyamically by the ugate 3200. I think this may, also be the reason that
> I can't get SAMBA to work, but I don't know, for sure. Also, when I boot
> up, sendmail and httpd take a long time, and I get error messages that
> httpd cannot identify local host name. (This started after I used
> netconf to assign a machine name of chinook, rather than localhost. I
> don't have qualified domain names, so I don't use anything more than a
> single name, with no extra .xxx.com or whatever on any of my machines.
> (Is this a problem? Should I just make up a random name, or do I need to
> use the domain name of the comcast network that is in the router? (I
> suspect I don't need to do this, because the windows boxes work ok.) I
> can also telnet or ftp into the linux box, but I have to use the ip
> address rather than the name. 

Yes, you can't ping by hostname, since they you have no DNS, and windows
machines use NetBIOS stuff for hostnames etc. Try nmblookup
<windowsmachine>. Also, make sure you are running the nmbd (NetBIOS
Nameserver Deamon) part of SAMBA (look in /etc/smb.conf, or the
documented one in /usr/doc/samba-<version>/

> I modified the /etc/hosts file to have only one line, which is 
> 127.0.0.1  chinook   chinook
             ^^^^^^^^^^^^^^^^^
             this should ALWAYS be localhost

> Rather than the original file which said
> 127.0.0.1  localhost.localname  localhost
> 
> Normally, I would have put in a line after the localhost line like
> 192.168.0.6  chinook   chinook
               ^^^^^^^^^^^^^^^^^
               This is better, although typically your private network
would be called localdomain, so instead you could have
               chinook.localdomain chinook

> But, because the ip address may change, due to dhcp, I don't see how I
> can do that. 

You should assign your servers static IP's, and make sure that the cable
modem will not assign that range. Perhaps even have them on a different
subnet.

> Also, in SWAT, when I try to set up samba, if I put /, or /home in the
> drive to share over the network, all looks fine until I go another
> screen and come back, when there are now no drives or directories listed
> again. 

Edit /etc/smb.conf instead, I wouldn't trust SWAT if its not saving
changed (have you checked permissions, looked in logs...)

> Also, I cannot get my linux box to print to a postscript printer that is
> on my network at address 192.168.0.10 and driven by one of the win2k
> boxes. I suspect all of these problems are related to something not
> being set,  but I don't know what.

You'll need to use smbprint for this (man smbprint perhaps)

HIH
--Cameron Kerr

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

From: Harry <[EMAIL PROTECTED]>
Subject: Re: PPPSETUP
Date: Sun, 21 Jan 2001 01:31:58 +0000

On Sat, 20 Jan 2001 20:58:59 GMT, olgnuby <[EMAIL PROTECTED]> wrote:

>Harry wrote:
>> 
>> Can someone tell me how to put a pause in the middle of the dialled
>> out telephone number, atdt?????
>> 
>> Thanks
>> 
>> Harry
>How bout just a common old comma. "," or two for a longer pause. Tilde
>"~" works also in modem init strings to compenstae for slow hardware in
>some instances. 
>
>I use em for getting through slow or stubborn switch boards. like
>atdt9,,,1,,800 etc. 
>
>Charlie


Yes, I found a comma worked shortly after my posting the question.
Still very grateful for your help, thanks,

Harry

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


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