June 2005 - openSUSE Users - openSUSE Mailing Lists

Torsmo and ACPI battery level indicator
by Peter N. Spotts 14 Jun '05

14 Jun '05

Folks, I'm running SuSE 9.1 Professional and am using Torsmo as a system monitor. After setting it up and finding that the battery indicator wasn't working, I Googled torsmo and ACPI, found a solution that, well, hasn't worked. It involved entering the following string in torsmorc: ${color grey}Battery:${color grey}{$battery} The default is bat0, so I have no battery designated. I've fiddled with a range of bracketing options, thinking I may have the syntax wrong. Still she no wanna fly. When I use Torsmo's ACPI ac indicator, Torsmo correctly shows if the AC is on line or off line. But the battery level still fails to display. Any thoughts? With best regards, Pete -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Peter N. Spotts | Science Correspondent The Christian Science Monitor One Norway Street, Boston MA 02115 Office: 617-450-2449 | Office in home: 508-520-3139 Email: pspotts(a)alum.mit.edu | www.csmonitor.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2 2

SuSE 9.0: kernel modules not found after upgrade from k_athlon-2.4.21-286 to k_athlon-2.4.21-291
by Sven.Hartrumpf＠fernuni-hagen.de 14 Jun '05

14 Jun '05

Hi all. On a SuSE 9.0 system, kernel modules are not found after a kernel upgrade from k_athlon-2.4.21-286 to k_athlon-2.4.21-291. /var/log/messages shows that the wrong modules.dep is searched for: Jun 10 08:50:45 localhost modprobe: modprobe: Can't open dependencies file /lib/modules/2.4.21-286-athlon/modules.dep (No such file or direc tory) Fortunately, switching back to k_athlon-2.4.21-286 was easy. Has anybody encountered the same problem? Or is it just me? Greetings Sven

5 7

RE: [SLE] Little_endian.h errors
by Khanh Tran 14 Jun '05

14 Jun '05

Just for the archives: I guess the if/endif wasn't matching the case right, so I did the following and it compiles: #include <linux/version.h> #include <asm/types.h> #define __le64 __u64 #define __le32 __u32 #define __le16 __u16 #define __be64 __u64 #define __be32 __u32 #define __be16 __u16 #include <linux/cdrom.h> -Khanh > -----Original Message----- > From: Khanh Tran > Sent: Tuesday, June 14, 2005 6:31 PM > To: Joe Morris (NTM); suse-linux-e(a)suse.com > Subject: RE: [SLE] Little_endian.h errors > > I looked at your post, and got this reply on the mythtv list, > but still > won't work. > > > > You can try the following workaround in all the source files that > > > #include <linux/cdrom.h>: > > > > > > #ifdef HAVE_LINUX_CDROM_H > > > /* linux 2.6.9 workaround */ > > > # include <linux/version.h> > > > # if LINUX_VERSION_CODE == KERNEL_VERSION(2,6,9) > > > # include <asm/types.h> > > > # define __le64 __u64 > > > # define __le32 __u32 > > > # define __le16 __u16 > > > # define __be64 __u64 > > > # define __be32 __u32 > > > # define __be16 __u16 > > > # endif /* linux 2.6.9 workaround */ > > > # include <linux/cdrom.h> > > > #endif > > -=Khanh=- > > > -----Original Message----- > > From: Joe Morris (NTM) [mailto:Joe_Morris@ntm.org] > > Sent: Tuesday, June 14, 2005 6:02 PM > > To: suse-linux-e(a)suse.com > > Subject: Re: [SLE] Little_endian.h errors > > > > Khanh Tran wrote: > > >I've been trying to compile MythTV 0.18.1 on SuSE 9.2, > > Are you sure that is 9.2 and not 9.3? > > >however I keep > > >getting the following errors. Anyone know what to do? > > > > > >mythcdrom-linux.cpp > > >In file included from /usr/include/asm/byteorder.h:59, > > > from /usr/include/linux/cdrom.h:14, > > > from mythcdrom-linux.cpp:3: > > >/usr/include/linux/byteorder/little_endian.h:43: error: > syntax error > > >before `(' token > > >/usr/include/linux/byteorder/little_endian.h:47: error: > syntax error > > >before `*' token > > >/usr/include/linux/byteorder/little_endian.h: In function `__u64 > > >__le64_to_cpup(...)': > > >/usr/include/linux/byteorder/little_endian.h:49: error: `p' > > undeclared > > >(first use this function) > > > > > This looks a lot like the bug I was working to figure out to > > get kscd to > > get compiled in 9.3 with cdda support. The kscd author told > > me it was a > > glibc bug. Assuming it is 9.3, the problem is [Disclaimer: > > I am not a > > programmer, and my code reading and terminology is therefore highly > > suspect] there is a reference to cdrom.h in > > mythcdrom-linux.cpp, which > > references byteorder, which references little_endian.h, which > > is defined > > in types.h as > > #if defined(__GNUC__) && !defined(__STRICT_ANSI__) > > *typedef* __u64 __bitwise __le64; > > *typedef* __u64 __bitwise __be64; > > #endif > > > > If cdrom.h is defined with __STRICT_ANSI__, it breaks the > > definition and > > causes the little_endian error. I unfortunately don't know > > which has a > > bug, what it is or should be. You could search the archives > > and take a > > look at the patch I used to get this to work with kscd. > > Maybe it will > > give you an idea of a fix? /workaround? > > > > -- > > Joe Morris > > New Tribes Mission > > Email Address: Joe_Morris(a)ntm.org > > Registered Linux user 231871 > > > > > > > > > > > > > > -- > > Check the headers for your unsubscription address > > For additional commands send e-mail to suse-linux-e-help(a)suse.com > > Also check the archives at http://lists.suse.com > > Please read the FAQs: suse-linux-e-faq(a)suse.com > > > > > > > > -- > Check the headers for your unsubscription address > For additional commands send e-mail to suse-linux-e-help(a)suse.com > Also check the archives at http://lists.suse.com > Please read the FAQs: suse-linux-e-faq(a)suse.com > > >

1 0

RE: [SLE] Little_endian.h errors
by Khanh Tran 14 Jun '05

14 Jun '05

I looked at your post, and got this reply on the mythtv list, but still won't work. > > You can try the following workaround in all the source files that > > #include <linux/cdrom.h>: > > > > #ifdef HAVE_LINUX_CDROM_H > > /* linux 2.6.9 workaround */ > > # include <linux/version.h> > > # if LINUX_VERSION_CODE == KERNEL_VERSION(2,6,9) > > # include <asm/types.h> > > # define __le64 __u64 > > # define __le32 __u32 > > # define __le16 __u16 > > # define __be64 __u64 > > # define __be32 __u32 > > # define __be16 __u16 > > # endif /* linux 2.6.9 workaround */ > > # include <linux/cdrom.h> > > #endif -=Khanh=- > -----Original Message----- > From: Joe Morris (NTM) [mailto:Joe_Morris@ntm.org] > Sent: Tuesday, June 14, 2005 6:02 PM > To: suse-linux-e(a)suse.com > Subject: Re: [SLE] Little_endian.h errors > > Khanh Tran wrote: > >I've been trying to compile MythTV 0.18.1 on SuSE 9.2, > Are you sure that is 9.2 and not 9.3? > >however I keep > >getting the following errors. Anyone know what to do? > > > >mythcdrom-linux.cpp > >In file included from /usr/include/asm/byteorder.h:59, > > from /usr/include/linux/cdrom.h:14, > > from mythcdrom-linux.cpp:3: > >/usr/include/linux/byteorder/little_endian.h:43: error: syntax error > >before `(' token > >/usr/include/linux/byteorder/little_endian.h:47: error: syntax error > >before `*' token > >/usr/include/linux/byteorder/little_endian.h: In function `__u64 > >__le64_to_cpup(...)': > >/usr/include/linux/byteorder/little_endian.h:49: error: `p' > undeclared > >(first use this function) > > > This looks a lot like the bug I was working to figure out to > get kscd to > get compiled in 9.3 with cdda support. The kscd author told > me it was a > glibc bug. Assuming it is 9.3, the problem is [Disclaimer: > I am not a > programmer, and my code reading and terminology is therefore highly > suspect] there is a reference to cdrom.h in > mythcdrom-linux.cpp, which > references byteorder, which references little_endian.h, which > is defined > in types.h as > #if defined(__GNUC__) && !defined(__STRICT_ANSI__) > *typedef* __u64 __bitwise __le64; > *typedef* __u64 __bitwise __be64; > #endif > > If cdrom.h is defined with __STRICT_ANSI__, it breaks the > definition and > causes the little_endian error. I unfortunately don't know > which has a > bug, what it is or should be. You could search the archives > and take a > look at the patch I used to get this to work with kscd. > Maybe it will > give you an idea of a fix? /workaround? > > -- > Joe Morris > New Tribes Mission > Email Address: Joe_Morris(a)ntm.org > Registered Linux user 231871 > > > > > > > -- > Check the headers for your unsubscription address > For additional commands send e-mail to suse-linux-e-help(a)suse.com > Also check the archives at http://lists.suse.com > Please read the FAQs: suse-linux-e-faq(a)suse.com > > >

1 0

how to install/update to java-1.5 in suse 9.3
by Gabor Istvan 14 Jun '05

14 Jun '05

Hello all: I am using Suse 9.3 installed with the default java-1.4 version. I would like to update java to 1.5. According to the infos I got by googling java 1.5 is available through YOU update. When I try to use YOU to install java 1.5 I can see java-1.5 patches only if the 'Show Patch Category' is set to 'All patches', however the patches are grayed out so I am not able to select them for installation. What should I do? I don't know if this does matter: I've installed Suse 9.3 from the CD set, not from the DVD as I have no DVD drive. Thanks, IG

2 3

Was there a question there?
by OldSarge 14 Jun '05

14 Jun '05

To Mr. Alfrey: Yes, the question was stated when I used the word "wish"!

3 2

How would I use this in linux.
by Carl William Spitzer IV 14 Jun '05

14 Jun '05

Seems to be a way to use USB to create a mini network of two computers? http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=… -- ___ _ _ _ ____ _ _ _ | | | | [__ | | | |___ |_|_| ___] | \/

5 6

Changing the label on a FAT partition?
by Kornelis Sietsma 14 Jun '05

14 Jun '05

This seems like a simple question, but I can't find a way to do it... How do I change the volume label on a FAT partition? Now that SuSE 9.3 mounts usb devices and the like on /media/VOLUME_LABEL, I want to change some of my devices to sensible names, but can't see how to do this without loading them in Windows, or re-formatting them. e2fs has the "e2label" program - is there an equivalent for Linux? - Korny -- Kornelis Sietsma e-mail: korny at my surname dot com

4 3

RE: [SLE] Top or bottom posting or being a troll or otherwise pos ting to either list.
by James D. Parra 14 Jun '05

14 Jun '05

>-----Original Message----- >From: Steven T. Hatton [mailto:hattons@globalsymmetry.com] >Sent: Tuesday, June 14, 2005 1:07 PM >To: suse-linux-e(a)suse.com >Subject: Re: [SLE] Top or bottom posting or being a troll or otherwise >posting to either list. > > One company, which shall remain nameless, introduced a mail >client that top posted by default, and made it difficult, or impossible, to >change that default. The result is that users of that inferior product.... <snip> Bravo! By the way, as a user of that unnamed inferior product, can you actually change the default to bottom post and, if so, how? Thanks, ~James

1 0

Re: [Samba] Permission on sharing file/folder
by James Knott 14 Jun '05

14 Jun '05

Paul Gienger wrote: >>Modifying a file and deleting it are two entirely different things. If >>you create or delete a file, you're modifying the file that describes >>the directory contents, not the contents of the directory. The most you >>can do, if you can't delete the file, is reduce it to zero bytes. >>However, you won't be able to delete the file. > > Since I think we've crossed into the theoretical here and completely > hijacked the OP, what use could this extra bit possibly have? If the data > is gone then the file just as well might be gone. I would have to think > this is probably close to the reason that there's only rwx in UNIX, > regardless of how many complex ACLs you have. > > I'm not discounting the possibility that the rwx+m permission structure has > a valid use-case, I'm just really struggling to find it. Can anyone > elaborate a good use? > It also prevents someone from creating a file. The whole idea is that one person can control what files are added or deleted in a directory, while allowing others to make changes to those files.

1 0