=?iso-8859-1?Q?OT:_20_signs_you_don't_want_that_web_design_project_by_Jef?= =?iso-8859-1?Q?frey_Zeldman?=

Painfully true! :-)
http://www.zeldman.com/2008/12/04/20-signs-you-dont-want-that-web-design-project/
Patty Ayers | www.WebDevBiz.com
Free Articles on the Business of Web Development
Web Design Contract, Estimate Request Form, Estimate
Worksheet

How many of us haven't done a Russian Nesting Doll Site? :-)
LOL!
Nancy O.
Alt-Web Design & Publishing
www.alt-web.com

Similar Messages

Arch-0.7.1.iso OR arch-0.7.1-base.iso???

whats the difference?

Insane-Boy wrote:Arch-base is only base pkgs.. you should download all other which you need.Archlinux-iso is base + a lot of other pkgs ( if I'm not in mistake it contains KDE .. ).This is the difference:)
Doesn't contain KDE.

Will iSO 6 to download on to iPad iSO 5.0.1?

Will iSo 6 download on a iPad iSO 5.0.1?

Assuming it is an iPad2 or New IPad, yes it should. 6 is not available for the original iPad.

How to set the Xml Encoding ISO-8859-1 to Transformer or DOMSource

I have a xml string and it already contains an xml declaration with encoding="ISO-8859-1". (In my real product, since some of the element/attribute value contains a Spanish character, I need to use this encoding instead of UTF-8.) Also, in my program, I need to add more attributes or manipulate the xml string dynamically, so I create a DOM Document object for that. And, then, I use Transformer to convert this Document to a stream.
My problme is: Firstly, once converted through the Transformer, the xml encoding changed to default UTF-8, Secondly, I wanted to check whether the DOM Document created with the xml string maintains the Xml Encoding of ISO-8859-1 or not. So, I called Document.getXmlEncoding(), but it is throwing a runtime error - unknown method.
Is there any way I can maintain the original Xml Encoding of ISO-8859-1 when I use either the DOMSource or Transformer? I am using JDK1.5.0-12.
Following is my sample program you can use.
I would appreciate any help, because so far, I cannot find any answer to this using the JDK documentation at all.
Thanks,
Jin Kim
import java.io.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
public class XmlEncodingTest
    StringBuffer xmlStrBuf = new StringBuffer();
    TransformerFactory tFactory = null;
    Transformer transformer = null;
    Document document = null;
    public void performTest()
        xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
                 .append("<TESTXML>\n")
                 .append("<ELEM ATT1=\"Yes\" />\n")
                 .append("</TESTXML>\n");
        // the encoding is set to iso-8859-1 in the xml declaration.
        System.out.println("initial xml = \n" + xmlStrBuf.toString());
        try
            //Test1: Use the transformer to ouput the xmlStrBuf.
            // This shows the xml encoding result from the transformer which will change to UTF-8
            tFactory = TransformerFactory.newInstance();
            transformer = tFactory.newTransformer();
            StreamSource ss = new StreamSource( new StringBufferInputStream( xmlStrBuf.toString()));
            System.out.println("Test1 result = ");
            transformer.transform( ss, new StreamResult(System.out));
            //Test2: Create a DOM document object for xmlStrBuf and manipulate it by adding an attribute ATT2="No"
            DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = dfactory.newDocumentBuilder();
            document = builder.parse( new StringBufferInputStream( xmlStrBuf.toString()));
            // skip adding attribute since it does not affect the test result
            // Use a Transformer to output the DOM document. the encoding becomes UTF-8
            DOMSource source = new DOMSource(document);
            StreamResult result = new StreamResult(System.out);
            System.out.println("\n\nTest2 result = ");
            transformer.transform(source, result);
        catch (Exception e)
            System.out.println("<performTest> Exception caught. " + e.toString());
    public static void main( String arg[])
        XmlEncodingTest xmlTest = new XmlEncodingTest();
        xmlTest.performTest();
}

Thanks DrClap for your answer. With your information, I rewrote the sample program as in the following, and it works well now as I intended! About the UTF-8 and Spanish charaters, I think you are right. It looks like there can be many factors involved on this subject though - for example, the real character sets used to create an xml document, and the xml encoding information declared will matter. The special character I had a trouble was u00F3, and somehow, I found out that Sax Parser or even Document Builder parser does not like this character when encoding is set to "UTF-8" in the Xml document. My sample program below may not be a perfect example, but if you replaces ISO-8859-1 with UTF-8, and not setting the encoding property to the transfermer, you may notice that the special character in my example is broken in Test1 and Test2. In my sample, I decided to use ByteArrayInputStream instead of StringBufferInpuptStream because the documentation says StringBufferInputStream may have a problem with converting characters into bytes.
Thanks again for your help!
Jin Kim
import java.io.*;
import java.util.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
* XML encoding test for Transformer
public class XmlEncodingTest2
    StringBuffer xmlStrBuf = new StringBuffer();
    TransformerFactory tFactory = null;
    Document document = null;
    public void performTest()
        xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
                 .append("<TESTXML>\n")
                 .append("<ELEM ATT1=\"Resoluci�n\">\n")
                 .append("Special charatered attribute test")
                 .append("\n</ELEM>")
                 .append("\n</TESTXML>\n");
        // the encoding is set to iso-8859-1 in the xml declaration.
        System.out.println("**** Initial xml = \n" + xmlStrBuf.toString());
        try
            //TransformerFactoryImpl transformerFactory = new TransformerFactoryImpl();
            //Test1: Use the transformer to ouput the xmlStrBuf.
            tFactory = TransformerFactory.newInstance();
            Transformer transformer = tFactory.newTransformer();
            byte xmlbytes[] = xmlStrBuf.toString().getBytes("ISO-8859-1");
            StreamSource streamSource = new StreamSource( new ByteArrayInputStream( xmlbytes ));
            ByteArrayOutputStream xmlBaos = new ByteArrayOutputStream();
            Properties transProperties = transformer.getOutputProperties();
            transProperties.list( System.out); // prints out current transformer properties
            System.out.println("**** setting the transformer's encoding property to ISO-8859-1.");
            transformer.setOutputProperty("encoding", "ISO-8859-1");
            transformer.transform( streamSource, new StreamResult( xmlBaos));
            System.out.println("**** Test1 result = ");
            System.out.println(xmlBaos.toString("ISO-8859-1"));
            //Test2: Create a DOM document object for xmlStrBuf to add a new attribute ATT2="No"
            DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = dfactory.newDocumentBuilder();
            document = builder.parse( new ByteArrayInputStream( xmlbytes));
            // skip adding attribute since it does not affect the test result
            // Use a Transformer to output the DOM document.
            DOMSource source = new DOMSource(document);
            xmlBaos.reset();
            transformer.transform( source, new StreamResult( xmlBaos));
            System.out.println("\n\n****Test2 result = ");
            System.out.println(xmlBaos.toString("ISO-8859-1"));
            //xmlBaos.flush();
            //xmlBaos.close();
        catch (Exception e)
            System.out.println("<performTest> Exception caught. " + e.toString());
        finally
    public static void main( String arg[])
        XmlEncodingTest2 xmlTest = new XmlEncodingTest2();
        xmlTest.performTest();
}

Mail adapter module UTF-8 to ISO-8859-1 conversion

Hi!
I've a problem with a mail attachment which is generated by an adapter module for the mail adapter. The content type is set to "Application/EDIFACT; charset=iso-8859-1" when I add the attachment, but the mail adapter ignores the charset-setting.
Therefore german "umlauts" like ü are displayed in a wrong way: Ã¼
When I set the content, I transform it in ISO-8859-1 : attachment.setContent(edifactString.getBytes("ISO-8859-1"),"ISO-8859-1");
When I test the result of edifactString.getBytes("ISO-8859-1"), I get the String in the right character encoding, but the mail adapter seems to "fix" the encoding
I also tried to use the messageTransformBean, but it doesn't worked.
Anyone knows how to solve this issue?
Best regards,
Daniel

Hi all!
I found a solution for this problem: First I used the TextPayload-Object for the Attachment which should be added. It seems that the TextPayload-Object has some bugs handling different encodings (handels only Unicode and deletes the charset=... setting from the ContentType).
When using the Payload object for the attachment (which handles binary data), there is no conversion to Unicode, so I get my attachment as desired (but still without the charset-setting).
Best regards,
Daniel

Codepage Conversionerror UTF-8 from System-Codepage to Codepage iso-8859-1

Hello,
we have on SAP PI 7.1 the problem that we can't process a IDOC to Plain HTTP.
The channel throws "Codepage Conversionerror UTF-8 from System-Codepage to Codepage iso-8859-1".
The IDOC is 25 MB. Does anybody have a idea how we can find out what is wrong with the IDOC?
Thanks in advance.

In java strings are always unicode i.e. utf16. Its the byte arrays that are encoded. So use the following codeString iso,utf,temp = "�� ";
byte b8859[] = temp.getBytes("ISO-8859-1");
byte butf8= temp.getBytes("utf8");
try{
iso = new String(b8859,"ISO-8859-1");
utf = new String(butf8,"UTF-8");
System.out.println("ISO-8859-1:"+iso);
System.out.println("UTF-8:"+utf);
System.out.println("UTF to ISO-8859-1:"+new String(utf.getBytes("iso8859_1"),"ISO-8859-1"));
System.out.println(utf);
System.out.println(iso);
}catch(Exception e){ }Also keep in mind that DOS window doesnot support international characters so write it to a file

Help needed to enable ISO-8859-1 encoding in Weblogic 10.3

We have upgraded from Weblogic 10 to Weblogic 10.3. In the old environment foreign characters (iso-8859-1 charater set) were enabled using the Java properties "*-Dfile.encoding=iso-8859-1 -Dclient.encoding.override=iso-8859-1*".
Also, we set the page encoding in the JSPs to be
_'<%@ page pageEncoding="iso-8859-1" contentType="text/html; charset=iso-8859-1" %>'._
This was working fine. We were able to input characters like euro (€) and display it back to user.
After we upgraded to Weblogic 10.3, I applied the same Java properties, all the special characters of the 8859-1 set like Æ, Ã etc are just displayed as garbled text like 'ï¿½ï¿½ï' etc. So, the new server is unable to handle/encode these characters.
Our weblogic environment is - Weblogic appserver 10.3, JRockit 1.6.0_31-R28.2.3-4.1.0 running on Linux OS.
Is there any additional seting in 10.3 to encode character sets?
Thanks in advance.

Hi Kalyan,
Thanks for the info. Please help me understand just one more thing, before I ask our server team to apply the patch.
I checked the full version of our Weblogic server from WEBLOGIC_HOME/registry.xml. It is *<component name="WebLogic Server" version="10.3.6.0" >*.
The patch from MOS says it is *"Release WLS 10.3.3"*. Does this mean the version 10.3.6 should already have this patch? Is the release of Patch same as WLS version?
Should I still go ahead and install the patch for this version 10.3.6 also?
Thanks again.
- Shankar.

[Solved] how do i build my ISO image with archiso?

hi all
i've been following this wiki and it's been going really well (it hasn't gone wrong...). but the wiki page just sort of stops halfway through the configuration bit
a google search brought me to this page which suggests using the "build.sh" script located in my chroot environment's /tmp/releng/ directory.
running this script returns the error "build.sh: line 207: syntax error near unexpected token '('
line 207 of the file reads:
paste -d"\n" <(sed "s|%ARCH%|i686|g" ${script_path}/aitab.${_iso_type}) \
i don't really know much about scripts so i can't see what's wrong
any advice?
sorry if i've missed a wiki or something n00bish like that. also i'm aware that someone who doesn't know what they're doing shouldn't be attempting archiso but i thought it would be a fun learning experience
here's the full build.sh in case it is helpful:
#!/bin/bash
set -e -u
iso_name=archlinux
iso_label="ARCH_$(date +%Y%m)"
iso_version=$(date +%Y.%m.%d)
install_dir=arch
arch=$(uname -m)
work_dir=work
out_dir=out
verbose=""
script_path=$(readlink -f ${0%/*})
# Base installation (root-image)
make_basefs() {
mkarchiso ${verbose} -w "${work_dir}" -D "${install_dir}" -p "base" create
mkarchiso ${verbose} -w "${work_dir}" -D "${install_dir}" -p "memtest86+ syslinux mkinitcpio-nfs-utils nbd curl" create
# Additional packages (root-image)
make_packages() {
mkarchiso ${verbose} -w "${work_dir}" -D "${install_dir}" -p "$(grep -v ^# ${script_path}/packages.${arch})" create
# Copy mkinitcpio archiso hooks (root-image)
make_setup_mkinitcpio() {
if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then
local _hook
for _hook in archiso archiso_shutdown archiso_pxe_common archiso_pxe_nbd archiso_pxe_http archiso_pxe_nfs archiso_loop_mnt; do
cp /lib/initcpio/hooks/${_hook} ${work_dir}/root-image/lib/initcpio/hooks
cp /lib/initcpio/install/${_hook} ${work_dir}/root-image/lib/initcpio/install
done
cp /lib/initcpio/install/archiso_kms ${work_dir}/root-image/lib/initcpio/install
cp /lib/initcpio/archiso_shutdown ${work_dir}/root-image/lib/initcpio
cp /lib/initcpio/archiso_pxe_nbd ${work_dir}/root-image/lib/initcpio
cp ${script_path}/mkinitcpio.conf ${work_dir}/root-image/etc/mkinitcpio-archiso.conf
: > ${work_dir}/build.${FUNCNAME}
fi
# Prepare ${install_dir}/boot/
make_boot() {
if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then
local _src=${work_dir}/root-image
local _dst_boot=${work_dir}/iso/${install_dir}/boot
mkdir -p ${_dst_boot}/${arch}
mkarchroot -n -r "mkinitcpio -c /etc/mkinitcpio-archiso.conf -k /boot/vmlinuz-linux -g /boot/archiso.img" ${_src}
mv ${_src}/boot/archiso.img ${_dst_boot}/${arch}/archiso.img
mv ${_src}/boot/vmlinuz-linux ${_dst_boot}/${arch}/vmlinuz
cp ${_src}/boot/memtest86+/memtest.bin ${_dst_boot}/memtest
cp ${_src}/usr/share/licenses/common/GPL2/license.txt ${_dst_boot}/memtest.COPYING
: > ${work_dir}/build.${FUNCNAME}
fi
# Prepare /${install_dir}/boot/syslinux
make_syslinux() {
if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then
local _src_syslinux=${work_dir}/root-image/usr/lib/syslinux
local _dst_syslinux=${work_dir}/iso/${install_dir}/boot/syslinux
mkdir -p ${_dst_syslinux}
for _cfg in ${script_path}/syslinux/*.cfg; do
sed "s|%ARCHISO_LABEL%|${iso_label}|g;
s|%INSTALL_DIR%|${install_dir}|g;
s|%ARCH%|${arch}|g" ${_cfg} > ${_dst_syslinux}/${_cfg##*/}
done
cp ${script_path}/syslinux/splash.png ${_dst_syslinux}
cp ${_src_syslinux}/*.c32 ${_dst_syslinux}
cp ${_src_syslinux}/*.com ${_dst_syslinux}
cp ${_src_syslinux}/*.0 ${_dst_syslinux}
cp ${_src_syslinux}/memdisk ${_dst_syslinux}
mkdir -p ${_dst_syslinux}/hdt
wget -O - http://pciids.sourceforge.net/v2.2/pci.ids | gzip -9 > ${_dst_syslinux}/hdt/pciids.gz
cat ${work_dir}/root-image/lib/modules/*-ARCH/modules.alias | gzip -9 > ${_dst_syslinux}/hdt/modalias.gz
: > ${work_dir}/build.${FUNCNAME}
fi
# Prepare /isolinux
make_isolinux() {
if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then
mkdir -p ${work_dir}/iso/isolinux
sed "s|%INSTALL_DIR%|${install_dir}|g" ${script_path}/isolinux/isolinux.cfg > ${work_dir}/iso/isolinux/isolinux.cfg
cp ${work_dir}/root-image/usr/lib/syslinux/isolinux.bin ${work_dir}/iso/isolinux/
cp ${work_dir}/root-image/usr/lib/syslinux/isohdpfx.bin ${work_dir}/iso/isolinux/
: > ${work_dir}/build.${FUNCNAME}
fi
# Customize installation (root-image)
# NOTE: mkarchroot should not be executed after this function is executed, otherwise will overwrites some custom files.
make_customize_root_image() {
if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then
cp -af ${script_path}/root-image ${work_dir}
chmod 750 ${work_dir}/root-image/etc/sudoers.d
chmod 440 ${work_dir}/root-image/etc/sudoers.d/g_wheel
mkdir -p ${work_dir}/root-image/etc/pacman.d
wget -O ${work_dir}/root-image/etc/pacman.d/mirrorlist http://www.archlinux.org/mirrorlist/all/
sed -i "s/#Server/Server/g" ${work_dir}/root-image/etc/pacman.d/mirrorlist
chroot ${work_dir}/root-image /usr/sbin/locale-gen
chroot ${work_dir}/root-image /usr/sbin/useradd -m -p "" -g users -G "audio,disk,optical,wheel" arch
: > ${work_dir}/build.${FUNCNAME}
fi
# Split out /lib/modules from root-image (makes more "dual-iso" friendly)
make_lib_modules() {
if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then
mv ${work_dir}/root-image/lib/modules ${work_dir}/lib-modules
: > ${work_dir}/build.${FUNCNAME}
fi
# Split out /usr/share from root-image (makes more "dual-iso" friendly)
make_usr_share() {
if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then
mv ${work_dir}/root-image/usr/share ${work_dir}/usr-share
: > ${work_dir}/build.${FUNCNAME}
fi
# Make [core] repository, keep "any" pkgs in a separate fs (makes more "dual-iso" friendly)
make_core_repo() {
if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then
local _url _urls _pkg_name _cached_pkg _dst _pkgs
mkdir -p ${work_dir}/repo-core-any
mkdir -p ${work_dir}/repo-core-${arch}
pacman -Sy
_pkgs=$(comm -2 -3 <(pacman -Sql core | sort | sed 's@^@core/@') \
<(grep -v ^# ${script_path}/core.exclude.${arch} | sort | sed 's@^@core/@'))
_urls=$(pacman -Sddp ${_pkgs})
pacman -Swdd --noprogressbar --noconfirm ${_pkgs}
for _url in ${_urls}; do
_pkg_name=${_url##*/}
_cached_pkg=/var/cache/pacman/pkg/${_pkg_name}
_dst=${work_dir}/repo-core-${arch}/${_pkg_name}
cp ${_cached_pkg} ${_dst}
repo-add -q ${work_dir}/repo-core-${arch}/core.db.tar.gz ${_dst}
if [[ ${_pkg_name} == *any.pkg.tar* ]]; then
mv ${_dst} ${work_dir}/repo-core-any/${_pkg_name}
ln -sf ../any/${_pkg_name} ${_dst}
fi
done
: > ${work_dir}/build.${FUNCNAME}
fi
# Process aitab
# args: $1 (core | netinstall)
make_aitab() {
local _iso_type=${1}
if [[ ! -e ${work_dir}/build.${FUNCNAME}_${_iso_type} ]]; then
sed "s|%ARCH%|${arch}|g" ${script_path}/aitab.${_iso_type} > ${work_dir}/iso/${install_dir}/aitab
: > ${work_dir}/build.${FUNCNAME}_${_iso_type}
fi
# Build all filesystem images specified in aitab (.fs .fs.sfs .sfs)
make_prepare() {
mkarchiso ${verbose} -w "${work_dir}" -D "${install_dir}" prepare
# Build ISO
# args: $1 (core | netinstall)
make_iso() {
local _iso_type=${1}
mkarchiso ${verbose} -w "${work_dir}" -D "${install_dir}" checksum
mkarchiso ${verbose} -w "${work_dir}" -D "${install_dir}" -L "${iso_label}" -o "${out_dir}" iso "${iso_name}-${iso_version}-${_iso_type}-${arch}.iso"
# Build dual-iso images from ${work_dir}/i686/iso and ${work_dir}/x86_64/iso
# args: $1 (core | netinstall)
make_dual() {
local _iso_type=${1}
if [[ ! -e ${work_dir}/dual/build.${FUNCNAME}_${_iso_type} ]]; then
if [[ ! -d ${work_dir}/i686/iso || ! -d ${work_dir}/x86_64/iso ]]; then
echo "ERROR: i686 or x86_64 builds does not exist."
_usage 1
fi
local _src_one _src_two _cfg
if [[ ${arch} == "i686" ]]; then
_src_one=${work_dir}/i686/iso
_src_two=${work_dir}/x86_64/iso
else
_src_one=${work_dir}/x86_64/iso
_src_two=${work_dir}/i686/iso
fi
mkdir -p ${work_dir}/dual/iso
cp -a -l -f ${_src_one} ${work_dir}/dual
cp -a -l -n ${_src_two} ${work_dir}/dual
rm -f ${work_dir}/dual/iso/${install_dir}/aitab
rm -f ${work_dir}/dual/iso/${install_dir}/boot/syslinux/*.cfg
if [[ ${_iso_type} == "core" ]]; then
if [[ ! -e ${work_dir}/dual/iso/${install_dir}/any/repo-core-any.sfs ||
! -e ${work_dir}/dual/iso/${install_dir}/i686/repo-core-i686.sfs ||
! -e ${work_dir}/dual/iso/${install_dir}/x86_64/repo-core-x86_64.sfs ]]; then
echo "ERROR: core_iso_single build is not found."
_usage 1
fi
else
rm -f ${work_dir}/dual/iso/${install_dir}/any/repo-core-any.sfs
rm -f ${work_dir}/dual/iso/${install_dir}/i686/repo-core-i686.sfs
rm -f ${work_dir}/dual/iso/${install_dir}/x86_64/repo-core-x86_64.sfs
fi
paste -d"\n" <(sed "s|%ARCH%|i686|g" ${script_path}/aitab.${_iso_type}) \
<(sed "s|%ARCH%|x86_64|g" ${script_path}/aitab.${_iso_type}) | uniq > ${work_dir}/dual/iso/${install_dir}/aitab
for _cfg in ${script_path}/syslinux.dual/*.cfg; do
sed "s|%ARCHISO_LABEL%|${iso_label}|g;
s|%INSTALL_DIR%|${install_dir}|g" ${_cfg} > ${work_dir}/dual/iso/${install_dir}/boot/syslinux/${_cfg##*/}
done
mkarchiso ${verbose} -w "${work_dir}/dual" -D "${install_dir}" checksum
mkarchiso ${verbose} -w "${work_dir}/dual" -D "${install_dir}" -L "${iso_label}" -o "${out_dir}" iso "${iso_name}-${iso_version}-${_iso_type}-dual.iso"
: > ${work_dir}/dual/build.${FUNCNAME}_${_iso_type}
fi
purge_single ()
if [[ -d ${work_dir} ]]; then
find ${work_dir} -mindepth 1 -maxdepth 1 \
! -path ${work_dir}/iso -prune \
| xargs rm -rf
fi
purge_dual ()
if [[ -d ${work_dir}/dual ]]; then
find ${work_dir}/dual -mindepth 1 -maxdepth 1 \
! -path ${work_dir}/dual/iso -prune \
| xargs rm -rf
fi
clean_single ()
rm -rf ${work_dir}
rm -f ${out_dir}/${iso_name}-${iso_version}-*-${arch}.iso
clean_dual ()
rm -rf ${work_dir}/dual
rm -f ${out_dir}/${iso_name}-${iso_version}-*-dual.iso
make_common_single() {
make_basefs
make_packages
make_setup_mkinitcpio
make_boot
make_syslinux
make_isolinux
make_customize_root_image
make_lib_modules
make_usr_share
make_aitab $1
make_prepare $1
make_iso $1
_usage ()
echo "usage ${0} [options] command <command options>"
echo
echo " General options:"
echo " -N <iso_name> Set an iso filename (prefix)"
echo " Default: ${iso_name}"
echo " -V <iso_version> Set an iso version (in filename)"
echo " Default: ${iso_version}"
echo " -L <iso_label> Set an iso label (disk label)"
echo " Default: ${iso_label}"
echo " -D <install_dir> Set an install_dir (directory inside iso)"
echo " Default: ${install_dir}"
echo " -w <work_dir> Set the working directory"
echo " Default: ${work_dir}"
echo " -o <out_dir> Set the output directory"
echo " Default: ${out_dir}"
echo " -v Enable verbose output"
echo " -h This help message"
echo
echo " Commands:"
echo " build <mode> <type>"
echo " Build selected .iso by <mode> and <type>"
echo " purge <mode>"
echo " Clean working directory except iso/ directory of build <mode>"
echo " clean <mode>"
echo " Clean working directory and .iso file in output directory of build <mode>"
echo
echo " Command options:"
echo " <mode> Valid values 'single' or 'dual'"
echo " <type> Valid values 'netinstall', 'core' or 'all'"
exit ${1}
if [[ ${EUID} -ne 0 ]]; then
echo "This script must be run as root."
_usage 1
fi
while getopts 'N:V:L:D:w:o:vh' arg; do
case "${arg}" in
N) iso_name="${OPTARG}" ;;
V) iso_version="${OPTARG}" ;;
L) iso_label="${OPTARG}" ;;
D) install_dir="${OPTARG}" ;;
w) work_dir="${OPTARG}" ;;
o) out_dir="${OPTARG}" ;;
v) verbose="-v" ;;
h|?) _usage 0 ;;
_msg_error "Invalid argument '${arg}'" 0
_usage 1
esac
done
shift $((OPTIND - 1))
if [[ $# -lt 1 ]]; then
echo "No command specified"
_usage 1
fi
command_name="${1}"
if [[ $# -lt 2 ]]; then
echo "No command mode specified"
_usage 1
fi
command_mode="${2}"
if [[ ${command_name} == "build" ]]; then
if [[ $# -lt 3 ]]; then
echo "No build type specified"
_usage 1
fi
command_type="${3}"
fi
if [[ ${command_mode} == "single" ]]; then
work_dir=${work_dir}/${arch}
fi
case "${command_name}" in
build)
case "${command_mode}" in
single)
case "${command_type}" in
netinstall)
make_common_single netinstall
core)
make_core_repo
make_common_single core
all)
make_common_single netinstall
make_core_repo
make_common_single core
echo "Invalid build type '${command_type}'"
_usage 1
esac
dual)
case "${command_type}" in
netinstall)
make_dual netinstall
core)
make_dual core
all)
make_dual netinstall
make_dual core
echo "Invalid build type '${command_type}'"
_usage 1
esac
echo "Invalid build mode '${command_mode}'"
_usage 1
esac
purge)
case "${command_mode}" in
single)
purge_single
dual)
purge_dual
echo "Invalid purge mode '${command_mode}'"
_usage 1
esac
clean)
case "${command_mode}" in
single)
clean_single
dual)
clean_dual
echo "Invalid clean mode '${command_mode}'"
_usage 1
esac
echo "Invalid command name '${command_name}'"
_usage 1
esac
Last edited by gav989 (2012-02-12 10:59:11)

thanks for that, according to this it should be run like
/path/to/build.sh build single netinstall
from inside the chroot
posting this for my own reference and in case it helps others, will mark as solved
thanks again for your help
Last edited by gav989 (2012-02-12 10:58:04)

[SOLVED, kind of] UEFI bootable USB from ISO doesn't start

Hi there,
out of curiosity I wanted to create an UEFI bootable usb stick with the latest Archiso 2013.01.04. I've followed https://wiki.archlinux.org/index.php/UE … B_from_ISO
and created two directories
# mkdir -p /mnt/{usb,iso}
Then I've mounted Archiso to /mnt/iso
# mount -o loop Download/ISO-Images/archlinux-2013.01.04-dual.iso /mnt/iso
After this I used cfdisk to create a FAT32 filesystem /dev/sdb1 on the usb stick, followed by
# awk 'BEGIN {FS="="} /archisolabel/ {print $3}' /mnt/iso/loader/entries/archiso-x86_64.conf | xargs mkfs.vfat /dev/sdb1 -n
Then I've mounted /dev/sdb1 to /mnt/usb and copied all iso-files there:
# mount /dev/sdb1 /mnt/usb
# cp -r /mnt/iso/* /mnt/usb
Followed by:
# umount /mnt/{usb,iso}
# sync
After rebooting and hitting F11 I was presented with the UEFI firmware-tool from which I can choose UEFI (and other) applications to start. I could choose my usb stick in UEFI mode, but - only the screen turned blank for the blink of a second and the UEFI tool was on again.
Because my system is already booting in UEFI mode using rEFInd, I wanted to try rEFInd on the usb stick instead of gummiboot.
Following https://wiki.archlinux.org/index.php/UE … B_from_ISO I've copied /usr/lib/refind/refind_x64.efi (from refind-efi 0.6.4-1) to /mnt/usb/EFI/boot/bootx64.efi and created a /mnt/usb/EFI/boot/refind.conf with this text:
timeout 5
textonly
showtools about,reboot,shutdown,exit
# scan_driver_dirs EFI/tools/drivers_x64
scanfor manual,internal,external,optical
scan_delay 1
dont_scan_dirs EFI/boot
max_tags 0
default_selection "Arch Linux Archiso x86_64 UEFI USB"
menuentry "Arch Linux Archiso x86_64 UEFI USB" {
loader /arch/boot/x86_64/vmlinuz
initrd /arch/boot/x86_64/archiso.img
ostype Linux
graphics off
options "pci=nocrs add_efi_memmap archisobasedir=arch archisolabel=ARCH_201301"
menuentry "UEFI x86_64 Shell v2" {
loader /EFI/shellx64_v2.efi
graphics off
menuentry "UEFI x86_64 Shell v1" {
loader /EFI/shellx64_v1.efi
graphics off
And yes, I've checked the "loader" and "initrd"-Paths - they are correct, as well as the archisolabel
But - again - after rebooting and hitting F11 I could select my usb stick as UEFI boot device, but all that happened was the screen going blank for the glimpse of a second and returning to the UEFI chooser.
Even my last attempt - keeping the original name refind_x64.efi in /mnt/usb/EFI/boot didn't help.
Via efibootmgr I can see:
$ sudo efibootmgr
BootCurrent: 0001
Timeout: 5 seconds
BootOrder: 0001,0002,0007,0005,0006
Boot0001* rEFInd 0.6.4-1
Boot0002* rEFInd_recover
Boot0005* Hard Drive
Boot0006* USB
Boot0007* UEFI: TOSHIBA TransMemory PMAP
with "Boot0007" as my usb stick.
So my question is: Did I miss something or have I found a bug ?
Last edited by swordfish (2013-01-13 12:43:33)

Hm, funny thing - now it's working, but I don't know why
I've tried to convert the partition table of the usb stick from MBR to GPT using cgdisk. There I had a problem with setting the partition type to EF00. It worked under cgdisk, but then I couldn't mount my usb stick (dev/sdb1) anymore to /mnt/usb. Then I've tried to set the partition type to vfat, but couldn't identify what is vfat under cgdisk . I've tried different types of "Windows" but whatever I tried, the usb stick won't mount on /mnt/usb.
Journalctl always says:
Jan 13 12:23:03 sushi sudo[727]: nihonto : TTY=pts/0 ; PWD=/home/nihonto ; USER=root ; COMMAND=/usr/bin/cgdisk /dev/sdb
Jan 13 12:23:03 sushi sudo[727]: pam_unix(sudo:session): session opened for user root by nihonto(uid=0)
Jan 13 12:23:11 sushi sudo[727]: pam_unix(sudo:session): session closed for user root
Jan 13 12:24:00 sushi su[972]: (to root) nihonto on /dev/pts/0
Jan 13 12:24:00 sushi su[972]: pam_unix(su:session): session opened for user root by nihonto(uid=1000)
Jan 13 12:24:18 sushi kernel: loop: module loaded
Jan 13 12:24:18 sushi kernel: ISO 9660 Extensions: RRIP_1991A
Jan 13 12:24:35 sushi kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
Jan 13 12:24:35 sushi kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
Jan 13 12:24:35 sushi kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
Jan 13 12:24:35 sushi kernel: FAT-fs (sdb1): bogus number of reserved sectors
Jan 13 12:24:35 sushi kernel: FAT-fs (sdb1): Can't find a valid FAT filesystem
Jan 13 12:24:35 sushi kernel: ISOFS: Unable to identify CD-ROM format.
So I tried it again with cfdisk which nagged about "unsupported GPT" but kept working. This time I choose "0C W95 FAT32 (LBA)" as partition type - maybe this did the trick because in my earlier attempts I did choose "0B W95 FAT32".
Anyway - after following the advice stated in https://wiki.archlinux.org/index.php/UE … B_from_ISO and installing rEFInd to the usb stick I could boot the usb stick in UEFI mode
But - as I said earlier - I don't know what did the trick
Last edited by swordfish (2013-01-13 12:38:18)

Windows Vista, 7 and 8 ISO / Image file Download Links

Series: How to Re-Install Windows when you don't have the Recovery Discs
Intro: What is an ISO? Why is it used?
Step 1 - Get the ISO - ISO Download Links
Step 2 - Burn the ISO to a DVD or USB
Step 3 - What to do with the ISO DVD/USB? Change the Boot Order
Step 4 - What to do After Windows is Installed? How to Get HP Drivers?
Step 1 - Get the ISO - ISO Download Links
First, look at the Product Key label on the bottom of the computer and make sure you can still read it, before proceeding.
How is this legal? As long as you have the Product Key (from the bottom of a computer you paid for) for the corresponding version of Windows you download, it is perfectly legitimate and legal.
The ISO Links:
Windows Vista SP1 32 & 64-bit
*****With that link, you will have to combine the three files into an Image file (aka ISO) first (How to create an image file from files/folders) , using a program like ImgBurn.*****
Windows 7 32 & 64-bit
Windows 8 32 & 64-bit
See Step 2 - Burn the ISO to a DVD or USB
If you have any questions, create a new post (How to Create a New Post - Video), copy and paste it's link into a private message to me, and I will respond on your thread

You shouldn't need to edit any of the files. The Windows 7 ISO is a retail, untouched version. It doesn't have a Product Key embedded into it.
You should be able to use a Windows 7 Product Key from the label on the bottom of the computer with no issues. The installation will ask you for a Windows 7 Product Key. The only exception would be if the Product Key were in use on a different computer. From my understanding, as long as it is not already in use, it should activate.
Please let me know if you have any questions on that

Iso to usb drive tool doesn't work

whenever I try to create a bootable usb drive so I can install my Windows 7 it tells me "The selected file is not a valid ISO file. Please select a valid ISO file and try again"
its a iso, I thought it was supposed to be easy but its a pain in the ____

Hi Com,
The Windows 7 USB download tool is using a open-source code. When you select a custom ISO file, you will receive the error “The selected file is not a valid ISO file. Please Select a valid ISO file and try again”. In order to use a custom ISO file, please refer to Use the Windows 7 USB/DVD Download Tool with custom ISOs
Please note: we provide 3rd party link for references. There may be some changes without notice, Microsoft doesn't guarantee any accuracy on contacting information.
For more references:
Installing Windows 7 using usb thumb drive
Best Regards
Dale

How do I make a bootable cd from the windows .iso file

I am trying to install windows xp on my iMac. My univeristy gives me free copy of XP but I have to download the .iso file. I tried burning the .iso file to a cd but bootcamp says it can not recognize the cd for installation. How can a make a bootable copy of the windows xp .iso file so that I can install it on my iMac.

You used Disk Utility I take it?
http://en.wikipedia.org/wiki/ISO-9660
http://www.ezbsystems.com/ultraiso/
This is for creating a custom Vista SP1 EFI-enabled DVD:
http://www.jowie.com/post/2008/02/Select-CD-ROM-Boot-Type--prompt-while-trying-t o-boot-from-Vista-x64-DVD-burnt-from-iso-file.aspx

[Solved] problem with virtualbox-iso-additions for virtualbox v. 4.2

VirtualBox 4.2 was released recently and one of the features mentioned is support for Mac OSX. However, having installed it (an Arch virtualbox 4.2 host, and an osx guest), I found that I couldn't install guest additions via the devices menu on my osx guest. Whereupon I examined the file corresponding to virtualbox-iso-additions (/usr/lib/virtualbox/additions/VBoxGuestAdditions.iso) and found that in fact there were no scripts or drivers for osx (darwin) like there are for windows and linux. Is it possible that the Arch release of this file has not been updated properly or am I missing anything else?
Update: I downloaded the current iso (VBoxGuestAdditions_4.2.0.iso) from http://download.virtualbox.org/virtualbox/4.2.0/ and found that that too has no files that appear linked to osx or darwin. That rules out an Arch packaging issue and I'll need to pursue things at virtualbox.org itself.
Last edited by kinleyd (2013-07-18 12:03:48)

I think I've figured it out, finally. It seems v. 4.2 introduces virtualbox on a mac osx host. osx guests are apparently not officially supported with guest additions. I had assumed that host support already existed, and that the new stuff in v. 4.2 was for guests.

How to get ISO week number?

hi,
I need to interact with a server that expects to be passed the ISO week number. The Calendar class doesn't seem to support this though (although the documentation claims that it is ISO 8601 compliant).
For instance the web page here gives today (Jan 10th 2005) as being in Week 2
http://personal.ecu.edu/mccartyr/isowdcal.html
but this code snippet returns "Week 3"
import java.util.*;
public class WeekOfYear {
     public static void main(String[]arg) {
          Calendar c = Calendar.getInstance();
          System.out.println("Week "+c.get(Calendar.WEEK_OF_YEAR));
}does anyone know a correct way of getting the ISO 8601 Week number without reimplenting a lot of delicate code?
thanks,
asjf
ps. of course for now, and the rest of 2005, i'm going to hard code subtracting 1 as a gratuitous hack :o)

hi,
thanks - i did check the docs :)
the problem is that Calendar's idea of what the first week in the year is differs from the ISO standard
the problem is that the ISO standard defines the first week of the year as that containing the first Thursday (ie some days may become part of the previous year's weeks)
and Calendar defines it as the docs state - so to change the value returned would mean you having to change the "FirstDayOfWeek" or the "MinimalDaysInFirstWeek" - which (without checking recently) I think the ISO standard also defines so you can't safely change these
I might raise a RFE against Calendar about this in a week or two since it seems quite important?
thanks,
asjf

Which iso is right one for Athlon XP 1.8G?

I will have ethernet connection while installing but which CD iso do I need?
Sorry about the real newbie question.
A. archlinux-2009.08-netinstall-i686.iso i686/32bit CD-ISO
B. archlinux-2009.08-netinstall-x86_64.iso x86_64/64bit CD-ISO
thanks in advance.
gychang

Anything before Athlon64 doesn't have 64 bit support. It's pretty easy with AMD .

=?iso-8859-1?Q?OT:_20_signs_you_don't_want_that_web_design_project_by_Jef?= =?iso-8859-1?Q?frey_Zeldman?=

Similar Messages

Maybe you are looking for