LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 07-24-2010, 11:34 PM   #16
rdgreenlaw
Member
 
Registered: May 2007
Location: Newport, Maine, USA
Distribution: Debian 8.7
Posts: 72

Rep: Reputation: 18

Quote:
grub> cat (hdo,3)/boot.ini
error: no such disk
grub> cat (hdo,3) /boot.ini
error: file name required
It appears from your posting that you used the letter O instead of the number ZERO in your commands to GRUB. It is critical that you use 0 (Zero) in the command "cat (hd0,3)/boot.ini" and do not include any spaces anywhere except after the word "cat" The first error (no such disk) would be because you used hdo instead of hd0 , and the second would be because there is a space between the ) and / ") /" should be ")/"

Hope this helps...
 
1 members found this post helpful.
Old 07-24-2010, 11:48 PM   #17
Kenny_Strawn
Senior Member
 
Registered: Feb 2010
Location: /usa/ca/orange_county/lake_forest
Distribution: ArchBang, Google Android 2.1 + Motoblur (on Motortola Flipside), Google Chrome OS (on Cr-48)
Posts: 1,791
Blog Entries: 62

Rep: Reputation: 56
Quote:
Originally Posted by mowley View Post
I disconnected the second hard drive (sdb) and followed the instructions above. From 'c' at the Grub menu:
grub> ls (hd0,3)
Partition hdo,3: filesystem type ntfs-Label "Fixed Disc" UUID 5639c291826637e4
grub> cat (hdo,3)/boot.ini
error: no such disk
grub> cat (hdo,3) /boot.ini
error: file name required

Every attempt to boot Windows ends in STOP: 0x0000007B which is interpreted as "unable to find boot device". "Fixed Disk" is "C" in the Windows partition.

I can view boot.ini via Linux and "Fixed Disk" in File Manager. The Windows partition is set at hdo,3
Please note that you need to use a zero, not an 'o', when determining the disk using GRUB. If you use 'hdo' instead of 'hd0', you will get the no such disk error.
 
Old 07-25-2010, 03:23 AM   #18
mowley
Member
 
Registered: Jul 2010
Posts: 30

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by mowley View Post
From 'c' at the Grub menu:
grub> ls (hd0,3)
Partition hdo,3: filesystem type ntfs-Label "Fixed Disc" UUID 5639c291826637e4
grub> cat (hdo,3)/boot.ini
error: no such disk
...
GRUB HD Label Misspelling
Thanks to Kenny_Strawn for pointing that the error ('o' instead of '0'). I was not aware that I had done that after doing the right thing in the first command!
On repeating the second command I get:
grub> cat (hd0,3)\boot.ini
[bootloader] <d>
timeout=20
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS<d>
operating systems<d>
multi(0)disk(0)partition(3)\WINDOWS\="Microsoft WindowsXP Professional" /noexecute=optin /fastdetect<d>
What is the significance of "<d>"?
As I mentioned before, boot.ini exists in "Fixed Disk".
 
Old 07-25-2010, 06:03 AM   #19
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
I think a good strategy is to boot the Xp first by Grub2. If that fails restore Xp's MBR.

Xp will boot if the following conditions are satisfied

(1) The system must have been installed and booted from the same partition number and the drive letter has not been changed in the process. Post #18 confirm that the system was bootable from the 3rd partition of 1st disk of the 1st controller by "multi(0)disk(0)partition(3)". Therefore the OP information that the Xp is in the 3rd partition has been substantiated. This will be known to Grub2 as (hd0,3). MS boot loaders and Grub2 counts the disks from 0 and partitions from 1.

(2) Xp would have be operational inside a NTFS partition and its root directory must have (a) NTLDR, (b) boot.ini and (c) ntdetect.com. OP has managed to confirmed by Grub2 that there is a boot.ini inside (hd0,3). I expect the rest of the files will be there. This can be seen if OP issue this Grub2 command
Code:
ls (hd0,3)/
Grub2's "ls" command works the same as in Linux's own "ls" or Xp's "dir" command. In addition Grub2 broke the barrier for being the first Linux boot loader able to read a NTFS partition so why not use its ability?

(3) The third essential condition for Xp to boot is it must have a boot sector code installed inside (hd0,3). The majority of partitions created by Linux and all those by Dos/Windows have a reserved front area, commonly referred to as the boot sector, for the boot loader. This area is used only by the boot loader or left empty. MS system from every Dos to Win7 uses it. The code can be re-generated by a Xp installation CD in a recovery console by command
Code:
fixboot
or by a Vista/Win7 installation DVD in a Command prompt by command
Code:
bootsect /nt52 c:
(4) The Xp requires the partition it resides to have been marked "active" and if it boots from it that partition must also be a primary partition too. An "active" partition in MS Windows is "bootable" in Linux or Grub term. Every MS Windows or Linux partition tool can be used to make a
partition bootable. That fact that Xp is now inside the 3rd partition or (hd0,3) confirms Xp is in a primary because in a PC hard disk the first 4 partitions are reserved as primaries and all logical partitions starts with the 5th partition. The status of partition (hd0,3) can be checked in a Grub2 prompt by command
Code:
parttool (hd0,3) boot
To make it active is simply by adding a "+" to the end command
Code:
parttool (hd0,3) boot+
For assistance get the word directly from the horse's mouth with
Code:
parttool (hd0,3) help
and Grub2 will explain its command.

Assuming the essential conditions have been fullfilled then I expect Xp will start booting by Grub2 commands
Code:
set root=(hd0,3)
chainloader +1
boot
If the Xp has been migrated to a vastly different hardware then the internal EULA checking mechanism will lock the Xp on completion of the booting. A locked up Xp can only be unlocked by MS by the telephone. They will do it from the Internet side with the PC switched on. This is possibly the best demonstration how MS can control your PC. You can have a locked up Xp totally unusable in front of you. You call a stranger somewhere in the world, he/she dispatches an Internet signal and your Xp suddenly springs up to life.

If the hardware change is tolerable then the Xp will boot up to a message saying the OP has 3 days to re-activate the license. During the intervening period you have Xp operational. The re-activation should be done first by Internet of just clicking the appropriate button. If that fails the OP has to call MS by phone. Normally he would be then given a code to re-activate the Xp.

If for any reason the Xp doesn't boot at all then my recommendation is to run the Xp as the only operating system in the hard disk by restoring its boot sector code and Xp's MBR. This can be achieved by boot up any Xp installation CD, select "repair" and drop into a recovery console to issue these two commands
Code:
fixboot
fixmbr
If you have a floppy drive you can also put the NTLDR, boot.ini and ntdetect.com on a Dos bootable floppy to boot up the Xp. MS web site has also documented this procedure.

Lastly the <d> at the end of leach line of boot.ini is just the normal termination interpreted by Grub2. It would be invisible if you edit the boot.ini as a text file.

Let us know your progress.

Last edited by saikee; 07-25-2010 at 06:33 AM.
 
Old 07-31-2010, 08:44 AM   #20
mowley
Member
 
Registered: Jul 2010
Posts: 30

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by saikee View Post
I think a good strategy is to boot the Xp first by Grub2. If that fails restore Xp's MBR.
.............
Assuming the essential conditions have been fullfilled then I expect Xp will start booting by Grub2 commands
Code:
set root=(hd0,3)
chainloader +1
boot
..................
If you have a floppy drive you can also put the NTLDR, boot.ini and ntdetect.com on a Dos bootable floppy to boot up the Xp. MS web site has also documented this procedure.
Let us know your progress.
I do not have a Win XP CD available to do a Repair or MBR restore.
I have not been able to boot either the clone on the dual-boot system [A](on Partition 3) or on another drive [B] where it is the only restored system (Partition 1). Partition 3 on [A] has all the files previously on the original C:\ partition.

On [A] I did the following:
1. Created XP boot floppy and booted from it which produced this error:
"Windows could not start because the following file is missing or corrupt: <Windows root>\System32\hal.dll
Please reinstall a copy of the above file"
(I am not sure if Partition 3 is recognised as the C: drive, see below)
2.At the Grub prompt,
grub> parttool (hd0,3) boot
Partition 2 is active now
(even though Partition 3 had been marked Active and Partition 2 is Linux Swap)
grub> ls
(hd0) (hd0,3) (hd0,2) (hd0,1) (fd0)
grub> parttool (hd0,3) boot+
Partition 2 is active now
set root=(hd0,3)
chainloader +1
boot.............
result- boot stops at ..\drivers\Mup.sys then STOP: 0x0000007B

Similar result on 500GB drive [B] with single partition
Here after booting from BootitNG floppy and viewing Partition info:
MBR Entry 0 Filesystem 7/7H HPFS/NTFS Bootable NTFS
Warning Filesystem ends at LBA 66493031
This partition may not boot Win NT
[LBA info= Start 63 End 66493034]

I now propose to try again using Acronis True Image Home 2010 with Plus Pack which claims to transfer to dissimilar hardware, but any further suggestions welcome. In the end, it may be fruitless if I succeed in transfer but cannot reactivate.

Last edited by mowley; 07-31-2010 at 08:47 AM.
 
Old 07-31-2010, 02:26 PM   #21
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
I think it has been pointed out before that there is a good chance if you used an installed Windows Xp imaged from one PC an "restore" it on another it may not boot.

I am not sure of the root cause your current error but since you are now booting it with a floppy directly with a Xp system, where all programs and boot loader files are 100% Windows' own and it has not fired up. I am not hopeful that your effort will pay off eventually.
 
Old 08-06-2010, 02:13 AM   #22
mowley
Member
 
Registered: Jul 2010
Posts: 30

Original Poster
Rep: Reputation: 15
Failed to boot Restored image

Quote:
Originally Posted by saikee View Post
I think it has been pointed out before that there is a good chance if you used an installed Windows Xp imaged from one PC an "restore" it on another it may not boot.

I am not sure of the root cause your current error but since you are now booting it with a floppy directly with a Xp system, where all programs and boot loader files are 100% Windows' own and it has not fired up. I am not hopeful that your effort will pay off eventually.
I started afresh after purchasing Acronis True Image Home with Plus Pack ("Universal Restore") latest build (7046). Used it to Recover the C: drive partition image to an empty 500GB SATA drive on a desktop computer. This began with booting from a Bootable CD-ROM created by the program. Drivers for the new hardware downloaded from the M/B and Chipset manufacturer were provided for use during the Restore on a separate USB drive. I have no way of knowing if they were used.
The operation completed succesfully but Windows XP Pro would not boot normally. Selecting Safe Mode it booted OK and found new hardware, but drivers for Multimedia Audio Controller and VGA graphics on the USB stick were not suitable (AGP drivers provided on USB during copy).There were no problems with Display.
All folders and files are accessible in Safe Mode, and all Devices OK in Device Manager except Multimedia Audio Controller (ignored).
Booting Windows normally ends in STOP: 0x000000C2.
Booting Windows with bootlog failed-STOP: 0x00000024 (no bootlog obtained)
Ran chkdsk from NTFS4DOS- no problems.
In safe Mode uninstalled antivirus program (AVG).
Same result with boot.

P.S. I have just learned from Acronis Support that I should download an ISO image to create another Bootable Disk and then try a Restore again, but I will wait for suggestions.

Last edited by mowley; 08-06-2010 at 03:58 AM. Reason: typo
 
Old 08-07-2010, 11:02 PM   #23
mowley
Member
 
Registered: Jul 2010
Posts: 30

Original Poster
Rep: Reputation: 15
Further to my post #22, some of the (bracketed) error messages have changed, possibly as a result of uninstalling the antivirus program.
Normal Windows boot and Safe Mode boot now both result in:
BAD_POOL_CALLER STOP:0x000000C2(0x00000007,0x00000CD4,0x00720067,0xF7ADA4A8)
There is no apparent problem with ntfs.sys (0x00000024 appeared earlier)
I believe C2/7 = invalid software interrupt
C2/CD24 = uncertain
C2/67 = config initialisation failed
C2/A8 = uncertain
Unable to uninstall other possibly troublesome programs in Safe Mode.
System Event log error (attached) lists drivers which did not load. (Bootup stops at Mup.sys).
No new dump files found on the target disk.
The computer Name was not changed (see Event log) because I was not presented with the option to change the name or the SID number during recovery though I was expecting it.
Therefore I intend to start afresh with a new Acronis Bootable (multiparameter) disk which may provide more drivers during Recovery unless anyone has other advice to offer.
Attached Files
File Type: txt eventlog1.txt (566 Bytes, 6 views)
 
Old 08-08-2010, 01:16 AM   #24
PhantasyConcepts
LQ Newbie
 
Registered: May 2009
Posts: 19

Rep: Reputation: 3
Unhappy

Let me try again to state this, as I think you are still not getting it. I don't care what program you use to make an image to boot from, if the hardware is not an exact match, Windows will not boot. I say that because if you, for example, swap out the network card and the sound card and the video card, you will have to re-register Windows. That has always been the case. Windows XP and forward limited the user to only a set number of hardware changes - I think three - before you had to re-register. That meant that if you started out on an HP computer and swapped the motherboard out for a newer one, you were pretty much screwed unless it was the exact same motherboard model. Your errors indicate that you are experiencing problems because your 'image' is not one of the machine you are trying to dual-boot.

My suggestion is to get a Windows XP install disk, with a valid serial number and start from scratch there.
 
Old 08-08-2010, 02:48 AM   #25
mowley
Member
 
Registered: Jul 2010
Posts: 30

Original Poster
Rep: Reputation: 15
Moving Windows to dissimilar hardware

Quote:
Originally Posted by PhantasyConcepts View Post
Let me try again to state this, as I think you are still not getting it. I don't care what program you use to make an image to boot from, if the hardware is not an exact match, Windows will not boot. ........ Your errors indicate that you are experiencing problems because your 'image' is not one of the machine you are trying to dual-boot.
My suggestion is to get a Windows XP install disk, with a valid serial number and start from scratch there.
Actually I do get it! Thanks for the suggestion but it has been made previously in this thread. If you look here http://kb.acronis.com/content/5410 you will see what I am trying to do- but knowing it may not succeed, or if it does, that I might need re-activation of Windows.
There could still be problems with dissimilar hardware using a Windows XP disk to Repair over the restored image. I want to move my existing system (and not have to reinstall programs or upgrade Windows) to a different computer, and then delete the system on my ageing laptop.
Also, I am now Restoring to the first partition of a single disk, not dual-booting.

Last edited by mowley; 08-08-2010 at 02:50 AM. Reason: typo
 
Old 08-08-2010, 04:30 AM   #26
feinbein
Member
 
Registered: Jan 2010
Location: Norway
Posts: 76

Rep: Reputation: 12
Quote:
Originally Posted by mowley View Post

Every attempt to boot Windows ends in STOP: 0x0000007B which is interpreted as "unable to find boot device". "Fixed Disk" is "C" in the Windows partition.
It seems like Grub is working just fine and booting XP but XP is slightly disturbed by the fact that it is on a different partition now.
You must edit the file boot.ini on the Xp-partition and change all occurences of 'partition(1)' to 'partition(3)' like this
Code:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
Then the 'real' problems will start! You will have to boot in safe-mode and remove all non-existent (e.g. no-longer-existant) hardware from device-manager. After that you need to install drivers for new hardware and still have to convince MS to activate your installation. Good Luck with that!

If you ask me - get rid of it!
 
Old 08-08-2010, 06:20 AM   #27
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
A definitive answer of if it is possible to use an existing Xp installed in one computer and move it to another is to clone the whole disk.

One can clone the target directly as an internal hard disk by putting the target inside the first PC.

Alternatively the new disk can be externally hooked up as a USB hard disk (inside a hard disk enclosure). Needless to say the target disk has to be the type suitable for the final destination of the second PC but it is possible to change from 2.5" to 3.5", IDE to Sata etc.

Once cloned the target can in inserted into the new PC and boot from there as the internal hard disk.

If it is not convenient to moved the internal disks then a USB hard disk can be used as a go between by having the cloning operation done twice; once with source to the USB and then from the USB to the target.

The following conditions should be adhered to

(1) If the target disk boots then the original source should ceased to be used, say the source machine is obsolete and its hard disk becomes a backup. In other word the licensing agreement must be respected and adhered.

(2) The target disk must be either exactly in size or just larger than the source disk if using dd command to clone.

(3) For the cloning operation a third part source software ware like Acronis or Ghost can be used and they may even be able to shrink a Windows image from a bigger hard disk to a smaller one. I always use dd which is available in every Linux and Unix as it is the simplest and sometime can be the fastest too. If the source disk is device sda and the target is sdb I find putting the block size equal to one track of 63 sector x 512 bytes per sector = 32256 bytes is about the optimum
Code:
dd if=/dev/sda of=/dev/sdb bs=32256
The above is equivalent of removing a hard disk, with the operating system inside, from one PC and use it directly on a new PC, except a backup is made first. dd only provides a 100% exact mirror of the first hard disk image. It clones empty spaces same as data because to it everything is either "1" or "0" in the hard disk. Therefore one can have any number of different operating systems inside a source hard disk and everyone must boot in the target because not one binary bit will be different between the two disks within the hard disk area prescribed by the same partition table.

The read/write head of a modern hard disk always moves one sector or 512 bytes in any operation so by omitting the block size parameter of "bs=32256" dd will automatically default to "bs=512" and the same track will be cloned in 63 operations instead of one. If a users wants anything less than 512 bytes the controller still reads and writes 512 bytes every time leaving the operating system to strip or reassemble the information in unit of one sector.

The Windows in the new environment should always boot.

If the old PC is the same model as the old and the two have the same specification or hardware then it will boot perfectly and without any complaint, as it did only last month to my work laptop which had the mobo fired. The transfer was done by the company IT engineer in front of my eye.

If the source PC and the target PC are different then a re-activation will be the minimum requirement. A user is given normally a set period, say within 3 days, to re-activate. In the mean time the drivers from the new PC can be installed. Not having the correct hardware drivers should only cause some components inoperable but it should not prevent the system from booting up.

The other common scenario is the Xp on finding itself in a new environment, after completing the booting process, with all drivers mismatched. Very quickly it would come to the conclusion that it has been illegally moved or copied. It will then issue a warning requiring activation with MS then locks up itself immediately. Further attempts to boot the Windows will only lead to a blank screen. If this situation is explained to MS, via a telephone, stating that the old PC is faulty then MS has been known to honour the reactivation for the Xp to be usable on the new PC.

I have personally experienced every scenario described above.

Last edited by saikee; 08-08-2010 at 06:44 AM.
 
Old 08-08-2010, 10:23 AM   #28
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 12,899
Blog Entries: 27

Rep: Reputation: 2185Reputation: 2185Reputation: 2185Reputation: 2185Reputation: 2185Reputation: 2185Reputation: 2185Reputation: 2185Reputation: 2185Reputation: 2185Reputation: 2185
Hi,
Quote:
Originally Posted by PhantasyConcepts View Post
Let me try again to state this, as I think you are still not getting it. I don't care what program you use to make an image to boot from, if the hardware is not an exact match, Windows will not boot. I say that because if you, for example, swap out the network card and the sound card and the video card, you will have to re-register Windows. That has always been the case. Windows XP and forward limited the user to only a set number of hardware changes - I think three - before you had to re-register. That meant that if you started out on an HP computer and swapped the motherboard out for a newer one, you were pretty much screwed unless it was the exact same motherboard model. Your errors indicate that you are experiencing problems because your 'image' is not one of the machine you are trying to dual-boot.

My suggestion is to get a Windows XP install disk, with a valid serial number and start from scratch there.
I swapped many sub-systems on a Xp install without ever having to re-register with M$. As for moving between systems that is a requirement in the EULA that registration for the install.

Not a requirement to re-register when changing sub-systems. Motherboard is not a subsystem. Hard drive failure would require a new or replacement drive so a fresh install or backup would indeed require registration. Not a problem for a valid license holder.
 
Old 08-08-2010, 10:52 AM   #29
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
Never had a problem of changing a hard drive for a MS Windows in my case.

The disk must be a 100% clone. When the clone is booted the MS Windows will immediately detect that everything is exactly as before except the hard disk serial number no long matches. It will claim a new hardware has been detected, have the driver selected successfully but the new hardware will not work properly untill the PC is rebooted immediately. The system actuially demands an immediate reboot. After a reboot it will work perfectly again. That has been my case if I change the hard disk for every Xp, Vista na Win7.

I have a HP laptop that came with a Vista in a 160Gb hard disk. The day I bought it I also purchased a 250Gb 2.5" hard disk and swapped it within the first 24 hours. Later I swapped the 250Gb for a 320Gb hard disk, then to a 128Gb SSD and finally back to a conventional hard disk 500Gb.
 
Old 08-11-2010, 11:56 PM   #30
mowley
Member
 
Registered: Jul 2010
Posts: 30

Original Poster
Rep: Reputation: 15
Moving XP to dissimilar hardware

Quote:
Originally Posted by feinbein View Post
It seems like Grub is working just fine and booting XP but XP is slightly disturbed by the fact that it is on a different partition now.
You must edit the file boot.ini on the Xp-partition and change all occurences of 'partition(1)' to 'partition(3)' like this
Code:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
Then the 'real' problems will start! You will have to boot in safe-mode and remove all non-existent (e.g. no-longer-existant) hardware from device-manager. After that you need to install drivers for new hardware and still have to convince MS to activate your installation. Good Luck with that!

If you ask me - get rid of it!
I probably will soon get rid of it- at least on the dual-boot drive! You are quite right about a successful boot being just the start of more problems.
May I point out that boot.ini was in the form you suggest (see posts #18 and #19) when boot failure occurred on the dual-boot system.
But more recently I have tried restoring the whole XP drive by itself on a new drive (C: in the first partition) and this also failed (post #23). So the thread topic has really changed to "moving XP to dissimilar hardware" as a result of the many useful suggestions received.In a sense it is still related to my initial question, but perhaps this thread needs to be closed as an unresolvable problem. For the moment I will continue working on the drive with the single Restored system.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
dual boot fedora & vista - boot error - "GRUB loading stage 2" ans Fedora 1 08-20-2007 04:35 AM
Constant "Resolving host" on linux dual boot system fof3 Linux - Networking 10 07-05-2007 03:20 PM
Grub/Dual boot - Windows partition restored via dd won't boot pazzport Ubuntu 1 01-06-2006 02:29 PM
Dual-boot install: "Could not find kernel image: linux / boot:" JEBBEDIAH C Linux - Newbie 16 02-02-2005 09:25 PM
I Dual Boot, Is there Compatable "Drive imaging" that works with linux joncolby Linux - Software 6 06-21-2004 04:11 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 05:54 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration