Re: NEWBEE "reverse ioctl" or someting like
Hello, On Thu, 3 May 2001, sébastien person wrote: > I think that use of pipe isn't preconised because I must fork process > to use pipe, I search something like ioctl but in the other way : > > kernel process ---> user process What about using /proc/ ? Gruß, Markus -- | Gluecklich ist, wer vergisst, was nicht aus ihm geworden ist. +---. ,> http://www.uni-ulm.de/~s_mschab/ \ / mailto:[EMAIL PROTECTED] \_/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
The further way? (was: Re: AHA-154X/1535 not recognized any more)
Hello, Markus Schaber wrote: [some Test results] So what's the further way to go? We found out that the kernel isapnp fails, while the isapnptools (with "check" entry removed and the driver as a module) and a non-pnp environment (where the BIOS initialzies it, and either a modularized and a compiled in driver) work with this card. Do I (as a non-kernel-hacker, and with only basic C experience) have any chance to quickly read into the code and find and correct the bug? Or is there anyone around here who just needs five minutes to adjust a few lines? As I said, I don't need the card any more, and am just waiting for this thing to be resolved, and then I remove this ancient thing. I could even send it to one of you per snail mail for some weeks to let you do further tests. My intention was to give a possibility to get the bug fixed :-) markus -- Markus Schaber -- http://www.schabi.de/ -- ICQ: 22042130 +-+ | Allgemeine Sig-Verletzung 0815/4711| +-+ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Single user linux
On Wed, 25 Apr 2001, Rick Hohensee wrote: > [EMAIL PROTECTED] wrote: > > for those who didn't read that patch, i #define capable(), > > suser(), and fsuser() to 1. the implication is all users > > will have root capabilities. > > How is that not single user? Every user still has it's own account, means profile etc. Gruß, Markus -- | Gluecklich ist, wer vergisst, was nicht aus ihm geworden ist. +---. ,> http://www.uni-ulm.de/~s_mschab/ \ / mailto:[EMAIL PROTECTED] \_/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [OFFTOPIC] Re: [PATCH] Single user linux
Hello, On Tue, 24 Apr 2001, Alan Cox wrote: > > Now, in order for step 4 to be done safely, procmail should be running > > as the user it's meant to deliver the mail for. for this to happen > > sendmail needs to start it as that user in step 3 and to do that it > > needs extra privs, above and beyond that of a normal user. > > email -> sendmail > sendmail 'its local' -> spool > > user: > get_mail | procmail > mutt > > The mail server doesnt need to run procmail. If you wanted to run mail batches > through on a regular basis you can use cron for it, or leave a daemon running Oh, well, cron is just another suid program. This example would just be the ideal scenario for posix- or novell-style ACLs in the filesystem. You run the MDA/MTA under some mailerdaemon uid. And then a user can explicitly give this daemon read access to .procmail etc. You can also give the MTA (and nobody else) write access to /var/spool/mail. The MDA then gives the specifical user full access to the spoolfile when creating it, or adding mail to it. And the user can fetch his mail and truncate or delete the file just as he and his software is used to. There are much more things with ACLs, especially in workgroup environments (That's why I loved the old Novel server in our university), but they never got into the kernel. And as far as I (as a non-hacker) understand, the fields reserved for this feature were dropped for the large file support, so we may never see ACLs. Gruß, Markus -- | Gluecklich ist, wer vergisst, was nicht aus ihm geworden ist. +---. ,> http://www.uni-ulm.de/~s_mschab/ \ / mailto:[EMAIL PROTECTED] \_/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHA-154X/1535 not recognized any more [Repost]
As it seems my original Messages didn't get through, a Repost here: Original Message Subject: Re: AHA-154X/1535 not recognized any more Date: Fri, 20 Apr 2001 14:07:51 +0200 (MEST) From: Markus Schaber <[EMAIL PROTECTED]> To: Alan Cox <[EMAIL PROTECTED]> CC: Markus Schaber <[EMAIL PROTECTED]>,Linux Kernel Mailing List <[EMAIL PROTECTED]> On Wed, 18 Apr 2001, Alan Cox wrote: > > Well, as this device is already configured by the bios, I just tried > > to load it giving the right IO port, and got the following message: > > The kernel PnP will deconfigure it Ah, interesting. > The module parameters are > > aha1542=io, irq, busff, dmaspeed I recompiled the kernel with isapnp-support and statically compiled driver. I then typed aha1542=0x330 at the lilo prompt, but the card wasn't recognized (see dmesg_pnp_bootparam.txt on http://schabi.de/scsi/). isapnp will initialize the card when the check entry is removed, but doesn't activate the driver. I'll next test with modularized driver, and the isapnp tools. markus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHA-154X/1535 not recognized any more [Repost]
As my original message seems to have disappeared, here a Repost:
Original Message
Subject: Re: AHA-154X/1535 not recognized any more
Date: Fri, 20 Apr 2001 14:28:14 +0200 (MEST)
From: Markus Schaber <[EMAIL PROTECTED]>
To: "Rafael E. Herrera" <[EMAIL PROTECTED]>
CC: Markus Schaber <[EMAIL PROTECTED]>,Alan Cox
<[EMAIL PROTECTED]>,Linux Kernel Mailing List
<[EMAIL PROTECTED]>
On Wed, 18 Apr 2001, Rafael E. Herrera wrote:
> > lunix:~# isapnp pnpconfig.txt
> > Board 1 has Identity 08 0f 6d b9 45 42 15 90 04: ADP1542 Serial No 258849093
>[checksum 08]
> > pnptext:60 -- Fatal - IO range check attempted while device activated
> > pnptext:60 -- Fatal - Error occurred executing request ' ' --- further
>action aborted
>
> I've a pnp sound card that fails to configure with a similar error
> message when a (CHECK) entry was found in an (IO ...) block. Removing
> those entries solved the problem. Try this in your pnpconfig.txt:
>
> (IO 0 (SIZE 4) (BASE 0x0330))
In this case, isapnp configures the card.
Using a modularized kernel, modprobe also loads the driver without any
further parameters:
lunix:/home/schabi/public_html/scsi# /rescue/sbin/isapnp
pnpconfig_nocheck.txt
Board 1 has Identity 08 0f 6d b9 45 42 15 90 04: ADP1542 Serial No
258849093 [checksum 08]
ADP1542/258849093[0]{SCSI Host Adapter }: Port 0x330; IRQ10 DMA0 ---
Enabled OK
lunix:/home/schabi/public_html/scsi# modprobe aha1542
lunix:/home/schabi/public_html/scsi#
ls /proc/scsi
advansys aha1542 ide-scsi scsi sg
lunix:/home/schabi/public_html/scsi# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: YAMAHA Model: CRW8424S Rev: 1.0j
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: IOMEGA Model: ZIP 100 Rev: 03.H
Type: Direct-AccessANSI SCSI revision:
Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: SAMSUNG Model: CD-ROM SCR-3231 Rev: S104
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 06 Lun: 00
Vendor: IOMEGA Model: ZIP 100 PLUS Rev: J.66
Type: Direct-AccessANSI SCSI revision: 02
So the isapnp tools can configure the card correctly.
markus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [kbuild-devel] Request for comment -- a better attribution system
Hi, mirabilos wrote: > > > It whould nice also if we include the type of the license (GPL,...). > > > This for a fast parsing (and maybe also to replace the few lines > > > of license) > > Is there any kernel code that isn't GPLed? > It must not, due to the GPL viral effect. Well, would it be possible to create some module under LGPL, and then have included it into the kernel? Maybe it needs to maintain the LGPL version out of the kernel, and transform a copy to the GPL before submitting? Or what about using a "twin-licence" that states "you can apply GPL or $another_licence, whichever you want"? And what about real "public domain" software, where the author gave up all rights? (AFAIK, this is not legally possible in the German copyright laws, as you can't licence uses that'll be invented in the future). markus, not a lawyer -- Markus Schaber -- http://www.schabi.de/ -- ICQ: 22042130 +-+ | Allgemeine Sig-Verletzung 0815/4711| +-+ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHA-154X/1535 not recognized any more
On Wed, 18 Apr 2001, Rafael E. Herrera wrote:
> > lunix:~# isapnp pnpconfig.txt
> > Board 1 has Identity 08 0f 6d b9 45 42 15 90 04: ADP1542 Serial No 258849093
>[checksum 08]
> > pnptext:60 -- Fatal - IO range check attempted while device activated
> > pnptext:60 -- Fatal - Error occurred executing request ' ' --- further
>action aborted
>
> I've a pnp sound card that fails to configure with a similar error
> message when a (CHECK) entry was found in an (IO ...) block. Removing
> those entries solved the problem. Try this in your pnpconfig.txt:
>
> (IO 0 (SIZE 4) (BASE 0x0330))
In this case, isapnp configures the card.
Using a modularized kernel, modprobe also loads the driver without any
further parameters:
lunix:/home/schabi/public_html/scsi# /rescue/sbin/isapnp pnpconfig_nocheck.txt
Board 1 has Identity 08 0f 6d b9 45 42 15 90 04: ADP1542 Serial No
258849093 [checksum 08]
ADP1542/258849093[0]{SCSI Host Adapter }: Port 0x330; IRQ10 DMA0 ---
Enabled OK
lunix:/home/schabi/public_html/scsi# modprobe aha1542
lunix:/home/schabi/public_html/scsi#
ls /proc/scsi
advansys aha1542 ide-scsi scsi sg
lunix:/home/schabi/public_html/scsi# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: YAMAHA Model: CRW8424S Rev: 1.0j
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: IOMEGA Model: ZIP 100 Rev: 03.H
Type: Direct-AccessANSI SCSI revision:
Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: SAMSUNG Model: CD-ROM SCR-3231 Rev: S104
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 06 Lun: 00
Vendor: IOMEGA Model: ZIP 100 PLUS Rev: J.66
Type: Direct-AccessANSI SCSI revision: 02
So the isapnp tools can configure the card correctly.
markus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: AHA-154X/1535 not recognized any more
On Wed, 18 Apr 2001, Alan Cox wrote: > > Well, as this device is already configured by the bios, I just tried > > to load it giving the right IO port, and got the following message: > > The kernel PnP will deconfigure it Ah, interesting. > The module parameters are > > aha1542=io, irq, busff, dmaspeed I recompiled the kernel with isapnp-support and statically compiled driver. I then typed aha1542=0x330 at the lilo prompt, but the card wasn't recognized (see dmesg_pnp_bootparam.txt on http://schabi.de/scsi/). isapnp will initialize the card when the check entry is removed, but doesn't activate the driver. I'll next test with modularized driver, and the isapnp tools. markus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHA-154X/1535 not recognized any more
Hello, On Wed, 18 Apr 2001, Alan Cox wrote: > Ok if you use the old style usermode isapnp tools to configure it and then > force aha1542 to use the right io, irq to find it does it then work ? Well, as this device is already configured by the bios, I just tried to load it giving the right IO port, and got the following message: lunix:/home/schabi# modprobe aha1542 io=0x330 /lib/modules/2.4.3/kernel/drivers/scsi/aha1542.o: invalid parameter parm_io /lib/modules/2.4.3/kernel/drivers/scsi/aha1542.o: insmod /lib/modules/2.4.3/kernel/drivers/scsi/aha1542.o failed /lib/modules/2.4.3/kernel/drivers/scsi/aha1542.o: insmod aha1542 failed It seems as the driver doesn't accept a given IO port as parameter. Using isapnptools (which I never had to use before), I got the following error message: lunix:~# isapnp pnpconfig.txt Board 1 has Identity 08 0f 6d b9 45 42 15 90 04: ADP1542 Serial No 258849093 [checksum 08] pnptext:60 -- Fatal - IO range check attempted while device activated pnptext:60 -- Fatal - Error occurred executing request ' ' --- further action aborted /proc/isapnp also states that the device is active, but no ports, irq, dma and memory is mapped. I put the pnpconfig.txt and the contents of /proc/isapnp also onto http://schabi.de/scsi/. In some other tests, I compiled the kernel without Plug and Play support. The module loaded without any parameters (and didn't accept an parm_io value) when typing modprobe aha1542. As expected by me, it didn't make any difference whether I told my bios that there's an pnp-OS installed or not, as the Host adapter is a bootable device and so initialized both ways. Pnpdump had the same output, as far as I saw. I also retried a statically compiled driver (no module) without isapnp (the combination my 2.2.19 kernel used), and it also worked as expected. So this is clearly a isapnp triggered problem. Another point: I compile my kernel with the debian command "make-kpkg kernel-image", and then install the created kernel .deb - I hope this doesn't make any difference with my problem. markus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AHA-154X/1535 not recognized any more
Alan Cox wrote: > > > Now I have the problem that kernels 2.4.2 and 2.4.3 don't recognize this > > adapter any more, while all 2.2-kernels I used (I currently remember > > 2.2.19, 2.2.18 and debian-2.2.17pre6) work with it without problems. > > Load the module with isapnp=1. It defaults to not scanning isapnp boards which > strikes me as odd. Let me know if that fixes it if so I think I'll tweak the > default This gives me the following message: lunix:/lib/modules/2.4.3# modprobe aha1542 isapnp=1 /lib/modules/2.4.3/kernel/drivers/scsi/aha1542.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.3/kernel/drivers/scsi/aha1542.o: insmod /lib/modules/2.4.3/kernel/drivers/scsi/aha1542.o failed /lib/modules/2.4.3/kernel/drivers/scsi/aha1542.o: insmod aha1542 failed markus -- Markus Schaber -- http://www.schabi.de/ -- ICQ: 22042130 +-+ | Allgemeine Sig-Verletzung 0815/4711| +-+ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
AHA-154X/1535 not recognized any more
Hello, In my computer, I use an old ISA PNP SCSI host adapter, where I connectend an external Iomega ZIP plus - this strange device (PPA and SCSI on the same connector) doesn't like to share its SCSI-Bus with other devices - thus I need two host adapters for two devices :-( Now I have the problem that kernels 2.4.2 and 2.4.3 don't recognize this adapter any more, while all 2.2-kernels I used (I currently remember 2.2.19, 2.2.18 and debian-2.2.17pre6) work with it without problems. The BIOS message states it is an AHA 1540CP/1542CP BIOS V1.2, Win98SE recognizes it as an AHA-154X/AHA-1535 Plug and Play SCSI Adapter, and runs it with IRQ 10 and DMA 7. According to dmesg, the 2.2.X kernels recognize it as an AHA 1542, whereas the 2.4 series says that isapnp found an aha1535, but no driver is loaded. pnpdump from isapnptools-1.21 recognizes it as an ADP1542 - even when running with an 2.4.3-kernel. I have put both dmesg-outputs and some other hopefully debugging output on the web at http://schabi.de/scsi/ - I didn't want to post those files on the mailing list, but if some of don't have http access, I'll happily mail you those files personally. Now I want to know whether this is a bug in the kernel (and where to search to eventually fix it) or a misconfiguration in my host. If you need some other info, or want me to run some tests, feel free to mail me. It might even be possible to borrow the card to someone, as I'll by a second hand IDE ZIP tomorrow, and then I could spare the card for some weeks. Thanks a lot, markus PS: I subscribed to the kernel list, so you don't have to BCC your answers to me. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
