Custom Query (344 matches)
Results (109 - 111 of 344)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #124 | fixed | os2-base-hfs 0.0.0-10 has typo in description | ||
| Description |
Minor nit: Adds /bin to provide posix directory compatibility for shell script esecution should be: Adds /bin to provide posix directory compatibility for shell script execution ;-) |
|||
| #330 | fixed | os2-base spec | ||
| Description |
after the new libc release we should remove the fhs part completely. as we never have a /@unixroot/bin directory anymore. |
|||
| #340 | fixed | os2-base insists upon modifying C:\CONFIG.SYS rather than os2_boot_drive CONFIG.SYS | ||
| Description |
This is not a failure of getbootdrive.exe (as I originally thought). After reading ticket #339 and updating os2-rpm to 1-9, I can still reproduce the failure of the os2-base package to edit the correct CONFIG.SYS. Example: C:\CONFIG.SYS exists, but does not have any SHELL= statements in it. U: is the current boot volume. Reinstall, downgrade, or update os2-base on U:, and C:\CONFIG.SYS is edited to insert: SET SHELL=U:/usr/bin/sh.exe SET EMXSHELL=U:/usr/bin/sh.exe SET CONFIG_SHELL=U:/usr/bin/sh.exe SET MAKESHELL=U:/usr/bin/sh.exe SET EXECSHELL=U:/usr/bin/sh.exe U:\CONFIG.SYS is untouched (if entries are manually removed before reinstall/update, they are not added). As getbootdrive.exe does return the correct drive, I'm not sure where else the os2_boot_drive or os2_config_sys macros could be failing. While this ticket is opened against os2-base, clearly the problem lies in an rpm macro which can potentially impact a number of other packages. |
|||
