Re: [yoper-dev] feedback for gtk2 app crash bug required
Hi Tobias,On 6/30/06, Tobias Gerschner <[EMAIL PROTECTED]> wrote: Hi,to fix this issue : http://www.yoper.com/bugtracker/view.php?id=137 Ineed some help fromsomebody who is able to produce this bug please go to the console and try strace -ff -eopen gftp in a non-root consolePlease send me the output. I have already posted in the forums. Here is the link, http://www.yoper.com/forum/index.php?showtopic=7691&hl=gftp cheers--Tobias GerschnerMember of Board of Yoper Ltd. NZKnowing is not enough; we must apply. Willing is not enough; we must do. ___yoper-dev mailing listyoper-dev@lists.yoper.com https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev-- Regards,C.C.Chakkaradeep,Novatium Solutions Limited,Chennai. http://www.novatium.comhttp://www.yoper.comhttp://wiki.freespire.org/index.php/Freespire_Community_Board_Home --"Sometimes it's better not to ask - or to listen - when people tell you something can't be done. I didnt ask for permission or approval. I just went ahead and did it." - from "Direct from Dell" ___ yoper-dev mailing list yoper-dev@lists.yoper.com https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
[yoper-dev] feedback for gtk2 app crash bug required
Hi, to fix this issue : http://www.yoper.com/bugtracker/view.php?id=137 I need some help from somebody who is able to produce this bug please go to the console and try strace -ff -eopen gftp in a non-root console Please send me the output. cheers -- Tobias Gerschner Member of Board of Yoper Ltd. NZ Knowing is not enough; we must apply. Willing is not enough; we must do. ___ yoper-dev mailing list yoper-dev@lists.yoper.com https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
[yoper-dev] new project for Yoper started
Hi, to address some of the outstanding issues in a proper way I started a subproject : http://www.yoper.com/wiki/index.php?title=Yopermaintain Anybody welcome to contribute ideas and review other distributions to enhance our view. Packages will be available in my personal repository branch. regards -- Tobias Gerschner Member of Board of Yoper Ltd. NZ Knowing is not enough; we must apply. Willing is not enough; we must do. ___ yoper-dev mailing list yoper-dev@lists.yoper.com https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
[yoper-dev] in chat again for a while
Hi, just thought it might be worth to mention that I am in chat for a view hours. In case somebody misses me :D . Won't be online tomorrow though. cheers -- Tobias Gerschner Member of Board of Yoper Ltd. NZ Knowing is not enough; we must apply. Willing is not enough; we must do. ___ yoper-dev mailing list yoper-dev@lists.yoper.com https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
[yoper-dev] 3d maybe interisting
Moin, found this: http://people.redhat.com/laroche/pyrpm/ greets Arnulf ___ yoper-dev mailing list yoper-dev@lists.yoper.com https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
Re: [yoper-dev] Current Blacksand installer
In regard to XFS, I just tried a reinstall and selected the ext3 file system. This yielded no change in the error. The system still boots and then complains as follows. "kernel panic - not syncing: VFS: unable to mount root fs on unknown-lock(8,1)" Okay, I am wondering if using XFS is somehow a problem. I can try ext3 and see if I get similar behaviour. If no one has any good ideas, I will try mounting the install cd and building a custom kernel with built in scsi support. Cheers. Dion. -- "Never ascribe to malice that which may adequately be explained by incompetence." - Napoleon Bonaparte ___ yoper-dev mailing list yoper-dev@lists.yoper.com https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
Re: [yoper-dev] Current Blacksand installer
Hi Tobias, Some small progress. Please see the inline comments. Tobias Gerschner wrote: Hi Dion, When the installation cd does boot you should be able to use Yoper on your system. It is using exactly the same kernel. To build an initrd image via yaird from the live cd into an existing system you have to do the following : 1) mount your root partition : 'mount /dev/sda1 /media/sda1' (make sure the only mount option is rw) In my last post, I couldn't get yaird to produce an image. I failed to add a -rw to the above mount. Doing this enabled me to create an initrd image. 2) copy your device node files from the live cd into the new root file system 'cp -a /dev/hd* /dev/sd* /media/sda1/dev' 3) chroot into the new installation 'chroot /media/sda1' 4) mount the kernel file systems 'mount /proc' , 'mount /sys' 5) try to rebuild the image with yaird yaird -o /boot/initrd.whatever I created the new image with a -v switch and was able to see the symbios 53c875 module included in the image. I had to use the -f cpio option as the -f cramfs appears to be for older kernels and would not work. Make sure the installation of the bootloader does really work properly. I adjusted the lilo.conf and rerun lilo. I received some complaints. "proc/partitions does not match /dev" "name change '/dev/loop0' -> '/dev/loop0' They were spelled identically, so I'm guessing something within that location got a name chage. regards and good luck Thanks, I wasn't lucky enough. The system still boots and then complains as follows. "kernel panic - not syncing: VFS: unable to mount root fs on unknown-lock(8,1)" Okay, I am wondering if using XFS is somehow a problem. I can try ext3 and see if I get similar behaviour. The next option I was considering was mounting the blacksand install cd and copying the kernel source and the kernel config file to my 2.1.0_4 system and building a kernel with symbios 53c875 and relevant scsi disc support into the kernel. If that fixes the problem at least we would know the scope of the problem I am having. I wonder if other people with sata and or other scsic ontrollers and the like are likely to experience this problem? This may be something for the installer to handle, perhaps by offering the user the option of selecting kernel drivers to be included in the initrd image? I appreciate your help. Cheers. D. -- "Never ascribe to malice that which may adequately be explained by incompetence." - Napoleon Bonaparte ___ yoper-dev mailing list yoper-dev@lists.yoper.com https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
