January 2004 - openSUSE Users - openSUSE Mailing Lists

Re: [SLE] Can I convert a windows partition to linux?
by GarUlbricht7＠netscape.net 03 Feb '04

03 Feb '04

James Knott <james.knott(a)rogers.com> wrote: > >Tom Nielsen wrote: >> (snip) My issueis can I convert a windows partition on hda1 (0,0). >> If I do, does this wipe out my mbr? > > All you have to do, is use fdisk to make it the appropriate file type > and then format. > > It shouldn't affect the MBR. > Tom, Have you done it yet? Did it work ??? If you haven't done it yet you might want to think: What is your recovery strategy in case he is wrong, do you have aback-up. Do you know how to re-install grub (or lilo) ??? And do you have copy of your /etc/fstab ?? Do you know where your rescuse CD is ?? Then go for it. I am sure James is right, but you will be the one to suffer if he's wrong. HTH, Gar -- In the Beginning was the Command Line ---Neal Stephenson -- __________________________________________________________________ New! Unlimited Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register Act now to get a personalized email address! Netscape. Just the Net You Need.

2 2

DriveReady SeekComplete Error...hd broken?
by Sven Burmeister 03 Feb '04

03 Feb '04

Hello everybody, when booting my Suse 9.0 I get the following messages in the bootlog, that I do not knwo what to do with. The hd is just about half a year old. Cheers, Sven <4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device ide0(3,2)) ... <4>for (ide0(3,2)) <4>hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } <4>hda: drive_cmd: error=0x04 { DriveStatusError } <4>hda: cache flushing failed. disable write back cacheing for journalled file systems <4>hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } <4>hda: drive_cmd: error=0x04 { DriveStatusError } <4>hda: cache flushing failed. disable write back cacheing for journalled file systems <4>Using r5 hash to sort names <4>VFS: Mounted root (reiserfs filesystem) readonly. <5>Trying to move old root to /initrd ... failed <5>Unmounting old root <5>Trying to free ramdisk memory ... okay <6>Freeing unused kernel memory: 176k freed <6>md: Autodetecting RAID arrays. <6>md: autorun ... <6>md: ... autorun DONE. <4>reiserfs: enabling write barrier flush mode <6>lvm-mp: allocating 42 lowmem entries at c233a000 <6>LVM version 1.0.5+(mp-v6c)(22/07/2002) module loaded <4>reiserfs: enabling write barrier flush mode <6>Adding Swap: 1036184k swap-space (priority 42) <4>reiserfs: enabling write barrier flush mode <4>reiserfs: enabling write barrier flush mode <4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device ide0(3,4)) ... <4>for (ide0(3,4)) <4>Using r5 hash to sort names <4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device ide0(3,5)) ... <4>for (ide0(3,5)) <4>Using r5 hash to sort names <4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device ide0(3,67)) ...

5 5

GPL Issues
by expatriate 02 Feb '04

02 Feb '04

Hello Everyone. I'm going to embark on a project that will require me to butt heads with some high-level kahunas regarding Linux. I work for a very very big company that has enormous clout but is not as risk-taking as I would like them to be. Anyway my question is: If we decide to use a standard distribution of Linux, are we forced to publish our own source code if we statically or dynamically link to GPL libraries, use gcc to compile and use GPL header files? I'm getting different answers from different sources. We are not planning to change the kernel in any way. Maybe create our own drivers for proprietary hardware and install them at runtime. Can anyone shed a bit more light on this? TIA

5 9

Procmail + Maildir
by Hans du Plooy 02 Feb '04

02 Feb '04

Hi all, I'm sure this has been mentioned before, but I can't seem to get it right. I have this in my procmailrc :0 * ^Subject:.**SPAM** ! spambox(a)company.co.za Which works fine except that the mail loops once, so I get two of each in the spambox. I would rather like to do :0 * ^Subject:.**SPAM** /home/spambox/Maildir/ The mail gets delivered fine, except that it belongs to root instead of user spambox. How do I specify in procmail that this the ownership shouldn't change? All other users mail is fine, just this one account that gets delivered directly. Thanks -- Kind regards Hans du Plooy hansdp(a)newingtoncs.co.za

8 40

BadCRC ?
by Alain Barthélemy 02 Feb '04

02 Feb '04

Hi, During boot-up (SuSE-8.1) I always have the two next lines: hda: dma_intr: status=0x051 { DriveReady SeekComplete Error } hda: dma_intr: error:0x841 { DriveStatus Error BadCRC } If anybody can tell me what could be the problem? -- Alain Barthélemy cassandre(a)bartydeux.be http://www.bartydeux.be Linux User #315631

6 7

CVS with SSH from a private subnet (savana.gnu.org)
by Steven T. Hatton 02 Feb '04

02 Feb '04

I just discovered that I can access the emacs cvs repository anonymously from my firewall/router, but not from my workstation which is a member of a private subnet setup using IP masquerading. Has anybody encountered this kind of thing? Is there something I can do on my end to make it possible to access the CVS repository from my workstation? STH

2 1

k3b issues
by Chris Herrnberger 02 Feb '04

02 Feb '04

Greets: On upgrading to KDE 3.2 RC1 from SuSE on 8.2 K3b giving me very strange results. SuSE version:k3b-0.10-2 The error message is as follows: ---------------------------------------------------------------------------- System ----------------------- K3b Version: 0.10 KDE Version: 3.2.0 RC1 QT Version: 3.3.0-snapshot-20040113 cdrecord ----------------------- /usr/bin/cdrecord: Warning: not running as root user, fs= option ignored. scsidev: '1,0,0' scsibus: 1 target: 0 lun: 0 Linux sg driver version: 3.1.24 cdrecord comand: ----------------------- /usr/bin/cdrecord -v gracetime=2 dev=1,0,0 speed=1 -eject -data -tsize=17504s - mkisofs ----------------------- 17504 /usr/bin/mkisofs: Resource temporarily unavailable. cannot fwrite 32768*1 mkisofs comand: ----------------------- /usr/bin/mkisofs -gui -graft-points -V K3b data project -volset -A K3B THE CD KREATOR VERSION 0.10 (C) 2003 SEBASTIAN TRUEG AND THE K3B TEAM -P -p K3b - Version 0.10 -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-chris123/k3buaBjtb.tmp -r -hide-list /tmp/kde-chris123/k3bRkTSua.tmp -l -iso-level 2 -path-list /tmp/kde-chris123/k3bKT4XBa.tmp ---------------------------------------------eof---------------------- What interesting here is that K3b claims that mkisofs> resource is temporarily unavailable and cannot write. The default K3b setting would point this to /tmp/kde-username which is set 777, usersname: users just to open it up. However the location and permission settings do not seem to affect the error output. mkisofs is currently also set as 777 and root:users to ensure that k3b has access No idea whats going on here..anyone have any light they can shed. Doing the process manually of course works just fine..:) and all CDROM drives are detected and properly configured. Best and tia.. /ch

7 13

Re: [SLE] bad sectors on hard drive (suse 9.0)
by Ales Jagodnik 02 Feb '04

02 Feb '04

Thank you very much. Could you perhaps tell me the xt3 format command? I will just run CD1 suse rescue , reformat existing partions to ext3 and swap (your command) , as they will all be the same size. Then I will run the e2fsck commands. Ales

6 7

.wmv player for Linux
by Jim 02 Feb '04

02 Feb '04

Does anyone know of a Linux video player that will play .wmv format?? Thanks, Jim

11 18

How to set a reiserfs partition fsck occasionally?
by Michael James 02 Feb '04

02 Feb '04

While the new logging filesystems are a great improvement my experience is that they can't survive forever in the real world without an occasional rebuild or fsck. This list has had warnings by people burnt by reiserfs. I haven't (yet) lost any data but have had some scary times. This hasn't been bugs in reiserfs (3.6) itself as most instability was tracked to (very marginally) flakey RAM. However while the glitches were caused by corrupt RAM they left me with faults in the filesystem, faults that persisted across reboots. These included un-list-able and un-cat-able files. ie: read or ask the size of that file and it's bye-bye to that terminal. It made the whole system unuseable as processes "trod on the cracks" and hung. Backups? Hah, not with that file in the partition. So I think a lot of bad press stems from the misconception that any filesystem can avoid bitrot forever without an fsck. But this is painful to do by hand, I have to boot a rescue system and run reiserfsck by hand, to do the root and system partitions. How can I get back the old behaviour an fsck happening during reboot every x reboots or y days? Or, how can I trigger an "fsck reboot"? TIA, michaelj PS: I've just realized I can do it by adding an fsck into the linuxrc script of a cooked initrd image. That would give me an "fsck boot" option in grub. Comments? -- Michael James michael.james(a)csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166

4 5