M Harris wrote:

I always create a local directory on my usb drive partitions because sometimes the permissions get messed up on the mount point. So, instead of trying to create new directories on the mount point... I create them on an "inside" directory one level off the mount point... if that makes sense.

I do this too, I always have done since I first ran into the problem that Duff is having now. But it always seems like a bodge to me, does anyone know if it is possible to allow unrestricted access to the root of a filesystem or do you always need to be root? James.

Hi all, My laptop was running Suse 9.3 until recently, and the wireless networking was working pretty well. It showed up as ath0, and I used "netgo" to manually activate it and connect to any given network. Since upgrading to 10.1 I don't seem to have any live wireless device at all, and Atheros isn't on the list of wireless network hardware that Yast is offering me. hwinfo still shows the device, but I don't really know what the output means. Can someone point me in the right direction? Ideally, I'd like to have manual control of wireless, as I like to leave it off until I deliberately choose to connect to a network. Also, I connect to both secured (WEP) and open networks. TIA, Simon "You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." — Naguib Mahfouz __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Gosh, wow, that was unexpected! I don't recall anything like this in the 9.3 release. Oh well, I'll give that a go. Hope I can get wired networking to work! Thanks all for the pointers, Cheers, Simon --- Per Jessen wrote:

Simon Roberts wrote:

...

Since upgrading to 10.1 I don't seem to have any live wireless device at all, and Atheros isn't on the list of wireless network hardware that Yast is offering me.

Correct, you need to install the madwifi stuff yourself. (licensing issue, I believe) Personally, I just downloaded the latest and greatest from madwifi and did the install, but there might very well be an RPM package out there somewhere.

/Per Jessen, Zürich

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

"You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." — Naguib Mahfouz __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

This worked. Thanks! Simply installing the rpm didn't work, the rpm didn't include the ath_pci module file at all. Very strange. But when I got the source, and built it according to these instructions, it's now working great. Even the NetworkManager thing works well too, which is a great improvement over 9.3. Thanks all, Simon --- Geoffrey wrote:

Simon Roberts wrote:

...

Gosh, wow, that was unexpected! I don't recall anything like this in the 9.3 release. Oh well, I'll give that a go. Hope I can get wired networking to work!

I found this page and followed these instructions and it worked like a champ:

http://linux.wordpress.com/2006/05/21/suse-101-and-atheros-based-wifi-cards/

-- Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin

"You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." — Naguib Mahfouz __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

On 26/09/06 17:22, Bruce Marshall wrote:

On Tuesday 26 September 2006 17:28, Simon Roberts wrote:

...

Gosh, wow, that was unexpected! I don't recall anything like this in the 9.3 release. Oh well, I'll give that a go. Hope I can get wired networking to work!

All non-kernel modules were dropped by SuSE in 10.1.. That is, modules which were not officially part of the kernel. The kernel developers want it this way. Thus, you must add in your own wifi module.

Scenario: a brand new SuSE user buys a brand new computer and gets a brand new internet connection from a service provider. They are of course shifty folks, and sell him on the idea of connecting to their brand new city-wide wireless network (and of course, this will not add to the traffic on their already-saturated cable network, so it is a benefit to them). Oops, our brand new SuSE user has bought 10.1, and has no wifi support on the DVD.. he cannot get on the internet to download the wifi module(s) he needs, and what is even worse, the 10.1 installer probably will not even tell him he needs to do so (even if it does happen to recognize his nifty new 802.11n prototype card the ISP is hawking which it probably won't). All of you who think the kernel developers are smart folks, and who think our brand new SuSE user is going to dash off to his local city library, floppy in hand, to download, configure/compile, and install the module source he needs (to say nothing of recompiling the kernel, if necessary), please raise your hands. None of you? How many think our brand new SuSE user will simply toss his package into the trash, and dash off to buy <the operating system from Redmond>, which he knows from all his friends will support his nifty new wireless card, right out of the box? (For Jeff Rollins: this is sarcasm and condescension, not abusiveness -- I trust/hope you know the difference.)

On 26/09/06 19:55, Simon Roberts wrote:

<snip>

Meanwhile, what other modules will I find I don't have? So far stuff is working fairly well (except vmware at least).

As of the moment, nothing that I can think of. In the future, nothing important.. just a bunch of non-GPL USB stuff.

--- Darryl Gregorash wrote: ...

Oops, our brand new SuSE user has bought 10.1, and has no wifi support on the DVD How many think our brand new SuSE user will simply toss his package into the trash, and dash off to buy <the operating system from Redmond>, which he knows from all his friends will support his nifty new wireless card, right out of the box?

Native driver support in Windows is very poor compared to Linux, the only difference is that if you buy a peripheral it'll come with a Windows driver CD. It's not fair to blame Linux for a lack of drivers when more often then not when you install it it'll support all your hardware from the off whereas you'll need driver disks for each device to get Windows to do the same. M.

Darryl Gregorash wrote:

...

a brand new SuSE user buys a brand new computer and gets a brand new internet connection from a service provider. They are of course shifty folks, and sell him on the idea of connecting to their brand new city-wide wireless network (and of course, this will not add to the traffic on their already-saturated cable network, so it is a benefit to them).

Oops, our brand new SuSE user has bought 10.1, and has no wifi support on the DVD.. he cannot get on the internet to download the wifi module(s) he needs, and what is even worse, the 10.1 installer probably will not even tell him he needs to do so (even if it does happen to recognize his nifty new 802.11n prototype card the ISP is hawking which it probably won't).

A brand new user right out there on the bleeding edge? - that's asking for it. Selber schuld. I said I was being sarcastic, Per -- but go to madwifi's website, and

On 27/09/06 02:14, Per Jessen wrote: pick any card with 802.11a/b or g that is listed. If that is what our brand new user gets from his provider, he's still f***ed right from the start, and he's still going to dump linux and go back to windows.

On Tue, Sep 26, 2006 at 07:22:15PM -0400, Bruce Marshall wrote:

On Tuesday 26 September 2006 17:28, Simon Roberts wrote:

...

Gosh, wow, that was unexpected! I don't recall anything like this in the 9.3 release. Oh well, I'll give that a go. Hope I can get wired networking to work!

All non-kernel modules were dropped by SuSE in 10.1.. That is, modules which were not officially part of the kernel. The kernel developers want it this way. Thus, you must add in your own wifi module.

Wrong, we only dropped kernel modules which do not comply with the GPL. Ciao, Marcus

----- Original Message ---- From: Simon Roberts To: SLE Sent: Tuesday, September 26, 2006 9:16:19 AM Subject: [SLE] Wireless config in Suse 10.1 Hi all, My laptop was running Suse 9.3 until recently, and the wireless networking was working pretty well. It showed up as ath0, and I used "netgo" to manually activate it and connect to any given network. Since upgrading to 10.1 I don't seem to have any live wireless device at all, and Atheros isn't on the list of wireless network hardware that Yast is offering me. <snip> Try adding http://madwifi.org/suse/ to your installation sources. Then you should be able to install the packages that you need.

On 9/26/06, James Watkins wrote:

Thanks for prodding my brain into gear Carlos. The mistake I had been making was to change the permissions before mounting the filesystem and wondering why they would always revert to 755 after mounting. It also turns out that you can in fact change the permissions and even the ownership for "/". Funnily enough "chmod 777 /" is not a command that I've ever tried before.

Makes me think about rm -rf /. Another command I've never tried (and hopefully never will.) As they say, UNIX/Linux is not designed to protect you from yourself so most commands work, even if you think they are too dangerous to try. Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century

On Tuesday 26 September 2006 1:20 pm, stephan beal wrote:

i once had my laptop at work and it had an open shell window. When i wasn't looking, a Linux-knowledgable colleague of mine thought it would be funny to type in 'rm -fr /' and see if i got upset. Being a seasoned Viet Nam veteran with a few notches, no colleague of mine would dare :-) -- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-09-26 at 17:49 +0100, James Watkins wrote:

Thanks for prodding my brain into gear Carlos. The mistake I had been making was to change the permissions before mounting the filesystem and wondering why they would always revert to 755 after mounting.

That's easy to forget ;-)

It also turns out that you can in fact change the permissions and even the ownership for "/". Funnily enough "chmod 777 /" is not a command that I've ever tried before.

Gosh! :-O I had no idea that would be possible. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFGaI7tTMYHG2NR9URAufTAJ9ZiOXLgVUb288o2qzS/ikavdwljwCfU4K+ E4AlwzISgjsUJPvaXKQogTg= =V5j7 -----END PGP SIGNATURE-----

On 9/28/06, Duff Mckagan wrote:

On 9/26/06, Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Tuesday 2006-09-26 at 13:10 +0100, James Watkins wrote:

...

I do this too, I always have done since I first ran into the problem that Duff is having now. But it always seems like a bodge to me, does anyone know if it is possible to allow unrestricted access to the root of a filesystem

Of course you can, provided you define the appropriate permissions.

But I very seldom use konqueror; if it can't, it is a bug.

I guess it really is a bug...

Wait, hold on! If by "root" you mean "/", then no, you can not. If you

...

mean the root of something mounted in /mnt/data (for instance), then yes, you can.

What exactly do you mean by that??

I forgot to tell you guys something that makes my point... I also have Slackware installed on this very same system. But it never exhibited a problem with the inability to create a new Directory/ File. The command entered to change the permissions on the mounted partition was the same everywhere. #chmod -R 777 /mnt/data After this, be it an arbitrary user or whoever...the user was able to write and read into this mounted XFS partition. Also, this partition is there in fstab and it automatically mounts at boot. The options are "default" . But as it turns out, the problem is only there in SuSE. A bug..maybe?? - --

...

Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76

iD8DBQFFGTvGtTMYHG2NR9URAsOFAJoC7+nW5q6y5l5GcBEfKUxf4ZRrJwCfV6Uu jWfav6lRvs44y90RDQj/N4o= =+bOx -----END PGP SIGNATURE-----

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

-- http://mckagan.googlepages.com

-- http://mckagan.googlepages.com

On 9/28/06, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Thursday 2006-09-28 at 09:22 +0530, Duff Mckagan wrote:

...

...

...

Wait, hold on! If by "root" you mean "/", then no, you can not. If you mean the root of something mounted in /mnt/data (for instance), then yes, you can.

What exactly do you mean by that??

That you can't change the permissions of the root directory, ie, "/".

Or that's what I thought, but James Watkins proved me wrong.

Thats what I thought too..but the text was quite confusing. :)

I forgot to tell you guys something that makes my point...

...

I also have Slackware installed on this very same system. But it never exhibited a problem with the inability to create a new Directory/ File.

The command entered to change the permissions on the mounted partition

was

...

the same everywhere.

#chmod -R 777 /mnt/data

Remember, just in case, that the partition should be mounted at that time. Also (I prefer letters to octal mode) remember that directories must have the "x" permission. I don't remember what "7" means, my octal math neurone is sleeping yet. :-)

...

After this, be it an arbitrary user or whoever...the user was able to write and read into this mounted XFS partition.

Also, this partition is there in fstab and it automatically mounts at boot. The options are "default" .

Try the same changes as user with command line. If you can, but Konqueror can't, it is a bug. Or it needs to reload the tree to see changes.

Yes. I will try it out via command line. But there's one more thing..if I create a new folder, I have to refresh the page in order to see the newly created or deleted file... It requires to Reload the Tree maybe...but I don't think that is anyway related to my problem..of not being able to create new folders. I guess its a Konqueror Bug. Will add inputs about the command line part later...:)

But as it turns out, the problem is only there in SuSE.

...

A bug..maybe??

Dunno. As I said, I almost don't use konqueror.

- -- Cheers, Carlos E. R.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76

iD8DBQFFG53UtTMYHG2NR9URAnw/AJsG91ekNy5nSQDYGmmmNbxq5zAqjACghFQQ 9yjhsex6Csy1s6gPESN/bwI= =oED6 -----END PGP SIGNATURE-----

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

-- http://mckagan.googlepages.com