No that I am too concerned with it but did anyone receive one of these 2
fedora-list-admin(a)redhat.com; on behalf of;
...then followed by my MacAfee message
****************** McAfee VirusScan ************************
******* Alert generated at: Fri, 30 Jan 2004 19:42:19 -0500 *********
McAfee VirusScan has detected a potential threat in this e-mail
sent by fedora-list-request(a)redhat.com.
The following actions were attempted on each suspicious part.
We strongly recommend that you report this virus-related activity
The attachment "E-mail body" is infected with the W32/Mydoom.eml!exe
This attachment has been quarantined.
So far, the only updates for test1 of FC1 for the x86_64 seem to be an update
for the 2163 kernel.
Is there any plan to start making the updates (testing and regular) available
for i386 also available for x86_64?
So far I have been very pleased with the x86_64 version but I would like to
get more "current" (especially the security fixes) and building the rpms
myself (while doable) is a bit of a pain (and needs to be repeated by every
one of us who wants to update).
So far my experience in trying to port some software (which is also designed
to run on MS Windows) has proved to be a real learning experience. This is
especially true for the "long" variable which is 4 bytes on 32 bit systems, 8
bytes on 64 bit *nix and Linux systems, and 4 bytes on MS Windows 64 bit
What is the release schedule for updates currently in updates testing?
i.e. kernel-2.4.22-1.2154.nptl has been in there since 13th Jan and some
such as postfix-2.0.16-1.i386.rpm have been there since late Nov. Is it
all part of the QA process that governs some packages taking months to
reach updates released?
Any idea when kernel 2154 or 2163 will be released?
I successfully installed Fedora 64 on a system comprised of the
Tyan S2882 Thunder K8S Pro Motherboard w/ IDE, SATA, SCSI, RAID
Dual Opteron 240 chips
2 GB Ram
160 GB Maxtor IDE HD
Creative Sound Blaster Live
GFORCE FX 5200 PCI dual vga video
Casio Digital Camera
To start with, I burned the three iso's to cds...
The install was pretty smooth, although on reboot it seemed to hang on
enabling swap space. I booted into my 32-bit install on a separate
partition, edited /etc/inittab to boot into init 3, and remarkably this
cured the problem.
Setting up X using nvidia's drivers was no problem. Sound took nothing
special at all. The printer and digital camera were both recognized,
and while I haven't used the printer yet, I was able to easily mount the
camera and get pictures off.
So far I have had no problems, other than having to compile xmms and
mplayer from source. After that was done, they both work well. I have
yet to get gaim-encryption successfully working, but maybe if I do a
recompile of gaim and gaim-encryption, perhaps it will work.
Thus far I've been very happy as either RPMs or SRPMs are usually
available making it easy. A few hiccups occured on some SRPMs for some
packages I was just trying out (can't really even remember what the
software was), so I downloaded the source and it seemed to work. I
believe for one kde application I had to create a link in /usr/lib to
one of the libraries in /usr/lib64/...
I guess if I had any complaints right now it would be the lack of
repositories for yum, but its understandable as this isn't even a stable
release yet. I also hope vmware produces a workstation release that
works in 64-bit mode, as I know they have started working on it and are
in either alpha or beta stage.
I have had no lock-ups or crashes, and everything is smooth.
Feel free to ask any questions about the hardware, the software or
anything else related to my use of fedora 64.
Do the cast warning messages I see when compiling previously 32 bit
applications on the amd64 really mean all that much?
Now I understand that you do not want to store an 8 byte pointer into a 4 byte
variable or get a 8 byte pointer from a 4 byte variable. If the code
underlying the calls does the "right thing" (e.g., defines the actual storage
space with something like "void *" or "long"), then is there really a problem
underlying the cast warnings? That is, is it worth the pain to go fix things
so that the cast messages do not occur?
I went to some effort to clean up nessus so building it had no cast messages.
But was it worth it. As I am rebuilding some of the i386 updated packages on
the amd64, I am seeing cast messages in existing packages that seem to work
OK (e.g., ethereal).
So again, is it worth much effort to clean these up other than having clean
(no warning) compiles. For example, you have a function which extracts
something from an array/table and may return a pointer sometimes and other
times an integer. If you know that when you call it in a certain manner it
will return an integer, then what does the cast warning matter?
OK, I asked some of this before and got some answers that explained things but
I am still a little confused.
I have a local repository which includes both the i386 updates and (mostly
locally built) x86_64 updates ... this is a single directory tree and
yum-arch has been run to create the appropriate header files for both i386
and x86_64 packages.
When I ran up2date yesterday to update both gcc and glibc on the x86_64
system, I noticed that the x86_64 packages were installed and then the i386
(from previous messages, I thought it would be the reverse). That is,
glibc-devel...x86_64.rpm was installed before glibc-devel...i386.rpm. This
should not create any problems because these packages have libraries in their
appropriate directory trees and data files (identical in both packages).
I now want to install the i686 version of openssl. The x86_64 version of
openssl is already install when I created the system. However, openssl has
the program file /usr/bin/openssl. So, how should I go about manually
installing (running rpm) to install the i386 package?
quota is not working for reiserfs filesystems. reiserfs partitions can
not be mounted with 'usrquota' option. Does anyone know something about
Juan Pablo Abuyeres <jpabuyer(a)tecnoera.com>
I downloaded the latest kernel and source.
In the source (/usr/src/linux-2.4) dir I made:
make mrproper - OK
make xconfig -OK
In the xconfig I loaded from
/boot/config-2.4.22-1.2149.nptl file, then save and quit.
make dep - OK
make bzImage - come with the next failure:
kernel/kernel.o(.text+0x108c): In function `schedule':
: undefined reference to `active_load_balance'
fs/fs.o(.text+0x37b05): In function `zisofs_readpage':
: undefined reference to `zlib_inflateInit_'
fs/fs.o(.text+0x37c07): In function `zisofs_readpage':
: undefined reference to `zlib_inflate'
fs/fs.o(.text+0x37cb9): In function `zisofs_readpage':
: undefined reference to `zlib_inflateEnd'
fs/fs.o(.text.init+0xacc): In function `mnt_init':
: undefined reference to `init_rootfs'
fs/fs.o(.text.init+0x1011): In function `zisofs_init':
: undefined reference to `zlib_inflate_workspacesize'
make: *** [kallsyms] Error 1
make: Leaving directory `/usr/src/linux-2.4.22-1.2149.nptl'
make: *** [vmlinux] Error 2
.. and stop. What made I wrong?