 Relationships |
|
| Anonymous | Login | Signup for a new account | 11-10-2008 11:22 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 | ||||
| 0001604 | [BusyBox] Standards Compliance | minor | always | 11-23-07 07:19 | 02-14-08 04:00 | ||||
| Reporter | alonbl | View Status | public | ||||||
| Assigned To | BusyBox | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | svn | ||||||
| Summary | 0001604: umount -D | ||||||||
| Description |
Hello, I am not sure how to classify this... But util-linux does not have -D argument... The default behavior is not to free loop device allocation, unless -d is used. Any reason why busybox behaves differently? Thanks! |
||||||||
| Additional Information |
Busybox: -D Do not free loop device (if a loop device has been used) util-linux: -d In case the unmounted device was a loop device, also free this loop device. |
||||||||
| Attached Files | |||||||||
|
|
|||||||||
|
Relationships |
|
|
Notes |
|
|
(0004584) vda 02-14-08 04:00 |
Fixed in rev. 21015. Thanks! |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 11-23-07 07:19 | alonbl | New Issue | |
| 11-23-07 07:19 | alonbl | Status | new => assigned |
| 11-23-07 07:19 | alonbl | Assigned To | => BusyBox |
| 02-14-08 04:00 | vda | Status | assigned => closed |
| 02-14-08 04:00 | vda | Note Added: 0004584 | |
| 02-14-08 04:00 | vda | Resolution | open => fixed |
| Copyright © 2000 - 2006 Mantis Group |  |
