March 2006 - openSUSE Users - openSUSE Mailing Lists

Suse 10.0 dd problems
by Carl William Spitzer IV 20 Apr '06

20 Apr '06

/dev/hdc /media/dvdrecorder auto noauto,ro,nosuid,nodev,exec 0 0 /dev/fd0 /media/floppy auto noauto,user 0 0 Assuming these changes are correct to rid me of automount. How do I make a DD of a cdrom? dd if=/media/cdrom/ of=./Suse9.2-1.dd bs=1k -- ___ _ _ _ ____ _ _ _ | | | | [__ | | | |___ |_|_| ___] | \/

6 10

[opensuse] Banners for OpenSuSE
by Chuck Payne 16 Apr '06

16 Apr '06

Is a place where I can get banners that I can place on my site? -- Do you know why we fall Master Wayne...so we can learn to get up. Alfred - Batman Begins

8 13

2006-03-07 status meeting
by Christian Boltz 15 Apr '06

15 Apr '06

Hello, I just put some points to the agenda of the http://en.opensuse.org/2006-03-07-status-meeting I also checked the old meeting minutes for open action items. Here's what seems to be still open (I added some comments in "[...]"): http://en.opensuse.org/2006-01-24-status-meeting Mailinglists: Action Item skh, henne: [on hold till after 10.1 launch] - Prepare and announcement for list migration to the internal SUSE lists. - risk assesment for the internal packagers list. Action Item adrian: - check again with IS&T about searchable archives. [nearly running] FOSDEM: Action Item cthiel, pascal: - evaluate our FOSDEM participation after FOSDEM Build Service: Action Item everybody: - Discuss Trust/Rating system at FOSDEM http://en.opensuse.org/2006-02-07-status-meeting Mirrors Action Item henne: - Discuss mirror situation in opensuse(a)opensuse.org [ongoing/done?] - Involve ftpadmin@suse in the discussion Action Item schiele: [2006-02-21: Discuss this at FOSDEM] - discuss how we can make the drpmsync service better - help in the documentation process, extending http://en.opensuse.org/How_to_setup_a_drpmsync_server Action Item notlocalhorst: - upload final 10.1 torrents to the wiki [just for the records, can't be done yet obviously ;-) ] opensuse.org frontpage redesign Action Item michl: - discuss front page redesign on opensuse-wiki Forum discussion Action Item Viras: - take the discussion to the forum people in suselinuxsupport.de forum Action item skh: - talk to suse internal people to see about resources, etc if the forum idea goes ok Action Item StormX: - invite the other forum maintainers to the suselinuxsupport.de opensuse-forum category subfs discussion Action Item henne: - write SDB article about alternatives of subfs [ -> http://en.opensuse.org/2006-02-21-status-meeting Action item skh - Add to the task force page ] LinuxTag [not an action item, but open questions:] - status of community booth? - really no "commercial" Novell booth? SDB migration to wiki Action Item notlocalhorst: - write HOWTO style-guide [2006-02-21: ongoing] - communicate that we want to keep SDB clean of HOWTO like writings [2006-02-21: unclear] 10.1 status Action Item notlocalhorst: [+ garloff] - write documentation about the end user part of the KMP switch http://en.opensuse.org/2006-02-21-status-meeting Status 10.1 Action Item AJaeger - add info about all the small YaST tools to the libzypp Wiki page Action Item skh / AJaeger - explain "Feature Freeze" on Factory and write something about the development model to Factory Status mailinglists Action Item henne/Klaus - find out if we can help heiko with the postfix rewrites for the new list server [additionally, a short status update would be a good idea] Creation of a Community Task from Meetings Action Item skh - create the Tasks Wiki page Action Item darix - take care of Bugzilla->Wiki piping for that page Wiki old Action Item henne: - Rework download page to match the new media layout -> Action item skh - Put on the task page old Action item michl: - Discuss front page redesign on opensuse-wiki -> Action item shk - Put on the task page I hope I did not miss anything and also didn't list things that are done already ;-) - feel free to correct me. While doing this list, I thought about a wiki page to manage open "action items" which could be a good method to avoid that things are forgotten. Proposed handling: - create a page "open action items" - after every meeting, collect all action items on that page (yes, that duplicates that information. But on the other hand, it avoids that you have to scan all meeting minutes - it needs more time, trust me ;-) - when an item is done, simply remove it from the "open action items" page (or: mark them as done, remove them two weeks later after the next meeting) Do you think this would be a good idea? If yes, I will create the "Open Action Items" page and add the listed items there. Regards, Christian Boltz -- >... Bücher sind ein grässliches Medium ... Ich schätze daran die leichte Portierbarkeit vom Sofa ins Bett. [Bjoern Hoehrmann und Peter Bieling in dciwam]

9 16

Re: [SLE] Suse 10.0 boot problem
by Carl William Spitzer IV 14 Apr '06

14 Apr '06

On Wed, 2006-03-29 at 09:20 +0200, Gerrit Jan > Try LILO...? > If you have more harddrives, where is Grub on? > You must change that in your bios? > The grub works once I get to the HD. The other drives from the old PIII died untimely deaths possibily caused by a faulty power supply. Only two drives survive that system the floppy and DVDRW. Powering them off does not prevent the boot problem. Looks like the bios just does not want to work correctly in spite of being told to boot from HD. -- ___ _ _ _ ____ _ _ _ | | | | [__ | | | |___ |_|_| ___] | \/

3 5

(IDE) Iomega ZIP 250 troubles on SUSE 10.0
by pelibali 11 Apr '06

11 Apr '06

Hi, I have a SUSE 10.0 system, having an internal Iomega 250Mb ZIP drive as secondary slave. Writing to any FAT-formatted ZIP disk the transfer was extremely SLOW and after I checked up the corresponding bug- reports and the list archive, saw two possibilities to move to higher writing speed. First I attempted to deactivate the sync writing, but that particular drive had no uuid under lshal, so couldn't define the async writing exclusively for that device. (I took the info from the SDB for 9.3.) Then I decided to move on automounting generally deactivated, but this with both sync and async didn't solve my problem. Of course async was seemingly quicker, but then attempting to umount the disk caused still 12-15 minutes waiting... I also checked the DMA settings, but the max. DMA/4.3 or similar I could activate, there was no other possibility. I don't think that it really counts, but the drive was not originally there in the comp, but was added later. Probably that's why an extra problem used to happen, when booting up with no ZIP disk in the drive I get only /dev/hdd, but no /dev/hdd4, so generally I can't even later manually mount the device! If I boot up with disk in the drive, the /dev/hdd4 is there or if was not there, alternatively I plug the disk in and then do _eject_ for it, then on a ridiculous way /dev/hdd4 appears suddenly... So I put back the disk and then I can really mount it. Is that bug or feature that SUSE recognizes the ZIP and doesn't put the corresponding device file there for manual mounting?! Of course /media/zip I made also by myself, but after deactivating automounter it is very OK. So at present I don't know, what is wrong; I read already, that the "slow-writing" bug should be gone by now. FYI: it is not with all the newest updates... Please is there anyone out there using internal ZIP drive and not having the above or very similar problems?! Thank you, Pelibali PS. Personal comment. I read the thread SUSE back and similar. For me SUSE means always _less_ and makes me worrying why I should load an earlier SUSE 9.x variant or use another distro everytime when I wish to do backup to a common ZIP-disk with no issues and/or speed-con- cerns.

3 8

official Novell translation team
by jdd 07 Apr '06

07 Apr '06

Hello :-) is there a mean to have contacts to the official Novell translation team? my purpose is to make the french translation of openSUSE compliant with the vocabulary used in the manuals I have a page here: http://fr.opensuse.org/Glossaire_d'équivalences_entre_l'anglais_et_le_français with some officials (government) french translation terms, I would like to have a similar thing from Novell. I beleive there are several translators and I could use some of they references or tools thanks jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos

7 16

connect to cellphone
by Richard 06 Apr '06

06 Apr '06

My new cellphone charges thru USB cable, dmesg says, "usb 1-10: new full speed USB device using ohci_hcd and address 9" when it is connected. What is this telling me about how I might access the linux file system on the phone? How do I discover the/a device name to use? Thanks for guidance to the confused. Richard

4 14

Could not mount device. floppy problem?
by C. Brouerius van Nidek 05 Apr '06

05 Apr '06

Have not used the floppy drive since quiet some time. As I wanted to mount the floppy I got the following info; Could not mount device. The reported error was: mount: only root can mount /dev/fd0 on /media/floppy Tried as as root and got the information; :/home/cons # mount /media/floppy mount: unknown filesystem type 'subfs' My fstab has following info about the floppy; /dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0 Have in the meantime also tried to mount the floppy as vfat because I use them mostly as DrDOS media. No success either. Could somebody help me with this medium? Additional info; I am running 9.3 on a Pentium II with KDE 3.5.

3 9

Re: [SLE] Which Linux?
by Allen 05 Apr '06

05 Apr '06

This was sent to me off list, I have no idea why. On Wednesday 29 March 2006 6:08 am, you wrote: > On 3/28/06, Allen <slackwarewolf(a)comcast.net> wrote: > > That's the scarey part. > > Now you are getting the implications of Novell's new SUSE strategy. > > After all these years? WTF are you talking about? I wasn't eh one saying > > > KDE > > was gone or not useable anymore.... > > Foul langauge ambly emphazies your shaky position. It is you who has now > chanced upon the supriority of Gnome, thus relegating KDE to the second > position. Can you learn how to actually quote? Dam I'm readin half my text with yours. What the HELL are you talking about foul lanaguage and a shaky what? > > > May be. But your priorities are changing. That is what the SUSEites are > > > > > worried about. > > > > Mine are changing? Don't think so. > > SUSE users will be really glad if it is actually so. > > Where in the hell are you getting this from? Novell never said they were > > > getting rid of KDE or any other desktop manager, so how would you NOT > > click > > on Gnome and hit enter? See that, it's the mangled left overs of a quote.... We sure got a smart one here. > > Your point - Gnome as default desktop is not a big issue. My point (and > many others', as you too pointed out earlier) - KDE - as default desktop is > not a big issue. Since we don't differ much, why tinker around with SUSE > for no valid reason? What the hell are you talking about tinkering? The WHOLE thing was about SUSE using Gnome by default, I pint out that was a load and not happening, and you... Are an idiot. > Actually it does as Slackware was what SUSE started with, so it would still > > > be > > on topic. And I've never heard one person complain about how Slackware is > > made. And being made by one person.... Whatever man. > > Not whatever man, Allen. The Man. > * > *From http://www.slackware.com/about/* > <volkerdi(a)slackware.com>*"Patrick Volkerding > <volkerdi(a)slackware.com>* *Also known to many as The Man. Without > Patrick, there would be no Slackware. > He has worked for many years and continues to work on this popular and > extremely stable distribution." > > See http://www.slackware-advocacy.org/whyuse.html > > "Slackware is maintained by a single person, Patrick Volkerding, who aims > at delivering a stable, reliable, and trustworthy operating system. Patrick > pays special attention to stability because an unstable system can neither > be trusted nor relied upon. For this reason, every version of Slackware > incorporates only the most stable, mature software packages available at > the time of its release." He's also one of my friends. What's your point?

15 35

...packages/SOURCES: getting full?; prod588.spec vs prod.spec; security concerns
by Linda Walsh 05 Apr '06

05 Apr '06

I was wondering how distribution creators dealt with this problem. It seems that the "sources" part of RPM management gets a bit confusing after a time. There isn't an "erase" or "uninstall" for source packages -- after they are distributed into the the /usr/src/packages directory, there isn't easy way to tell which sources in the "SOURCES" dir go with which package. Sure, one can go through each spec file by hand and attempt to come up with a list of sources one would remove from SOURCES, but it's not like in the "BUILD" directory where everything you need to delete regarding a package is generally in 1 directory. Would it be violating some "spec" or cause major disruptions if the SuSE distro managers/creators were to create package-specific subdirectories under SOURCES to hold the sources for the specific packages? I tend to build packages every once in a while and run into the problem of being able to "cleanup". The BUILD and SPEC directories are simple enough, but SOURCES? Ick. Another "problem", which is less of a problem is when one installs 2 SRPMS (say from suse 93 & suse 10) for the same package so one can compare changes and/or differences, etc. It would really be "useful" if, at least, the _spec_ files were named slightly differently for different major&minor versions. I.e. "Bash-3.0" would have spec bash30.spec, 3.1 -> bash31.spec. While the naming issue isn't too difficult to work around, the idea of putting each RPM's sources in a different subdirectory would be real helpful and significantly less of a security problem. It isn't unlikely that 2 different packages might have the same name for some source or patch, possibly variants on each other, or possibly nothing to do with each other. If one unpacks both, it's possible that one package might be built using the wrong source. I would agree it is an unlikely occurrence, but separate subdirectories under SOURCES would virtually eliminate possible source file name collisions between different packages. Is this doable or desirable? Linda

5 7