All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
* 2.2.x kernels and u grading software to minimum req.
@ 1999-03-02 21:17 Paul Barrette
  1999-03-03  7:11 ` Michel Lanners
  0 siblings, 1 reply; 3+ messages in thread
From: Paul Barrette @ 1999-03-02 21:17 UTC (permalink / raw
  To: linuxppc-user-digest, linuxppc-dev


I have 2.2.2 running on R4.  I read the
/usr/src/linux/Documentation/Changes file and noticed that there are a
number of updates needed (see below).  I have noticed problems with  tx
packets:
root ~># ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
          EtherTalk Phase 2 addr:0/0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:277 errors:0 dropped:0 overruns:0 frame:0
     >>>     TX packets:0 errors:79193 dropped:277 overruns:0 carrier:0 coll:0

eth0      Link encap:Ethernet  HWaddr 00:05:02:70:06:45
          inet addr:10.0.0.1  Bcast:10.0.0.255  Mask:255.255.255.0
          EtherTalk Phase 2 addr:65280/34
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6539 errors:0 dropped:0 overruns:0 frame:0
       >>>   TX packets:0 errors:0 dropped:6737 overruns:5 carrier:0 coll:0
          Interrupt:14 Base address:0x1000

ppp0      Link encap:Point-to-Point Protocol
          inet addr:130.113.xx  P-t-P:130.113.xx  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:350 errors:0 dropped:0 overruns:0 frame:0
        >>>  TX packets:0 errors:9477 dropped:341 overruns:0 carrier:0 coll:0

I'm not sure what TX does, but when I upgraded to net-tools-1.49 on an
intel RH 5.1 box, these errors (no ppp0 there) disappeared.  Problem is
that net-tools-1.49 doesn't compile without errors on linuxppc. (or I'm not
able to correct these errors).

I also noticed that the following pkgs need to be updated from the standard
R4 dist:
insmod (I compiled 2.1.121 a while ago), egcs-2.90.25 980302, ld,
libc-1.99.so, procps 1.2.7, pstree 16, net-tools1.432, NFS 2.2beta29,
util-linux 2.6

Now the $10 question, are there rpms around?  I had a look at
ftp.linuxppc.org, no luck except for egcs and libc (which I will download
and re try compilation.)

Should I be concerned with these (apart from net-tools I think I can squeek
by)?   Are others upgrading or noticing problems having done so?

>>>>>>>>>>
  Upgrade to at *least* these software revisions before thinking you've
encountered a bug!  If you're unsure what version you're currently
running, the suggested command should tell you.

- Kernel modules         2.1.121                 ; insmod -V
- Gnu C                  2.7.2.3                 ; gcc --version
- Binutils               2.8.1.0.23              ; ld -v
- Linux libc5 C Library  5.4.46                  ; ls -l /lib/libc.so.*
- Linux libc6 C Library  2.0.7pre6               ; ls -l /lib/libc.so.*
- Dynamic Linker (ld.so) 1.9.9                   ; ldd --version or ldd -v
- Linux C++ Library      2.7.2.8                 ; ls -l /usr/lib/libg++.so.*
- Procps                 1.2.9                   ; ps --version
- Procinfo               15                      ; procinfo -v
- Psmisc                 17                      ; pstree -V
- Net-tools              1.49                    ; hostname -V
- Loadlin                1.6a
- Sh-utils               1.16                    ; basename --v
- Autofs                 3.1.1                   ; automount --version
- NFS                    2.2beta40               ; showmount --version
- Bash                   1.14.7                  ; bash -version
- Ncpfs                  2.2.0                   ; ncpmount -v
- Pcmcia-cs              3.0.7                   ; cardmgr -V
- PPP                    2.3.5                   ; pppd -v
- Util-linux             2.9g                    ; chsh -v


--
Paul Barrette
Ph.D. candidate, dept. of Classics
System Administrator
McMaster University

umbra loco deerat; qua postquam parte resedit
Dis genitus vates et fila sonantia movit,
umbra loco venit.                  (Ov. Met. 10. 88 ff.)
http://www.humanities.mcmaster.ca/~barrette/



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2.2.x kernels and u grading software to minimum req.
  1999-03-02 21:17 2.2.x kernels and u grading software to minimum req Paul Barrette
@ 1999-03-03  7:11 ` Michel Lanners
  1999-03-03 22:10   ` P. Barrette
  0 siblings, 1 reply; 3+ messages in thread
From: Michel Lanners @ 1999-03-03  7:11 UTC (permalink / raw
  To: barretp; +Cc: linuxppc-user-digest, linuxppc-dev


On   2 Mar, this message from Paul Barrette echoed through cyberspace:
> I have 2.2.2 running on R4.  I read the
> /usr/src/linux/Documentation/Changes file and noticed that there are a
> number of updates needed (see below).
[snip]
> I also noticed that the following pkgs need to be updated from the standard
> R4 dist:
> insmod (I compiled 2.1.121 a while ago), egcs-2.90.25 980302, ld,
> libc-1.99.so, procps 1.2.7, pstree 16, net-tools1.432, NFS 2.2beta29,
> util-linux 2.6

.... which brings up a big question: Shouldn't there be upgrade areas
for LinuxPPC's releases, like there are for normal RedHat releases? It
seems to me that R4 still contains all the way old ackages, and that
the only updates available are from september last year or so...

Then, this sparks a second question: how about actuallay changing the
packages list in the distribution, so that if I net-install LinuxPPC, I
will always have the latest&greatest, but also bug- and
security-problem-free instal _without_ doing manual upgrades later on?

> Now the $10 question, are there rpms around?  I had a look at
> ftp.linuxppc.org, no luck except for egcs and libc (which I will download
> and re try compilation.)

I had no problem upgrading most (and all the critical ones) from the
mentioned packages, though by getting the maintainer's official and
latest release (not .src.rpm's).

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2.2.x kernels and u grading software to minimum req.
  1999-03-03  7:11 ` Michel Lanners
@ 1999-03-03 22:10   ` P. Barrette
  0 siblings, 0 replies; 3+ messages in thread
From: P. Barrette @ 1999-03-03 22:10 UTC (permalink / raw
  To: Michel Lanners; +Cc: linuxppc-user-digest, linuxppc-dev


that would be nice, I just spend the last hour upgrading my i386 RH5.1
machine from rh's errata page (actually a mirror to it), and that was
relatively painless. 
> .... which brings up a big question: Shouldn't there be upgrade areas
> for LinuxPPC's releases, like there are for normal RedHat releases? It
> seems to me that R4 still contains all the way old ackages, and that
> the only updates available are from september last year or so...
> 

I guess that would be nice too, but  I'm under the
impression that the linuxppc staff is substantially smaller than RH,
correct me if I am wrong, so this strikes me as unlikely.

> Then, this sparks a second question: how about actuallay changing the
> packages list in the distribution, so that if I net-install LinuxPPC, I
> will always have the latest&greatest, but also bug- and
> security-problem-free instal _without_ doing manual upgrades later on?
> 

I grabbed all the sources and they compiled ok once I applied Gary's
glibc1_99 patch.
 
> I had no problem upgrading most (and all the critical ones) from the
> mentioned packages, though by getting the maintainer's official and
> latest release (not .src.rpm's).
> 
> Michel


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~1999-03-03 22:10 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-03-02 21:17 2.2.x kernels and u grading software to minimum req Paul Barrette
1999-03-03  7:11 ` Michel Lanners
1999-03-03 22:10   ` P. Barrette

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.