[opensuse] If I got SLES would my problems be solved quicker?
Am Sonntag, 5. Juni 2011, 14:12:04 schrieb Roger Oberholtzer:
It wants me to remove the package NetworkManager-kde4. Has that functionality been moved to other packages?
It is recommended to use the plasmoid for KDE > 4.5. The package is called plasmoid-networkmanagement or something like that and it replaces the monolithic knm, i.e. NetworkManager-kde4. There has been a lot of progress in the plasmoid so trying it is definitely worth it. Yeah. Thanks. Only just got around to it. It works well with supported wirless chipsets. But it still doesn't work with broadcom. I tried to install one and ended up having to leave her with a cable. This and graphic tablets still need attention I would say. Then opesuse would be a killer. Unless you pay for a wacom and even then it doesn't work. The Samba with apparmor still doesn't work. Serious network users need networking That Works out of the box. If I bought SLES would my problems be solved faster? Cheers. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 24 June 2011 10:17:11 pm lynn wrote:
Am Sonntag, 5. Juni 2011, 14:12:04 schrieb Roger Oberholtzer:
It wants me to remove the package NetworkManager-kde4. Has that functionality been moved to other packages?
It is recommended to use the plasmoid for KDE > 4.5. The package is called plasmoid-networkmanagement or something like that and it replaces the monolithic knm, i.e. NetworkManager-kde4.
There has been a lot of progress in the plasmoid so trying it is definitely worth it.
Yeah. Thanks. Only just got around to it. It works well with supported wirless chipsets. But it still doesn't work with broadcom. I tried to install one and ended up having to leave her with a cable.
This and graphic tablets still need attention I would say. Then opesuse would be a killer. Unless you pay for a wacom and even then it doesn't work.
The Samba with apparmor still doesn't work. Serious network users need networking That Works out of the box.
If I bought SLES would my problems be solved faster?
Cheers. L x
I still have 11.1 on my dell vostro 1710. the standard wifi card is a broadcom 4312. after installing the *oldest* possible firmware and running wicd instead of networkmanager (can't find that firmawre on the net any more), the wifi just works. sometimes it is a little slow in establishing a connection, but, in almost 3 years now, it has *never* failed in the us (la, sf,new york, dallas, seattle,pittsburgh etc),in canada (vancouver), in hawaii, in europe (france, italy, germany, austria, switzerland, slovakia, greece, hungary). tried 11.4 on a spare 12gb partition on the same laptop, could never make wifi to work, even with wicd. tried gubuntu 11.04 and kubuntu11.04 on the same partition, neither had a problem with the wifi, actually both make the connection almost instantaneously, faster than my standard 11.1. since i really don't know enough about ubuntu, my *main* os is still 11.1 /kde3. i will keep experimenting, but so far, that is my personal experience. my versions of firmware and fw cutter in 11.1 /x86-64 are: b43-firmware: 4.150.10.5-1.pm1.1 b43legacy-firmware: 3.130.20.0-1.pm1.1 b43-fwcutter 011.2.49 good luck, d. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 25/06/11 10:06, kanenas@hawaii.rr.com wrote:
It wants me to remove the package NetworkManager-kde4. Has that functionality been moved to other packages? It is recommended to use the plasmoid for KDE> 4.5. The package is called
Am Sonntag, 5. Juni 2011, 14:12:04 schrieb Roger Oberholtzer: plasmoid-networkmanagement or something like that and it replaces the monolithic knm, i.e. NetworkManager-kde4.
There has been a lot of progress in the plasmoid so trying it is definitely worth it.
Yeah. Thanks. Only just got around to it. It works well with supported wirless chipsets. But it still doesn't work with broadcom. I tried to install one and ended up having to leave her with a cable. Did you go through the firmware extraction process ('/usr/sbin/install_b43_firmware')? Otherwise, did you try the broadcom-wl package from packman? This and graphic tablets still need attention I would say. Then opesuse would be a killer. Unless you pay for a wacom and even then it doesn't work.
The Samba with apparmor still doesn't work. Serious network users need networking That Works out of the box.
If I bought SLES would my problems be solved faster?
Cheers. L x I still have 11.1 on my dell vostro 1710. the standard wifi card is a broadcom
On Friday 24 June 2011 10:17:11 pm lynn wrote: 4312. after installing the *oldest* possible firmware and running wicd instead of networkmanager (can't find that firmawre on the net any more), the wifi just works. sometimes it is a little slow in establishing a connection, but, in almost 3 years now, it has *never* failed in the us (la, sf,new york, dallas, seattle,pittsburgh etc),in canada (vancouver), in hawaii, in europe (france, italy, germany, austria, switzerland, slovakia, greece, hungary). tried 11.4 on a spare 12gb partition on the same laptop, could never make wifi to work, even with wicd. tried gubuntu 11.04 and kubuntu11.04 on the same partition, neither had a problem with the wifi, actually both make the connection almost instantaneously, faster than my standard 11.1. since i really don't know enough about ubuntu, my *main* os is still 11.1 /kde3. i will keep experimenting, but so far, that is my personal experience.
my versions of firmware and fw cutter in 11.1 /x86-64 are:
b43-firmware: 4.150.10.5-1.pm1.1 b43legacy-firmware: 3.130.20.0-1.pm1.1 b43-fwcutter 011.2.49
good luck, d.
My 4312 on 11.4 worked pretty much out of the box with b43-firmware etc., with the caveat that you have to add "pio=1 qos=0" to the b43 module options (found from the b43 web page). Regards, Tejas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 6/25/2011 4:16 AM, Tejas Guruswamy wrote:
My 4312 on 11.4 worked pretty much out of the box with b43-firmware etc., with the caveat that you have to add "pio=1 qos=0" to the b43 module options (found from the b43 web page).
That's a long way from out of the box if you ask me. Enough to stymy most novices and more than few ubuntu converts. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2011-06-25 at 10:17 +0200, lynn wrote:
Am Sonntag, 5. Juni 2011, 14:12:04 schrieb Roger Oberholtzer:
It wants me to remove the package NetworkManager-kde4. Has that functionality been moved to other packages?
It is recommended to use the plasmoid for KDE > 4.5. The package is called plasmoid-networkmanagement or something like that and it replaces the monolithic knm, i.e. NetworkManager-kde4.
There has been a lot of progress in the plasmoid so trying it is definitely worth it.
Yeah. Thanks. Only just got around to it. It works well with supported wirless chipsets. But it still doesn't work with broadcom. I tried to install one and ended up having to leave her with a cable.
This and graphic tablets still need attention I would say. Then opesuse would be a killer. Unless you pay for a wacom and even then it doesn't work.
The Samba with apparmor still doesn't work. Serious network users need networking That Works out of the box.
If I bought SLES would my problems be solved faster?
Cheers. L x Have you tried a nic wrapper? Does SLES have all the codecs? ie video and sound/music. Maybe an SLES and OpenSuse Online Store?
Sincerely, -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 25/06/11 04:17, lynn escribió:
Am Sonntag, 5. Juni 2011, 14:12:04 schrieb Roger Oberholtzer:
If I bought SLES would my problems be solved faster?
No, SLES is for servers and SLED is targetted at corporations. If you describe your problem clearly we may be able to help you. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 6/25/2011 1:17 AM, lynn wrote:
The Samba with apparmor still doesn't work. Serious network users need networking That Works out of the box.
Cheers. L x
I can't comment on any of your other points, but the above is simply not true. Samba works fine with AppArmor. The "out of the box" bit suggests you want to put it up with no configuration and expect it to work immediately, which, if it would work that way would be rather insecure, and / or require omniscience that no one really has. So just a small amount of configuration is necessary for AppArmor. Leave AppArmor running and fire up samba. It will probably fail. As root Open Yast and select Update Profile Wizard. (or use command line "genprof") It will list everything Samba tried to access before AppArmor shut it down for access violations. Look carefully at these to make sure they are Samba related (under the scenario of a new machine they always will be), and use the controls in the Profile Wizard to allow access to these. Restart Samba. Rinse, lather, repeat. Each time Samba gets a little farther. The whole process takes about 5 minutes and about 3 to 5 retries. When Samba is up and running, have someone open a few files . Probably AppArmor will stop that as well. Again launch profile wizard, but this time notice that "Glob" button. So even tho the user tried to open /corporate/data/historical-documents/fy1993-capital-budget.doc you don't want to be building AppArmor rules for that level of detail. So each time you hit the Glob button, it will remove a directory node. In this case you would hit glob till only /corporate was left in the path and tell AppArmor to go ahead with that. This whole process takes 15 minutes, and then its done. You have your Samba and your AppArmor too. I don't think that is too much for a System Administrator to do. Should the Samba configuration also tap AppArmor on the shoulder and tell the detailed changes it needs? Perhaps. But instead of writing code to be inserted in every project, (A never ending task), the AppArmor guys wrote a wizard that can figure out what is needed for ANY package, and give the user detailed control over it. So you can just as easily customize the AppArmor profiles on the fly. I haven't had a bit of trouble with AppArmor and Samba since I did this. There should be some rather lucid html documentation on this located in /usr/share/doc/manual/opensuse-manuals/cha.apparmor.start.html but quite frankly it just started playing with the wizard in yast and figured it out. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 25 Jun 2011 19:56:26 you wrote:
On 6/25/2011 1:17 AM, lynn wrote:
The Samba with apparmor still doesn't work. Serious network users need networking That Works out of the box.
Cheers. L x
I can't comment on any of your other points, but the above is simply not true. Samba works fine with AppArmor.
The "out of the box" bit suggests you want to put it up with no configuration and expect it to work immediately, which, if it would work that way would be rather insecure, and / or require omniscience that no one really has.
So just a small amount of configuration is necessary for AppArmor.
Leave AppArmor running and fire up samba. It will probably fail.
As root Open Yast and select Update Profile Wizard. (or use command line "genprof")
It will list everything Samba tried to access before AppArmor shut it down for access violations.
Look carefully at these to make sure they are Samba related (under the scenario of a new machine they always will be), and use the controls in the Profile Wizard to allow access to these.
Restart Samba.
Rinse, lather, repeat. Each time Samba gets a little farther. The whole process takes about 5 minutes and about 3 to 5 retries.
When Samba is up and running, have someone open a few files . Probably AppArmor will stop that as well.
Again launch profile wizard, but this time notice that "Glob" button. So even tho the user tried to open /corporate/data/historical-documents/fy1993-capital-budget.doc you don't want to be building AppArmor rules for that level of detail. So each time you hit the Glob button, it will remove a directory node. In this case you would hit glob till only /corporate was left in the path and tell AppArmor to go ahead with that.
This whole process takes 15 minutes, and then its done. You have your Samba and your AppArmor too. I don't think that is too much for a System Administrator to do.
Should the Samba configuration also tap AppArmor on the shoulder and tell the detailed changes it needs? Perhaps. But instead of writing code to be inserted in every project, (A never ending task), the AppArmor guys wrote a wizard that can figure out what is needed for ANY package, and give the user detailed control over it.
So you can just as easily customize the AppArmor profiles on the fly.
I haven't had a bit of trouble with AppArmor and Samba since I did this.
There should be some rather lucid html documentation on this located in /usr/share/doc/manual/opensuse-manuals/cha.apparmor.start.html but quite frankly it just started playing with the wizard in yast and figured it out. Well I tried that and the only way Samba would work was to disable apparmor. That was months ago but it's still working. N. What I was looking for was a fix, not stp staty worksround. Thanks for repling in detil though. Lx -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Jun 26, 2011 at 08:36:22AM +0200, lynn wrote:
On Saturday 25 Jun 2011 19:56:26 you wrote:
On 6/25/2011 1:17 AM, lynn wrote:
The Samba with apparmor still doesn't work. Serious network users need networking That Works out of the box.
Cheers. L x
I can't comment on any of your other points, but the above is simply not true. Samba works fine with AppArmor.
The "out of the box" bit suggests you want to put it up with no configuration and expect it to work immediately, which, if it would work that way would be rather insecure, and / or require omniscience that no one really has.
So just a small amount of configuration is necessary for AppArmor.
Leave AppArmor running and fire up samba. It will probably fail.
As root Open Yast and select Update Profile Wizard. (or use command line "genprof")
It will list everything Samba tried to access before AppArmor shut it down for access violations.
Look carefully at these to make sure they are Samba related (under the scenario of a new machine they always will be), and use the controls in the Profile Wizard to allow access to these.
Restart Samba.
Rinse, lather, repeat. Each time Samba gets a little farther. The whole process takes about 5 minutes and about 3 to 5 retries.
When Samba is up and running, have someone open a few files . Probably AppArmor will stop that as well.
Again launch profile wizard, but this time notice that "Glob" button. So even tho the user tried to open /corporate/data/historical-documents/fy1993-capital-budget.doc you don't want to be building AppArmor rules for that level of detail. So each time you hit the Glob button, it will remove a directory node. In this case you would hit glob till only /corporate was left in the path and tell AppArmor to go ahead with that.
This whole process takes 15 minutes, and then its done. You have your Samba and your AppArmor too. I don't think that is too much for a System Administrator to do.
Should the Samba configuration also tap AppArmor on the shoulder and tell the detailed changes it needs? Perhaps. But instead of writing code to be inserted in every project, (A never ending task), the AppArmor guys wrote a wizard that can figure out what is needed for ANY package, and give the user detailed control over it.
So you can just as easily customize the AppArmor profiles on the fly.
I haven't had a bit of trouble with AppArmor and Samba since I did this.
There should be some rather lucid html documentation on this located in /usr/share/doc/manual/opensuse-manuals/cha.apparmor.start.html but quite frankly it just started playing with the wizard in yast and figured it out. Well I tried that and the only way Samba would work was to disable apparmor. That was months ago but it's still working. N. What I was looking for was a fix, not stp staty worksround. Thanks for repling in detil though. Lx
You could have just removed/disabled the samba related profiles. /etc/apparmor.d/usr.sbin.nmbd and /etc/apparmor.d/usr.sbin.smbd (perhaps just smbd for fileserving) Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Sonntag, 26. Juni 2011, 08:36:22 schrieb lynn:
I can't comment on any of your other points, but the above is simply not true. Samba works fine with AppArmor.
The "out of the box" bit suggests you want to put it up with no configuration and expect it to work immediately, which, if it would work that way would be rather insecure, and / or require omniscience that no one really has.
So just a small amount of configuration is necessary for AppArmor.
Leave AppArmor running and fire up samba. It will probably fail.
As root Open Yast and select Update Profile Wizard. (or use command line "genprof")
It will list everything Samba tried to access before AppArmor shut it down for access violations.
Look carefully at these to make sure they are Samba related (under the scenario of a new machine they always will be), and use the controls in the Profile Wizard to allow access to these.
Restart Samba.
Rinse, lather, repeat. Each time Samba gets a little farther. The whole process takes about 5 minutes and about 3 to 5 retries.
When Samba is up and running, have someone open a few files . Probably AppArmor will stop that as well.
Again launch profile wizard, but this time notice that "Glob" button. So even tho the user tried to open /corporate/data/historical-documents/fy1993-capital-budget.doc you don't want to be building AppArmor rules for that level of detail. So each time you hit the Glob button, it will remove a directory node. In this case you would hit glob till only /corporate was left in the path and tell AppArmor to go ahead with that.
This whole process takes 15 minutes, and then its done. You have your Samba and your AppArmor too. I don't think that is too much for a System Administrator to do.
Should the Samba configuration also tap AppArmor on the shoulder and tell the detailed changes it needs? Perhaps. But instead of writing code to be inserted in every project, (A never ending task), the AppArmor guys wrote a wizard that can figure out what is needed for ANY package, and give the user detailed control over it.
So you can just as easily customize the AppArmor profiles on the fly.
I haven't had a bit of trouble with AppArmor and Samba since I did this.
There should be some rather lucid html documentation on this located in /usr/share/doc/manual/opensuse-manuals/cha.apparmor.start.html but quite frankly it just started playing with the wizard in yast and figured it out.
Should this HOWTO not be in the openSUSE wiki? Would you mind me putting it there? Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 6/26/2011 1:52 AM, Sven Burmeister wrote:
Am Sonntag, 26. Juni 2011, 08:36:22 schrieb lynn:
I can't comment on any of your other points, but the above is simply not true. Samba works fine with AppArmor.
The "out of the box" bit suggests you want to put it up with no configuration and expect it to work immediately, which, if it would work that way would be rather insecure, and / or require omniscience that no one really has.
So just a small amount of configuration is necessary for AppArmor.
Leave AppArmor running and fire up samba. It will probably fail.
As root Open Yast and select Update Profile Wizard. (or use command line "genprof")
It will list everything Samba tried to access before AppArmor shut it down for access violations.
Look carefully at these to make sure they are Samba related (under the scenario of a new machine they always will be), and use the controls in the Profile Wizard to allow access to these.
Restart Samba.
Rinse, lather, repeat. Each time Samba gets a little farther. The whole process takes about 5 minutes and about 3 to 5 retries.
When Samba is up and running, have someone open a few files . Probably AppArmor will stop that as well.
Again launch profile wizard, but this time notice that "Glob" button. So even tho the user tried to open /corporate/data/historical-documents/fy1993-capital-budget.doc you don't want to be building AppArmor rules for that level of detail. So each time you hit the Glob button, it will remove a directory node. In this case you would hit glob till only /corporate was left in the path and tell AppArmor to go ahead with that.
This whole process takes 15 minutes, and then its done. You have your Samba and your AppArmor too. I don't think that is too much for a System Administrator to do.
Should the Samba configuration also tap AppArmor on the shoulder and tell the detailed changes it needs? Perhaps. But instead of writing code to be inserted in every project, (A never ending task), the AppArmor guys wrote a wizard that can figure out what is needed for ANY package, and give the user detailed control over it.
So you can just as easily customize the AppArmor profiles on the fly.
I haven't had a bit of trouble with AppArmor and Samba since I did this.
There should be some rather lucid html documentation on this located in /usr/share/doc/manual/opensuse-manuals/cha.apparmor.start.html but quite frankly it just started playing with the wizard in yast and figured it out.
Should this HOWTO not be in the openSUSE wiki? Would you mind me putting it there?
Sven
Have at it. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Yes, I think more attention is paid to SLES/SLED bugs. I've opened the same bug for both and when openSUSE was closed/ignored as usual, enterprise bug stayed open and received more attention. Soon is starting some SLE beta testing. If you can get in that and report your issues there's a good chance it will be solved. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Andrew Joakimsen -
Cristian Rodríguez -
John Andersen -
kanenas＠hawaii.rr.com -
lynn -
Marcus Meissner -
Sven Burmeister -
Tejas Guruswamy -
William Schifano