Howto install Arch from iso (without buring CD) -unable to chroot ...

Hi.
I have successfully used the method to install from another linux partition in the past - as outlined here - http://wiki.archlinux.org/index.php/Ins … ting_Linux
- However I want to install the X86_64 version and my current machine doesn't have a pre-existing 64bit distro to chroot from....
I do not want to use floppy or cd to install - I always install from iso now, managed to get Fedora,Ubuntu, Gentoo and opensuse to install without burning the iso - Installing from iso is usually quicker and less prone to errors.........
I've tried the old method to boot from iso - here - http://wiki.archlinux.org/index.php/Fas … nux_System
However when I boot I get this
:: Scanning for boot cdrom device...
Failed to mount /dev/cd/cdrom-sr0
Failed to mount /dev/cd/cdrw-sr0
Failed to mount /dev/cd/dvd-sr0
ERROR: cannot find booted cdrom device, cannot continue...
Kernel panic - not syncing: Attempted to kill init!
Below is my grub menu.lst
title ArchCD
kernel (hd0,5)/boot/vmlinuz26 root=/dev/sda6 BOOTMEDIA=cd
initrd (hd0,5)/boot/archlive.img
Also tried (and various other combinations)
title ArchCD
kernel (hd0,5)/boot/vmlinuz26 root=/dev/sda6 BOOTMEDIA=cd lang=en locale=en_US.UTF-8 ramdisk_size=75%
initrd (hd0,5)/boot/archlive.img
Has anyone got any ideas ?
Cheers

You could try something like UNetbootin.

Similar Messages

Howto install Vista from servicepartition without formatting the HD

Hello, when my notebook was delivered I removed the original Vista-installation and installed openSuse. Now I need to use a Windows OS so I prepared my system by creating a fat32-partition in order to fire-up the Lenovo Service Button and simply install Vista right to that partition. Obviously this option doesnt exist - the only way to recover Vista is to completely format the harddrive. I dont want that - I'm gonna stick with Linux as my working OS and just wanna use the Vista OS for a single purpose. So? How can I reinstall the Vista OS I paid for in a place on my laptop I want it to be? Thanks for advice.

create a dual boot sytem and also remember "Vista" is "NTFS" sytem why not go the other way,, reload or re factory install 'Vista" then create a virtual machine and use easy partion in Disk Manager,, create "linux partition" as a dual boot and then create an icon on task bar and switch back and forth,, both "systems" will boot up and a quick 'click" you are vista, and quick click you are Linux I set up a triple boot this way but found it worked best with 'Vista 'as primary and linux, solaris etc secondary systems.. just keep an eye on your allocations or size Quotas on each partition, for the secondary systems,, and also "MAKE SURE IN CONTROL PANEL IN VISTA THAT "VIRTUAL MEMORY" AND PAGING FILE IS MANAGED BY SYTEM .........NOT A MANUAL SETTING.............. other wise your paging file will go out of control and use up all physical ram and hello blue screen..
check MS for a free multi boot configurer,, all the 'paid ' for sub software are nothing but problems in a disc

Install Arch from 2007.05 "base" iso or the "current" iso?

My old Arch install (0.7.2, upgraded in Nov. 06) may be broken, and I'm thinking of doing a fresh install of 2007.05. For the old install, I'd followed the recommended procedure of installing just the base system from the CD iso image, then installed the xorg and kde metapackages via pacman and then built the system from there.
At present, Arch offers a 2007.05-Duke.current iso of 550 MB that includes Xorg plus other things (but not KDE), on top of the base package. What exactly is the virtue of this bigger iso over the base package iso (150 MB). Why are the devs offering this bigger "current" iso, and is this the preferred way of installing Arch now?

You could also take it one step further, and use the ftp iso (a mere 27MB for i686, 35MB for x86_64) - that basically provides the installer only, and downloads everything else from the repos. Of course, as with slackhack's "base + upgrade" suggestion, a decent net connection is essential for an ftp install.

How to install Arch from hard drive?

Hello
I have an old laptop - Pentium II 266 MHz, 128Mb RAM and I want to install Arch on it.
The problem is that there is no way to boot from this laptop -> floppy is broken, CD drive is not bootable, no available boot options from BIOS to boot from PXE or USB.
So, I found this link useful (but not enough).
I have done everything as described on the upper link, but on the final step 7 I don't know how to proceed.
What I have got is:
Arch installation CD is in the CD drive.
After loading vmlinuz26 and archiso.img (which is RAM Disk or initrd) it shows this message: "waiting 30 seconds for device /dev/disk/by-label/"
And another message: "ERROR: boot device didn't show up after 30 seconds" and after that it put me in the ramfs prompt.
I try this in ramfs prompt, but without success:
1. ln -s /dev/sr0 /dev/archiso
2. exit (and try again)
What I want is to tell the installer that it must proceed with the installation files on my CD drive.
But how to do that?
If it is not possible, then how could I install Arch on this old laptop? Is there any other methods to try?
PS: There is Windows 2000 and Windows 98 installed on this laptop, but I want to install Arch on it. The whole hard drive is one partition.
Last edited by clovenhoof (2011-08-09 06:49:48)

Try either of the following:
* Add archisolabel=LABEL to the kernel line in menu.lst, where LABEL is the filesystem label of the partition where the ISO resides.
* Add archisodevice=/dev/sdaX to the kernel line in menu.lst, where sdaX should be replaced with the partition where the ISO resides.
[Edit]
Hmmm, sorry I think I was wrong. With the above, you need also extract the ISO, put the arch/ directory at the root of the partition.
Alternatively, you can put the ISO to the root of that partition, and add img_dev=/dev/sdaX and img_loop=foo-bar.iso. For details, see:
https://projects.archlinux.org/archiso.git/tree/README
BUT even if it loads, I don't think you will be able to install Arch on the same partition since it's mounted readonly to /bootmnt, (unless, you explicitly add copytoram to the kernel line, in which case, everything is copied to RAM, but since the machine has got only 128MB of RAM, this is not gonna happen). So, you need to put the ISO (or the extracted squashfs images) to a different partition than your target installation partition...
There probably are other things I'm missing... Gotta say this sounds quite challenging.
[Edit2]
Bah! Try archisodevice=/dev/sr0 then!
Last edited by lolilolicon (2011-08-09 07:48:17)

Not able to install arch from USB stick.

Hi all
First off I'm trying to install arch into my 8540w hp laptop. I have failed and here I'm seeking for help.
I have downloaded the latest arch iso image and put it into a usb stick for the installation
Here is how i prepared the usb.
tried :
sudo dd bs=4M if=archlinux-2013.06.01-dual.iso of=/dev/sdb
to write the iso in to the usb.
I have no success to boot up my 8540w machine (machine stalled on the HP logo)
I went through the wiki and found there some bugs which related to some old firmware (doesn't make any sense)
My laptop relatively new about 2 year old machine bios firmware upgraded a year ago. ( I have no problem to boot with my old Ibm T60)
To rectify the bugs Wiki guided me to:
1. sudo isohybrid.pl -offset 1 archlinux-2013.06.01-dual.iso
2. sudo dd if=archlinux-2013.06.01-dual.iso of=/dev/sdX
I have successfully boot up but the hope soon died
I'm getting these error messages:
mount: you must specify the filesystem type
ERROR;Failed to mount 'dev/disk/by-label/ARCH_201306"
here a snap shot of entire messages
Any help would be greatly appreciated.
thanks
Last edited by archlux (2013-06-12 21:52:10)

The filesystem needs to be labeled ARCH_201306. If you dd the iso to the USB, this stays in tact, but it would seem that if you use the method mentioned by the wiki above this filesystem label is not preserved...
Does this machine have UEFI? If so, then you can make a UEFI USB live media and have at it that way. There are instructions on the UEFI wiki page.
FWIW, new and updated firmware does not equate to bug free. I have a Thinkpad E430 that is less than a year old, and the original firmware was not without its bugs. If I have a certain USB stick in the USB 3.0 ports the machine won't get past POST. For a couple bios versions aes-ni was totally borked. There have been other minor issues as well.

Install windows from iso on older mac

Hi everybody
I have a mid 2010 MacBook Pro (15"), running Yosemite, and I want to install Windows on it using bootcamp.
Since my optical drive doesn't work properly, I hope for installing windows from an iso file.
The problem is the system's bootcamp assistant have not such option.
Is there a workaround for it?

You can modify the Bootcamp info.plist using Enable Bootcamp to install from usb for OSX 10.9**WORKS** , but for Macs with built-in Optical drives, BC Assistant sets the CSM-BIOS layer to boot from the Optical drive. There is no way for a user to change it. Some 2011/2012 Macs allow a USB/ISO combination, but older Macs will run into issues with Keyboard and Mouse drivers which may not work.

Unable to install Windows7 from ISO file

Hello,
i've read for hours about this but still i can't figure out how to make it work. I've an original ISO of Windows 7
and using the Bootcamp version of Mountain Lion. I follow the instruction but there is not way to let
bootcamp seeing the iso. I placed the iso in a usb drive, ran bootcamp, it download the windows support
but then is asking for the disc of windows... But i need to install it from usb. Any help? Should
i rename the iso or doing something else? thanks...

Alessandro Lorenzo wrote:
I know sometimes may sound stupid and lazy to ask something that as been asked million times but as there are just few steps to do, and every combination of it doesn't work, i wanted to try ask anyway. I think i've tried a few different ways to solve this and no one worked. Sorry, no offence.
None taken, but ths will be much easier if you replace the optical (you'll almost certainly have to remove a drive in order to install Windows however you do it.)

[HOWTO] Installing Arch Linux stable release on Acer Aspire One 522

[This is a work on progress and my first howto ever]
These steps will teach you how to install ArchLinux x64 stable release (currently 2010.05) on Acer Aspire One 522 from an existing ArchLinux (your desktop computer)
As you need a 2.6.37+ kernel to make networking work on the AO522, installing stable release as is won't work.
This Howto borns with the intention to address this problem.
You need to be familiarized with Linux internals to follow this howto.
(Expect this howto to become useless with new stable releases of ArchLinux.)
Remember to make a backup of your Windows 7 Starter system before installing ArchLinux.
I did a full raw copy of the harddisk by using systemrescuecd, an external harddisk and dd utility:
Just boot with systemrescuecd
Mount your external harddisk on /mnt/floppy for example
Clone harddisk with: dd if=/dev/sda |gzip -c > /mnt/floppy/ao522.img
This process took me a lot of time since my external harddisk is USB-1 (almost an entire evening)
Result image was about 22GB size
This image will restore partition table, boot sector and all data if things go wrong.
I followed some of the steps from this guide: https://wiki.archlinux.org/index.php/In … ting_Linux
If you have some Gentoo Linux experience you will find those steps really familiar.
You will need 2 USB pendrives or similar storage options.
One is needed to boot into your netbook, and the other to store our custom archlinux build.
Making an updated ArchLinux system
1) Make a local dir on your existing linux system
# mkdir ./newarch
2) Install pacman database on it
# pacman -Sy -r ./newarch
3) Install base system
# pacman -S base -r ./newarch
4) Let's chroot inside
# cp /etc/resolv.conf ./newarch/etc/
# cp /etc/pacman.d/mirrorlist ./newarch/etc/pacman.d
# mount -t proc proc ./newarch/proc
# mount -t sysfs sys ./newarch/sys
# mount -o bind /dev ./newarch/dev
# chroot ./newarch /bin/bash
5) Edit configuration files
# nano -w /etc/rc.conf
# nano -w /etc/hosts
# nano -w /etc/mkinitcpio.conf
Forget /etc/fstab for now since you don't know what partitions to use yet
6) Generate kernel image
# mkinitcpio -p kernel26
7) Generate locales
# nano -w /etc/locale.gen
# locale-gen
8) Make a tarball with our custom ArchLinux
# exit
# umount ./newarch/proc
# umount ./newarch/dev
# umount ./newarch/sys
# tar -cvpf newarch.tar ./newarch
9) Copy this tarball to an USB pendrive or external harddisk
10) Boot your netbook with a Linux bootable USB stick (I used systemrescuecd, and remember to pick the x64 bit kernel at grub screen)
You can use any linux distribution with usb bootable options. I suppose ArchLinux works too
To install SystemRescueCD on an USB stick follow this tutorial -> SystemRescueCD on usb stick
Insert the usb stick on your netbook, switch on, hit F2 to enter BIOS menu, and choose to boot from USB as first option. Save and Exit.
You should be booting into SystemRescueCD without any problem.
After initialization you will end in a root prompt.
11) Let's partition the disk
You will find 3 partitions if this is your first time:
/dev/sda1 2048 29362175 14680064 27 Hidden NTFS WinRE
/dev/sda2 * 29362176 29566975 102400 7 HPFS/NTFS/exFAT
/dev/sda3 29566976 488397167 229312696 7 HPFS/NTFS/exFAT
My recomendation is to leave sda1 and sda2 intact, as they have the recovery information to restore Windows 7 Starter
You have plenty of space with sda3, about 230G.
So run fdisk/cfdisk and delete /dev/sda3
Now create a 100M partition for boot
Now create a Extended partition with all the space left
Now create a 1GB logical partition for swap
Now create a 10-15 GB logical partition for root system
And finally a logical partition for our home partition with all space left
Your partition table should look like this:
/dev/sda1 2048 29362175 14680064 27 Hidden NTFS WinRE
/dev/sda2 * 29362176 29566975 102400 7 HPFS/NTFS/exFAT
/dev/sda3 29566976 29771775 102400 83 Linux
/dev/sda4 29771776 488397167 229312696 5 Extended
/dev/sda5 29773824 31821823 1024000 83 Linux
/dev/sda6 31823872 63281151 15728640 83 Linux
/dev/sda7 63283200 488397167 212556984 83 Linux
12) Create filesystems
I choosed ext2 for boot, and reiserfs for root and home partitions.
# mke2fs /dev/sda3
# mkreiserfs /dev/sda6
# mkreiserfs /dev/sda7
# mkswap /dev/sda5
13) Mount partitions
# mkdir arch
# mount /dev/sda6 arch
# mkdir arch/boot
# mount /dev/sda3 arch/boot
# mkdir arch/home
# mount /dev/sda7 arch/home
14) Copy our custom ArchLinux build on it
# mount /dev/sdb1 /mnt/floppy (for example)
# cd arch
# tar -xvpf /mnt/flopy/newarch.tar
15) Configure /etc/fstab
Mine is as follows:
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
/dev/sda3 /boot ext2 defaults 0 1
/dev/sda6 / reiserfs defaults 0 1
/dev/sda7 /home reiserfs defaults 0 1
/dev/sda5 swap swap defaults 0 0
16) Chroot in your new system
# mount -t proc proc ./proc
# mount -t sysfs sys ./sys
# mount -o bind /dev ./dev
# chroot ./ /bin/bash
17) Install grub
# grub-install
Edit /boot/grub/menu.lst to suit your needs
Mine looks like this:
timeout 5
default 0
color light-blue/black light-cyan/blue
title Arch Linux
root (hd0,2)
kernel /vmlinuz26 root=/dev/sda6 ro
initrd /kernel26.img
title Arch Linux Fallback
root (hd0,2)
kernel /vmlinuz26 root=/dev/sda6 ro
initrd /kernel26-fallback.img
title Windows 7 Recovery
rootnoverify (hd0,0)
makeactive
chainloader +1
As you see, you can restore Windows 7 Starter from Grub.
18) Change root password
# passwd
19) Add a regular user account
# useradd -G video,audio,users -m username
# passwd username
20) You're done!
# exit
# cd ..
# umount ./arch/proc
# umount ./arch/dev
# umount ./arch/sys
# umount ./arch/boot
# umount ./arch/
# reboot
Remove the usb stick from your netbook.
If all went ok, you will be inside your new stable and updated ArchLinux system
Next post is reserved for software configurations specific to the Acer Aspire One 522
Last edited by tigrezno (2011-04-20 12:22:38)

Using acpid to achieve the following:
- Change screen brightness when operating in battery mode
- Power off when the power button is pressed
- Suspend when the lid is down
- Reduce CPU frequency speed to maximize battery usage
Remember that system suspend is only supported by ati free driver xf86-video-ati
1) Install acpid daemon and cpufrequtils
# pacman -S apcid cpufrequtils
2) edit acpid handler script
# nano -w /etc/acpi/handler.sh
Change the following section:
ac_adapter)
case "$2" in
AC)
case "$4" in
00000000)
echo -n $minspeed >$setspeed
#/etc/laptop-mode/laptop-mode start
00000001)
echo -n $maxspeed >$setspeed
#/etc/laptop-mode/laptop-mode stop
esac
*) logger "ACPI action undefined: $2" ;;
esac
for:
ac_adapter)
case "$2" in
ACAD)
case "$4" in
00000000)
echo 3 > /sys/devices/virtual/backlight/acpi_video0/brightness
cpufreq-set -c 0 -f 800Mhz
cpufreq-set -c 1 -f 800Mhz
00000001)
echo 9 > /sys/devices/virtual/backlight/acpi_video0/brightness
cpufreq-set -c 0 -f 1000Mhz
cpufreq-set -c 1 -f 1000Mhz
esac
*) logger "ACPI action undefined: $2" ;;
esac
Make sure you changed AC) for ACAD)
Now change this other section:
button/power)
#echo "PowerButton pressed!">/dev/tty5
case "$2" in
PWRF) logger "PowerButton pressed: $2" ;;
*) logger "ACPI action undefined: $2" ;;
esac
with:
button/power)
#echo "PowerButton pressed!">/dev/tty5
case "$2" in
PWRF) poweroff ;;
*) logger "ACPI action undefined: $2" ;;
esac
Change:
button/lid)
#echo "LID switched!">/dev/tty5
logger "ACPI group/action undefined: $1 / $2"
for:
button/lid)
pm-suspend && /etc/rc.d/network restart
logger "ACPI group/action undefined: $1 / $2"
Network restart is used because wlan0 will disconnect from AP after some time. You can try using iwconfig wlan0 essid <ap> key <key> instead of the network script, but haven't tested it myself.
3) Start acpid and load modules
# modprobe powernow-k8
# /etc/rc.d/acpid start
Add "acpid" to DAEMONS in /etc/rc.conf to start on boot
Add "powernow-k8" to the modules sections on /etc/rc.conf to load at boot
Stopping system freezes due to ethernet driver
The only way people have found to avoid freezes is by blacklisting atheros kernel drivers.
To do it at boot just edit /etc/rc.conf and change the MODULES line as this:
MODULES=(!ath9k !atl1c)
Reboot and you're done, but remember to not press the Wifi key, because it can freeze your system.
Correctly starting wireless at boot
I've found that standard scripts wont load properly my wireless lan. It gave an error telling you to use the WIRELESS_TIMEOUT variable and such.
To solve this, edit /etc/rc.d/network script and change the wi_up function by adding a second iwconfig command like this:
wi_up()
eval iwcfg="\$wlan_${1}"
[[ ! $iwcfg ]] && return 0
/usr/sbin/iwconfig $iwcfg
[[ $WIRELESS_TIMEOUT ]] || WIRELESS_TIMEOUT=2
sleep $WIRELESS_TIMEOUT
/usr/sbin/iwconfig $iwcfg
bssid=$(iwgetid $1 -ra)
It will do the trick and will start at boot correctly. This is not a solution but a fix.
Adjust Touchpad to disable false taps
What I did here is defining an area to be ignored. This area are 3 rectangles on top, left and right of the touchpad.
This means you can write and press space without having the cursor click out of the window and such.
# synclient AreaLeftEdge=150
# synclient AreaRightEdge=1300
# synclient AreaTopEdge=300
Also, add it to your /etc/X11/xorg.conf.d/10-evdev.conf:
Section "InputClass"
Identifier "evdev touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "AreaTopEdge" "300"
Option "AreaLeftEdge" "150"
Option "AreaRightEdge" "1300"
EndSection
You can play with those values. They just work for me.
Last edited by tigrezno (2011-04-23 13:49:48)

HOWTO: Install Arch for Newbies

Hello,
Yesterday was my fist installation of Arch and i've found that the informations are not very well combined for a newbie/new to arch, am not newbie to linux but am new to arch so i've spend quite time to figure out some things or to know some links, due to this fact i've decided to write an easy guide that combine the whole installation from Downloading Till getting an up & running Arch with Gnome
the HOWTO can be found here please i need your opinions/corrections so we can make it as easy as installing ubuntu for newbies

Try my gdm.conf, it's an unchanged one, and normally it would work
# GDM Configuration file. You can use gdmsetup program to graphically
# edit this, or you can optionally just edit this file by hand. Note that
# gdmsetup does not tweak every option here, just the ones most users
# would care about. Rest is for special setups and distro specific
# tweaks. If you edit this file, you should send the HUP or USR1 signal to
# the daemon so that it restarts: (Assuming you have not changed PidFile)
# kill -USR1 `cat /var/run/gdm.pid`
# (HUP will make gdm restart immediately while USR1 will make gdm not kill
# existing sessions and will only restart gdm after all users log out)
# You can also use the gdm-restart and gdm-safe-restart scripts which just
# do the above for you.
# For full reference documentation see the gnome help browser under
# GNOME|System category. You can also find the docs in HTML form on
# http://www.gnome.org/projects/gdm/
# NOTE: Some of these are commented out but still show their default values.
# If you wish to change them you must remove the '#' from the beginning of
# the line. The commented out lines are lines where the default might
# change in the future, so set them one way or another if you feel
# strongly about it.
# Have fun! - George
[daemon]
# Automatic login, if true the first local screen will automatically logged
# in as user as set with AutomaticLogin key.
AutomaticLoginEnable=false
AutomaticLogin=
# Timed login, useful for kiosks. Log in a certain user after a certain
# amount of time
TimedLoginEnable=false
TimedLogin=
TimedLoginDelay=30
# The gdm configuration program that is run from the login screen, you should
# probably leave this alone
#Configurator=/opt/gnome/sbin/gdmsetup --disable-sound --disable-crash-dialog
# The chooser program. Must output the chosen host on stdout, probably you
# should leave this alone
#Chooser=/opt/gnome/libexec/gdmchooser
# The greeter for local (non-xdmcp) logins. Change gdmlogin to gdmgreeter to
# get the new graphical greeter.
#Greeter=/opt/gnome/libexec/gdmlogin
# The greeter for xdmcp logins, usually you want a less graphically intensive
# greeter here so it's better to leave this with gdmlogin
#RemoteGreeter=/opt/gnome/libexec/gdmlogin
# Launch the greeter with an additional list of colon seperated gtk
# modules. This is useful for enabling additional feature support
# e.g. gnome accessibility framework. Only "trusted" modules should
# be allowed to minimise security holes
#AddGtkModules=false
# By default these are the accessibility modules
#GtkModulesList=gail:atk-bridge:/opt/gnome/lib/gtk-2.0/modules/libdwellmouselistener:/opt/gnome/lib/gtk-2.0/modules/libkeymouselistener
# Default path to set. The profile scripts will likely override this
DefaultPath=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/opt/gnome/bin
# Default path for root. The profile scripts will likely override this
RootPath=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/opt/gnome/sbin:/opt/gnome/bin
# If you are having trouble with using a single server for a long time and
# want gdm to kill/restart the server, turn this on
#AlwaysRestartServer=false
# User and group used for running gdm GUI applicaitons. By default this
# is set to user gdm and group gdm. This user/group should have very
# limited permissions and access to ony the gdm directories and files.
User=nobody
Group=gdm
# To try to kill all clients started at greeter time or in the Init script.
# doesn't always work, only if those clients have a window of their own
#KillInitClients=true
LogDir=/var/log/gdm
# You should probably never change this value unless you have a weird setup
PidFile=/var/run/gdm.pid
# Note that a post login script is run before a PreSession script.
# It is run after the login is successful and before any setup is
# run on behalf of the user
PostLoginScriptDir=/opt/gnome/etc/gdm/PostLogin/
PreSessionScriptDir=/opt/gnome/etc/gdm/PreSession/
PostSessionScriptDir=/opt/gnome/etc/gdm/PostSession/
DisplayInitDir=/opt/gnome/etc/gdm/Init
# Distributions: If you have some script that runs an X server in say
# VGA mode, allowing a login, could you please send it to me?
#FailsafeXServer=
# if X keeps crashing on us we run this script. The default one does a bunch
# of cool stuff to figure out what to tell the user and such and can
# run an X configuration program.
XKeepsCrashing=/opt/gnome/etc/gdm/XKeepsCrashing
# Reboot, Halt and suspend commands, you can add different commands
# separated by a semicolon and gdm will use the first one it can find
RebootCommand=/sbin/shutdown -r now "Rebooted from gdm menu."
HaltCommand=/sbin/shutdown -h now "Halted from gdm menu."
SuspendCommand=/usr/bin/apm --suspend
# Probably should not touch the below this is the standard setup
ServAuthDir=/opt/gnome/var/gdm
# This is our standard startup script. A bit different from a normal
# X session, but it shares a lot of stuff with that. See the provided
# default for more information.
BaseXsession=/opt/gnome/etc/gdm/Xsession
# This is a directory where .desktop files describing the sessions live
# It is really a PATH style variable since 2.4.4.2 to allow actual
# interoperability with KDM. Note that <sysconfdir>/dm/Sessions is there
# for backwards compatibility reasons with 2.4.4.x
SessionDesktopDir=/etc/X11/sessions/:/etc/dm/Sessions/:/usr/share/xsessions/:/opt/gnome/share/gdm/BuiltInSessions/:/opt/gnome/share/xsessions/
# This is the default .desktop session. One of the ones in SessionDesktopDir
#DefaultSession=gnome.desktop
# Better leave this blank and HOME will be used. You can use syntax ~/ below
# to indicate home directory of the user. You can also set this to something
# like /tmp if you don't want the authorizations to be in home directories.
# This is useful if you have NFS mounted home directories. Note that if this
# is the home directory the UserAuthFBDir will still be used in case the home
# directory is NFS, see security/NeverPlaceCookiesOnNFS to override this behaviour.
UserAuthDir=
# Fallback if home directory not writable
UserAuthFBDir=/tmp
UserAuthFile=.Xauthority
# The X server to use if we can't figure out what else to run.
StandardXServer=/usr/X11R6/bin/X
# The maximum number of flexible X servers to run.
#FlexibleXServers=5
# And after how many minutes should we reap the flexible server if there is
# no activity and no one logged on. Set to 0 to turn off the reaping.
# Does not affect Xnest flexiservers.
#FlexiReapDelayMinutes=5
# the X nest command
Xnest=/usr/X11R6/bin/Xnest -audit 0 -name Xnest
# Automatic VT allocation. Right now only works on Linux. This way
# we force X to use specific vts. turn VTAllocation to false if this
# is causing problems.
FirstVT=7
VTAllocation=true
# Should double login be treated with a warning (and possibility to change
# vts on linux and freebsd systems for console logins)
#DoubleLoginWarning=true
# Should a second login always resume the current session and
# switch vts on linux and freebsd systems for console logins
#AlwaysLoginCurrentSession=true
# If true then the last login information is printed to the user before
# being prompted for password. While this gives away some info on what
# users are on a system, it on the other hand should give the user an
# idea of when they logged in and if it doesn't seem kosher to them,
# they can just abort the login and contact the sysadmin (avoids running
# malicious startup scripts)
#DisplayLastLogin=false
# Program used to play sounds. Should not require any 'daemon' or anything
# like that as it will be run when no one is logged in yet.
#SoundProgram=/usr/bin/play
# These are the languages that the console cannot handle because of font
# issues. Here we mean the text console, not X. This is only used
# when there are errors to report and we cannot start X.
# This is the default:
#ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh
# This determines whether gdm will honor requests DYNAMIC requests from
# the gdmdynamic command.
#DynamicXServers=false
# This determines whether gdm will send notifications to the console
#ConsoleNotify=true
[security]
# If any distributions ship with this one off, they should be shot
# this is only local, so it's only for say kiosk use, when you
# want to minimize possibility of breakin
AllowRoot=false
# If you want to be paranoid, turn this one off
AllowRemoteRoot=false
# This will allow remote timed login
AllowRemoteAutoLogin=false
# 0 is the most restrictive, 1 allows group write permissions, 2 allows all
# write permissions
RelaxPermissions=0
# Check if directories are owned by logon user. Set to false, if you have, for
# example, home directories owned by some other user.
CheckDirOwner=true
# Number of seconds to wait after a bad login
#RetryDelay=1
# Maximum size of a file we wish to read. This makes it hard for a user to DoS
# us by using a large file.
#UserMaxFile=65536
# If true this will basically append -nolisten tcp to every X command line,
# a good default to have (why is this a "negative" setting? because if
# it is false, you could still not allow it by setting command line of
# any particular server). It's probably better to ship with this on
# since most users will not need this and it's more of a security risk
# then anything else.
# Note: Anytime we find a -query or -indirect on the command line we do
# not add a "-nolisten tcp", as then the query just wouldn't work, so
# this setting only affects truly local sessions.
DisallowTCP=true
# By default never place cookies if we "detect" NFS. We detect NFS
# by detecting "root-squashing". It seems bad practice to place
# cookies on things that go over the network by default and thus we
# don't do it by default. Sometimes you can however use safe remote
# filesystems where this is OK and you may want to have the cookie in your
# home directory.
#NeverPlaceCookiesOnNFS=true
# XDMCP is the protocol that allows remote login. If you want to log into
# gdm remotely (I'd never turn this on on open network, use ssh for such
# remote usage that). You can then run X with -query <thishost> to log in,
# or -indirect <thishost> to run a chooser. Look for the 'Terminal' server
# type at the bottom of this config file.
[xdmcp]
# Distributions: Ship with this off. It is never a safe thing to leave
# out on the net. Setting up /etc/hosts.allow and /etc/hosts.deny to only
# allow local access is another alternative but not the safest.
# Firewalling port 177 is the safest if you wish to have xdmcp on.
# Read the manual for more notes on the security of XDMCP.
Enable=false
# Honour indirect queries, we run a chooser for these, and then redirect
# the user to the chosen host. Otherwise we just log the user in locally.
#HonorIndirect=true
# Maximum pending requests
#MaxPending=4
#MaxPendingIndirect=4
# Maximum open XDMCP sessions at any point in time
#MaxSessions=16
# Maximum wait times
#MaxWait=15
#MaxWaitIndirect=15
# How many times can a person log in from a single host. Usually better to
# keep low to fend off DoS attacks by running many logins from a single
# host. This is now set at 2 since if the server crashes then gdm doesn't
# know for some time and wouldn't allow another session.
#DisplaysPerHost=2
# The number of seconds after which a non-responsive session is logged off.
# Better keep this low.
#PingIntervalSeconds=15
# The port. 177 is the standard port so better keep it that way
#Port=177
# Willing script, none is shipped and by default we'll send
# hostname system id. But if you supply something here, the
# output of this script will be sent as status of this host so that
# the chooser can display it. You could for example send load,
# or mail details for some user, or some such.
Willing=/opt/gnome/etc/gdm/Xwilling
[gui]
# The specific gtkrc file we use. It should be the full path to the gtkrc
# that we need. Unless you need a specific gtkrc that doesn't correspond to
# a specific theme, then just use the GtkTheme key
#GtkRC=/opt/gnome/share/themes/Default/gtk-2.0/gtkrc
# The GTK+ theme to use for the gui
#GtkTheme=Default
# If to allow changing the GTK+ (widget) theme from the greeter. Currently
# this only affects the standard greeter as the graphical greeter does
# not yet have this ability
#AllowGtkThemeChange=true
# Comma separated list of themes to allow. These must be the names of the
# themes installed in the standard locations for gtk themes. You can
# also specify 'all' to allow all installed themes. These should be just
# the basenames of the themes such as 'Thinice' or 'LowContrast'.
#GtkThemesToAllow=all
# Maximum size of an icon, larger icons are scaled down
#MaxIconWidth=128
#MaxIconHeight=128
[greeter]
# Greeter has a nice title bar that the user can move
#TitleBar=true
# Configuration is available from the system menu of the greeter
#ConfigAvailable=true
# Face browser is enabled. This only works currently for the
# standard greeter as it is not yet enabled in the graphical greeter.
Browser=false
# The default picture in the browser
#DefaultFace=/opt/gnome/share/pixmaps/nobody.png
# User ID's less than the MinimalUID value will not be included in the
# face browser or in the gdmselection list for Automatic/Timed login.
# They will not be displayed regardless of the settings for
# Include and Exclude.
MinimalUID=1000
# Users listed in Include will be included in the face browser and in
# the gdmsetup selection list for Automatic/Timed login. Users
# should be separated by commas.
#Include=
# Users listed in Exclude are excluded from the face browser and from
# the gdmsetup selection list for Automatic/Timed login. Excluded
# users will still be able to log in, but will have to type their
# username. Users should be separated by commas.
Exclude=bin,daemon,mail,nobody
# By default, an empty include list means display no users. By setting
# IncludeAll to true, the password file will be scanned and all users
# will be displayed except users excluded via the Exclude setting and
# user ID's less than MinimalUID. Scanning the password file can be
# slow on systems with large numbers of users and this feature should
# not be used in such environments. The setting of IncludeAll does
# nothing if Include is set to a non-empty value.
#IncludeAll=false
# If user or user.png exists in this dir it will be used as his picture
#GlobalFaceDir=/opt/gnome/share/pixmaps/faces/
# File which contains the locale we show to the user. Likely you want to use
# the one shipped with gdm and edit it. It is not a standard locale.alias file,
# although gdm will be able to read a standard locale.alias file as well.
#LocaleFile=/opt/gnome/etc/gdm/locale.alias
# Logo shown in the standard greeter
#Logo=/opt/gnome/share/pixmaps/gdm-foot-logo.png
# The standard greeter should shake if a user entered the wrong username or
# password. Kind of cool looking
#Quiver=true
# The Actions menu (formerly system menu) is shown in the greeter, this is the
# menu that contains reboot, shutdown, suspend, config and chooser. None of
# these is available if this is off. They can be turned off individually
# however
SystemMenu=true
# Should the chooser button be shown. If this is shown, GDM can drop into
# chooser mode which will run the xdmcp chooser locally and allow the user
# to connect to some remote host. Local XDMCP does not need to be enabled
# however
#ChooserButton=true
# Welcome is for all console logins and RemoteWelcome is for remote logins
# (through XDMCP).
# DefaultWelcome and DefaultRemoteWelcome set the string for Welcome
# to "Welcome" and for DefaultWelcome to "Welcome to %n", and properly
# translate the message to the appropriate language. Note that %n gets
# translated to the hostname of the machine. These default values can
# be overridden by setting DefaultWelcome and/or DefaultRemoteWelcome to
# false, and setting the Welcome and DefaultWelcome values as desired.
# Just make sure the strings are in utf-8 Note to distributors, if you
# wish to have a different Welcome string and wish to have this
# translated you can have entries such as "Welcome[cs]=Vitejte na %n".
DefaultWelcome=true
DefaultRemoteWelcome=true
#Welcome=Welcome
#RemoteWelcome=Welcome to %n
# Don't allow user to move the standard greeter window. Only makes sense
# if TitleBar is on
#LockPosition=false
# Set a position rather then just centering the window. If you enter
# negative values for the position it is taken as an offset from the
# right or bottom edge.
#SetPosition=false
#PositionX=0
#PositionY=0
# Xinerama screen we use to display the greeter on. Not for true
# multihead, currently only works for Xinerama.
#XineramaScreen=0
# Background settings for the standard greeter:
# Type can be 0=None, 1=Image, 2=Color
#BackgroundType=2
#BackgroundImage=
#BackgroundScaleToFit=true
#BackgroundColor=#76848F
# XDMCP session should only get a color, this is the sanest setting since
# you don't want to take up too much bandwidth
#BackgroundRemoteOnlyColor=true
# Program to run to draw the background in the standard greeter. Perhaps
# something like an xscreensaver hack or some such.
#BackgroundProgram=
# if this is true then the background program is run always, otherwise
# it is only run when the BackgroundType is 0 (None)
#RunBackgroundProgramAlways=false
# Show the Failsafe sessions. These are much MUCH nicer (focus for xterm for
# example) and more failsafe then those supplied by scripts so distros should
# use this rather then just running an xterm from a script.
#ShowGnomeFailsafeSession=true
#ShowXtermFailsafeSession=true
# Normally there is a session type called 'Last' that is shown which refers to
# the last session the user used. If off, we will be in 'switchdesk' mode where
# the session saving stuff is disabled in GDM
#ShowLastSession=true
# Always use 24 hour clock no matter what the locale.
#Use24Clock=false
# Use circles in the password field. Looks kind of cool actually,
# but only works with certain fonts.
#UseCirclesInEntry=false
# Do not show any visible feedback in the password field. This is standard
# for instance in console, xdm and ssh.
#UseInvisibleInEntry=false
# These two keys are for the new greeter. Circles is the standard
# shipped theme. If you want gdm to select a random theme from a list
# then provide a list that is delimited by /: to the GraphicalThemes key and
# set GraphicalThemeRand to true. Otherwise use GraphicalTheme and specify
# just one theme.
#GraphicalTheme=circles
#GraphicalThemes=circles/:happygnome
GraphicalThemeDir=/opt/gnome/share/gdm/themes/
GraphicalThemeRand=false
# If InfoMsgFile points to a file, the greeter will display the contents of the
# file in a modal dialog box before the user is allowed to log in.
#InfoMsgFile=
# If InfoMsgFile is present then InfoMsgFont can be used to specify the font
# to be used when displaying the contents of the file.
#InfoMsgFont=Sans 24
# If SoundOnLogin is true, then the greeter will beep when login is ready
# for user input. If SoundOnLogin is a file and the greeter finds the
# 'play' executable (see daemon/SoundProgram) it will play that file
# instead of just beeping
#SoundOnLogin=true
#SoundOnLoginFile=
# If SoundOnLoginSuccess, then the greeter will play a sound (as above)
# when a user successfully logs in
#SoundOnLoginSuccess=false
#SoundOnLoginSuccessFile=
# If SoundOnLoginFailure, then the greeter will play a sound (as above)
# when a user fails to log in
#SoundOnLoginFailure=false
#SoundOnLoginFailureFile=
# The chooser is what's displayed when a user wants an indirect XDMCP
# session, or selects Run XDMCP chooser from the system menu
[chooser]
# Default image for hosts
#DefaultHostImg=/opt/gnome/share/pixmaps/nohost.png
# Directory with host images, they are named by the hosts: host or host.png
HostImageDir=/opt/gnome/share/hosts/
# Time we scan for hosts (well only the time we tell the user we are
# scanning actually, we continue to listen even after this has
# expired)
#ScanTime=4
# A comma separated lists of hosts to automatically add (if they answer to
# a query of course). You can use this to reach hosts that broadcast cannot
# reach.
Hosts=
# Broadcast a query to get all hosts on the current network that answer
Broadcast=true
# Set it to true if you want to send a multicast query to hosts.
Multicast=false
# It is an IPv6 multicast address.It is hardcoded here and will be replaced when
# officially registered xdmcp multicast address of TBD will be available
#Multicast_Addr=ff02::1
# Allow adding random hosts to the list by typing in their names
#AllowAdd=true
[debug]
# This will enable debugging into the syslog, usually not neccessary
# and it creates a LOT of spew of random stuff to the syslog. However it
# can be useful in determining when something is going very wrong.
Enable=false
[servers]
# These are the standard servers. You can add as many you want here
# and they will always be started. Each line must start with a unique
# number and that will be the display number of that server. Usually just
# the 0 server is used.
0=Standard
#1=Standard
# Note the VTAllocation and FirstVT keys on linux and freebsd.
# Don't add any vt<number> arguments if VTAllocation is on, and set FirstVT to
# be the first vt available that your gettys don't grab (gettys are usually
# dumb and grab even a vt that has already been taken). Using 7 will work
# pretty much for all linux distributions. VTAllocation is not currently
# implemented on anything but linux and freebsd. Feel free to send patches.
# X servers will just not get any extra arguments then.
# If you want to run an X terminal you could add an X server such as this
#0=Terminal -query serverhostname
# or for a chooser (optionally serverhostname could be localhost)
#0=Terminal -indirect serverhostname
# If you wish to run the XDMCP chooser on the local display use the following
# line
#0=Chooser
## Note:
# is your X server not listening to TCP requests? Perhaps you should look
# at the security/DisallowTCP setting!
# Definition of the standard X server.
[server-Standard]
name=Standard server
command=/usr/X11R6/bin/X -audit 0
flexible=true
# To use this server type you should add -query host or -indirect host
# to the command line
[server-Terminal]
name=Terminal server
# Add -terminate to make things behave more nicely
command=/usr/X11R6/bin/X -audit 0 -terminate
# Make this not appear in the flexible servers (we need extra params
# anyway, and terminate would be bad for xdmcp choosing). You can
# make a terminal server flexible, but not with an indirect query.
# If you need flexible indirect query server, then you must get rid
# of the -terminate and the only way to kill the flexible server will
# then be by Ctrl-Alt-Backspace
flexible=false
# Not local, we do not handle the logins for this X server
handled=false
# To use this server type you should add -query host or -indirect host
# to the command line
[server-Chooser]
name=Chooser server
command=/usr/X11R6/bin/X -audit 0
# Make this not appear in the flexible servers for now, but if you
# wish to allow a chooser server then make this true. This is the
# only way to make a flexible chooser server that behaves nicely.
flexible=false
# Run the chooser instead of the greeter. When the user chooses a
# machine they will get this same server but run with
# "-terminate -query hostname"
chooser=true

Boot from floppy and install arch from flash stick - NO CDR - USB 1.1

MY PREVIOUS POST BELOW BECAME A HARD DRIVE INSTALL POST WHICH HAS HELPED THOUGH ISN'T ON SUBJECT CURRENTLY AND I STILL NEED SOLUTION - Now at day 3 :-) - sorry!
I have old laptop with a very broken CDR... so just a floppy and a hard drive and 2 USB 1.1 ports.
[Need commands and which floppy is best]
The USB install WIKI
http://wiki.archlinux.org/index.php/Ins … _USB_stick
says to write the .img file to flash stick...
--- that I can do!
Though trying a similar process:
I've had no luck with a hard drive install (also on wiki) as I believe that once I write the .img file to the hard drive it WILL boot though can't create mount points as the drive's in use!
Anyways...
IF I have the flash stick with the .img file on it as per the wiki instructions
what commands would I use and what boot floppy would work for:
- booting from floppy
- mounting? the flash stick with arch core on it
- then installing from there to single hard drive partition.
thing is I'm just barely ok with using
dd fdisk and mke2fs
So: I need to know what command to mount USB stick... then HOW do I get arch installer on the img file to boot up??
Any guru tips really needed ....thank you!
Last edited by yvonney (2009-01-28 08:44:59)

nice Kirurgs
doesn't boot from usb... and CDR very broken... good though as I've learned a lot....
dell inspiron 2500 1 ghz pentium III
method 1) used puppy after booting off wakepup2 floppy ....very handy that wakepup flopppy though be advised there's several versions of wakpup2 and try the second boot option on the aug or sept 2008 version it WILL find your USB device even if like me I had an old 128 meg one. also, Crash, a guy at the puppy forums has a 3 floppy set that's specific to whatever puppy version you're running... try that as a last resort
UN-NECESSARY BLATHER COMMENT: The way those puppys are created weird me out., the more I looked around, Yes, I've read a wee bit about Aufs, and what goes into the whole persistent thing.... seems like lotsa almost impossible to ever 'really' know stuff is going on it there.... Consider the source of that comment of course... I have huge blank spots in my knowledge and skill and am actually only a relentless year one linux'r... [not counting 6 years of hum and haw] though I'd wanna build my own live arch usb with tips from here before I ever tried to REALLY figure out what goes into creating puppy. I'm saying that at one or two points I thought.. hmnmm... perhaps puppy on this old laptop.... though concluded that ARCH for ALL things is really the only option. puppy's a great boot and hunt around thing though (for me, and in my current opinion).
method 2) eldamar and eldamar's guide which started me towards success .. which I basically now just do the dd command to an empty partition after booting from puppy .... THEN thrown in a supergrub floppy .... have it 'bring alive' the partition I've just dd'd the arch .img to.... and reboot.... oh, and from puppy I can create partitions as well.. gparted I think.
method 3) untested also can use plop floppy it's a boot loader... you may be able to get slitaz distro to create one for you through the 'bootfloppybox' terminal command... not sure if it uses the old floppy linux version of PloP or the win version or what.... dunnno dunno!!! gotta go! :--)
crazy busy so writing to say... pretty much all fine! :--)
for me this move was 3-4 days of lots of WONDERFUL bad luck... with everything from puppy hell, my partial-dumbness and back..
thing is.... I'm real good at it now.... hehehehe
gotta love problems!
Last edited by yvonney (2009-02-03 17:27:56)

Installing Arch on PC without Internet Connection/Slow Connection

Arch Linux requires a fairly good internet connection to set up. How can one install it on machines which don't have any internet connectivity? Is there any way to make a DVD of Arch on a computer connected to internet and having Arch setup(DE,Media Players,Codecs etc) which can then be used on machines without internet connections This would come useful for me to install at my friends place. Does anyone even has a remote solution on this?

https://wiki.archlinux.org/index.php/Of … f_Packages
https://wiki.archlinux.org/index.php/Lo … ory_HOW-TO
and, of course:
https://wiki.archlinux.org/index.php/Beginners%27_Guide
You could also install on a computer with a connection, then use something like Clonezilla to deploy it.

Boot arch from iso and grub2

Hello,
I'm trying configure grub2 for boot iso image of arch but don't work:
My grub.cfg entry is:
menuentry "ArchLinux ISO" {
loopback loop (hd0,3)/iso/arch.iso
linux (loop)/boot/vmlinuz26 findiso=/iso/arch.iso lang=en locale=en_US.UTF-8 archisolabel=ARCHISO_KE1AECIE ramdisk_size=75%
initrd (loop)/boot/archiso_pata.img
boot
Arch start correctly boot fail and hope 30 seconds for image of /dev/archiso, I think.
Is the above entry correct?.
Regards.

I wouldn't really call it a bug. It is more like an enhancement that Arch Linux does not currently have, AFAIK.
example:
menuentry "Arch Linux 2009.08 netinstall 64bit" {
loopback loop /boot/iso/archlinux-2009.08-netinstall-x86_64.iso
linux (loop)/boot/vmlinuz26 lang=en locale=en_US.UTF-8 archisolabel=ARCHISO_OHD8FOH5 ramdisk_size=75%
initrd (loop)/boot/archiso_pata.img
What happens with the grub2 is as follows:
loopback loop /boot/iso/archlinux-2009.08-netinstall-x86_64.iso
1) mount the iso image as a loopback
linux (loop)/boot/vmlinuz26 lang=en locale=en_US.UTF-8 archisolabel=ARCHISO_OHD8FOH5 ramdisk_size=75%
2) load the kernel from the iso image (and pass command line options)
initrd (loop)/boot/archiso_pata.img
3) load the initd from the iso image
The problem comes after this.
Once the kernel and the initd are loaded grub2 leaves the picture, as well as the loopback iso image.
The loaded kernel starts the boot process and looks for the files/filesystem it expects to be there.
But it can't find it because the iso loopback device is gone (or as far as it knows, never was there to begin with).
To get around this problem many distros include kernel command line options such as:
iso-scan/filename, findiso, and isofrom
These command line options are pretty much scripts to find and mount the iso image and use it as the root partition. Much like what we did with grub2.
I don't know if the command line options are part of the initd or the kernel itself, but either way I would like to see it as part of Arch Linux default iso.
If I knew how to modify the initd I would make a patch for it or the iso as a whole, but my knowledge doesn't go that far

Installing mathematica from .iso

My College was nice enough to round me a up a linux version of mathematica (i.e. one of the math profs uses Ubuntu and it was covered under their distribution agreement) I have an .iso extracted from a zip file but when I try to run the installer nothing happens, I assume I'm missing some dependency. Anyone else have any luck with it?
If not I can always run the window's version under wine or the mac version on my macbook pro so no worries, it'd just be nice to have it on my more powerful machine.

Where are you running the installer from? I would try to run it from the command-line as it should give you some output. Also, if you are running the installer off the ISO, make sure it's not mounted with the noexec option as this will not allow you to run anything directly off it.

Installing App from Appstore without Password?

Last night, my nine year-old "nephew" (the son of a close friend) asked to install a game from the App Store. His mother wasn't keen on letting him play it, so I refused to key in the password. He said he would just "hack" it instead -- my mistake. I watched as he went to Settings -> General -> Network -> VPN ... and then I got lost. He typed in some numeric sequence, went back to the Appstore, and then proceeded to download the app. I asked him how he did it, but he clammed up. I told him no more iPad until I figure it out. It has been bugging me all night.
Today, I talked with his mother, who uses an iPhone 4, and reminded her that they share an OS. She talked with him about it, and he finally admitted that he had used the same hack on her phone. Eventually, he decided he "wanted to talk" (yes, I know -- this sounds so, well, weird) and gave her a number, either 370519 or 397051, which somehow he enters into the VPN area. I'm still in the dark how it works exactly, but I'm wondering if this is a known route around the Appstore password restrictions. Has anyone seen such a hack?

Just change your Apple ID password.
https://iforgot.apple.com/cgi-bin/WebObjects/DSiForgot.woa/wa
IMHO... never allow anyone to use your computer that has access to information to alter system data, nor an iOS device such as an IPad or iPhone.
Might be a good idea to change the admin password on your Mac also.
http://support.apple.com/kb/ht1274
If the future, if necessary, you can report unauthorized purchases.
http://www.apple.com/support/itunes/

Want to purchase new mac mini but I do not know how I would install programs from dvd without internal optical drive

I am planning to purchase new mac mini that just came out today but I do not know how I will be able to install programs or save stuff to disk when there is now internal optical drive. I know I could purchase an external drive but is that necesary. Thanks.

If you have access to another Mac with an DVD drive you should be able to share it using Apple's drive sharing feature in the OS or at the very least if you have a firewire cable boot into firewire disk mode...

Howto install Arch from iso (without buring CD) -unable to chroot ...

Similar Messages

Maybe you are looking for