1 |
On Wednesday, 2 January 2019 08:48:19 GMT Dan Johansson wrote: |
2 |
> > Hmm ... I've mounted it, modified it and eventually tried to run the bash |
3 |
> > script to copy it over to a USB stick. It wasn't happy to run this time, |
4 |
> > following my modifications: |
5 |
> > |
6 |
> > # bash ./usb_inst.sh |
7 |
> > Device [/dev/sdb] detected as [ USB DISK Pro ] is removable and |
8 |
> > size=954MB |
9 |
> > * Device [/dev/sdb] is not mounted |
10 |
> > Device [/dev/sdc] detected as [ USB DISK Pro ] is removable and |
11 |
> > size=1MB |
12 |
> > * Device [/dev/sdc] is not mounted |
13 |
> > dialog: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof |
14 |
> > (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed. |
15 |
> > ./usb_inst.sh: line 491: 6296 Aborted ${PROG_DIALOG} -- |
16 |
> > infobox "$1" 20 75 |
17 |
> > dialog: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof |
18 |
> > (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed. |
19 |
> > ./usb_inst.sh: line 491: 6297 Aborted ${PROG_DIALOG} -- |
20 |
> > infobox "$1" 20 75 |
21 |
> |
22 |
> I had the same issue some days ago. Try unset'ing all LC_ variables in |
23 |
> your shell before you run usb_inst.sh as "dialog" in the iso can |
24 |
> apparently not handle something else than "C" (or empty). |
25 |
|
26 |
Thanks Dan, seeing the LC_TIME related error I tried changing mine to 'C' and |
27 |
also to unset it, but it kept failing. Eventually I set LC_ALL to 'C' which |
28 |
allowed the script to run. |
29 |
|
30 |
Before this I tried running isohybrid, but I must have done it wrong. The USB |
31 |
stick gave an error when I tried to boot with it, some boot binary file |
32 |
missing. :-/ |
33 |
|
34 |
I now have a sysrescuecd with graphics and wireless firmware needed by my |
35 |
system. |
36 |
|
37 |
Sadly it won't boot on a more recent HP laptop which came with MSWindows 10 |
38 |
and Secure Booting enabled. I was able to boot clonezilla with the Ubuntu |
39 |
kernel, but not sysrescuecd. I assume it requires signing the kernel with the |
40 |
MS/RHL keys to allow it to boot, but I have not looked into it further. |
41 |
|
42 |
-- |
43 |
Regards, |
44 |
Mick |