|
2022-01-21
| ||
| 05:40 | • Ticket [5922adbc29] Contrintuitive work of cdrom --eject status still Open with 3 other changes artifact: ef16f6be72 user: vitus | |
| 05:24 | • Ticket [5922adbc29]: 3 changes artifact: 4d3a1b09ef user: vitus | |
| 05:21 | • Ticket [5922adbc29]: 5 changes artifact: 8f2e4a36f2 user: vitus | |
| 05:18 | • New ticket [5922adbc29]. artifact: a3672d188f user: vitus | |
| Ticket Hash: | 5922adbc290101925669403bdbee8223831bc065 | |||
| Title: | Contrintuitive work of cdrom --eject | |||
| Status: | Open | Type: | Code_Defect | |
| Severity: | Cosmetic | Priority: | Medium | |
| Subsystem: | Resolution: | Open | ||
| Last Modified: | 2022-01-21 05:40:52 | |||
| Version Found In: | 0.8 | |||
| User Comments: | ||||
|
vitus added on 2022-01-21 05:18:25:
It is reported that command with only cdrom in virtual machine doesn't work without argument, but happily accepts empty string as argument. vws cdrom --eject tstmchn I vitus added on 2022-01-21 05:24:22: It sueems that more than one cdrom is quite rare. Co may be use --eject without argument and requiire some other option to specify device in these rare cases vitus added on 2022-01-21 05:40:52: It found out that syntax is designed as descripbed above, but implementation is bad. IT stores special value None into file field of Namespace. Better to use separate field to indicate eject. | ||||