Install Pacman on non-arch system

Heya. I'm running a server that's hosting an arch repo, but the server itself isn't running arch. I was wonderin' if it was possible to install basic commands like repo-add and pacman, so I can manage the repo from the server, instead of having to manage it on my local comp and upload everything. Anyone know if this is possible?

Yes, just build pacman from source on the server.

Similar Messages

  • How to install Oracle on NON FILE SYSTEM platform(UNIX OR NT)

    Anyone tell me

    First of all thanks for your help,
    I tried again with ./runInstall -ignoreSysPrereqs but I got another error...
    "Starting Oracle Universal Installer...
    Checking Temp space: must be greater than 120 MB. Actual 63827 MB Passed
    Checking swap space: must be greater than 150 MB. Actual 6233 MB Passed
    Checking monitor: must be configured to display at least 256 colors
    >>> Could not execute auto check for display colors using command /usr/X11R6/bin/xdpyinfo. Check if the DISPLAY variable is set. Failed <<<<
    Ignoring required pre-requisite failures. Continuing...Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-02-19_12-16-16PM. Please wait ...sh: /home/octopus/downloads/database/install/unzip: not found"
    every time I try another way to install I get another error or something...
    I tried the installations with the response file but I got the same error...
    "Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-02-19_12-16-16PM. Please wait ...sh: /home/octopus/downloads/database/install/unzip: not found"
    When I search for that file in " /home/octopus/downloads/database/install/" "unzip" is there.....
    Any ideas???
    Thanks in advance!

  • How to install SAPOSCOL in non-sap server ?

    Hi,
    Please advise how to install SAPOSCOL into non sap system ? any related document / help ?
    Thank You and Best Regards
    Fernand

    Hi,
    The reason why, i want to install saposcol and sapagent in non sap system because i want to monitoring this serve with system monitoring.
    Finally, i can install with install.cmd from this notes : 704349
    Thank You and Best Regards
    Fernand

  • Networked or non-networked system?

    Hello people.Me again with stupid questions. As I said, I want to use my computer as server, to serve web pages in local area network, for my family and my neighbours. What I want to do is to set up a network, and on the very first step of the installation I am in dilemma. Should my system be a networked? What solaris mean under 'networked'? Is this settings for my network, or for internet? I use ADSL, and I get the dynamic Ip adress, each time I connect. So what to do? To say that my system is networked, and should I enable DHCP, or should I configure it manually? I am really confused. I tried to set it up manually, but installation did not found any default routers... I want to my server have a static Ip adress... What to do? And is this a settings for the internet, of for local area network? Thank you again, and sorry for stupid question.
    Sincerely Oziris

    I think that things are much clearer now. Now i want
    to summarize your post, just to see if I understood
    you good. First i will install solaris as
    Non-networked system, and later, when I boot solaris,
    and when it is working i will apply this pkg file
    (which i downloaded with windows, and have it on
    flash). On the site where you tell me to download
    this pkg it writes:
    # wget
    http://www.opensolaris.org/os/community/laptop/downloa
    ds/inetmenu-2.3.2.pkg.gz
    # gunzip inetmenu-2.3.2.pkg.gz
    # pkgadd -d ./inetmenu-2.3.2.pkg
    I suppose that this first line i don`t need to type,
    because it is wget (suppose web get), and i will have
    no network, and internet (right?). And where I should
    type this, probably in some 'shell' or something like
    that (i am as I already said a total newbie). The first line is simply a way to download the pkg. Do the appropriate
    thing under Windows. Once you have downloaded the pkg and on a media which can been accessed by Solaris, then the other two steps can be performed within a terminal window after Solaris is installed.
    jAnd ust one more question, i want dual boot, and i read
    about it on forums. I think that on my first hard
    disc (where windows is installed, I must make a new
    raw partition, so I will be able to chose whic OS i
    want to boot). How much space this partition must
    have? Is 20 gb ok? Yes 20GB is sufficient. When installing Solaris and you get the choice of partitions, I would recommend adding an extra partition of about 4GB. This will allow you to do Live Upgrades. Google for dual boot Solaris and Live Upgrade there is plenty of documentation on this.
    `cos I have 200 gb secondary disc
    and all data will be on it, the first disc (80 gb) is
    only for OS`s. Thank you very very much!

  • Trying to install Windows7 on osx Lion using USB or External superdrive but the message i get is "NON DISK SYSTEM"

    Trying to install Windows7 on osx Lion using USB or External superdrive but the message i get is "NON DISK SYSTEM"
    i also tried rEFIt but...the same....i tried using bootcamp to create a bootable usb stick but i lost this option after i upgraded BOOTCAMP to 5.0.4

    Trying to install Windows7 on osx Lion using USB or External superdrive but the message i get is "NON DISK SYSTEM"
    i also tried rEFIt but...the same....i tried using bootcamp to create a bootable usb stick but i lost this option after i upgraded BOOTCAMP to 5.0.4

  • Pacman -Su killed my system!

    Hi
    I made a systemupgrade and now is my system (rootserver) dead!
    How can i save my system remote?
    [root@rocky pacman.d]# pacman -Su
    Targets: automake-1.10-1 damageproto-1.1.0-1 freetype2-2.3.1-1 gcc-4.1.2-3 glibc-2.5-4
    kernel-headers-2.6.20-1 kernel26-2.6.20-3 xcb-proto-1.0-1 libxcb-1.0-2
    libx11-1.1.1-2 libxdamage-1.1-1 libxml2-2.6.27-2 libxslt-1.1.20-2
    randrproto-1.2.0-1
    Total Package Size: 52.7 MB
    Proceed with upgrade? [Y/n] y
    :: Retrieving packages from testing...
    automake-1.10-1 [#######################] 100% 317K 80.0K/s 00:00:03
    damageproto-1.1.0-1 [#######################] 100% 2K 2.0K/s 00:00:01
    freetype2-2.3.1-1 [#######################] 100% 702K 150.0K/s 00:00:04
    gcc-4.1.2-3 [#######################] 100% 18155K 224.2K/s 00:01:20
    glibc-2.5-4 [#######################] 100% 10310K 227.0K/s 00:00:45
    kernel-headers-2.6.20-1 [#######################] 100% 585K 135.1K/s 00:00:04
    kernel26-2.6.20-3 [#######################] 100% 19604K 189.4K/s 00:01:43
    libx11-1.1.1-2 [#######################] 100% 1974K 180.5K/s 00:00:10
    libxdamage-1.1-1 [#######################] 100% 7K 4.2K/s 00:00:01
    libxml2-2.6.27-2 [#######################] 100% 1531K 182.2K/s 00:00:08
    libxslt-1.1.20-2 [#######################] 100% 355K 78.9K/s 00:00:04
    randrproto-1.2.0-1 [#######################] 100% 4K 4.0K/s 00:00:01
    :: Retrieving packages from current...
    xcb-proto-1.0-1 [#######################] 100% 33K 18.3K/s 00:00:01
    libxcb-1.0-2 [#######################] 100% 333K 99.2K/s 00:00:03
    checking package integrity... done.
    loading package data... done.
    checking for file conflicts... done.
    upgrading automake... done.
    upgrading damageproto... done.
    upgrading freetype2... done.
    upgrading gcc... done.
    upgrading glibc... done.
    upgrading kernel-headers... done.
    upgrading kernel26... done.
    installing xcb-proto... done.
    installing libxcb... done.
    upgrading libx11... done.
    upgrading libxdamage... done.
    upgrading libxml2... done.
    upgrading libxslt... done.
    upgrading randrproto... done.
    [root@rocky pacman.d]# uname -r
    -bash: /bin/uname: No such file or directory
    [root@rocky pacman.d]# uname -r
    -bash: /bin/uname: No such file or directory
    [root@rocky pacman.d]# ls
    -bash: /bin/ls: No such file or directory
    [root@rocky pacman.d]# ls
    -bash: /bin/ls: No such file or directory
    [root@rocky pacman.d]# rebot
    -bash: rebot: command not found
    [root@rocky pacman.d]# reboot
    -bash: /sbin/reboot: No such file or directory
    [root@rocky pacman.d]# /bin/
    arch df hostname mountpoint su
    awk dir install mv sync
    bash dircolors isatty netstat tar
    bunzip2 dmesg kill nisdomainname touch
    bzcat dnsdomainname less pidof tr
    bzip2 domainname ln ping true
    bzip2recover du loadkeys ping6 umount
    cat echo loadkeys.static ps uname
    chgrp egrep login pwd uncompress
    chmod false ls readlink vdir
    chown fgrep lsmod rm ypdomainname
    compress gawk mbchk rmdir zcat
    cp gawk-3.1.5 mkdir sed zless
    cpio grep mkfifo sh
    cut groups mknod shred
    date gunzip more sleep
    dd gzip mount stty
    [root@rocky pacman.d]# /bin/
    arch df hostname mountpoint su
    awk dir install mv sync
    bash dircolors isatty netstat tar
    bunzip2 dmesg kill nisdomainname touch
    bzcat dnsdomainname less pidof tr
    bzip2 domainname ln ping true
    bzip2recover du loadkeys ping6 umount
    cat echo loadkeys.static ps uname
    chgrp egrep login pwd uncompress
    chmod false ls readlink vdir
    chown fgrep lsmod rm ypdomainname
    compress gawk mbchk rmdir zcat
    cp gawk-3.1.5 mkdir sed zless
    cpio grep mkfifo sh
    cut groups mknod shred
    date gunzip more sleep
    dd gzip mount stty
    [root@rocky pacman.d]# /bin/bash
    -bash: /bin/bash: No such file or directory

    My mkinitcpio.conf and grub/menu.lst was reset after the upgrade. After I chose the right modules and the right orderin mkinitcpio.conf and rebuilt my menu.lst it worked again. Of course, this was my personal experience with the 2.6.20 upgrade of archlinux.
    Best regards,
    Martin

  • ArchTaz Live: boot and run an Arch system entirely in RAM

    ArchTaz Live Boot: A method to boot and run an Arch system entirely in RAM using tmpfs.
    As the name suggests it was inspired by (copied entirely from) SliTaz http://www.slitaz.org/ and boots in exacly the same way.
    It needs a custom init script in the root directory and for some reason that I can't work out a hook for sysinit_premount in rc.sysinit to remount / rw.
    The /usr/bin/archfs script is just a chunk of Slitaz's Tazusb utility with some minor changes (and I haven't properly tested the lzma or no compression).
    The /init script is modified from the usual initramfs /usr/lib/initcpio/init with hints from the SliTaz /init script (and some personal additions for my system).
    Copy init to the root directory, run archfs (eg. # archfs writefs gzip) and move the resulting archfs.gz to your boot partition/directory and boot with archfs.gz as your initrd.
    I run a fairly light system (Openbox, Firefox, Gnome-Mplayer, SpaceFM, no dev packages) and gzip compression gives me an archfs.gz just over 230MB that boots in just over 30 seconds using 138MB RAM on startup, and most applications start instantly (2GHz Core2Duo, 4G RAM). Lzma compression generally gives a smaller archfs.gz but takes longer to boot. I have a persistent home partition, I install packages as I need them and then they're gone on next reboot if I don't do a new archfs.gz to keep them. I delete man pages, unneeded locales, etc. Obviously if you're running a hefty install on a limited box you may run into problems.
    Any tips, cleanups, corrections welcome. It's been a mostly copy and paste and mash stuff together process so it isn't neat. And I think I may need some serious help when systemd becomes default.
    /usr/bin/archfs:
    #!/bin/sh
    # Archfs - entirely copied from part of the Tazusb utility supplied with
    # SLiTaz GNU Linux - with some cosmetic changes.
    ### Tazusb - SliTaz LiveUSB
    ### Tazusb is an utility to generate, configure and manipulate SliTaz LiveUSB
    ### bootable media and/or USB /home partition, such as flash keys, SD card or
    ### USB harddisk.
    ### Authors : Christophe Lincoln (Pankso) <[email protected]>
    ### Andrew Miller (Spode) <[email protected]>
    COMMAND=$1
    case $COMMAND in
    writefs)
    # Writefs to rootfs.gz
    if [ -z $2 ]; then
    COMPRESSION=none
    else
    COMPRESSION=$2
    fi
    # Start info
    echo ""
    echo -e "\033[1mWrite filesystem\033[0m
    ===============================================================================
    The command writefs will write all the current filesystem into a suitable cpio
    archive (rootfs.gz) usable on a bootable LiveUSB media.
    Archive compression: $COMPRESSION"
    echo ""
    # Create list of files
    find /bin /etc /init /sbin /var /lib /lib64 /root /usr >/tmp/list
    for dir in /boot /dev /home /proc /sys /tmp /mnt /media /run
    do
    echo $dir >>/tmp/list
    done
    # Generate initramfs with specified compression
    if [ "$COMPRESSION" = "lzma" ]; then
    echo -n "Creating archfs.gz with lzma compression... "
    cat /tmp/list | cpio -o -H newc | lzma > /archfs.gz
    elif [ "$COMPRESSION" = "gzip" ]; then
    echo -n "Creating archfs.gz with gzip compression... "
    cat /tmp/list | cpio -o -H newc | gzip -9 > /archfs.gz
    else
    echo -n "Creating archfs.gz without compression... "
    cat /tmp/list | cpio -o -H newc > /archfs.gz
    fi
    # Get initramfs size
    size=`du -sh /archfs.gz | cut -f 1`
    echo "==============================================================================="
    echo "Root filesystem size: $size"
    echo ""
    echo -en "----\nENTER to continue..."; read i
    esac
    exit 0
    /init:
    #!/bin/bash
    PATH=/bin:/usr/bin:/usr/sbin:/sbin
    udevd_running=0
    if [ -x /usr/bin/systemd-timestamp ]; then
    RD_TIMESTAMP=$(systemd-timestamp)
    fi
    . /usr/lib/initcpio/init_functions
    mount -t proc proc /proc -o nosuid,noexec,nodev
    mount -t sysfs sys /sys -o nosuid,noexec,nodev
    mount -t devtmpfs dev /dev -o mode=0755,nosuid
    mount -t tmpfs run /run -o nosuid,nodev,mode=0755
    mkdir -m755 /run/initramfs
    # parse the kernel command line
    parse_cmdline
    for d in ${disablehooks//,/ }; do
    [ -e "/hooks/$d" ] && chmod 644 "/hooks/$d"
    done
    #. /config
    run_hookfunctions 'run_earlyhook' 'early hook' $EARLYHOOKS
    [ -n "${earlymodules//[[:space:]]}" ] && modprobe -qab ${earlymodules//,/ }
    [ -n "${MODULES//[[:space:]]}" ] && modprobe -qab $MODULES
    # If rootdelay is empty or not a non-negative integer, set it to 10
    if [ -z "${rootdelay}" ] || ! [ "${rootdelay}" -ge 0 ]; then
    rootdelay=10
    fi
    run_hookfunctions 'run_hook' 'hook' $HOOKS
    # honor the old behavior of break=y as a synonym for break=premount
    if [ "${break}" = "y" ] || [ "${break}" = "premount" ]; then
    echo ":: Pre-mount break requested, type 'exit' to resume operation"
    launch_interactive_shell
    fi
    rootdev=$(resolve_device "$root") && root=$rootdev
    unset rootdev
    #fsck_root
    # Make /new_root
    mkdir /new_root
    # Mount root at /new_root
    #${mount_handler:-default_mount_handler} /new_root
    echo -e "Switching / to tmpfs..."
    mount -t tmpfs tmpfs /new_root
    run_hookfunctions 'run_latehook' 'late hook' $LATEHOOKS
    run_hookfunctions 'run_cleanuphook' 'cleanup hook' $CLEANUPHOOKS
    # Stop udevd if is running
    if [ "${udevd_running}" -eq 1 ]; then
    udevadm control --exit
    udevadm info --cleanup-db
    fi
    # Copy root
    echo -e "Copying root..."
    for i in $(ls -a /); do
    case "$i" in
    .|..) ;;
    mnt) mkdir /new_root/mnt;;
    proc) mkdir /new_root/proc;;
    sys) mkdir /new_root/sys;;
    dev) mkdir /new_root/dev;;
    run) mkdir /new_root/run;;
    new_root) ;;
    *) cp -a /$i /new_root
    esac
    done
    # Create mountpoints
    mkdir /new_root/mnt/sda1
    mkdir /new_root/mnt/sda2
    mkdir /new_root/mnt/sda3
    mkdir /new_root/mnt/sda4
    init=${init:-/sbin/init}
    echo -e "Switching root..."
    exec env -i \
    "TERM=$TERM" \
    "RD_TIMESTAMP=$RD_TIMESTAMP" \
    /sbin/switch_root /new_root $init "$@"
    ## Mount root at /new_root
    #${mount_handler:-default_mount_handler} /new_root
    #run_hookfunctions 'run_latehook' 'late hook' $LATEHOOKS
    #run_hookfunctions 'run_cleanuphook' 'cleanup hook' $CLEANUPHOOKS
    init=${init:-/sbin/init}
    if [ "$(stat -c %D /)" = "$(stat -c %D /new_root)" ]; then
    # Nothing got mounted on /new_root. This is the end, we don't know what to do anymore
    # We fall back into a shell, but the shell has now PID 1
    # This way, manual recovery is still possible.
    err "Failed to mount the real root device."
    echo "Bailing out, you are on your own. Good luck."
    echo
    launch_interactive_shell --exec
    elif [ ! -x "/new_root${init}" ]; then
    # Successfully mounted /new_root, but ${init} is missing
    # The same logic as above applies
    err "Root device mounted successfully, but ${init} does not exist."
    echo "Bailing out, you are on your own. Good luck."
    echo
    launch_interactive_shell --exec
    fi
    if [ "${break}" = "postmount" ]; then
    echo ":: Post-mount break requested, type 'exit' to resume operation"
    launch_interactive_shell
    fi
    exec env -i \
    "TERM=$TERM" \
    "RD_TIMESTAMP=$RD_TIMESTAMP" \
    /sbin/switch_root /new_root $init "$@"
    # vim: set ft=sh ts=4 sw=4 et:
    /etc/rc.d/functions.d/root_rw:
    root_rw() {
    mount -o remount,rw /
    add_hook sysinit_premount root_rw
    archfs:
    http://pastebin.com/RNTDWhFc
    init:
    http://pastebin.com/n4vcqG62
    root_rw:
    http://pastebin.com/i1LV61SV
    Last edited by 0ddba11 (2012-12-30 10:12:35)

    Oh yes any man directory was symlinked to /tmp long ago, so they don't even get installed.
    Right, new boot process:
    Using hooks in normal initramfs-linux.img to unpack archfs.gz into tmpfs and boot it.
    Create an initcpio preset file /etc/mkinitcpio.d/archfs.preset:
    # mkinitcpio preset file for the 'archfs' package
    ALL_config="/etc/mkinitcpio.conf"
    ALL_kver="/boot/vmlinuz-linux"
    PRESETS=('archfs')
    archfs_config="/etc/mkinitcpio.conf"
    archfs_image="/boot/archfs-linux.lzo"
    archfs_options="-S fsck -A tmpfs -z lzop"
    Or append to the standard 'linux.preset' file so the initramfs is created automatically when you upgrade your kernel. Or alter /etc/mkinitcpio.conf to add options.
    Create the file /lib/initcpio/hooks/tmpfs:
    #!/usr/bin/ash
    run_latehook() {
    # Mount tmpfs root
    mount -t tmpfs tmpfs /mnt
    # Unpack rootfs
    msg "Unpacking rootfs..."
    cd /mnt
    # parse the kernel command line
    parse_cmdline
    for archfs in ${archfs//,/ }; do
    if [ "$archfs" = "xz" ]; then
    xz -d < /new_root/boot/archfs.xz | cpio -imd --no-absolute-filenames > /dev/null 2>&1
    elif [ "$archfs" = "gzip" ]; then
    gzip -dc /new_root/boot/archfs.gz | cpio -imd --no-absolute-filenames > /dev/null 2>&1
    elif [ "$archfs" = "lzo" ]; then
    lzop -d < /new_root/boot/archfs.lzo | cpio -imd --no-absolute-filenames > /dev/null 2>&1
    elif [ "$archfs" = "img" ]; then
    cpio -imd --no-absolute-filenames /new_root/boot/archfs.img > /dev/null 2>&1
    fi
    done
    # Switch tmpfs to new root
    umount /new_root
    mount -M /mnt /new_root
    # vim: set ft=sh ts=4 sw=4 et:
    And the file  /lib/initcpio/install/tmpfs:
    #!/bin/bash
    build() {
    add_dir /mnt
    add_module ext3
    add_binary cpio
    add_binary xz
    add_binary gzip
    add_binary lzop
    add_binary fsck.ext4
    add_symlink /usr/bin/fsck.ext2 fsck.ext4
    add_symlink /usr/bin/fsck.ext3 fsck.ext4
    add_runscript
    help() {
    cat <<HELPEOF
    This hook creates the tmpfs root, mounts the device that contains the
    rootfs and extracts it into the tmpfs root.
    HELPEOF
    # vim: set ft=sh ts=4 sw=4 et:
    This loads modules and fsck binaries for the filesystem of my /boot partition into the initramfs. It also adds all the relevant compression binaries (some which can also be compiled into busybox or left out if not needed). I'm working on automatically reading the filesystem from your /boot partition based on the "root=" kernel command line option and adding the appropriate modules.
    Create a new archfs.gz (or new extensions) with new cleaned up /usr/bin/archfs:
    http://pastebin.com/xiqgyYyL
    Now run with:
    # archfs lzo
    (or whichever crompression you choose). It also takes care of any mounting directories you have in /mnt. And "writefs" is no longer needed, that's all it does anyway.
    Then simply add the "root=(your boot partition)" and "archfs=lzo" (or whichever compression you chose) command line options to your grub.cfg.
    Run:
    # mkinitcpio -p archfs
    That'll create an initramfs: archfs-linux.lzo that you need to move to your boot partition with your kernel and archfs.gz. Then point grub to that as your initrd.
    This will boot and the tmpfs hook will do it's work just after init has mounted your boot partition and then init will switch roots and run /sbin/init as it would on any normal install.
    Mix and match as needed. You can remove the /init file from the root of your filesystem or leave it there and all but an xz compressed archfs.gz will boot the old way aswell (the kernel can't handle the xz version). It should all be fairly upgrade proof, barring any major changes to mkinitcpio.
    Boot for me with lzo compression is at least twice as fast as old method. Partly due to lzo compression which is super fast (especially creating the archfs.lzo). It makes for a bigger file but it's still only 350MB (pretty much half my uncompressed root filesystem).

  • Update Xorg 7 and arch-system, this is my contribution

    This works for me, this is my contribution, I hope can help someone in troubles:
    pacman -Sy
    pacman -Rd xorg-server xorg-clients (if installed)
    pacman -Sf xorg-xdm
    pacman -S xorg-clients xorg-server
    pacman -Sf xorg
    pacman -Syu (upgrade all system, almost 200mb)
    pacman -S xorg-fonts-75dpi
    pacman -S xorg-fonts-100dpi
    pacman -S libxcomposite libxss
    Enter in /etc/X11/xorg.conf and reconfigure the paths so:
    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    FontPath "/usr/share/fonts/misc/"
    FontPath "/usr/share/fonts/TTF/"
    FontPath "/usr/share/fonts/Type1/"
    FontPath "/usr/share/fonts/CID/"
    FontPath "/usr/share/fonts/75dpi/"
    FontPath "/usr/share/fonts/100dpi/"
    FontPath "/usr/share/fonts/local/"
    ModulePath "/usr/lib/xorg/modules"
    EndSection
    Write startx, if it doesn't works kdm or gdm, write:
    mkdir -p /usr/X11R6/bin/
    ln -s /usr/bin/X /usr/X11R6/bin/X
    If doesn't works, control the errors, maybe it misses a file, install it with pacman.
    Moreover, I've a ricompiled kernel with drivers nvidia, so I'm entered on my kernel source and I've written:
    make all && make modules_install
    generate-modprobe.conf
    cp -f System.map /boot
    cd arch/i386/boot
    cp -f bzImage /boot
    At this point I've rebooted and I've reinstalled Nvidia drivers:
    ./NVidia.xxxxxx.run (WITHOUT OVERWRITE FILE /etc/X11/xorg.conf)

    This works for me, this is my contribution, I hope can help someone in troubles:
    pacman -Sy
    pacman -Rd xorg-server xorg-clients (if installed)
    pacman -Sf xorg-xdm
    pacman -S xorg-clients xorg-server
    pacman -Sf xorg
    pacman -Syu (upgrade all system, almost 200mb)
    pacman -S xorg-fonts-75dpi
    pacman -S xorg-fonts-100dpi
    pacman -S libxcomposite libxss
    Enter in /etc/X11/xorg.conf and reconfigure the paths so:
    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    FontPath "/usr/share/fonts/misc/"
    FontPath "/usr/share/fonts/TTF/"
    FontPath "/usr/share/fonts/Type1/"
    FontPath "/usr/share/fonts/CID/"
    FontPath "/usr/share/fonts/75dpi/"
    FontPath "/usr/share/fonts/100dpi/"
    FontPath "/usr/share/fonts/local/"
    ModulePath "/usr/lib/xorg/modules"
    EndSection
    Write startx, if it doesn't works kdm or gdm, write:
    mkdir -p /usr/X11R6/bin/
    ln -s /usr/bin/X /usr/X11R6/bin/X
    If doesn't works, control the errors, maybe it misses a file, install it with pacman.
    Moreover, I've a ricompiled kernel with drivers nvidia, so I'm entered on my kernel source and I've written:
    make all && make modules_install
    generate-modprobe.conf
    cp -f System.map /boot
    cd arch/i386/boot
    cp -f bzImage /boot
    At this point I've rebooted and I've reinstalled Nvidia drivers:
    ./NVidia.xxxxxx.run (WITHOUT OVERWRITE FILE /etc/X11/xorg.conf)

  • Install 2nd instance of Arch Linux without internet connection

    I have successfully install a first instance of Arch Linux using Arch Linux ISO + pacstrap + pacman with internet connection.
    I have updated to latest package database list (/var/lib/pacman/sync) and package cache files (/var/cache/pacman/pkg) in first instance of Arch Linux with "pacman -Swyu".
    Next, I would like to install 2nd instance of Arch Linux without using internet connection.
    I share the "/var/lib/pacman/sync" and "/var/cache/pacman/pkg" via NFS from first Arch Linux instance.
    I boot the 2nd instance with Arch Linux ISO and attempt to install without internet connection.  I mount the two NFS shares from 1st instance to "/var/cache/pacman/pkg" and "/mnt/var/lib/pacman/sync" respectively.  I execute
       # pacstrap -i -c /mnt"
    to start installation.
    I found it is almost impossible with current implementation of pacstrap script.  The pacstrap script always attempt to update package database list with -Sy option.
    I think some amendments on pacstrap script is needed to install Arch Linux without internet connection.

    I made the edit by adding the option -o to do what you want.
    I am too lazy for a feature request right now...
    #!/bin/bash
    # Assumptions:
    # 1) User has partitioned, formatted, and mounted partitions on /mnt
    # 2) Network is functional
    # 3) Arguments passed to the script are valid pacman targets
    # 4) A valid mirror appears in /etc/pacman.d/mirrorlist
    shopt -s extglob
    out() { printf "$1 $2\n" "${@:3}"; }
    error() { out "==> ERROR:" "$@"; } >&2
    msg() { out "==>" "$@"; }
    msg2() { out " ->" "$@";}
    die() { error "$@"; exit 1; }
    in_array() {
    local i
    for i in "${@:2}"; do
    [[ $1 = "$i" ]] && return
    done
    track_mount() {
    mount "$@" && CHROOT_ACTIVE_MOUNTS=("$2" "${CHROOT_ACTIVE_MOUNTS[@]}")
    api_fs_mount() {
    CHROOT_ACTIVE_MOUNTS=()
    { mountpoint -q "$1" || track_mount "$1" "$1" --bind; } &&
    track_mount proc "$1/proc" -t proc -o nosuid,noexec,nodev &&
    track_mount sys "$1/sys" -t sysfs -o nosuid,noexec,nodev &&
    track_mount udev "$1/dev" -t devtmpfs -o mode=0755,nosuid &&
    track_mount devpts "$1/dev/pts" -t devpts -o mode=0620,gid=5,nosuid,noexec &&
    track_mount shm "$1/dev/shm" -t tmpfs -o mode=1777,nosuid,nodev &&
    track_mount run "$1/run" -t tmpfs -o nosuid,nodev,mode=0755 &&
    track_mount tmp "$1/tmp" -t tmpfs -o mode=1777,strictatime,nodev,nosuid
    api_fs_umount() {
    umount "${CHROOT_ACTIVE_MOUNTS[@]}"
    valid_number_of_base() {
    local base=$1 len=${#2} i=
    for (( i = 0; i < len; i++ )); do
    (( (${2:i:1} & ~(base - 1)) == 0 )) || return
    done
    mangle() {
    local i= chr= out=
    unset {a..f} {A..F}
    for (( i = 0; i < ${#1}; i++ )); do
    chr=${1:i:1}
    case $chr in
    [[:space:]\\])
    printf -v chr '%03o' "'$chr"
    out+=\\
    # fallthrough
    out+=$chr
    esac
    done
    printf '%s' "$out"
    unmangle() {
    local i= chr= out= len=$(( ${#1} - 4 ))
    unset {a..f} {A..F}
    for (( i = 0; i < len; i++ )); do
    chr=${1:i:1}
    case $chr in
    if valid_number_of_base 8 "${1:i+1:3}" ||
    valid_number_of_base 16 "${1:i+1:3}"; then
    printf -v chr '%b' "${1:i:4}"
    (( i += 3 ))
    fi
    # fallthrough
    out+=$chr
    esac
    done
    printf '%s' "$out${1:i}"
    dm_name_for_devnode() {
    read dm_name <"/sys/class/block/${1#/dev/}/dm/name"
    if [[ $dm_name ]]; then
    printf '/dev/mapper/%s' "$dm_name"
    else
    # don't leave the caller hanging, just print the original name
    # along with the failure.
    print '%s' "$1"
    error 'Failed to resolve device mapper name for: %s' "$1"
    fi
    fstype_is_pseudofs() {
    # list taken from util-linux source: libmount/src/utils.c
    local -A pseudofs_types=([anon_inodefs]=1
    [autofs]=1
    [bdev]=1
    [binfmt_misc]=1
    [cgroup]=1
    [configfs]=1
    [cpuset]=1
    [debugfs]=1
    [devfs]=1
    [devpts]=1
    [devtmpfs]=1
    [dlmfs]=1
    [fuse.gvfs-fuse-daemon]=1
    [fusectl]=1
    [hugetlbfs]=1
    [mqueue]=1
    [nfsd]=1
    [none]=1
    [pipefs]=1
    [proc]=1
    [pstore]=1
    [ramfs]=1
    [rootfs]=1
    [rpc_pipefs]=1
    [securityfs]=1
    [sockfs]=1
    [spufs]=1
    [sysfs]=1
    [tmpfs]=1)
    (( pseudofs_types["$1"] ))
    newroot=/mnt
    hostcache=0
    copykeyring=1
    copymirrorlist=1
    offline=0
    usage() {
    cat <<EOF
    usage: ${0##*/} [options] root [packages...]
    Options:
    -C config Use an alternate config file for pacman
    -c Use the package cache on the host, rather than the target
    -d Allow installation to a non-mountpoint directory
    -G Avoid copying the host's pacman keyring to the target
    -i Avoid auto-confirmation of package selections
    -M Avoid copying the host's mirrorlist to the target
    -o Do not update the pacman cache for offline installation
    -h Print this help message
    pacstrap installs packages to the specified new root directory. If no packages
    are given, pacstrap defaults to the "base" group.
    EOF
    if [[ -z $1 || $1 = @(-h|--help) ]]; then
    usage
    exit $(( $# ? 0 : 1 ))
    fi
    (( EUID == 0 )) || die 'This script must be run with root privileges'
    while getopts ':C:cdGiMo' flag; do
    case $flag in
    C)
    pacman_config=$OPTARG
    d)
    directory=1
    c)
    hostcache=1
    i)
    interactive=1
    G)
    copykeyring=0
    M)
    copymirrorlist=0
    o)
    offline=1
    die '%s: option requires an argument -- '\''%s'\' "${0##*/}" "$OPTARG"
    die '%s: invalid option -- '\''%s'\' "${0##*/}" "$OPTARG"
    esac
    done
    shift $(( OPTIND - 1 ))
    (( $# )) || die "No root directory specified"
    newroot=$1; shift
    pacman_args=("${@:-base}")
    if (( ! hostcache )); then
    pacman_args+=(--cachedir="$newroot/var/cache/pacman/pkg")
    fi
    if (( ! interactive )); then
    pacman_args+=(--noconfirm)
    fi
    if (( ! offline )); then
    pacman_args+=(-y)
    fi
    if [[ $pacman_config ]]; then
    pacman_args+=(--config="$pacman_config")
    fi
    [[ -d $newroot ]] || die "%s is not a directory" "$newroot"
    if ! mountpoint -q "$newroot" && (( ! directory )); then
    die '%s is not a mountpoint!' "$newroot"
    fi
    # create obligatory directories
    msg 'Creating install root at %s' "$newroot"
    mkdir -m 0755 -p "$newroot"/var/{cache/pacman/pkg,lib/pacman,log} "$newroot"/{dev,run,etc}
    mkdir -m 1777 -p "$newroot"/tmp
    mkdir -m 0555 -p "$newroot"/{sys,proc}
    # always call umount on quit after this point
    trap 'api_fs_umount "$newroot" 2>/dev/null' EXIT
    # mount API filesystems
    api_fs_mount "$newroot" || die "failed to setup API filesystems in new root"
    msg 'Installing packages to %s' "$newroot"
    if ! pacman -r "$newroot" -S "${pacman_args[@]}"; then
    die 'Failed to install packages to new root'
    fi
    if (( copykeyring )); then
    # if there's a keyring on the host, copy it into the new root, unless it exists already
    if [[ -d /etc/pacman.d/gnupg && ! -d $newroot/etc/pacman.d/gnupg ]]; then
    cp -a /etc/pacman.d/gnupg "$newroot/etc/pacman.d/"
    fi
    fi
    if (( copymirrorlist )); then
    # install the host's mirrorlist onto the new root
    cp -a /etc/pacman.d/mirrorlist "$newroot/etc/pacman.d/"
    fi
    # vim: et ts=2 sw=2 ft=sh:

  • How to implement SSO to non-SAP systems using SAP logon ticket?

    Hello,
    We would like to implement Single Sign On between our SAP Netweaver system and a Siebel which is a non-SAP system using SAP logon tickets.
    Can anyone please give me some leads on this, in particular:
    1. Is there a JAVA API or an SAP plug-in that can be implemented on the Siebel machine to extract the SAP logon ticket?
    2. As the other machine might seat on a complete different domain, is it possible to implement SAP logon ticket without using cookies (perhaps through the HTTP header?
    3. In case you think using SAP logon tickets is not the best solution here I would be happy to hear any other suggestions you might have.
    Roy

    Hi,
    I'm currently using SAML as well. Unfortunately the SAP J2EE cannot work as authority (identity provider) but what you can do is using an open implementation of SAML such as opensso which is an open version of SUNs Java System access manager.
    There are a couple of other projects such as opensaml, apache's wss4j or shibboleth that might be interesting in this context.
    I just installed opensso and got it working with SAP J2EE 7.0 using SAPs JAAS SAMLLoginModule to authenticate users within SAP J2EE.
    In this scenario opensso serves as identity provider just as you need! There are a couple of Policy agents available on SUNs Download site you can use with Apache, Tomcat, JBOSS, WebSphere, Bea Web Logic etc. in order to authenticate! Otherwise you just directly authenticate against opensso. When installing opensso you can configure the type of user store you want  to use! By default it uses LDAP but you can also use different types of user store using JDBC or other mechanisms. Since you have a Directory Service you could easily connect it to your existing directory.
    There is also a way to map user ids directly in opensso by adding a uid mapping class. I created some documentation with lots of screenshots about using opensso with SAP J2EE. You can easily use opensso with any other system that supports SAML. In the case of SAP the usage is currently limited to SAML versions 1.0 and 1.1. Version 2.0 is not yet supported but should be in one of the following versions.
    Here are some links you might want to check:
    OpenSAML: https://spaces.internet2.edu/display/OpenSAML/Home
    wss4j: http://ws.apache.org/wss4j/
    shibboleth: http://shibboleth.internet2.edu/
    opensso: https://opensso.dev.java.net/
    On SDN you will find a documentation on how to connect SUN Java System Access Manager to SAP J2EE (see https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/906d9fc6-31b9-2910-1385-90edad7d7570). As I said opensso is based on the SUN Access Manager code and looks quite the same. So you can adapt this documentation in order to configure opensso or you can just ask me for the documentation.
    Hope this is helpful...
    Let me know if you need further assistance on this topic
    Cheers

  • Interface b/w SAP and NON SAP system

    Hi GEMS,
    Please give me some suggestion .My requirement is i have to transfer data from sap system to non sap system.
    There is no middleware between these systems.The data will be in the xml format.
    Please help me regarding these how can we link these systems and transfer data
    Best Regards,
    Phani

    Please let us us know the platform of the non-sap system such as JAVA/.Net. It's can be done using PI/XI.
    As per my experience, I've worked with only SAP JCO and .NET connectors. These connectors can be downloaded from service marketplace and needs to be installed on the non SAP platform. The Data transfer can be done through RFCs, which will be called from the non-sap systems.
    Also, the data needs to be in XML format. XML transformations can be created using transaction XSLT_TOOL to convert the ABAP data to XML and viceversa. The generated XML string can be passed to non SAP system through RFC from SAP.
    If the process is not synchronous, another option can be dumping the SAP data to FTP, which will be used by the non-sap system whenever required.

  • HOWTO: Create a Boot Configuration That Has No Driver Signature Checks. Disable Driver Integrity Checks and Install a Custom Non-Signed Driver

    Hello,
    Recently, I had a task where I needed to install a custom non-signed driver onto my Windows 8 64-bit setup. As it is known, Windows has driver enforcement policies that, as a security measure, do not allow you to install non-signed drivers.
    I did not want to alter my current boot configuration so I decided to create a separate boot entry that would have driver signing policies disabled. For some reason I did not find any good source that would contain a step-by-step instruction on completing
    this task, so I decided that I'd better share my experience here.
    Lastly, there are multiple ways how you could turn off driver enforcement policies, but I find the way to do this via boot manager.
    Here's how you can do that.
    1. Press WindowsKey and type 'cmd' (without quotes) to find Command prompt, then click Command prompt icon. If you have User Account Control turned on, hold Ctrl+Shift keys pressed when clicking the icon.
    This will force Windows to ask you for elevation of command prompt. Elevation is necessary for editing Boot Configuration Database (BCD), the database used by Windows boot manager to store boot settings.
    2. In the User Account Control window click Yes to confirm elevation of command shell.
    3. At the command prompt type
    bcdedit
    to list your BCD entries.
    This will give you an output like:
    Windows Boot Manager
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    integrityservices Enable
    default {current}
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    {a329b5cc-fb29-11e1-a74d-f2c962d62240}
    {a329b5ca-fb29-11e1-a74d-f2c962d62240}
    {a329b5c2-fb29-11e1-a74d-f2c962d62240}
    {current}
    {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    toolsdisplayorder {memdiag}
    timeout 30
    Windows Boot Loader
    identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8prowmc01.vhdx
    path \Windows\system32\winload.efi
    description Windows 8
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5d1-fb29-11e1-a74d-f2c962d62240}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8prowmc01.vhdx
    systemroot \Windows
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    The section that starts with Windows Boot Manager lists current settings for the boot menu. Here you find what boot entry is chosen by default, this is the one what you will boot into if you do not select any boot entry in the
    boot menu.
    The following record
    default {current}
    indicates that by default my Windows boots into configuration which I use at the moment (currently booted Windows configuration).
    To find out what exactly is current configuration, look into the list of boot entries, records that contain boot loader configuration and are titled as Windows Boot Loader in the bcdedit output.
    For example, the entry shown above is one of my boot configurations. This is one of the boot entries listed on the boot manager screen when I start my PC and it looks like:
    Windows Boot Loader
    identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8prowmc01.vhdx
    path \Windows\system32\winload.efi
    description Windows 8
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5d1-fb29-11e1-a74d-f2c962d62240}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8prowmc01.vhdx
    systemroot \Windows
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    This record has a unique GUID identifier that can be used to reference this boot entry, which is:
    identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    If we look at the Windows Boot Manager settings, we'll see this entry is the first in order to be displayed in the boot menu on OS start (I marked the unique bits):
    displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    {a329b5cc-fb29-11e1-a74d-f2c962d62240}
    It references my VHD drive, a virtual hard drive where my Windwos 8 setup is residing:
    device vhd=[D:]\win8prowmc01.vhdx
    And it also specifies that the boot manager must use UEFI BIOS extension code to access my Windows boot partition:
    path \EFI\Microsoft\Boot\bootmgfw.efi
    3. Now locate the current boot entry.
    Current boot entry contains boot settings used to boot into Windows configuration to which you are currently booted. It is referenced in the list of boot entries as a Windows Boot Loader record that has the {current} keyword inside and may
    look like:
    Windows Boot Loader
    identifier {current}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description Windows 8 Enterprise RTM
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    Because we are more than happy with current configuration and want to base our new boot configuration on these settings, we need to copy this boot entry ({current}) to a new boot entry.
    This is done by running the following command:
    C:\Windows\system32>bcdedit /copy {current} /d "No Driver Signature Check"
    Parameter /d here indicates that the following sequence of characters specifies the display name for the new boot entry that we are creating. The name inside the double quotes will be displayed in the boot menu when you boot your Windows.
    In other words, if you know restart your system, you'll see the new No Driver Signature Check in the boot menu.
    When copied, the entry is automatically given a new GUID identifier, so upon running the command above, you'll see the following line returned (you'll have an other GUID since these are unique identifiers):
    The entry was successfully copied to {a329b5d8-fb29-11e1-a74d-f2c962d62240}.
    4. Make sure the entry has been successfully created.
    Run the same bcdedit. (You may specify /enum or /v, or both /enum /v parameters at the prompt to get more detail about boot entries, but simple bcdedit is just enough to see the new entry):
    C:\Windows\system32>bcdedit
    Windows Boot Manager
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    integrityservices Enable
    default {current}
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    {a329b5cc-fb29-11e1-a74d-f2c962d62240}
    {a329b5ca-fb29-11e1-a74d-f2c962d62240}
    {a329b5c2-fb29-11e1-a74d-f2c962d62240}
    {current}
    {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    toolsdisplayorder {memdiag}
    timeout 30
    Windows Boot Loader
    identifier {current}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description Windows 8 Enterprise RTM
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    Windows Boot Loader
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description No Driver Signature Check
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    The entry has been created and given a unique a329b5d8-fb29-11e1-a74d-f2c962d62240 ID. It now has exactly same boot settings as the boot entry we used to boot into current configuration of Windows.
    5. Modify created  No Driver Signature Check entry and specify that Windows must have driver integrity checks disabled when booted using this boot entry.
    Any modifications to boot entries are made using /set parameter. To indicate that we modify a specific boot entry, we must specify the GUID for the No Driver Signature Check record, which is:
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    In other words, to edit (add or change) an option for the boot entry, we need to use the following command syntax:
    C:\Windows\system32>bcdedit /set GUID <boot_option> [<option_value>]
    First, we must specify that we don't want integrity checks be made. This is done by adding the loadoptions option and setting it to DISABLE_INTEGRITY_CHECKS value:
    C:\Windows\system32>bcdedit /set {a329b5d8-fb29-11e1-a74d-f2c962d62240} loadopti
    ons DISABLE_INTEGRITY_CHECKS
    The operation completed successfully.
    6. Verify that load option has been added.
    Run the bcdedit command:
    Windows Boot Loader
    identifier {current}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description Windows 8 Enterprise RTM
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    Windows Boot Loader
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description No Driver Signature Check
    locale en-US
    loadoptions DISABLE_INTEGRITY_CHECKS
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    7. Add the option that turns on test signing mode and disables checks of driver signature.
    Adding the testsigning option and setting it to ON does the trick for us:
    C:\Windows\system32>bcdedit /set {a329b5d8-fb29-11e1-a74d-f2c962d62240} TESTSIGNING ON
    8. Now we have a boot entry that enables Windows not to do integrity checks and digital signature validation.
    We check it by running bcdedit:
    Windows Boot Loader
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description No Driver Signature Check
    locale en-US
    loadoptions DISABLE_INTEGRITY_CHECKS
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    testsigning Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    9. Type 'exit' without quotes to exit from command prompt, and restart Windows.
    Upon booting you will be present with a new boot option to start Windows in configuration that allows you to install custom non-signed drivers.
    Hope this will help anybody to create their own custom boot configurations.
    Well this is the world we live in And these are the hands we're given...

    Hi,
    Thank you for sharing the solutions & experience here. It will be very beneficial for other community members who have similar questions. 
    Regards,
    Kelvin hsu
    TechNet Community Support

  • [SOLVED] Installing Windows XP after Arch Linux

    I'm not sure at all where to post this, so I've decided to do it here since I have the problem on a laptop... Please move if it should be somewhere else.
    I installed Arch Linux on my new laptop a month ago or so, and am very pleased to have found the very kind of distro I've been looking for. However, I'm having trouble with my graphics (either wine doesn't support it, or the drivers don't have 2D/3D acceleration), and now I want to install Windows XP next to Arch Linux.
    Using a GParted LiveCD, I've repartitioned the harddrive as such: Unpartitioned Space (27GB), Linux (197GB), SWAP (5GB).
    I've also removed the bootable flag from the Linux partition, just to be sure. However, when I try to install Windows XP, it gets stuck after unpacking a bunch of drivers, giving me a bluescreen that tells me to make sure the hardware isn't broken, check my harddrive with CHKDSK /F, or look for viruses. Ofcourse I know none of these are true, since I'm running Arch Linux just fine.
    A friend suggested that maybe my hardware isn't supported by Windows XP, which sounds like the most reasonable explanation so far, but I can't find a list of supported hardware. The M$ homepage basicly says
    "Pentium 233-megahertz (MHz) processor or faster (300 MHz is recommended)"
    for CPU, which doesn't help me at all.
    My hardware is:
    Processor: Intel Celeron 2.2 Ghz
    Memory: 2GB DDR2
    Graphics: Intel 4500MHD
    And the laptop is called an "eMachines E525", though that doesn't say much since there are very, very many called this.
    Can anyone give me any hints as to what I might be doing wrong?
    Last edited by Noxic (2010-05-29 18:44:32)

    Sounds like something I'll want to do. Where did you download the drivers? Do I have to follow some guide? Thanks for the tip
    EDIT:
    Indeed I will want to install AHCI drivers, otherwise Arch Linux fails to boot quite badly. There is also a problem preventing me from booting when I'm using AHCI though;
    At boot, Arch Linux checks /dev/sda1 (NTFS) for errors, and expects to check an ext2 filesystem. Obviously, however, /dev/sda1 is an NTFS filesystem.
    Since it tries to read the NTFS partition as an ext2 filesystem, it panics. Arch Linux then prompts me for the root password (or Ctrl+D to reboot), but I've disabled root login and can therefore do nothing at this point.
    I have a GParted livecd and the Arch Linux livecd, so editing files on any of the filesystem isn't a problem at all, but I don't know what to do at this point. Help?
    Last edited by Noxic (2010-05-29 12:40:33)

  • Is there any way to get the server app other that through the app store. We do not have our system conneted to a network. I typical downloaded items on a non-apple system.

    is there any way to get the server app other than through the app store. The system that I need it on are not connected to the internet.
    We run a closed-loop network of apple systems and I tipically downloaded updates on a non-apple system that was on the internet.
    Any ideas?

    I did buy the server app, went to the app store to download it. This system I'm using for downloads is Snow Leopard 10.6.8, it shows that I can download it but only as an Install which says I need 10.8. I can't seem to find a way for it to just download as a package or .dmg file so that I can copy it to DVD/CD or flash drive.

  • Client Copy between unicode system and non-unicode system

    Hello,
    we have to build up a new system for japan. It is planned to install a new 4.7Ext200 unicode system and then make a client copy from a non-unicode 4.7Ext200 (language= german, english) system to the unicode system. I don't think that this is possible way, but I can't find information regarding client copies from non-unicode to unicode. I would advice the project to convert the existing non-unicode system to unicode, make a system copy for the new system and then install japan languages. Any information, which can help me.
    Regards,
    Alexander

    Hi,
    without conversion client copy is not possible
    look at following
    Re: Client copy between unicode and Non-unicode
    regards,
    kaushal

Maybe you are looking for