--prefix
. If not, the default --prefix=/usr/local
was used. Anyway your Makefile most probably contains some sort of installation target that would copy all the necessary files into their proper destinations. The problem is that you don't want to install locally in the first place and you don't have root access either. How are you going to package the application into a TAR.GZ with proper pathes and owners/permissions?=?UTF-8?B?U3plbcOpbHllcyBZb3VUdWJlLcOpcnRlc8OtdMWRIC0gMjAxMS4xMi4yOC4==?=
python -c "from email.header import decode_header; import sys; subject, encoding = decode_header(sys.stdin.readline())[0]; print subject if encoding == None else subject.decode(encoding)"
Személyes YouTube-értesítő - 2011.12.28.
.aapt_bin="$(which aapt)"
[ -n "$aapt_bin" -a -x "$aapt_bin" ] && find . -type f -iname '*.apk' -print0 | while IFS="" read -r -d "" j; do IFS="$(printf '\nX')"; IFS="${IFS%X}"; echo "${j}: $("$aapt_bin" dump badging "$j" 2> /dev/null | egrep '^(application|package):' | sort | sed -r "s/.*((name|label)='[^']*').*/\1/" | tr '\n' ' ')"; done
/system/app/Thinkfree.apk
and to back it up you simply have to make a copy of the apk./etc/init.d/checkfs.sh
for quite a long time, then moved it somewhere else). The point is that at some step of your boot process the fsck
tool is started with a set of commandline parameters. Eg. Ubuntu Hardy executes something like this:fsck -C -V -R -A -a -f
/dev/sdb1
partition. The PE size is the usual 4MB (4194304 bytes) and the PV size displayed by pvdisplay
is: 465.76 GiB / not usable 544.50 KiB. You take a look at how this space is distributed by running pvdisplay -m --units b /dev/sdb1
and get ...
Recent comments
2 years 15 weeks ago
3 years 36 weeks ago
3 years 36 weeks ago
3 years 38 weeks ago
3 years 39 weeks ago
3 years 46 weeks ago
3 years 46 weeks ago
3 years 46 weeks ago
3 years 46 weeks ago
3 years 47 weeks ago