I was thinking of buying Debian with the five DVDs of software from their co. Is this possible with Mint or Ubuntu or Fedora...? Does Debian have good security from data theft...? Password protection and encryption, I never needed it before now so much.
Can Debian dual boot with XP? Is WINE effective in Debian? I heard Debian has a lot of software, compared with say Slackware which it's users love however saying the software is upgraded better. Any comments? And Mint has all Debian and Ubuntu software available, sadly for me, I found it had a fault built in in Mint 9. I use a Pentium 4 dual core with 3Gb RAM and a NVIDIA graphics card built in with 512 Mb RAM of it's own.
I have just installed Ubuntu (/dev/sda7) and Debian (/dev/sda4), but since I have updated all informations on Ubuntu, then Debian did not appear anymore on the grub list. There is an wiki I have found, but I an not really sure about what to do.
Here are the boot informations: Boot Info Script 0.55 dated February 15th, 2010
Boot Info Summary:
=> Grub 2 is installed in the MBR of /dev/sda and looks at sector 488861020 of the same hard drive for core.img, core.img is at this location on /dev/sda and looks on partition #3 for (,gpt3)/grub.
[Code]...
ps: on this file, it says that the /boot is installed on the MBR and /dev/sda3. I will remove the boot from MBR as I am now using /dev/sda3 instead. Sorry for my english
This is the third time I try unsuccessfully to install Debian as a second OS on a hard drive. When it gets to the end of the installation process the installer asks whether I want to go ahead with the Grub Boot Loader, I choose yes. The end result is however that I can't boot that partition within the hard drive -- i.e., Debian. Can someone tell me what is going on? Should I not use the Grub Boot Loader when I have more than one operating system on a machine? Should I not install Grub on the Master Boot Record (MBR)?
Before the installation, I had triple boot of WinXP, Win 7, Ubuntu 10.10. As you can guess, the main boot-loader was grub. The second is Win 7 boot loader, and there it gives the option what to choose, load XP or Win 7.I made a decision to remove Ubuntu and install Debian(you know better than me why I did). So first, I searched a guide how to un-dual-boot. It told me to delete the two partition that Ubuntu use(swap and ext4) and write to MBR the win 7 boot-loader(using EasyBCD), so I delete them and use EeasyBCD. At this stage, I had 2 partitions: NTFS for XP and NTFS for Win 7, and the Win 7 boot-loader(and XP) worked pretty well.I install the latest testing of Debian(6 RC2) from DVD1 using this guide, except I choose to use the graphical installer, ext4(not ext3 as there), install the desktop environment, and choose to install grub(even know it didn't asked me). The swap partition I set is 3 GB because my RAM is 2 GB, even know that ubuntu set it in the past to 2 GB.The installation went pretty well, just when come to grub package, it says that there was an error with installing grub package(it didn't told me what), I had no choice, so I choose to skip over grub/lilo and finish with no boot manager. I was thinking to myself: "So I couldn't install grub, at least I have the Win 7 boot-loader(which contain XP loader), and maybe Win 7 boot-loader will recognize Debian too.". But I end up with no boot at all.It told me than when choose not to install boot-manager that I need to load /vmlinuz and give it the parameter root=/dev/sda4(my deb partition).I think that if I could install grub, I could load all my boots("sudo grub update" right?).How can I fix it?
Is it possible to install Windows XP on a machine that already has Debian 7.8? I find lots of articles on installing Debian after but not before XP.
I would like to get a prompt at startup to select Windows XP or Debian 7.8 and then choose which one I want. The reason I want to do that is because I have Guitar Pro on XP and cant find anything as good and also I want to watch Netflix and cant seem to be able to find a way to do that on Debian 7.8 except windows emulator which defeats the point of Debian anyway. Also my Epson V500 will not work on Debian 7.1 and I have tried everything, been to Epson, installed drivers etc..
I have Lenny installed & it works fine, in a few days will add Windows 7 (want to dual boot - 1 250 GB hard disk) used gparted to free up lots of room for Win 7
- My question is this, Debian then Win or Win then Debian (I want GRUB to manage both so hope since Lenny is installed Win 7 will use the free space no problem) ?
I was asked to research if it is possible to install a Debian distribution of Linux to HP Z420 Workstations as second OS (dual boot) in our lab. The lab is normally used for Computer Aided Design (Windows 7). The plan is to have parallel computing possible with these workstations on Linux side.
The link for HP Z420 Specs suggests amd64 distrubition should be supported. Tell me If I'm wrong as I have always been interested in software side of things.
Looking for info regarding installation of Debian to HP Z420 workstations as well as using these computers for parallel computing with Debian.
One of the things holding me back from building a new system with nothing but Linux is the vague possibility that that I might need to use some proprietary program that only works on Wind'ohs in the future. So far it has been easy to keep dual boot systems around, but a new system will be > 4 Gb of RAM of course, so I can't just install one of my copies of Win XP on it. But buying a new 64-bit version of Wind'ohs for ~$200 seems a waste.Is it now possible to run XP in a "virtual" machine under Debian? More importantly, is it possible to install XP completely from within the virtual machine so it never sees the > 4 Gb or RAM and freaks out? What sort of hardware is required to do something like this? I presume a CPU with certain special capabilities is essential, but wouldn't those special instructions (whatever they are) be pretty standard now? Would the virtual XP install need its own partition?
I have Debian installed but I need to dual boot with distribution based on Ubuntu 14.04. This is my first UEFI dual boot install attempt. And I must do it right. I must not lose my Debian !
Ubuntu will go to /dev/sdb5 but I don`t no for sure what to do when installing Ubuntu. How to select during install existing UEFI partition(/dev/sdb1) so Debian and Ubuntu can use it. Can I select existing UEFI partition like I would do for /home or /swap ? Will this work ?
And what will happen with Grub if I select install grub ? I want to manage grub from Debian, it is my main OS. Can I skip Grub install and just update grub on my debian after ubuntu install ? Or I just install grub, then after completed Ubuntu install I install it again from Debian. Will this work ?
Is procedure of installing dual boot trivial like before or UEFI hide`s some unpleasant surprise.
I'll start off with stating my problem and summarize how I got to it.
I installed Windows 10 on an SSD. I installed Debian 8.2 after it. The SSD was/is a GPT disk. I installed both installations from a UEFI booted device (DVD for Windows, and USB drive with Live CD for Debian).
I tested it after each installation making sure I could boot via UEFI into Windows, then Debian, then Windows, to make sure nothing broke.
I rebooted the machine. Suddenly, no more UEFI. Nothing. I didn't change any BIOS/UEFI setup menu settings. Not even my USB drive with Live CD will boot through UEFI anymore. Even when nothing else is plugged into the system.
My situation is actually a bit more complicated than that, but I think that will suffice for now. I can still boot into the Live CD on the USB drive, just in Legacy mode only. I mounted the EFI partition on /mnt/boot after I mounted the file system for Debian on /mnt. It is identical, as far as I can tell, to as it was before when it was working.
My motherboard has CSM and Secure Boot, both have been set up how they need to be to boot UEFI into Debian. Tinkering with them further after things broke did not fix it. I tried all variations of options/settings.
The GRUB Reinstall guide says to be in EFI mode before starting it, so I can't do that.
My motherboard is an ASUS X99 Deluxe, and I've heard ASUS has special "features" (read: bugs) that come with their boards. Searching hasn't brought up any other people with this issue. I believe the firmware is updated to it's most current one.
I've tried dd-ing my backup of my old system, from before trying to migrate to a Dual Boot system, to the SSD (after backing up the dual boot setup with dd -> <name>.img via the Live CD USB). However, that won't boot either as it is a UEFI install as well.
The layout of my EFI partition is as such: /boot/EFI/Boot/bootx64.efi /boot/EFI/Microsoft/<Microsoft-naming>.efi /boot/EFI/debian/grubx64.efi
I've heard that the standards on how that's supposed to be set up isn't a standard. However, since it worked booting into the OS' the first time, I don't see how that could be the issue (a bad hierarchy layout leading to the UEFI not being able to see the OS installs).
I've seen that I can boot to an EFI shell (called Shell.efi, apparently) via an option in my UEFI BIOS setup menu on my motherboard. Is that an option here to somehow bypass this strange issue?
All I can think to try is burn it all and start over. But not knowing what caused it means I could just make it happen again. Plus, I can't boot into UEFI install media, so I can't install UEFI boot OS'. :/
Initially had windows xp in my system. Picked up on free partition (*it was not a primary partition*) and installed Debian from CD. The installation went fine. Towards end of installation the grub install ran detected windows xp presence and I continued with the install. End of install, prompted that the system would reboot.
However on reboot, I wasnt presented when boot option ( windows xp vs debian) but my windows xp directly got booted. How to get this boot option.
I've recently bought a new computer and installed Windows 7 on it, but left 100GB of space on a separate partition so I could put Debian next to it in dual boot. I have the new Intel i7 950 processor and I run Windows 7 Proffesional 64 bit, so I assumed I had to pick the ia64 debian image. However the CD I burned from the ia64 image didn't boot. (a black screen started and an underscore kept flashing, but nothing else happened)[URL]
I've managed to install i386 Debian on a older intel pentium 4 computer before and that worked fine. I believe I used another application to burn the CD then. This time I've burned the CD with the default Windows CD burn application. I can try burn more CD's but I don't have much left so I want to make sure this is the problem before attempting again. (the burned files on the ia64 CD look exactly the same as the files on the i386 CD, when browsing through the cd files in windows) "If your PC has a 64-bit AMD or Intel processor, you will most likely need the "amd64" images (though "i386" is also fine), the "ia64" images will not work."This seems a bit strange, they recommend me to use the amd64 image if you have a "64-bit AMD or intel processor". I dunno if this is a typo, but it seems weird to me that the AMD-64 Debian version would also work on my Intel machine
Im currently not an linux expert so I turn to this forum after several attempts to fix my issue with grub.
I had a dualboot single HD with both win7 and win8.1 when I decided to install debian wheezy from usb.
I deleted the win7 partition and installed debian there. The partition scheme is separate /home
After reboot I automatically get into the "Grub rescue mode" and now I´m stuck.
I tried the commands:
set prefix=(hd0,msdosX)/boot/grub/ Insmod normal
I have msdos1, msdos3, msdos5 and msdos6 but nothing is listing anything from the grub rescue mode.
I get the "UNKNOWN FILE SYSTEM" error and cant get past that.
I also tried booting into rescue mode from usb iso install but nothing happens when choosing to repair GRUB.
The listed devices in rescue mode are:
/dev/sda1 /dev/sda2 /dev/sda3 /dev/sda5 /dev/sda6 debian uses sdb 1-2 and sdb1 is the only option to Reinstall GRUB on but it gives me "Unable to install GRUB in /dev/sdb1 This is a fatal error" message /dev/sdb1 /dev/sdb2
I have set up authentication when I am logging from my laptop using windows 7 (putty) into Debian server (see this post [URL].....) but since my laptop is dual boot (Windows 7 and Ubuntu) how would I set up authentication when i am using Ubuntu since from Ubuntu I will be logging into Debian SSH as same user that I am when logging from windows?
Have a little experience with backtrack 4, which is a Ubuntu distro. I'm changing to Lenny due to hardware limitations on my laptop, an older Dell inspiron 7000.
Here's the specs : 400 MHZ, 120 G HDD parted as C: = 20G (has bad sectors, left blank) and D: = 20G Windows part 128 Mb low density RAM ATI Rage Mobility ( not sure of video RAM, I think 8 Mb)
Now I liked running BT and liked the linux work, so when the BT install went south I started to look for another linux distro I can run, the BT tools I use are linux after all. Here's where I hit my stump. I decided to go with the Lenny distro, it already has some of the tools I need, but the first time I installed I had the HDD like this 20G, 20G, 20G,20G, 17.??G. I had windows installed on C: (of course, no problems, yet)
After I installed lenny to D: via an iso I downloaded, the Debian GNU/Linux 5.0.6 "Lenny" - Official i386 xfce+lxde-CD Binary-1, BTW first install was from booting from the disk. After reparting, format, etc. of the install, GRUB boot loader detects my D: Windows, great. Reboot to GRUB boot menu, select ddebian, and it loads...cool, until I realize I don't have synaptic, the tools, and apt isn't going to work unless I can load the linux driver from the cdrom...which I can't find.
Reboot...windows, internet for answers I'm thinkin. GRUB loads fine, select windows and get the following error message "Windows can't start because of hardware configuration problems. Could not read from selected boot disk, check boot path and hardware. Check configuration manual for disk configuration."
It took three days to get Windows reinstalled, and a LL format (zerowrite the drive) but during the process I discovered a possible hdw issue...bad sectors on the C: hdd. Solution: C: 20G = unused, D: = Windows xp. Worked great. No more windows issues, so try it again. This time I used the disks installer from windows. Everything started great, boot menuselected debian, install-graphic, but this time I let the part manager create a drive, 20G from the free space an it appropriately made it's swapfile...when lenny booted it was good, but still no synaptic, cd/rom, couldn't browse the computer.
Reboot to windows to get instructions from someone that really knows what's going on...no windows. exactly same message as before. I was able to boot into debian okay, but couldn't find any drives, utilities, wasn't very much, but I needed my windows and the internet to get lessons. I am familiar with the terminal console and KDE. Can use apt for updating, but prefer using the synaptic. Why does my windows keep disappearing? If I can solve the dual boot issue I can learn the system casually. Right now my config is: C: = 20G, nothing here, still haven't run a scandisk either...next on todo list. D: = 20G Windows install...what I'm using now. I'm not going to attempt to reinstall debian until I receive a efinate answer to the dissappearing config, or boot capacity. Oh, yeah, Did try a fdisk/mbr and fix. this didn't bring it back either.
This is a recollection of my experience using Microsoft Surface Pro 3. I am running Debian Jessie RC1, using the latest linux kernel (as of now, 3.19).
Assume that everything works, except:
- grub2 does not allow to select menu entries without TypeCover/USB Keyboard (Ubuntu had a popup software keyboard in the live CD) - there is no "right button click" on the touchscreen. Most interfaces use a long press as a right click. - the touchscreen is sometimes unresponsive, especially when plugging/unplugging the TypeCover; - cameras don't work (although there is a fix) - wireless card works 80% of the time only (but the newest marvell firmware from github solves the problem) - secure boot does not work (need to disable that from the boot menu) - touchpad gestures don't work (e.g. two fingers scrolling - this is particularly puzzling, as Ubuntu 14.10 live had the touchpad working (including two fingers scrolling) but not the TypeCover) - touchpad and touchscreen scrolling do not work in certain applications (e.g. in Iceweasel one needs to install an add-on) - pen works (even when the touchscreen is unresponsive), but only one of three buttons work (with xournal)
I had to boot into my Windows 7 install on my laptop for the first time in a few months and I noticed that the Windows clock was 4 hours ahead. Windows sync'd its time with the internet, then I booted back into Debian (Lenny) and my clock was now 4 hours behind. Both OS's are set to the same time zone (EDT). The minutes were correct in both systems. Could the fact that EDT is UTC-0400 be relevant?
I recently installed Debian 7 on a dual boot with Windows Vista. Thus, when I boot the computer, I am prompted by a GRUB screen to select Windows Vista loader, Debian, and Debian (recovery mode). I would like to upgrade Windows Vista to Windows 7. Will this cause an issue with GRUB? Will a Windows 7 loader be added to the list or will a Windows 7 loader replace the Windows Vista loader? Will there have to be a setting change within Debian? Within Windows?
My Toshiba Satellite C870-198 has Debian 7.7 installed in UEFI mode alongside Windows 8.1. The GRUB menu no longer displays, but the machine boots straight into Windows.
I can boot into Debian or Windows from rEFInd installed on a USB stick. The rEFInd menu has the following entries:
The Debian entry actually launches the GRUB menu which was installed with Debian.
Code: Select allBoot Microsoft EFI boot (Boot Repair backup) from Basic data partition. Boot supposed Microsoft EFI boot (probably GRUB) from Basic data partition. Boot EFIubuntugrubx64.efi from Basic data partition. Boot EFIdebiangrubx64.efi from Basic data partition. Boot bootootx64.efi from Basic data partition. Boot vmlinuz-3.2.0-4-amd64 from boot.
In an attempt to fix GRUB I executed the commands in the 'Reinstalling grub-efi on your hard drive' section of: [URL] ....
Code: Select allmount /dev/sda1 /boot/efi ... surprisingly returned: Code: Select all$LogFile version 2.0 is not supported. (This driver supports version 1.1 only.) $LogFile version 2.0 is not supported. (This driver supports version 1.1 only.) Did not find any restart pages in $LogFile and it was not empty. The file system wasn't safely closed on Windows. Fixing. Code: Select all[ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
... returned "EFI boot on HDD".
[Code] ....
... Where is Debian?
FULL HISTORY .... =============================
The laptop came with Windows 8 preinstalled. I switched off Secure Boot and installed Ubuntu for UEFI dual boot. I recall having to use Boot Repair to get the GRUB boot manager working properly for both systems.
Recently I decided to replace Ubuntu with Debian 7.7 and first cloned the entire hard drive to a USB drive (The Clone Drive). This drive successfully boots into Ubuntu in UEFI mode.
Following this I took the opportunity to update Windows to 8.1, which broke GRUB as expected, so that the machine would only boot straight into Windows.
I installed Debian from a live USB stick in the mistaken belief that it would be bootable in UEFI mode. It did boot OK in legacy mode.
I then burned the full Debian 'DVD' image to a USB stick, booted it in UEFI mode and reinstalled Debian. In UEFI mode GRUB allowed me to boot into both Debian and Windows.
At this point I tested The Clone Drive. It was still able to boot into Ubuntu as previously, but after powering down, unplugging The Clone Drive and rebooting, the GRUB menu failed to appear and the machine booted straight into Windows. This is its current state.
I'm inexperienced in Debian. I have a dual-boot machine (64-bit, Debian 7.3, Windows 7, legacy boot) and encouter a problem at boot ever since I completed the installation of Debian 7.3 alongside the exising Windows 7. This machine has six hard drives: two are intended for ntfs storage of general data (raided together by RAID1); two more are intended for ext4 storage of general data (also raided together by RAID1); the fifth contains the Windows OS files and the sixth contains the Debian OS files. The problem is that I arrive to the grub_rescue each time at boot, seeing the message:
GRUB loading. Welcome to GRUB!
error: no such device: e081517b-3399-4067-9294-8f0686f753ca. Entering rescue mode... grub_rescue>
I have a Dell laptop (inspiron 1150) which was dual booting Windows XP and Ubuntu 9.04. I have successfully installed Debian Jessie Standard over the Ubuntu. I pre-partitioned using gparted-live to make a separate single partition for the Debian install. Guided partitioning was then carried out by the installer producing separate /, /home, and swap partitions. After installation, the grub menu shows an entry for Debian and Windows XP. I can boot Debian, but not Windows XP. The symptoms are the same as reported in other forums: A terminal is displayed, vanishes and the system reboots defaulting to the Debian boot.
The grub.cfg file for the Jessie system has an other-os entry:
Code: Select allmenuentry "Microsoft Windows XP Home Edition (on /dev/sda2)" {   set root=(hostdisk//dev/sda, msdos2)   search --no-floppy --fs-uuid --set=root cc0ce0ab0ce091ae   drivemap -s (hd0) ${root}   chainloader +1 }
The original Windows entry for the Ubuntu install was:
Code: Select allmenuentry "Microsoft Windows XP Home Edition (on /dev/sda2)" {   insmod ntfs   set root=(hd0,2)   search --no-floppy --fs-uuid --set cc0ce0ab0ce091ae   drivemap -s (hd0) ${root}   chainloader +1 }
The partitions produced by partman look OK (during the pre-partitioning I did not touch sda1, sda2, or sda3):
Code: Select all~ # os-prober /dev/sda2:Microsoft Windows XP Home Edition:Windows:chain
So it seems that everything is in place, but there are perhaps important differences in the grub.cfg files. Are the two "set root" commands equivalent for example?
I have Windows 10 and Deb 8 dual boot, and I need to re-install Windows but want to avoid (or at least plan for) losing Grub/Linux boot.
Last time I re-installed Windows after Linux I ended up having to re-install Linux again afterwards as well, because I couldn't recover it (seemingly due to complications from encryption). So this time I'm wanting to plan and avoid that.
CURRENT DISK PARTITIONS:
Code: Select allsda1Â |Â 550MÂ Â |Â EFI System sda2Â |Â 128MÂ Â |Â Microsoft reserved sda3Â |Â 175.8G |Â Microsoft basic data sda4Â |Â 286MÂ Â |Â Linux filesystem (Boot) sda5Â |Â 28.2GÂ |Â Linux filesystem (Root) sda6Â |Â 91.3GÂ |Â Linux filesystem (Home) sda7Â |Â 1.9GÂ Â |Â Linux swap
[Code] ....
As there is a "Microsoft Reserved" partition and a separate Microsoft directory within the EFI partition, if I just go ahead and reinstall Windows will it install it's boot loader/image to one of it's own partitions? And NOT affect anything else like Grub and other Linux things?
Logic tells me yes, but there seems to be many issues on the internet about installing Windows after Linux.
My primary concern is whatever happens with Windows or anything to do with dual loading etc, is that Linux will still just boot, or I can get it working again without much hassle.
Why is there a reserved Microsoft partition AND a Microsoft directory in the EFI partition? Which one boots Windows?
Why is there a separate Linux Boot partition AND a Linux directory in the EFI partition? Which one boots Linux? Where is Grub invoked from, is one redundant, etc?
How these work. It is possible I've set them up wrong, or with redundant partitions, but both systems have been booting ok for months.
I've been using Debian for a few years but always on dedicated boxes and/or VMs.
Finally decided to dual boot Debian and Windows on my main Desktop PC.
Installed as I normally would using, however this time using a seperate drive (one for the existing Windows 10 install and the other for Debian), Debian install detects that windows has an EFI partition and sticks an entry in there, which is fair enough, and everything working fine. Then I spent some time configuring all my software and set it all up just the way I like it. I've rebooted Debian a few times to check it's working correctly and it is.
The issue arrives when I reboot and load into Windows 10. It boots fine.
However after a further reboot GRUB no longer loads... and the machine just boots directly into Windows 10.
After doing some further digging into my EFI partition (and reinstalling various times) it would appear that after a reboot Windows 10 deletes the entry GRUB creates in my EFI partition after EVERY reboot.
Done some googling and most people advise turning off 'fast boot' in Windows as it locks certain partitions to facilitate the machine going into hibernation, only to find that it's always been turned off on my machine (I recall due to a driver issue with my graphics card this had to be turned off when I installed Windows 10).
I've found this article on the Ubuntu forums : [URL] .... however I've tried their steps and windows is still doing a hostile takeover of my EFI partion after a reboot!
Any way to stop Windows 10 from interfering with my EFI files after a reboot? (without doing the obvious thing and kill Windows off).
I have used dual boot systems using various versions of windows and Debian for many years and have encountered no problems. However, I have a problem with installing Debian on a EeePC (ASUS PC1201) which uses Winows 7. I can not even get started because I can not understand the information that I have on my hard drive partitions. Windows 7 says that I have the following :
Local Disk(C:) 78.1 GB free of 99.9GB Local Disk(D:) 49.8 GB free of 83.8.GB NewVolume(G:) 948 KB of 0.99 GB Local Disk(F:) 37.9 GB free of 38..0 GB (Originally the ASUS only had two partitions C: and D: I used Gparted to genetate F: and G:) gparted-live-0.7.1.5 says that I have the following :- /dev/sda1 ntfs 992.5 KB /devf/sda2 ntfs 100.00 GB with 66.09GB unused /dev/sda3 ntfs 132.88GB with 129.88 GB unused unallocated 1.00 GB
Debian Squeeze (the net install version) will not install. G was the result of trying to provide some swap space. How do I prepare the hard drive so that Squeeze it will install on F: ?
how to install Debian after Windows is already installed. Could someone give me a brief guide to begin the process of installing Windows? When I installed Debian I already made a partition for windows (in the same hard disk), I hope I did it right.
I am new to Linux and Debian. I have Compaq Presario R3000 laptop, which is 5 years old now. I have RealTek RTL8139 family PCI Fast Ethernet NIC. Currently I have a broadband connection at home. I have dual boot Windows XP Professional and Debian (which I installed a week ago through CD). I have done some preliminary tests for the network and I am posting the screenshots for the tests (e.g. lspci, ifconfig, etc.). I also did two more commands. For 'cat /etc/network/ifstate' the output was 'No such file or directory'. Same output was for the command 'cat /etc/network/options'.
I've a Lenovo G50-80T with W8.1. I want to install Debian 8.1 in dualbooting mode. I've done this other times without problems. But this time I want encrypt the Linux partition (not the Windows partition). I'll use dm-crypt to do that. I want to know if this way is secure for protect the data on Linux partition or if I need encrypt the entire drive.
I'm currently dual-booting Squeeze & Windows XP on a machine i use frequently.
In my experience on the desktop, i now see no reason to have Windows XP as a boot option, & wanted to try & avoid a full re-installation of Debian in order to remove XP (merging it's partition with / ).
I have a checklist that i put together, but wanted to be sure this was all correct before going forward.
1. Perform full back-up of all data.
2. Boot into Debian, through GUI -
System Tools > Disk Utility
- Select HDD (80GB Hard Disk) - Select windows partition ( /dev/sda1 ) - Format /dev/sda1 to Ext4 Filsystem
3. Boot Live CD
- Use gParted to extend /dev/sda2 (was 38GB, will extend to 78GB)
4. Remove XP from the boot menu.
( Note: My ~ folder is on the same physical drive as / (same volume), but i actually store all Media on a separate physical drive which is formatted in NTFS. I plan on reinstalling XP using a virtual hard disk, & sharing that with the virtual machine.Here is a screenshot of my Disk Utility - [URL]
