Hi,
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.
Cheers
Damir
--
=====================================================================
| 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 |
=====================================================================
mailto:buskulic@lapp.in2p3.fr
Hi there,
I'm sorry for sending you this query maybe you can help since I cant find
any info elsewhere,
Ive installed suse 10.0 on a b50 all is well there. The problem I have is
that I've set up another b50
With fedora 5 but I have a garbled screen problem. I was wondering if I can
copy xorg.conf from suse and apply it to fedora.
Once again sorry ..
What are the goals for the next version? Is this something that is
posted on the openSuSE.org site, or is this something that some of us
can get into some discussion about. I realized that keeping synched
with the main x86 tree is probably the most important, but what kind of
PPC specific stuff is planned?
1. There was talk about dropping some support for legacy hardware. I
figure that this probably includes a lot of "Old World" macs or pre-G3
machines.
2. What type of restrictions are in place regarding the code? I've
seen versions for the x86 like Super/SLICK. Would it be possible to
have an informal split to concentrate on older hardware?
3. YaST and the current problems with integrating Zen. What can be
done to make it leaner and better?
I've only installed v10.1 on my B&W G3, and even then it is text only
and doesn't get used due to the video problems I have had(I do have a
Rage128 on the way, so hopefully that will be resolved). I can't
install it at all on any "Old World" machines. What type of info would
be helping to getting this taken care of? Or is it possible to start a
v10.1 install by using the v10.0 bootup?
I'm going to make every effort to be as involved as I was in the v10.0
process, and hopefully more so. I am not a programmer, but anything I
can do to contribute let me know.
Thanx
___________________________________________________
Try the New Netscape Mail Today!
Virtually Spam-Free | More Storage | Import Your Contact List
http://mail.netscape.com
Hello,
I sent it originally to the openSUSE mailing list, but i was warned,
that some people might read only suse-ppc, so here it is :-) Bye,
CzP
-------- Eredeti üzenet --------
Tárgy: PackMan packages for SUSE Linux 10.1 are ready
Dátum: Wed, 17 May 2006 18:22:52 +0200
Feladó: Peter Czanik <pczanik(a)fang.fa.gau.hu>
Címzett: opensuse(a)opensuse.org
Hello,
I'm glad to announce, that after long days of compiling, testing and
debuging, I put on-line a large number PackMan packages for SUSE Linux
10.1 PPC. For those of you, who don't know it yet: these are the
packages, which make SUSE Linux a lot more useful, but are left out from
the official SUSE release mainly for legal reasons (mp3, divx, DVD
support, etc.), or sometimes newer versions of included packages. More
info on Packman is available at http://packman.links2linux.de
About my recompilation of Packman packages: these are maintained by
different people without a standardized environment. For reproducibility
I used y2pmbuild, and modified sources to compile in this strict,
chrooted environment.
I had to leave out a number of packages:
- some few, special interest packages did not compile, like synfig
animation studio
- requiring lot's of additional work, like haskel development
environment and related packages, as it needs to be bootstrapped on PPC
- x86 binary only, like the official divx drivers, rar support, etc.
For obvious reasons, I could not sign it with SUSE private keys, so the
installer complains, but installs these packages.
As I needed to modify sources and SPEC files, my packages are not yet
integrated with the rest of the PackMan website, mirror system. You can
download them using ftp, from:
ftp://spike.fa.gau.hu/pub/pmppc101/
Which can also be used as an installation source.
Please let me know, if you have any troubles! And of course, remember to
have a lot of fun! (SUSE (tm)) Smile
CzP
Hey guys. I aquired a B&W G3 the other day. I have since installed a
G4/400 in it. I have only been able to get to the install point 1
time. I had to quit because I had to swap the HD I was going to use
for the install. Since then, I cannot get past the first few screens.
The system "hangs" and won't do anything. Since I only have an old 4MB
ATI Rage IIC PCI card, I have to use "textmode=1" to get to the text
installer. The install screens will "freeze" at various point and
won;t do anything else. I can't get to another tty. However, the caps
& num locks will light up. I had tried several different memory chips
and CD/DVD drives as well as different HDs to no avail. I plan on
getting a Radeon for it shortly, but really don't want to sink any more
money in if it won't work. And, it runs Mac OS v9.2.2 with no
problems. I have also tried a G3/266 and it does the same thing. I am
stumped. Any suggestions would be appriciated. Thanx
___________________________________________________
Try the New Netscape Mail Today!
Virtually Spam-Free | More Storage | Import Your Contact List
http://mail.netscape.com
I tried YDL several times. However, with v3.0, I had major problems.
See, I don't use the onboard SCSI on the old world Macs because it is
SOOOO SLOW. The MESH controller that every old mac I have has it's
SCSI drives on is only 5MB/s. Most of my SCSI drvies are 40MB/s. So
I use Adaptec cards flashed with the MAC ROM. Anyway, with v3.0, the
installer saw the Adaptec cards and happily installed to it, but when
you rebooted, it caused a kernel panic because there was no official
support for those cards in the main kernel. I tried compiling my own
kernels and ended up giving up. I was also told to try v2.3 and then
upgrade, but that failed as well. And, since YDL is based on RedHat,
and I don't care for RedHat, I just lost interest.
I always burn CDs for these machines at 24x.
I do have a copy of OS 8.5, but I was under the impression that YaST
was supposed to be "fixed: in this release. However, I was able to get
YaST to partition just fine under v10.0. It just wouldn't make and
format the Apple_HFS partition, which is the same problem I have now.
So long as you delete the suggestion for the Apple partition, it
partitions just fine. With the old world macs, you have to use BootX,
so it didn't matter. However, with this newer machine, I didn't want
to even have MacOS on it, and that's where I ran into the problem. The
workaround for v10.0 works just fine for v10.1 as well. Of course,
this may not be a problem on the newer machines. This is just the
newest Mac I have.
v10.0 will install on an old world mac just fine. v10.1 will not. I
intend to do a whole lot more beta testing w/ v10.2. Just make sure
when you start install that you add textmode=1 on the BootX command
line. Also, a CD-burner or USB key that will work under OS 8/9 would
be helpful because when you update the kernel you have to copy the new
kernel and initrd files to the MacOS partition. I always just use a
seperate drive on the Old World macs. Especially since some of them
were only 1GB anyway. Let me know if you need help. I have installed
v10.0 on the following Macs:
7500/100 w/604ev-200 & G3/400
9600/300
G3/266 Beige
I also have a 6500/250 that I am going to try putting v10.0 on. I am
looking for an upgraded G3 card for it, but they have been kinda pricey
lately......Stay away from the 52/5300 5300/6300 61/71/8100s since they
are nubus. Also, the 54/6400s have a framebuffer that I haven't been
able to get to work. The 55/6500s have a 2MB ATI chips, so don't
expect X to be very fast.
Biggest problem I had was the RPM install failures. I even had
problems installing from a network. I'm willing to bet that the md5
checker has problems because of the slow processor speeds. I tried
different RAM and everything with the same problems. Unless its a bug
somewhere. I usually do a text install and then add the graphical
installation after the system is setup.
Just remember, YMMV
Good Luck
-----Original Message-----
From: George Simpson <gasjr4wd(a)mac.com>
Back when I was running SuSE on PPC, I had better luck partitioning
with the apple software. Not sure why... it just worked.
maybe format with OS9 then install Linux?
If you get things running, please let me know. I have two boxes with
that card and I was thinking of trying a linux PPC again.
I don't remember if I ever tried to put Linux on those or not but I
think it was in a Umax S900 (clone).
On burning Images...I always burn at about half the speed it says I
can. Much less coasters and errors.
Have you tried yellowdog? I had better luck on PPC with that... I wish
SuSE didn't kill the retail PPC version way back when.
___________________________________________________
Try the New Netscape Mail Today!
Virtually Spam-Free | More Storage | Import Your Contact List
http://mail.netscape.com
Well, I am finally installing v10.1 on my Blue & White G3. There is
evidently a bug in the ATI setup with this machine. No matter what I
did, I was unable to get YaST to actually start installing the system
with my ATI 3D Rage II card w/ 4MB VRAM. I finally dug out an old
IXMicro Twin Turbo/8M card and it is now installing. I had problems
with this card overheating and locking the system up, so I have a fan
on the main chip and it is fine. I also overclocked the G4/400 to
450Mhz. With a small fan on the heat sink, it is running a cool 26-28
degrees C while installing. I'm almost tempted to try 500Mhz. Maybe.
I must say it is definately installing a whole lot faster than my Beige
G3 ever did. At least now I know it is not the machine that was the
problem.
With the Twin Turbo card, the graphical X installation fails, but it
automatically loads the text based system. I am curious to see if it
will actuallu run X on this card since I was only able to do so once
before, and it quit working after I tried to modify the X settings.
Last thing - Does anyone know how much Linux is actually able to make
use of the Altivec instructions on the G4? PowerLogix has a G3/1.0Ghz
that I am thinking about getting, and if there isn't that much support
for the Atlivec, is there any other reason to stay with the G4? Thanx
___________________________________________________
Try the New Netscape Mail Today!
Virtually Spam-Free | More Storage | Import Your Contact List
http://mail.netscape.com
Well, I found out a few things:
1. YaST will NOT properly initialize the hard drive to make use of
yaboot on this machine. I had to go in and manually setup the
partition table with pdisk as explained in the guide for v10.0. Of
course, v10.0 would not even boot on this machine. YaST would also NOT
format the Apple_HFS partition if setup with YaST. It was able to
successfully format it after I initialized and set the disk up with
pdisk. It kept telling me it was a Linux native partition. Also,
cfdisk doesn't work properly and probably should be removed since it
showed that pdisk had done nothing and pdisk showed that cfdisk had
done nothing.
2. YaST will not work with the ATI Rage IIc/PCI card. After
installing with the Twin Turbo, I swapped in the ATI card and it locked
up the system every time.
3. You cannot run the installation system on an Old World Mac with
v10.1. I have tried the following with no luck. It locks up during
the reboot process. The machines I have tested are: 5400/180,
6500/250, G3/266(with and without a G4/400). I still have to check my
7500 and 9600 machines.
4. I have no idea why I still get installation errors on random RPMs.
v10.0 was generally able to ignore them and continue, but with v10.1
the errors almost always caused YaST to crash. Plus, they were random
and one time the same package would install while another it would fail.
I currently have the system setup with a minimal text install until I
can get a real video card for it to be able to run X. It seems that
support for the TwinTurbo has been completely removed. The one time I
actually got it to come up with KDM, it must have had a 4 color
pallete. So far it is sitting here stable with YaST just running.
Also, why is it that I have to waste Hard Drive space by installing
packages for stuff I have NEVER had and don't even have connected to
the conputer? Bluetooth, IRDA, Pilot, ISDN, etc? Why are these
required dependecies? It is shoddy programming from the developers of
the packages? I'm sorry to vent, but it's exasperating to have so many
problems traced to packages that I don't need, have never used, and if
they weren't flagged to be installed that maybe this thing would be up
and running by now. This isn't just a PPC gripe. I see the same
problem on the i386 side as well.
___________________________________________________
Try the New Netscape Mail Today!
Virtually Spam-Free | More Storage | Import Your Contact List
http://mail.netscape.com
Well, all is not well. I am on my 3rd attempt at installation. I
selected use the add-on CD the first time. After finishing Disk 1, it
asked for the add-on. Weird, but. Then it asked for disk 1, then the
add-on, then disk 1, then the add-on, and then YaST crashed. Tried
rebooting hoping that it had successfully installed the boot loader.
No such luck. It showed a folder on the screen and the computer was
locked up.
2nd attempt. Decided to restart without the add-on CD. Started the
installer. YaST reported that the 39.2MB Mac_HFS partition I had
created was an HPFS/NTFS partition. Deleted it and redid and
restarted. YaST failed to install gconf, and then crashed again with
about 20-30 packages left :( .
3rd shot. The HFS patition was labeled as a Linux partition this time.
Redid and am now re-installing yet again. Bootloader again failed.
Rebooted and started installed system. System booted and started YaST.
Detected network cards, asked for disk 2 and resumed installing. I
dropped to a shell and check the Mac_HFS partition. It is once again
labeled as a Linux Native partition type. YaST once again locked up
with only 14 packages remaining. I was able to switch to a terminal
and use reboot instead of just powering off or using the apple reboot
key command.
4th. Of course, now the dang video card is once again refusing to show
yaboot. This is getting to be ridiculous. Of course, I had problems
installing v10.0 on my other "old world" macs, but at least they would
show something. I realy wish that I had done some testing for v10.1
because it is falling way short of what I was expecting. v10.0 was a
great system once it got installed. I expected issues with the Old
World machines, but I am definately dismayed that I am having so many
problems with this B&W G3. Finally got into yaboot and started the
installed system yet again. Granted, I guess some of the problems
could be coming from the overclocked processor, so I will try another
install to see if I can reproduce these problems. Anyway, YaST
started, and detected the nework cards yet again. Hopefully CD 2 took,
and all I will need to do is run CD 3 again. It did, it saw none of
the packages that had been instaled from CD 3. Isn't there a way to
log what packages have been installed soi that if the computer needs a
reboot for some reason that it doesn't have to start from the beginning
of the last disk?
Another thing is that I have never had the installer verify the CDs on
the PPC systems. Never. It failes them every time.
Well it once ahain failed to install vcdimager-0.7.23-19.ppc.rpm. Here
we go again. From scratch. I really can't be the only one who is
having this much trouble installing this stuff can I?
___________________________________________________
Try the New Netscape Mail Today!
Virtually Spam-Free | More Storage | Import Your Contact List
http://mail.netscape.com
Actually, I never found that to be true. It was the Apple_HFS
partition that I had the problem with. If I deleted that, YaST worked
just fine. And, it had the problem with formatting the HFS+, not
creating the partition. v10.0 partitioned just fine for me even during
the Betas as long as I deleted the HFS+ suggestion.
-----Original Message-----
From: Olaf Hering <olh(a)suse.de>
You will have more luck with 10.1, the yast in 10.0 cant repartition
your drive.
___________________________________________________
Try the New Netscape Mail Today!
Virtually Spam-Free | More Storage | Import Your Contact List
http://mail.netscape.com
