Anonymous | Login | Signup for a new account | 11-10-2008 10:55 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0000630 | [BusyBox] Other | minor | always | 01-09-06 03:49 | 01-09-06 19:42 | ||||
Reporter | hifly | View Status | public | ||||||
Assigned To | BusyBox | ||||||||
Priority | normal | Resolution | unable to reproduce | ||||||
Status | closed | Product Version | svn | ||||||
Summary | 0000630: cat works for directories too | ||||||||
Description |
I did `cat /tmp` on my busybox 1.10-pre1 where / is on jffs2. It produces a lot of &*%@##%^((# I think cat shouldn't work with directories. |
||||||||
Additional Information | There is no 1.10 version in "Product Version" in BusyBox bug tracking system | ||||||||
Attached Files | |||||||||
|
Notes | |
(0000888) robang74 01-09-06 06:27 |
I cannot replicate on ext3 [roberto@wsraf busybox]$ ./busybox cat /tmp cat: Read Error: Is a directory |
(0000896) landley 01-09-06 19:42 |
I can't replicate it either. ./busybox cat util-linux/ cat: Read Error: Is a directory Sounds like you have a kernel bug. If your kernel lets us open something and read from it, then cat will happily spit it out. And that is the correct behavior. Cat works on not just files but character devices, block devices, pipes, fifos, symlinks... You name it. If a directory _can_ be opened for read, it's not cat's job to say it won't read it. It's your kernel's job to get the behavior right. |
Copyright © 2000 - 2006 Mantis Group |