I got some problems (disk access denied, bus errors,...) that led me to
go into single user mode and fsck my partitions. I noticed then that
there were some directories created in the tmp directory, called "dev"
and "etc", and one file in the / directory called "success" with 0
length. At reboot, these files disapeared. Does anybody know if this
could be a sign of a hacked computer ? I mean could someone have
installed a rootkit or some such ?
I'm not paranoid but this indeed seems strange.
| Damir Buskulic | Universite de Savoie/LAPP |
| | Chemin de Bellevue, B.P. 110 |
| Tel : +33 (0)450091600 | F-74941 Annecy-le-Vieux Cedex |
| e-mail: buskulic(a)lapp.in2p3.fr | FRANCE |
Did anyone manage to successfully boot Linux on an RS/6000 43p 140 ?
I tried using ftp://ftp.suse.com/pub/suse/ppc/7.1/unsorted/prep/43p_140/zImage.140.chrp
and followed the instructions in the German SuSE manual (ie copied the image to an MS-DOS
formatted floppy disk, renaming the image to "zimage" there).
At the OpenFirmware prompt I typed
boot floppy:,zimage root=/dev/fd0 load_ramdisk=1 fake_initrd
I also tried using ftp://ftp.suse.com/pub/suse/ppc/kernel/BETA/deflt/zImage.prep
and followed the instructions on http://sdb.suse.de/de/sdb/html/olh_ppc_43p140.html
(ie copied the image as a raw disk image using dd).
At the OpenFirmware prompt I typed
In BOTH cases, the symptoms are identical:
The floppy is read (takes half a minute or so).
The OpenFirmware cursor moves to the next line or the line after that.
The system freezes (or reboots after a long time).
(None of the IPL or memory messages ever appear.)
So obviously, none of these approaches works for me.
What is the difference between the images copied as raw disk images and those copied
as files on an MS-DOS disk?
Which approach is *supposed* to work? Both are declared as solutions for 140 43p.
BTW: The firmware version of the machine I tried this on is TIG97251.
Thanks in advance for any hints or solutions.
Announcing: OpenOffice.org 1.0.1 for PPC Linux
What is it?
OpenOffice.org provides a free (source LGPL and no $) almost drop-in
replacement for Microsoft Office and is available for Solaris (Sparc and
x86), Linux (x86 and PPC), WIN (NT, 200, XP, 98, 95, etc), and coming real
soon now (RSN) for FreeBSD, NetBSD, Irix, and Mac OSX. It provides almost
transparent file access to Microsoft Office files.
Please see http://www.openoffice.org for more info and additional download
sites for major platforms. PPC Linux specific download sites are provided
What's New in This Release?
- built using gcc-3.1.1 pre
- improved font handling
- new shared dictionary support
- user-installed hyphenation dictionaries now possible
- huge number of bug fixes and stability improvments
For a more complete listing of fixed bugs:
This version should work on stock Debian, SuSE 7.3, YDL 2.2 and YDL 2.3,
and almost any other PPC Linux distribution using at least glibc 2.2.1.
Please Note: Debian users may want to use the official Debian builds which
include better desktop integration for Debian users and have been built
and tested on Debian systems (although this version will work too)
This is the usual disclaimer. OOo 1.0.1 should be a rock steady release
but please don't complain if you loose everything! I use it constantly
and have not experienced any problems but I can make no guarantees.
If interested, you can build your own binary direct from source.
Please check out http://www.openoffice.org for more info on the
What's Available (English Only)?
inside the installer is a complete installation/setup
guide in pdf format.
Where can I download it?
And it is available from up-to-date YellowDog Linux Mirrors:
Hopefully it will appear on penguinppc.org sites soon.
Building your own from Source
Building your own OOo binary is not for the faint hearted and takes at
least 2 gig of free disk space and up to date tools. If you are
interested in building your own version direct from source, please contact
me and I will try to provide you with and recent or nedded patches and
some short build instructions. Right now the build of 1.0.1 requires gcc
Kevin B. Hendricks
I am trying to install FireWire on my PPC Cube. I found on SuSe-Site an
.rpm-Packet to install. There are a view problems with it.
- It should, as far as I understood, upgrade the Kernel.
- This shoud work, according to SuSe, work without problem. But, I have
got problems with package-depencies. So, I installed it with rpm -U
- now, the system doesn't recognise the datas modules.dep
- I tried to remake it with depmode -a...
Who can help me?
As I know, SuSe 7.3 has got Kernel Version 2.4.12, but when I have a
look with uname -r it shows me 2.2.16 why that?
There is no support from SuSe-Side..., no Kernel with FireWire, no
possibility to make backups from a Cube (But, backups are so important).
And, SuSe sais, Cube is a supported PPC.
Thanks very much for help!
Peter, Berne, Switzerland
Sorry I have difficulty to properly categorize this message into any mailing list.
I am intenting to run a database and a POP3 mail server on SuSE 8.0 with a second hand SMP mainboard in order to save some cost. cost.
Before making the purchase, I would like to run a few tests to ensure the hardware is sound. However, I only know the SuSE 8.0 "Memory Test" and the "top" command to test the function of the memory unit and the SMP part of the mainboard.
I wonder if there is anyone out there has already over come this problem with a solution, so I would not need to re-invent the wheel again.
Thank you! :)
Info provided if needed:
Mainboard Model: Legend QDI BrillianX 4
Is there any way to activate the ibook G3 366 external video out with SuSE
7.3 running the default 2.4.16 kernel (downloaded from ftp.suse.com)?
| Emiliano Grilli | GNU/Linux |
/^\_/`·.|O emillo(a)libero.it | proud user |
| | |
for good old knews I made some changes to ~/.Xdefaults and wondered why
thy showed no effect: SuSE 7.3 has xrdb -merge in all xinit/session
scripts. Manually doing xrdb -load activated my changes.
What is -merge good for anyway? Is it safe to change ~/.xinitrc to
during installation SuSE 7.3 recognized the CDRW in my iBook 2001 and
correctly added the kernel parameter "hdb=ide-scsi" and linked dev/cdrom
to sr0. But ide-scsi is built as a module (I didn't change the kernel)
and currently I have to insmod it manually. Kerneld doesn't seem to be
on the CDs, but kmod support is included (that is,
I suppose some etc/modules.conf change is in order, but the manpage is
very confuse. Help? Please?
I am a first year Linux student and in my first month using Linux. Today in
class I tried to create a hard link from my home directory to a file about 4
directories away from my home directory using the command: ln
/home/myhomedirectoryname/dir1/dir2/dir3/dir4/file newfilename. When I went
to the GUI, I noticed that it created a file with the newfilename with a #
in front and a # in the back of it looked like #newfilename#. Why did it do
this? Thank you for your help!!
Join the worlds largest e-mail service with MSN Hotmail.