Bug 257960 - mkimg: partition 1: No such file or directory when using a ":" in the file name
Summary: mkimg: partition 1: No such file or directory when using a ":" in the file name
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 13.0-RELEASE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: regression, vendor
Depends on:
Blocks:
 
Reported: 2021-08-20 07:06 UTC by Franco Fichtner
Modified: 2024-10-14 00:55 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Franco Fichtner 2021-08-20 07:06:13 UTC 
Hi,

This was working on 12.1 at least, but due to new syntax additions this broke file name read.


Cheers,
Franco
Comment 1 Ed Maste freebsd_committer freebsd_triage 2021-08-20 22:47:47 UTC 
Can you add an example failing command line
Comment 2 Franco Fichtner 2021-08-21 06:17:54 UTC 
Sorry, was in a hurry yesterday:

# touch th:is
# mkimg -s gpt -o out:ok -p freebsd-ufs:=th:is
mkimg: partition 1: No such file or directory

There's two possible workarounds at the moment: use relative paths if the directory contains a colon or use a symbolic link if the file name contains it.

If you do

# touch th

and run the prior command you can see that it does find the file now and fails with

mkimg: writing metadata: Device not configured

as expected.


Cheers,
Franco
Comment 3 Ed Maste freebsd_committer freebsd_triage 2024-09-05 16:54:50 UTC 
manu it looks like this comes from 8f3c71c85e5f