I just put some points to the agenda of the
I also checked the old meeting minutes for open action items. Here's
what seems to be still open (I added some comments in "[...]"):
Action Item skh, henne: [on hold till after 10.1 launch]
- Prepare and announcement for list migration to the internal SUSE
- risk assesment for the internal packagers list.
Action Item adrian:
- check again with IS&T about searchable archives. [nearly running]
Action Item cthiel, pascal:
- evaluate our FOSDEM participation after FOSDEM
Action Item everybody:
- Discuss Trust/Rating system at FOSDEM
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
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
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
Action Item henne:
- write SDB article about alternatives of subfs
Action item skh
- Add to the task force page
[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
Action Item notlocalhorst: [+ garloff]
- write documentation about the end user part of the KMP switch
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
Action Item henne/Klaus
- find out if we can help heiko with the postfix rewrites for the new
[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
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
- 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
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.
>... 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]
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.
___ _ _ _ ____ _ _ _
| | | | [__ | | |
|___ |_|_| ___] | \/
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
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
Please is there anyone out there using internal ZIP drive and not
having the above or very similar problems?!
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-
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.
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.
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
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
> 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?
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
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
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?
I wonder how SUSE Firewall works.
Back in Windows, with ZoneAlarm, when I first install it, it asks me for
permission and preconfigures my default browser and mail client to access the
net. After that, every new application that tries to access the net or every
incoming connection from the net, it asks me for permission.
But SUSE Firewall never asks me anything.
How do I know which applications it forbids and which it allows? How does it
know which applications to forbid and which to allow?
I would much prefer a ZoneAlarm-like firewall that tells me what it is doing.
Please share your knowledge with me. Thank you.
Tux #395953 resides at http://samvit.org
playing with KDE 3.51 on SUSE Linux 10.0
$ date  CCE +2006-03-10 W10-5 UTC+0530
Hi, i am downloaded and burned the first CD OSS installation CD.
Due to limited number of CD and fast internet connection, i wish to install
After mounting the NIC, I can't find installation file on ftp server.
I am using
Is this the right place to install via ftp?
If not, can you point me to a right directory. I am fast access to
mirror.ac.uk and wondering if there is direct installation files available
on the ftp server.
Thanks for your help!