Re: Zip: what does that mean?
Greg, Just to make a point on that, as I recall Zip and other super floppy media *shouldn't* be partitioned. It's certainly possible to do but it's anyone's guess on how different OS+revs will treat it. Josh __SIG__ On Fri, 15 Jun 2001, Gregoire Favre wrote: > On Fri, Jun 15, 2001 at 08:40:57AM +0200, Philipp Matthias Hahn wrote: > > > Nothing. Somethings is reeding /proc/partitions which lists all known > > partitions. "fdisk" or "mount" do this. > > > > When reading the file the kernel has to check the media in your zip-drive. > > Problem is, you havn't put in one. So there is no partition table to read > > and the kernel complains and returns the default values of a typical > > 100MB zip media. > > Thanks for your answer, in fact, there was a media in my zip, but > without any partition (as I don't see any other reason than avoiding > those errors messages to make just one partition on my disk). > > Thanks, > > Greg > > http://ulima.unil.ch/greg ICQ:16624071 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: Zip: what does that mean?
Greg, Just to make a point on that, as I recall Zip and other super floppy media *shouldn't* be partitioned. It's certainly possible to do but it's anyone's guess on how different OS+revs will treat it. Josh __SIG__ On Fri, 15 Jun 2001, Gregoire Favre wrote: On Fri, Jun 15, 2001 at 08:40:57AM +0200, Philipp Matthias Hahn wrote: Nothing. Somethings is reeding /proc/partitions which lists all known partitions. fdisk or mount do this. When reading the file the kernel has to check the media in your zip-drive. Problem is, you havn't put in one. So there is no partition table to read and the kernel complains and returns the default values of a typical 100MB zip media. Thanks for your answer, in fact, there was a media in my zip, but without any partition (as I don't see any other reason than avoiding those errors messages to make just one partition on my disk). Thanks, Greg http://ulima.unil.ch/greg ICQ:16624071 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: floppy programming
Actually... that sounds like zone bit recording. As I understand it, that
sort of thing is handled by the floppy controller and isn't under the
purview of the OS. Anyhoo, what really got me on this, is I understand
there will be some new floppy drives out soon that'll do this sort of
thing by default. It allows ~33MB of data on a 1.44MB floppy. (let's just
forget how often disks bo bad here)
Pretty cool if can do it w/o changing the hardware.
Josh
___SIG___
$_='while(read+STDIN,$_,2048){$a=29;$b=73;$c=142;$t=255;@t=map{$_%16or$t^=$c^=(
$m=(11,10,116,100,11,122,20,100)[$_/16%8])&110;$t^=(72,@z=(64,72,$a^=12*($_%16
-2?0:$m&17)),$b^=$_%64?12:0,@z)[$_%8]}(16..271);if((@a=unx"C*",$_)[20]&48){$h
=5;$_=unxb24,join"",@b=map{xB8,unxb8,chr($_^$a[--$h+84])}@ARGV;s/...$/1$&/;$
d=unxV,xb25,$_;$e=256|(ord$b[4])<<9|ord$b[3];$d=$d>>8^($f=$t&($d>>12^$d>>4^
$d^$d/8))<<17,$e=$e>>8^($t&($g=($q=$e>>14&7^$e)^$q*8^$q<<6))<<9,$_=$t[$_]^
(($h>>=8)+=$f+(~$g&$t))for@a[128..$#a]}print+x"C*",@a}';s/x/pack+/g;eval
On Sun, 18 Mar 2001, Leandro Bernsmuller wrote:
>
> Hi,
>
> some body know if exist or is possible to do one
> driver
> to makes floppy drive use some type of "balanced" bits
> distribution?
> The idea is simple: format a disk doing inner tracks
> with less bits than
> in external tracks.
> Maybe is better think in sectors and not bits
> banlancing?
>
> I want opinions about the idea, pleace.
>
> Where can I find information about floppy drivers
> programming, DMA setup,...?
>
> Thanks,
>
> Leandro
>
> __
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail.
> http://personal.mail.yahoo.com/
> -
> 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/
>
-
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: floppy programming
Actually... that sounds like zone bit recording. As I understand it, that
sort of thing is handled by the floppy controller and isn't under the
purview of the OS. Anyhoo, what really got me on this, is I understand
there will be some new floppy drives out soon that'll do this sort of
thing by default. It allows ~33MB of data on a 1.44MB floppy. (let's just
forget how often disks bo bad here)
Pretty cool if can do it w/o changing the hardware.
Josh
___SIG___
$_='while(read+STDIN,$_,2048){$a=29;$b=73;$c=142;$t=255;@t=map{$_%16or$t^=$c^=(
$m=(11,10,116,100,11,122,20,100)[$_/16%8])110;$t^=(72,@z=(64,72,$a^=12*($_%16
-2?0:$m17)),$b^=$_%64?12:0,@z)[$_%8]}(16..271);if((@a=unx"C*",$_)[20]48){$h
=5;$_=unxb24,join"",@b=map{xB8,unxb8,chr($_^$a[--$h+84])}@ARGV;s/...$/1$/;$
d=unxV,xb25,$_;$e=256|(ord$b[4])9|ord$b[3];$d=$d8^($f=$t($d12^$d4^
$d^$d/8))17,$e=$e8^($t($g=($q=$e147^$e)^$q*8^$q6))9,$_=$t[$_]^
(($h=8)+=$f+(~$g$t))for@a[128..$#a]}print+x"C*",@a}';s/x/pack+/g;eval
On Sun, 18 Mar 2001, Leandro Bernsmuller wrote:
Hi,
some body know if exist or is possible to do one
driver
to makes floppy drive use some type of "balanced" bits
distribution?
The idea is simple: format a disk doing inner tracks
with less bits than
in external tracks.
Maybe is better think in sectors and not bits
banlancing?
I want opinions about the idea, pleace.
Where can I find information about floppy drivers
programming, DMA setup,...?
Thanks,
Leandro
__
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
-
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/
-
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: trouble with apm on dell latitude cs in 2.2.1[67]
I seem to recall there is mention of this in the recent pcmcia-cs sources. This requires playing with hdparm if I remember correctly. Josh On Tue, 31 Oct 2000 [EMAIL PROTECTED] wrote: > > I've recently upgraded a latitude cs running redhat 6.2 on 2.2.14 with > card services v3.1.14 to 2.2.17 with card services v3.1.21. Immediately > I noticed that suspend/resume was broken. Well, suspend was working fine > but when I raised the lid, the system would come back like normal, then > the HD drive light would go solid and a few seconds later the system > would lock hard. No oops or any other indicators. I tried tailing the > /var/log/messages file (starting before the suspend), but this revealed > nothing at first. After about 5 tries I managed to elicit one error > in the log: > > "hda: timeout waiting for DMA" > > but this message did not show up consistently. I tried backing down to > 2.2.16 in case it was a recent bug and then also tried backing up to a > previous version of card services, but none of this helps. Unless I go > back to 2.2.14, this system will lock hard on a resume about 7-10 seconds > after I raise the lid. > > Lacking any other kernel debugging skills, I compiled sysrq into the kernel > hoping to get something more useful for the list. Although 'showkey -s' > does generate 0x54 codes, pressing alt-sysrq- yields nothing in the > kernel I just built it into (2.2.17). > > One another kernel note, I cannot get the 2.4.0-test9/10 kernels to boot > on this machine. After lilo, it says: > > "Uncompressing Linux... Ok, booting the kernel." > > then the machine hangs solid. It is not recoverable via alt-ctrl-del. > I have to hold the power button until the machine cycles. I have no data > for earlier 2.4.0 kernels. > > What else can I do to debug this and what other info will help in > identifying the problem? > > Thanks, > > Stewart > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: trouble with apm on dell latitude cs in 2.2.1[67]
I seem to recall there is mention of this in the recent pcmcia-cs sources. This requires playing with hdparm if I remember correctly. Josh On Tue, 31 Oct 2000 [EMAIL PROTECTED] wrote: I've recently upgraded a latitude cs running redhat 6.2 on 2.2.14 with card services v3.1.14 to 2.2.17 with card services v3.1.21. Immediately I noticed that suspend/resume was broken. Well, suspend was working fine but when I raised the lid, the system would come back like normal, then the HD drive light would go solid and a few seconds later the system would lock hard. No oops or any other indicators. I tried tailing the /var/log/messages file (starting before the suspend), but this revealed nothing at first. After about 5 tries I managed to elicit one error in the log: "hda: timeout waiting for DMA" but this message did not show up consistently. I tried backing down to 2.2.16 in case it was a recent bug and then also tried backing up to a previous version of card services, but none of this helps. Unless I go back to 2.2.14, this system will lock hard on a resume about 7-10 seconds after I raise the lid. Lacking any other kernel debugging skills, I compiled sysrq into the kernel hoping to get something more useful for the list. Although 'showkey -s' does generate 0x54 codes, pressing alt-sysrq-key yields nothing in the kernel I just built it into (2.2.17). One another kernel note, I cannot get the 2.4.0-test9/10 kernels to boot on this machine. After lilo, it says: "Uncompressing Linux... Ok, booting the kernel." then the machine hangs solid. It is not recoverable via alt-ctrl-del. I have to hold the power button until the machine cycles. I have no data for earlier 2.4.0 kernels. What else can I do to debug this and what other info will help in identifying the problem? Thanks, Stewart - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: IDE-Floppy and devfs
I did report this back a month or so ago. Another work around is to have a device node (22,0 in my case) around to bang on for a sec. After having the kernel poke the device, the appropriate devfs node appears automagically. My 0.02USD. Josh On Sun, 22 Oct 2000, Andreas Franck wrote: > Hi Paul, hi linux-kernel audience, > > some szggestion for the upcoming 2.4 release ide-floppy driver: It > really works > nice without devfs, but the ide-floppy behaviour in connection with > devfs is > a bit strange. > > If ide-floppy is compiled as a module, which is loaded (or autoloaded by > some smart > devfs rule) when no disk is in the drive, NO devfs entries are created, > so there > is no way to access the drive. Even worse, when a disk is inserted, the > module is > still loaded so there is no way to access the disk! Only manual > unloading and reloading > of the module will do the trick. > > I'd suggest something like the cdrom approach: There is always one > device node for > removable devices, regardless of any media present in the drive. This > could > be /dev/ide/host0/bus1/target1/lun0/floppy or something like that. > > Accessing this file should trigger a probe for the media (which may be > partitioned > in ide-floppy devices, which makes life a bit harder). By this probe, > the > /dev/ide/.../lun0/disc and /dev/ide/.../lun0/part4 (or any other > partitions) > might be created, if there is a medium in the drive; a symlink to the > "right" partition > (part4 for normal ZIP disks, AFAIK) shhould be placed in a directory of > its own, > for example /dev/ide/floppy/c0b1t1u0, and anotherone perhaps in > /dev/idefloppy/floppy0 > or something. > > I have already implemented the first half of this (creation of the > floppy node which will > trigger the partition scan when accessed), I have attached my patch for > review here. > Its still quite hackish, but I'm sure you can follow my ideas with what > I explained above > - if not, don't hesitate to ask. > > ->- snip -<- > > -- > ->>>--- Andreas Franck <<<- > ---<<< [EMAIL PROTECTED] --->>>--- > ->>> Keep smiling! <<<- > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: IDE-Floppy and devfs
I did report this back a month or so ago. Another work around is to have a device node (22,0 in my case) around to bang on for a sec. After having the kernel poke the device, the appropriate devfs node appears automagically. My 0.02USD. Josh On Sun, 22 Oct 2000, Andreas Franck wrote: Hi Paul, hi linux-kernel audience, some szggestion for the upcoming 2.4 release ide-floppy driver: It really works nice without devfs, but the ide-floppy behaviour in connection with devfs is a bit strange. If ide-floppy is compiled as a module, which is loaded (or autoloaded by some smart devfs rule) when no disk is in the drive, NO devfs entries are created, so there is no way to access the drive. Even worse, when a disk is inserted, the module is still loaded so there is no way to access the disk! Only manual unloading and reloading of the module will do the trick. I'd suggest something like the cdrom approach: There is always one device node for removable devices, regardless of any media present in the drive. This could be /dev/ide/host0/bus1/target1/lun0/floppy or something like that. Accessing this file should trigger a probe for the media (which may be partitioned in ide-floppy devices, which makes life a bit harder). By this probe, the /dev/ide/.../lun0/disc and /dev/ide/.../lun0/part4 (or any other partitions) might be created, if there is a medium in the drive; a symlink to the "right" partition (part4 for normal ZIP disks, AFAIK) shhould be placed in a directory of its own, for example /dev/ide/floppy/c0b1t1u0, and anotherone perhaps in /dev/idefloppy/floppy0 or something. I have already implemented the first half of this (creation of the floppy node which will trigger the partition scan when accessed), I have attached my patch for review here. Its still quite hackish, but I'm sure you can follow my ideas with what I explained above - if not, don't hesitate to ask. -- snip -- -- Andreas Franck - --- [EMAIL PROTECTED] -- - Keep smiling! - - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
Huh? *is* supposed to be equivalent to according to RFC822. >From the spec: SPACE = ; ( 40, 32.) HTAB= ; ( 11, 9.) LWSP-char = SPACE / HTAB ; semantics = SPACE linear-white-space = 1*([CRLF] LWSP-char) ; semantics = SPACE ; CRLF => folding Josh (not that I need linux-kernel-digest, pine separates linux-kernel to a folder just fine) On Wed, 20 Sep 2000, Matti Aarnio wrote: > I think DaveM also supplied an answer: "procmail" > > Select by header: > > X-Mailing-List: [EMAIL PROTECTED] > > Do note that TAB character, for some reason it really is not space.. > Store into separate folder from your normal inbox. > > > On Wed, Sep 20, 2000 at 02:26:33PM -0400, Dmitry Pogosyan wrote: > > Date: Wed, 20 Sep 2000 14:26:33 -0400 > > From: Dmitry Pogosyan <[EMAIL PROTECTED]> > > X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-12 i686) > > X-Accept-Language: en > > To: [EMAIL PROTECTED] > > Subject: Re: linux-kernel-digest ? > > Precedence: bulk > > X-Mailing-List: [EMAIL PROTECTED] > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
Huh? TAB *is* supposed to be equivalent to SPACE according to RFC822. From the spec: SPACE = ASCII SP, space; ( 40, 32.) HTAB= ASCII HT, horizontal-tab ; ( 11, 9.) LWSP-char = SPACE / HTAB ; semantics = SPACE linear-white-space = 1*([CRLF] LWSP-char) ; semantics = SPACE ; CRLF = folding Josh (not that I need linux-kernel-digest, pine separates linux-kernel to a folder just fine) On Wed, 20 Sep 2000, Matti Aarnio wrote: I think DaveM also supplied an answer: "procmail" Select by header: X-Mailing-List: TAB [EMAIL PROTECTED] Do note that TAB character, for some reason it really is not space.. Store into separate folder from your normal inbox. On Wed, Sep 20, 2000 at 02:26:33PM -0400, Dmitry Pogosyan wrote: Date: Wed, 20 Sep 2000 14:26:33 -0400 From: Dmitry Pogosyan [EMAIL PROTECTED] X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-12 i686) X-Accept-Language: en To: [EMAIL PROTECTED] Subject: Re: linux-kernel-digest ? Precedence: bulk X-Mailing-List: [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
