>
> Jeepers creepers... ;o)
>
> This is one of the biggest FAQ's I think in all of Linux
> land... People argue about how they use compiler XXX.YYY and it
> works for them, so it should work for everyone, when Linus, and
;-)
You do like going off half-cocked, don't you Mike?
I said it works
>
> I'll bet there are more as well. There are also architectures
> that arrange the bit order inside the bytes differently for what
> it is worth.
I know Intel NAMES them back-to-front. I started out in a simple world:
Memory locations numbered (as one might view them) left to right.
Bytes|c
> The following ipchains rules are working for kernel 2.2.x. Which are
> the corresponding rules with ipbables and kernel 2.4.x?
> Which modules to load?
>
> 2.2.x: working
> /sbin/modprobe ip_masq_ftp
> ipchains -P forward DENY
> ipchains -A forward -s 192.168.0.4 -j MASQ
>
>
> 2.4.x: my attem
> I downloaded the kernel-2.2.16 source rpm. I noticed a
> number of patches in there. What are these patches
> for? Are they RH specific. What would be the harm in
> just packaging the kernel source tarball by itself.
> I've never had the need to patch the kernel with any
> nonstandard patches.
>
> On Thu, 7 Sep 2000, John Summerfield wrote:
>
> >> >int main(void)
> >> >{
> >> >printf("%ld CPUs online\n", sysconf(_SC_NPROCESSORS_ONLN));
> ^^^
>
> >[root@dugite /root]# man getconf
> >No manual entry for getconf
> >[root@dugite /root]# getconf _N
> These bugs are around the gcc-2.95.2 and the kernel behind the 2.2.16, or the
> y
> are about even the 2.2.16 kernel?
> What I mean is that many distribution give the gcc-2.95.2, and I have an e-ma
> il
> from this mailing list that says in the RedHat Linux 7.0 there will be the
> gcc-2.95.2.
A
On Fri, Sep 08, 2000 at 11:15:20AM +0200, Ingo Luetkebohle wrote:
> On Thu, Sep 07, 2000 at 03:14:32PM -0400, Mark Shewmaker wrote:
> > Great! I had previously thought that if the gnome libraries weren't
> > installed or were corrupted, that GnoRPM couldn't be used to fix the
> > problem. I had
On Fri, Sep 08, 2000 at 09:15:27AM +0200, [EMAIL PROTECTED] wrote:
> > Harry Putnam wrote:
> > > What does `glint' do for you that you cannot easily duplicate from the
> > > command line?
> >
>
> Many things. Like looking through all installed RPMS searching for
> packages who are at the same t
>
> > > >
> > > >These bugs are around the gcc-2.95.2 and the kernel behind the 2.2.16, or they
> > > >are about even the 2.2.16 kernel?
> > > >What I mean is that many distribution give the gcc-2.95.2, and I have an e-mail
> > > >from this mailing list that says in the RedHat Linux 7.0 there wil
[EMAIL PROTECTED] wrote:
> > >
> > >These bugs are around the gcc-2.95.2 and the kernel behind the 2.2.16, or they
> > >are about even the 2.2.16 kernel?
> > >What I mean is that many distribution give the gcc-2.95.2, and I have an e-mail
> > >from this mailing list that says in the RedHat Linux
On Thu, Sep 07, 2000 at 03:14:32PM -0400, Mark Shewmaker wrote:
> Great! I had previously thought that if the gnome libraries weren't
> installed or were corrupted, that GnoRPM couldn't be used to fix the
> problem. I had not known that the program was written to somehow
> fallback gracefully if
> >
> >These bugs are around the gcc-2.95.2 and the kernel behind the 2.2.16, or they
> >are about even the 2.2.16 kernel?
> >What I mean is that many distribution give the gcc-2.95.2, and I have an e-mail
> >from this mailing list that says in the RedHat Linux 7.0 there will be the
> >gcc-2.95.2.
>
> Harry Putnam wrote:
> > What does `glint' do for you that you cannot easily duplicate from the
> > command line?
>
Many things. Like looking through all installed RPMS searching for
packages who are at the same time rarely used and relatively big so
uninstalling them will free significant
13 matches
Mail list logo
