I'm not sure this is the place to post but I don't have any other options.
I followed the instructions for the install pen drive creation and got it to run but was given no choice for a drive to install on. It chose the hard drive without telling me, wiped the drive and failed to install anything leaving me with a boat anchor. I had to install Windows 10, as there was no recovery partition left from the original 8.1 install.
The live image fails to boot.
So far I can't say I'm very impressed.
Any suggestions appreciated.
Dale
Sent from my Xperia™ tablet
Thanks a lot!
Will wait for the diff!
-Pradeep
On 29 January 2016 at 15:12, Antonio Murdaca <antoniomurdaca(a)gmail.com>
wrote:
> This is a known issue with docker 1.9 at the moment. In redhat I built our
> docker 1.9 just yesterday and I faced this issue. The solution was to edit
> the Dockerfile and update the version of go-md2man and its dependencies. As
> soon as I'm on my laptop I'll post a diff which when applied solves this
> issue.
> On Jan 29, 2016 3:09 PM, "Pradeep Kiruvale" <pradeepkiruvale(a)gmail.com>
> wrote:
>
>> Hi All,
>>
>> I got the source code from git and trying to build on ubuntu. But I am
>> facing below issue.
>>
>> Please let me know how to resolve the issue.
>>
>> Regards,
>> Pradeep
>>
>> If you want to create a new branch to retain commits you create, you may
>> do so (now or later) by using -b with the checkout command again. Example:
>>
>> git checkout -b new_branch_name
>>
>> + go get -v -d github.com/cpuguy83/go-md2man
>> package code.google.com/p/go.net/html: unable to detect version control
>> system for code.google.com/ path
>> INFO[0005] The command [/bin/sh -c set -x && export GOPATH="$(mktemp
>> -d)" && git clone -b v1.0.3 https://github.com/cpuguy83/go-md2man.git
>> "$GOPATH/src/github.com/cpuguy83/go-md2man" && git clone -b v1.2
>> https://github.com/russross/blackfriday.git "$GOPATH/src/
>> github.com/russross/blackfriday" && go get -v -d
>> github.com/cpuguy83/go-md2man && go build -v -o
>> /usr/local/bin/go-md2man github.com/cpuguy83/go-md2man && rm -rf
>> "$GOPATH"] returned a non-zero code: 1
>> make: *** [build] Error 1
>>
>> _______________________________________________
>> Dev mailing list
>> Dev(a)lists.clearlinux.org
>> https://lists.clearlinux.org/mailman/listinfo/dev
>>
>>
On 1/29/2016 2:25 AM, Pradeep Kiruvale wrote:
> Hi All,
>
> I am trying to set number of cpus by passing --cpu-shares 1024. I.e to set one cpu for the container. But its not passing the same value to the lkvm tool. The lkvm tool
> still shows as 6. Can you please help me how to pass number of cpus to a container/lkvm vm?
>
very likely the 6 "inside the container" cpus all end up sharing 1 actual CPU on the system...
Hi James,
Thanks for the clarification!.
Regards,
Pradeep
On 29 January 2016 at 11:45, Hunt, James O <james.o.hunt(a)intel.com> wrote:
> Hi Pradeep,
>
> I'm afraid that's a limitation right now. We'll look at removing this
> restriction for future releases...
>
> Kind regards,
>
> James.
>
>
> 2016-01-29 10:25 GMT+00:00 Pradeep Kiruvale <pradeepkiruvale(a)gmail.com>:
>
>> Hi All,
>>
>> I am trying to set number of cpus by passing --cpu-shares 1024. I.e to
>> set one cpu for the container. But its not passing the same value to the
>> lkvm tool. The lkvm tool still shows as 6. Can you please help me how to
>> pass number of cpus to a container/lkvm vm?
>>
>> My docker start script
>>
>> sudo docker run -ti -m 128M --memory-swap 300M --cpu-shares 1024
>> busybox:latest
>>
>> 4769 root lkvm run -c 6 -m 128 --nam 0 83000 83036
>> 84672
>>
>> tried even with
>> sudo docker run -it --rm busybox:latest --cpuset-cpus=1
>>
>> same result.
>>
>> Please let me know what I am missing.
>>
>> Thanks & Regards,
>> Pradeep
>>
>> _______________________________________________
>> Dev mailing list
>> Dev(a)lists.clearlinux.org
>> https://lists.clearlinux.org/mailman/listinfo/dev
>>
>>
>
>
> --
> James
> -----
> https://clearlinux.org
> Open Source Technology Center
> Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3
> 1RJ.
>
Hi Pradeep,
I'm afraid that's a limitation right now. We'll look at removing this
restriction for future releases...
Kind regards,
James.
2016-01-29 10:25 GMT+00:00 Pradeep Kiruvale <pradeepkiruvale(a)gmail.com>:
> Hi All,
>
> I am trying to set number of cpus by passing --cpu-shares 1024. I.e to set
> one cpu for the container. But its not passing the same value to the lkvm
> tool. The lkvm tool still shows as 6. Can you please help me how to pass
> number of cpus to a container/lkvm vm?
>
> My docker start script
>
> sudo docker run -ti -m 128M --memory-swap 300M --cpu-shares 1024
> busybox:latest
>
> 4769 root lkvm run -c 6 -m 128 --nam 0 83000 83036
> 84672
>
> tried even with
> sudo docker run -it --rm busybox:latest --cpuset-cpus=1
>
> same result.
>
> Please let me know what I am missing.
>
> Thanks & Regards,
> Pradeep
>
> _______________________________________________
> Dev mailing list
> Dev(a)lists.clearlinux.org
> https://lists.clearlinux.org/mailman/listinfo/dev
>
>
--
James
-----
https://clearlinux.org
Open Source Technology Center
Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3
1RJ.
Hi All,
I am trying to set number of cpus by passing --cpu-shares 1024. I.e to set
one cpu for the container. But its not passing the same value to the lkvm
tool. The lkvm tool still shows as 6. Can you please help me how to pass
number of cpus to a container/lkvm vm?
My docker start script
sudo docker run -ti -m 128M --memory-swap 300M --cpu-shares 1024
busybox:latest
4769 root lkvm run -c 6 -m 128 --nam 0 83000 83036 84672
tried even with
sudo docker run -it --rm busybox:latest --cpuset-cpus=1
same result.
Please let me know what I am missing.
Thanks & Regards,
Pradeep
Outstanding! Thanks a bunch.
-pwl
-----Original Message-----
From: Kok, Auke-jan H [mailto:auke-jan.h.kok(a)intel.com]
Sent: Wednesday, January 27, 2016 4:05 PM
To: Long, Paul <paul.long(a)intel.com>
Cc: dev(a)lists.clearlinux.org
Subject: Re: [Dev] how to find what package is in what bundle
And here's a github gist with the file - unmaliced by e-mail transactions:
https://gist.github.com/sofar/0a9077d5b12b12919abf
Cheers,
Auke
On Wed, Jan 27, 2016 at 4:02 PM, Kok, Auke-jan H <auke-jan.h.kok(a)intel.com>
wrote:
> On Wed, Jan 27, 2016 at 3:43 PM, Long, Paul <paul.long(a)intel.com> wrote:
>> What is the best way to figure out what packages are included in what
>> bundles?
>
> There is some work going on to make this functionality available from
> within the `swupd` command, but until then (as jaime notices) there's
> no builtin way to get the detailed information easily.
>
> However, we've had this idea around for a long time, and I wrote a
> shell script that basically does the pickling for you. You should be
> able to just call it with e.g. "bin/sar" if you're looking for the sar
> binary:
>
> $ clr-locate bin/sar
> [.....................................................................
> ............] sysadmin-advanced pnp-tools-basic pnp-tools-advanced
> pnp-tools-intermediate bat:
> /usr/bin/sar
>
> The periods are where it downloads all the compressed manifests. At
> the end it displays all matches, and for each match, it lists in what
> bundle you can find that match. In this case, there are several
> bundles that provide that binary.
>
> Note that currently, each invocation causes it to download about 50mb
> of data. So use this sparsely :^)
>
> Here's the script - It'll likely not survive copy-paste and mailers,
> though, so make sure you check it.
>
> Cheers,
>
> Auke
>
>
> ===========8<=============
> #!/bin/bash
>
> # grab $VERSION_ID from os-release
> eval `grep VERSION_ID /usr/lib/os-release`
>
> # fetch bundles
> BUNDLES=( `awk '{print $4}' /var/lib/swupd/${VERSION_ID}/Manifest.MoM`
> )
>
> NEXT=0
>
> if [ "$1" == "-h" ] || [ "$1" == "--help" ] || [ "$1" == "" ]; then
> >&2 echo "Usage: $0 [-n] [pattern]"
> >&2 echo "Options:"
> >&2 echo " -h | --help Display this help message"
> >&2 echo " -n Do not query external manifests"
> exit 1
> elif [ "$1" == "-n" ]; then
> NEXT=1
> shift
> fi
>
> TMP=`mktemp`
>
>>&2 echo -n "["
> for BUNDLE in ${BUNDLES[@]}; do
> if [ -f "/var/lib/swupd/${VERSION_ID}/Manifest.${BUNDLE}" ]; then
> awk '{print $4}'
> /var/lib/swupd/${VERSION_ID}/Manifest.${BUNDLE} | grep "$@" | sed
> "s/^/${BUNDLE}\t/"
> elif [ "$NEXT" != "1" ]; then
> (
> BV=`awk -v b=$BUNDLE '($4==b){print $3}'
> /var/lib/swupd/${VERSION_ID}/Manifest.MoM`
> curl --fail -s
> "https://download.clearlinux.org/update/${BV}/Manifest.${BUNDLE}.tar"
> | tar xJf - -O Manifest.${BUNDLE} | awk '{print $4}' | grep "$@" | sed
> "s/^/${BUNDLE}\t/"
> >&2 echo -n .
> ) &
> fi
> done > $TMP
> wait
>>&2 echo "]"
>
> for FILE in `awk '{print $2}' $TMP | sort | uniq`; do
> B=`awk -v file="${FILE}" '($2 == file){print $1}' $TMP | tr '\n' '
> ' | sed 's/ $//'`
> echo -e "${B}:\n\t${FILE}"
> done
>
> rm $TMP
> ===========8<=============
And here's a github gist with the file - unmaliced by e-mail transactions:
https://gist.github.com/sofar/0a9077d5b12b12919abf
Cheers,
Auke
On Wed, Jan 27, 2016 at 4:02 PM, Kok, Auke-jan H
<auke-jan.h.kok(a)intel.com> wrote:
> On Wed, Jan 27, 2016 at 3:43 PM, Long, Paul <paul.long(a)intel.com> wrote:
>> What is the best way to figure out what packages are included in what
>> bundles?
>
> There is some work going on to make this functionality available from
> within the `swupd` command, but until then (as jaime notices) there's
> no builtin way to get the detailed information easily.
>
> However, we've had this idea around for a long time, and I wrote a
> shell script that basically does the pickling for you. You should be
> able to just call it with e.g. "bin/sar" if you're looking for the sar
> binary:
>
> $ clr-locate bin/sar
> [.................................................................................]
> sysadmin-advanced pnp-tools-basic pnp-tools-advanced pnp-tools-intermediate bat:
> /usr/bin/sar
>
> The periods are where it downloads all the compressed manifests. At
> the end it displays all matches, and for each match, it lists in what
> bundle you can find that match. In this case, there are several
> bundles that provide that binary.
>
> Note that currently, each invocation causes it to download about 50mb
> of data. So use this sparsely :^)
>
> Here's the script - It'll likely not survive copy-paste and mailers,
> though, so make sure you check it.
>
> Cheers,
>
> Auke
>
>
> ===========8<=============
> #!/bin/bash
>
> # grab $VERSION_ID from os-release
> eval `grep VERSION_ID /usr/lib/os-release`
>
> # fetch bundles
> BUNDLES=( `awk '{print $4}' /var/lib/swupd/${VERSION_ID}/Manifest.MoM` )
>
> NEXT=0
>
> if [ "$1" == "-h" ] || [ "$1" == "--help" ] || [ "$1" == "" ]; then
> >&2 echo "Usage: $0 [-n] [pattern]"
> >&2 echo "Options:"
> >&2 echo " -h | --help Display this help message"
> >&2 echo " -n Do not query external manifests"
> exit 1
> elif [ "$1" == "-n" ]; then
> NEXT=1
> shift
> fi
>
> TMP=`mktemp`
>
>>&2 echo -n "["
> for BUNDLE in ${BUNDLES[@]}; do
> if [ -f "/var/lib/swupd/${VERSION_ID}/Manifest.${BUNDLE}" ]; then
> awk '{print $4}'
> /var/lib/swupd/${VERSION_ID}/Manifest.${BUNDLE} | grep "$@" | sed
> "s/^/${BUNDLE}\t/"
> elif [ "$NEXT" != "1" ]; then
> (
> BV=`awk -v b=$BUNDLE '($4==b){print $3}'
> /var/lib/swupd/${VERSION_ID}/Manifest.MoM`
> curl --fail -s
> "https://download.clearlinux.org/update/${BV}/Manifest.${BUNDLE}.tar"
> | tar xJf - -O Manifest.${BUNDLE} | awk '{print $4}' | grep "$@" | sed
> "s/^/${BUNDLE}\t/"
> >&2 echo -n .
> ) &
> fi
> done > $TMP
> wait
>>&2 echo "]"
>
> for FILE in `awk '{print $2}' $TMP | sort | uniq`; do
> B=`awk -v file="${FILE}" '($2 == file){print $1}' $TMP | tr '\n' '
> ' | sed 's/ $//'`
> echo -e "${B}:\n\t${FILE}"
> done
>
> rm $TMP
> ===========8<=============
On Wed, Jan 27, 2016 at 3:43 PM, Long, Paul <paul.long(a)intel.com> wrote:
> What is the best way to figure out what packages are included in what
> bundles?
There is some work going on to make this functionality available from
within the `swupd` command, but until then (as jaime notices) there's
no builtin way to get the detailed information easily.
However, we've had this idea around for a long time, and I wrote a
shell script that basically does the pickling for you. You should be
able to just call it with e.g. "bin/sar" if you're looking for the sar
binary:
$ clr-locate bin/sar
[.................................................................................]
sysadmin-advanced pnp-tools-basic pnp-tools-advanced pnp-tools-intermediate bat:
/usr/bin/sar
The periods are where it downloads all the compressed manifests. At
the end it displays all matches, and for each match, it lists in what
bundle you can find that match. In this case, there are several
bundles that provide that binary.
Note that currently, each invocation causes it to download about 50mb
of data. So use this sparsely :^)
Here's the script - It'll likely not survive copy-paste and mailers,
though, so make sure you check it.
Cheers,
Auke
===========8<=============
#!/bin/bash
# grab $VERSION_ID from os-release
eval `grep VERSION_ID /usr/lib/os-release`
# fetch bundles
BUNDLES=( `awk '{print $4}' /var/lib/swupd/${VERSION_ID}/Manifest.MoM` )
NEXT=0
if [ "$1" == "-h" ] || [ "$1" == "--help" ] || [ "$1" == "" ]; then
>&2 echo "Usage: $0 [-n] [pattern]"
>&2 echo "Options:"
>&2 echo " -h | --help Display this help message"
>&2 echo " -n Do not query external manifests"
exit 1
elif [ "$1" == "-n" ]; then
NEXT=1
shift
fi
TMP=`mktemp`
>&2 echo -n "["
for BUNDLE in ${BUNDLES[@]}; do
if [ -f "/var/lib/swupd/${VERSION_ID}/Manifest.${BUNDLE}" ]; then
awk '{print $4}'
/var/lib/swupd/${VERSION_ID}/Manifest.${BUNDLE} | grep "$@" | sed
"s/^/${BUNDLE}\t/"
elif [ "$NEXT" != "1" ]; then
(
BV=`awk -v b=$BUNDLE '($4==b){print $3}'
/var/lib/swupd/${VERSION_ID}/Manifest.MoM`
curl --fail -s
"https://download.clearlinux.org/update/${BV}/Manifest.${BUNDLE}.tar"
| tar xJf - -O Manifest.${BUNDLE} | awk '{print $4}' | grep "$@" | sed
"s/^/${BUNDLE}\t/"
>&2 echo -n .
) &
fi
done > $TMP
wait
>&2 echo "]"
for FILE in `awk '{print $2}' $TMP | sort | uniq`; do
B=`awk -v file="${FILE}" '($2 == file){print $1}' $TMP | tr '\n' '
' | sed 's/ $//'`
echo -e "${B}:\n\t${FILE}"
done
rm $TMP
===========8<=============
