back up an ext3 partition
heavytull
found nothing for that on the internet. I'm thinking of archiving all
files with tar and then I will copy them back on an other ext3
partition. But i'm wondering whether i will get errors.
also note that i'm using grub on that system.
The orther solution would be to use dd, but i think this could be
critical if the other ext3 partition is not identical in terms of
size. would it?
Bit Twister
> i would like to backup an ext3 partition on which there is a linux. I
> found nothing for that on the internet.
Why do you think backing up an ext3 would be different than doing your
current backups.
> I'm thinking of archiving all
> files with tar and then I will copy them back on an other ext3
> partition.
That works. From what you have said so far, I would format the target
partition, boot a rescue cd, and rsync current partition into new partition.
> But i'm wondering whether i will get errors.
Only if the media receiving the tar file or the media where the tar is
being unpacked has problems. I assume what files being tared are not
being written to at the time.
> also note that i'm using grub on that system.
Target or source does not matter to tar which boot loader is being used.
Worst that can happen is you have to use a rescue diskette/cd to
straighten out what you are doing.
> The orther solution would be to use dd, but i think this could be
> critical if the other ext3 partition is not identical in terms of
> size. would it?
It does help. You have wasted space on target partition if original
dd copy is smaller.
One downside of using dd is that any bad blocks on source will still
be marked bad on target disk. Any bad blocks on target drive will
not be marked bad. All though chances there are slim with new drives.
If moving your linux from one partition to another, why not use a live
cd and rsync old partition into the formatted new partition.
boot rescue cd
mkdir /old /new
mount -t auto /dev/XdYZ /old
mount -t auto /dev/XdYZ /new
rsync -av /old/ /new
Then modify the boot loader to manage what you have done.
Do not forget to modify /new's fstab if you are moving /root.
Vahis
Why not just cp?
Vahis
--
Vahis
http://waxborg.servepics.com
Congressman Wilson has an expression:
"You can teach them to type, but you can't teach them to grow tits."
bb
Backup of files is one thing, and the partition is another thing.
If you insist to save the complete partition, including MBR and table,
you should look at http://partimage.org and read, then grab the
rescue CD image from the link SystemSrescueCD Homepage.
Partimage only save used blocks, and compress them, so the image
is much smaller then the partition and can easy be saved on USB
disk even with fat, since partimage can split the image to many
files, less then 2GB.
I try to always have an partimage image of my system disk, for fast
bare metal recovery, but use normal backup for everything else.
/bb
Unruh
>i would like to backup an ext3 partition on which there is a linux. I
Backup to what? Another disk? Then use rsync. A dvd? Then use
mkidofs/cdrecord.
>found nothing for that on the internet. I'm thinking of archiving all
You did not look very hard.
>files with tar and then I will copy them back on an other ext3
?? No idea what it is you are wanting to do.
>partition. But i'm wondering whether i will get errors.
>also note that i'm using grub on that system.
grub has nothing to do with backing up.
>The orther solution would be to use dd, but i think this could be
Bad idea.
Unruh
>On 2008-08-21 16:01, heavytull wrote:
>> i would like to backup an ext3 partition on which there is a linux. I
>> found nothing for that on the internet. I'm thinking of archiving all
>> files with tar and then I will copy them back on an other ext3
>> partition. But i'm wondering whether i will get errors.
>> also note that i'm using grub on that system.
>>
>> The orther solution would be to use dd, but i think this could be
>> critical if the other ext3 partition is not identical in terms of
>> size. would it?
>Backup of files is one thing, and the partition is another thing.
>If you insist to save the complete partition, including MBR and table,
?? partition has nothing to do with MBR. It is not part of any partition.
Did you mean disk?
bb
> bb <spam...@norsborg.net> writes:
>
>> If you insist to save the complete partition, including MBR and table,
> ?? partition has nothing to do with MBR. It is not part of any partition.
> Did you mean disk?
>
No I mean backup of a partition, where MBR and partition table are
included in the backup, so they also can be restored.
/bb
J.O. Aho
> i would like to backup an ext3 partition on which there is a linux.
If you want to backup the complete file system, use dd
If you want to backup the files, use tar (don't forget to ignore content in
directories like /proc and /sys).
> I found nothing for that on the internet.
Then your internet is broken.
> I'm thinking of archiving all
> files with tar and then I will copy them back on an other ext3
> partition. But i'm wondering whether i will get errors.
Errors will occur if the source or destination storage is damaged, tar itself
won't generate any faults.
> also note that i'm using grub on that system.
Backup your /boot and you get all expect the binaries.
> The orther solution would be to use dd, but i think this could be
> critical if the other ext3 partition is not identical in terms of
> size. would it?
ext allows growing and shrinking, as long as the destination is larger you
won't have any trouble, just see to grow it to get use of the whole disk space.
--
//Aho
heavytull
> > also note that i'm using grub on that system.
>
> Target or source does not matter to tar which boot loader is being used.
> Worst that can happen is you have to use a rescue diskette/cd to
> straighten out what you are doing.
>
actually I specified that i was using grub because i don't know how it
works. I have only used lilo on my system.
i have to study how works grub.
heavytull
Bit Twister
> i though i could have some straight forward help on grub here.
It can be useful. Here is a snippet from my /boot/grub/menu.lst where
I can boot whatever I have it my /hotbu partition, a memory tester, or
boot whatever fedora iso I have downloaded.
title /hotbu
root (hd0,7)
configfile /boot/grub/hotbu.lst
title memtest-2.01
kernel (hd0,14)/boot/memtest-2.01.bin BOOT_IMAGE=memtest-2.01
title fedora_iso
kernel (hd1,0)/spare/vmlinuz BOOT_IMAGE=linux ro vga=791
initrd (hd1,0)/spare/initrd.img
> i have to study how works grub.
Look around on the grub installed system and you might find
something like
$ locate -i grub | grep /doc/
/usr/share/doc/grub-doc
/usr/share/doc/HOWTO/HTML/en/Linux+Win9x+Grub
/usr/share/doc/HOWTO/HTML/en/Multiboot-with-GRUB
/usr/share/doc/HOWTO/HTML/en/Linux+Win9x+Grub/index.html
/usr/share/doc/HOWTO/HTML/en/Linux+Win9x+Grub/intro.html
/usr/share/doc/HOWTO/HTML/en/Linux+Win9x+Grub/proc.html
/usr/share/doc/HOWTO/HTML/en/Linux+Win9x+Grub/reqs.html
/usr/share/doc/HOWTO/HTML/en/Multiboot-with-GRUB/Multiboot-with-GRUB-1.html
/usr/share/doc/HOWTO/HTML/en/Multiboot-with-GRUB/Multiboot-with-GRUB-2.html
/usr/share/doc/HOWTO/HTML/en/Multiboot-with-GRUB/Multiboot-with-GRUB-3.html
/usr/share/doc/HOWTO/HTML/en/Multiboot-with-GRUB/Multiboot-with-GRUB-4.html
/usr/share/doc/HOWTO/HTML/en/Multiboot-with-GRUB/Multiboot-with-GRUB.html
/usr/share/doc/HOWTO/HTML/en/Remote-Serial-Console/configure-boot-loader-grub.html
/usr/share/doc/HOWTO/HTML/en/Remote-Serial-Console/configure-kernel-grub.html
/usr/share/doc/grub-doc/AUTHORS
/usr/share/doc/grub-doc/BUGS
/usr/share/doc/grub-doc/ChangeLog
/usr/share/doc/grub-doc/NEWS
/usr/share/doc/grub-doc/README
/usr/share/doc/grub-doc/THANKS
/usr/share/doc/grub-doc/TODO
/usr/share/doc/grub-doc/grub.ps
/usr/share/doc/grub-doc/multiboot.ps
heavytull
as a lilo long time user i'm totally confused with grub.
the matter here is:
I rsynced a logical partition with another one on the same primary
partition. the former logical partition is to be removed, so now i
need to boot the OS on the new logical partition instead of the old
one.
Bit Twister
> On Aug 21, 10:42 pm, Bit Twister <BitTwis...@mouse-potato.com> wrote:
>
> as a lilo long time user i'm totally confused with grub.
>
> the matter here is:
>
> I rsynced a logical partition with another one on the same primary
> partition.
Hope you rsynced with a rescue cd instead of just rsyncing a running linux.
> the former logical partition is to be removed, so now i
> need to boot the OS on the new logical partition instead of the old
> one.
I might have mentioned that you might want to read
http://www.catb.org/~esr/faqs/smart-questions.html
Based on the inordinate lack of information provided. you
modify /etc/fstab and /boot/grub/menu.lst to use the new partition
on the new partition.
Add your new partition stanza to your current boot loader,
Boot new partition.
Install grub in the mbr.
Be aware grub does zero relative counting. Drive 0 partition 0 (0,0)
is /dev/hda1
noi ance
Sounds reasonable. I would suggest using a backup strategy that backups
by directories or folders and includes hidden files. Depending on your
need for recovery and available storage there're different methods.
Ordinarily, tar wouldn't back up hidden files so ~/.xine, ~/.thunderbird
would be missed, also very large tar files (> 900mb) take time to untar
and risk corruption.
You can experiment with $ find dirname -type f > dirnamelist.txt to
create a list of files for input to the tar command.
#1 You should ensure you backup important files, folders first, /home/
userid, /home/music, /home/videos/, /home/finances, etc.
#2 Backup all configuration files, ie, /etc/ wouldn't hurt
#3 If you're installing a new system /usr, /bin, /var, /tmp are overlaid
so those don't need backup.
If you have a spare partition you can back up the entire partition using
DD, $ man dd.
bb
> heavytull wrote:
>> i would like to backup an ext3 partition on which there is a linux.
>
> If you want to backup the complete file system, use dd
> If you want to backup the files, use tar (don't forget to ignore content
> in directories like /proc and /sys).
>
Using dd on a mounted file system is not to recommend , and the image will
be very big due to backup of free blocks too.
One thing that is possible is to write zeros in all free blocks, then compress
the image, but the result is that partimage should do a better job and more simple.
Anyway, do do it with dd :
zero free blocks:
dd if=/dev/zero of=bigfile || rm bigfile
in readonly (rescue boot):
dd if=<partition> | gzip -c > /<something>/save.img.gz
tar has the -l option ( --one-file-system ) to skip other
file systems.
/bb
heavytull
> Hope you rsynced with a rescue cd instead of just rsyncing a running linux.
>
yeah i did it using a live linux. I always have a live linux around in
case of problem.
> I might have mentioned that you might want to readhttp://www.catb.org/~esr/faqs/smart-questions.html
>
yes you mentioned;
but i have read it long ago. Here I didn't feel I needed to give more
info.
I think giving you the distro i'm running on that pc and the kernel
version is useless because it is a matte with grub only.
I just don't know how to use it, though i read the mini howto it is
really unclear.
As i have already mentioned i needed some quick and straight forward
lines.
> Based on the inordinate lack of information provided.
I have often noticed that you ask unneeded information.
> you
> modify /etc/fstab
That's done
>and /boot/grub/menu.lst to use the new partition
> on the new partition.
>
ok; that's the same philosophy than with lilo.
> Add your new partition stanza to your current boot loader,
you mean in menu.lst?
> Boot new partition.
wow?? with a kick in it??
booting the new partition is the actual problem man.
> Install grub in the mbr.
>
you're babbling? that's what i want to know.
Hey man, your help is far useless.
FIRST try to understand my question.
> Be aware grub does zero relative counting. Drive 0 partition 0 (0,0)
> is /dev/hda1
i saw that
Bit Twister
>>
> yes you mentioned;
> but i have read it long ago. Here I didn't feel I needed to give more
> info.
You really need to go back and read
http://www.catb.org/~esr/faqs/smart-questions.html
What you feel is un-necessary information may be necessary
information to the person trying to help you with your problem.
> I think giving you the distro i'm running on that pc and the kernel
> version is useless because it is a matte with grub only.
See, it is not just distro/verison needed for a problem.
Had you provided fstab info for the current/new partition,
which loader running, contents of new/old grug stanza, what did not
work, we would be able to point out problem(s) and provide solutions.
> I just don't know how to use it, though i read the mini howto it is
> really unclear.
Well, I have no idea what is unclear, so I can not help there.
What is unclear.
> As i have already mentioned i needed some quick and straight forward
> lines.
See there is where distro would be the required information.
putting restore grub mbr in the first box at
http://groups.google.com/advanced_search gives
Results 1 - 10 of 371 for restore grub mbr
using reinstall grub mbr, we see
Results 1 - 10 of 535 for reinstall grub mbr
If Mandriva Linux, I would point you to the Mandriva Control Center's
Boot section. It would make changes to grub's config file and update
the mbr. No sweat.
For another distribution, you could the provided grub installer.
Worse comes to worse, use the grub interface.
>> Based on the inordinate lack of information provided.
> I have often noticed that you ask unneeded information.
>
>> you
>> modify /etc/fstab
> That's done
Yes, but tells us nothing. We have no idea what you did, if you did it
right, much less see it correct information is in the current
boot loader config file let alone what needs to be in the new loader
config file.
>>and /boot/grub/menu.lst to use the new partition
>> on the new partition.
>>
> ok; that's the same philosophy than with lilo.
BFD, and yet, no information provided. Go read
http://www.catb.org/~esr/faqs/smart-questions.html
>> Add your new partition stanza to your current boot loader,
> you mean in menu.lst?
If using grub, yes.
>> Boot new partition.
> wow?? with a kick in it??
> booting the new partition is the actual problem man.
Oh, look, finally, one more piece of information. Dang.
Go read http://www.catb.org/~esr/faqs/smart-questions.html
With no error message, fstab/loader config info, no solution can be provided.
>> Install grub in the mbr.
>>
All right, you finally provide ONE piece of required information.
You do want to install in the mbr. Nice, getting information from you
is like pulling teeth.
> you're babbling? that's what i want to know.
Giving you what you "what to know" is not going to help if you are not
able to fix your current problem.
See last paragraph of this reply.
> Hey man, your help is far useless.
Glad to hear that. :-D
Had it been useless, it would be a complete waste of time. :-P
> FIRST try to understand my question.
I understood your question, I just do not know exactly what your problem is.
With this last post, I think you are telling me you cannot boot
the new partition using the current grub boot loader.
I do not know if it is a grub problem, or problem in the new partition.
>> Be aware grub does zero relative counting. Drive 0 partition 0 (0,0)
>> is /dev/hda1
> i saw that
So, you tell us you understand lilo. I told you to duplicate the
stanza and make changes for the new partition in grub's config file.
Now you tell us you know grub numbering scheme, so I have no clue
as to what the problem is with out you giving error message(s)
and providing old/new partition values and contents of current
boot loader config file.
As I misunderstand it so far, current boot loader is grub, installed
in the mbr.
You were unable to understand my generic instructions to make current
grub boot new install. Feel free to correct me if I am wrong.
If you cannot boot new install with current grub config, I sure as
H3ll will not give instructions to make the system un-bootable.
heavytull
> On Sat, 23 Aug 2008 08:15:36 -0700 (PDT), heavytull wrote:
>>>
>> yes you mentioned;
>> but i have read it long ago. Here I didn't feel I needed to give more
>> info.
>
> You really need to go back and read
> http://www.catb.org/~esr/faqs/smart-questions.html
>
It seems you're the kind of guy who never use common sence. you always
need to read instructions somewhere to do anything. Even simple things.
> What you feel is un-necessary information may be necessary information
> to the person trying to help you with your problem.
>
>> I think giving you the distro i'm running on that pc and the kernel
>> version is useless because it is a matte with grub only.
>
> See, it is not just distro/verison needed for a problem. Had you
> provided fstab info for the current/new partition
ok now you ask the information you need.
tha's a thing but as the issue is this is unneeded to tell anyone.
>, which loader running,
grub of course i told that in very first post, read it back.
> contents of new/old grug stanza,
what do you mean by stanza? state?
> what did not work,
you're really lacking of brain! tha's really astonishing you're still on.
I'm not offending you here, but that's really what I feel
look, i'm summarizing the issue here again:
1.I rsynced (with a live linux) a logical partition data (a linux) on a
newly created partition on the same primary partition (all ext3).
you get it?
IOW:
I have a computer on which there is (among others) a primary partition
with a logical one in it which holds a linux. I created a new logical
partition in the same primary partition. both are ext3. Then I
synchronised the data of the new partition with the old one holding a
linux with a live linux and rsync.
now you got it!??? :-|
2.The boot loader is Grub. I have never ever used it before, not even have
smelled it. ok?
my request: give me some straigh foreward instructions to make grub
loading the linux on the new logical partition instead of the old one.
that's all. extra information is unneeded. anyway if any wanted, he should
have asked.
extra comments: I emphasized that i was using logical partitions because
at my knowledge some boot loaders can only load one logical partition in a
primary one and only the first one in it.
ALA I didn't mention here any detail about the grub config file or
anything else you should assume that everything is working well with the
old partition. So you don't need to ask whether it's sunny or not or
whether the grass is growing or not.
Also don't ask why i rsynced a linux to a new logical partition on the
same primary one because, first, you don't need to know, second, it's a
bit too long to me to explain.
It's seems quite clear to me. You should take rest.
> If Mandriva Linux, I would point you to the Mandriva Control Center's
> Boot section.
you should go back to MSwin
>It would make changes to grub's config file and update the
> mbr. No sweat.
>
with lilo I always touch the lilo.conf and run lilo, and never sweated.
>
> Yes, but tells us nothing. We have no idea what you did, if you did it
> right,
don't worry about that.
Do you wonder everyday whether the postman's bicycle is OK so he can
deliver you your mails.
man, ALA i didn't mention any problem you worry for nothing.
> With no error message
why the hell you want error messages????
go straigh into a concrete wall and knock your head, then you'll get error
messages straight in your brain.
>>> Install grub in the mbr.
>>>
>>>
> All right, you finally provide ONE piece of required information.
that's seems to me quite obvious.
> Glad to hear that. :-D
forget about it, just be glad you're alive. With so damaged brain that's
really lucky.
>> FIRST try to understand my question.
>
> I understood your question,
you're too off to do.
> I just do not know exactly what your problem
find out your problem first.
> is. With this last post, I think you are telling me you cannot boot the
> new partition using the current grub boot loader.
>
no, you're really damaged.
> I do not know if it is a grub problem, or problem in the new partition.
>
shut up
...
heavytull
> Why not just cp?
>
i'm wondering the same
> Vahis
Bit Twister
> On Sat, 23 Aug 2008 16:42:46 +0000, Bit Twister wrote:
>
>> On Sat, 23 Aug 2008 08:15:36 -0700 (PDT), heavytull wrote:
>>>>
>>> yes you mentioned;
>>> but i have read it long ago. Here I didn't feel I needed to give more
>>> info.
>>
>> You really need to go back and read
>> http://www.catb.org/~esr/faqs/smart-questions.html
>>
> It seems you're the kind of guy who never use common sence. you always
> need to read instructions somewhere to do anything. Even simple things.
Not really, RTFM is usually the last thing I do. As an Oh, By The Way,
I usually do not give answers unless I feel it is beyond the expertise
of the poster. I try teach how to catch the fish instead of catching,
preparing, cutting, and hand feeding the fish to the poster.
I write mostly for the newbie lurkers and anyone who finds the thread
with the search engine and in the process solve your problem.
On the other hand you seem to be the one fighting with simple things.
Look how much time you have wasted wanting to know how to install
grub's boot loader.
Take number 3 in http://www.catb.org/~esr/faqs/smart-questions.html#before
A simple
$ man -k grub
grub (8) - the grub shell
grubby (8) - command line tool for configuring grub, lilo, and elilo
grub-install (8) - install GRUB on your drive
grub-md5-crypt (8) - Encrypt a password in MD5 format
grub-terminfo (8) - Generate a terminfo command from a terminfo name
Should have solved your question. Depending on what distribution, maybe not.
There can be another reason for that to not work, but I'll
save that for another class. I'll give you some slack there.
man grub indicates use info grub. Ok,
info grub
Would you look at that.
Fourth Asterisk has
* Installation:: Installing GRUB on your drive
Couple of down arrows and carriage return, second paragraph, second
sentence under 3 Installation and there is your command to use.
I would have thought anyone running Slackware had the brains to use
item 2.
But noooo, not you. I had to provide you with searching the web 101.
>> What you feel is un-necessary information may be necessary information
>> to the person trying to help you with your problem.
>>
>>> I think giving you the distro i'm running on that pc and the kernel
>>> version is useless because it is a matte with grub only.
>>
>> See, it is not just distro/verison needed for a problem. Had you
>> provided fstab info for the current/new partition
> ok now you ask the information you need.
> tha's a thing but as the issue is this is unneeded to tell anyone.
Let me guess, you played with either grub-install or used the grub
commands to reinstall grub in mbr and you were still unable to boot
the copy. Yes, I pretty much figured that out.
>> contents of new/old grug stanza,
> what do you mean by stanza? state?
The paragraph you are trying to boot the new copy.
I gave you 3 stanzas or paragraphs as an example.
>> what did not work,
> you're really lacking of brain! tha's really astonishing you're still on.
No, you are the one lacking the brain. Had you understood the smart
questions document, you would have shown us what you have done, the
files modified, and provided error information. Have you done any of
that to date. NOooo.
> I'm not offending you here, but that's really what I feel
You would have to work pretty damn hard to offend me. Then I would
just score you 666 and give you a hard time anytime you posted.
> look, i'm summarizing the issue here again:
> 1.I rsynced (with a live linux) a logical partition data (a linux) on a
> newly created partition on the same primary partition (all ext3).
> you get it?
Yes, but to solve the problem, you have to provide the configuration
files you modified.
> IOW:
> I have a computer on which there is (among others) a primary partition
> with a logical one in it which holds a linux. I created a new logical
> partition in the same primary partition. both are ext3. Then I
> synchronised the data of the new partition with the old one holding a
> linux with a live linux and rsync.
> now you got it!??? :-|
Sure, but you still have to provide the files you modified and
I want to see the boot loader's config file.
>
> 2.The boot loader is Grub. I have never ever used it before, not even have
> smelled it. ok?
Fine, already figured that out. Why not just provide the files you modified.
> my request: give me some straigh foreward instructions to make grub
> loading the linux on the new logical partition instead of the old one.
> that's all. extra information is unneeded.
You can not solve the problem. By your words, you "have never ever
used it before, not even have smelled it."
How can you possibly know what information is unneeded?
Sometimes seemly unrelated information/questions is used to rule out
so possible problems. Just answer the freaking question. OK?
> anyway if any wanted, he should have asked.
I did ask and yet you have failed to provide them. One more time,
/boot/grub/menu.lst, /etc/fstab, from both partitions and distribution
and version.
> extra comments: I emphasized that i was using logical partitions because
> at my knowledge some boot loaders can only load one logical partition in a
> primary one and only the first one in it.
I understand what you are saying. But had we wanted to verify that, we
would ask for the output from a disk utility.
We do not care about why you did something, we cannot take your "word"
you did as we asked. We need to see the files you changed and any
requested information.
>
> ALA I didn't mention here any detail about the grub config file or
> anything else you should assume that everything is working well with the
> old partition.
BFD, we should assume nothing. We should get all the facts, make sure
we know where we are at what point in time, and then we can give much
more accurate instructions.
> So you don't need to ask whether it's sunny or not or
> whether the grass is growing or not.
Now you are getting into this section of the document.
http://www.catb.org/~esr/faqs/smart-questions.html#not_losing
> Also don't ask why i rsynced a linux to a new logical partition on the
> same primary one because, first, you don't need to know, second, it's a
> bit too long to me to explain.
I could care less and would not ask. I can say for a fact, how you
rsynced depends on Distribution, version. 8-)
> It's seems quite clear to me. You should take rest.
It is quite clear to me, if you want to learn where you screwed up,
you will provide the requested information.
There are two easy ways to fix your problem, the obvious way or
provide the requested information.
>> If Mandriva Linux, I would point you to the Mandriva Control Center's
>> Boot section.
> you should go back to MSwin
Tisk, tisk.
http://www.catb.org/~esr/faqs/smart-questions.html#not_losing
>
>
>>It would make changes to grub's config file and update the
>> mbr. No sweat.
>>
> with lilo I always touch the lilo.conf and run lilo, and never sweated.
See, with grub, you just need grub to boot.
You add/delete/modify a stanza and change is automagically available.
>
>
>>
>> Yes, but tells us nothing. We have no idea what you did, if you did it
>> right,
> don't worry about that.
> Do you wonder everyday whether the postman's bicycle is OK so he can
> deliver you your mails.
> man, ALA i didn't mention any problem you worry for nothing.
Heheheh, if you did it right, you would have not been back in this thread.
>
>> With no error message
> why the hell you want error messages????
> go straigh into a concrete wall and knock your head, then you'll get error
> messages straight in your brain.
Yet another stupid remark,
http://www.catb.org/~esr/faqs/smart-questions.html#not_losing
Error messages are used to jump closer to the problem instead of
blindly mucking about.
>
> forget about it, just be glad you're alive. With so damaged brain that's
> really lucky.
http://www.catb.org/~esr/faqs/smart-questions.html#not_losing
>>
> no, you're really damaged.
And yet, I use grub to boot standalone memory tester, iso images,
numerous distributions.
>
>> I do not know if it is a grub problem, or problem in the new partition.
>>
> shut up
HEHEHEHeheheheh, So how far along are we on getting your problem fixed?
heavytull
> > It seems you're the kind of guy who never use common sence. you always
> > need to read instructions somewhere to do anything. Even simple things.
>
> Not really, RTFM is usually the last thing I do.
that's quite a bad idea!
Reading the manual is often the first thing i do. ;)
and that's also what is advised anywhere, in any source code, in any
soft docs, in any any anything!
i didn't reproach you that you always read manuals, i reproached you
that you never use common sense.
manuals are to help understand how stuff works. While you never try to
understand anything.
> As an Oh, By The Way,
> I usually do not give answers unless I feel it is beyond the expertise
> of the poster. I try teach how to catch the fish instead of catching,
> preparing, cutting, and hand feeding the fish to the poster.
well said, but that's not what i see in your posts.
It seems that my above statement touched your feelings a lot.
> On the other hand you seem to be the one fighting with simple things.
no, actually I had about some hours to solve the problem at about the
time of the original post.
then after i had to leave that computer to its owner. after that i
gave up about grub. I'm planning of course to be back in it some day
just because i think i definitely need to know how it works, but now
i'm not in the appropriate mood for that.
So, here I'm not fighing to solve the problem, but to make you
understand that you are damn dumb!!! brain damaged, abnormal...
The only fact that you asked me in you last post which errors i got
tells really a lot. you're totally off.
anyway, your post i'm replying right now is too long, i'll probably
read it in the coming days, but for now i stop here
An advice: take rest. be far from stuff.
Bit Twister
> On Aug 24, 8:50 pm, Bit Twister <BitTwis...@mouse-potato.com> wrote:
>
>> > It seems you're the kind of guy who never use common sence. you always
>> > need to read instructions somewhere to do anything. Even simple things.
>>
>> Not really, RTFM is usually the last thing I do.
> that's quite a bad idea!
> Reading the manual is often the first thing i do. ;)
So far, your asking how to install grub, indicates otherwise.
>
>> As an Oh, By The Way,
>> I usually do not give answers unless I feel it is beyond the expertise
>> of the poster. I try teach how to catch the fish instead of catching,
>> preparing, cutting, and hand feeding the fish to the poster.
> well said, but that's not what i see in your posts.
Of course not. I can not get you past the first step. You know,
bring materials to class which can be used to catch this particular fish.
> It seems that my above statement touched your feelings a lot.
Not a bit. Just wanted you and the lurkers to know where I am coming from.
> then after i had to leave that computer to its owner.
Since I figured you were a slackware user, and latest slackware did not
give grub as an option, I was pretty sure it was someone else's system.
After that I wanted to make sure we could boot either system before
switching to the new copy.
> gave up about grub.
Yeah, was a little worried you might install lilo and the user might
become DOA on the first kernel update sent to their system.
> I'm planning of course to be back in it some day
> just because i think i definitely need to know how it works,
Yes, I was a lilo user up until about a year ago. Other distributions
were not offering lilo during install. In a multi-boot setup, there is
a feature to make life much easier during kernel updates.
Other tricks with fstab can make a format and a full restore from
backup run out of the box instead you having to get in there and
making the full backup run.
> So, here I'm not fighing to solve the problem, but to make you
> understand that you are damn dumb!!! brain damaged, abnormal...
OK, everyone is entitled to their own stupid opinion.
So far you have been the stupid person.
> The only fact that you asked me in you last post which errors i got
> tells really a lot. you're totally off.
Now your acting dumb.
> anyway, your post i'm replying right now is too long, i'll probably
> read it in the coming days, but for now i stop here
If your future reply is anything like this post, it would be a waste
of your time. Don't get me wrong, I do appreciate the smiles and grins
you have provided.
> An advice: take rest. be far from stuff.
Oh, no I try to help people help themselves for rest and relaxation.
Running across someone like you just makes my day. It beats reading
the funny pages. It also shows the newbie lurkers what not to do when
someone it trying to solve their problem.
You have a good day.
Unruh
>On Sat, 23 Aug 2008 16:42:46 +0000, Bit Twister wrote:
>> On Sat, 23 Aug 2008 08:15:36 -0700 (PDT), heavytull wrote:
>>>>
>>> yes you mentioned;
>>> but i have read it long ago. Here I didn't feel I needed to give more
>>> info.
>>
>> You really need to go back and read
>> http://www.catb.org/~esr/faqs/smart-questions.html
>>
>It seems you're the kind of guy who never use common sence. you always
>need to read instructions somewhere to do anything. Even simple things.
It seems you are the kind of guy that asks for help and then starts
demanding things of your helper. YOu want help. You need to supply the
helper with the information needed to help you.
>> What you feel is un-necessary information may be necessary information
>> to the person trying to help you with your problem.
>>
>>> I think giving you the distro i'm running on that pc and the kernel
>>> version is useless because it is a matte with grub only.
>>
>> See, it is not just distro/verison needed for a problem. Had you
>> provided fstab info for the current/new partition
>ok now you ask the information you need.
>tha's a thing but as the issue is this is unneeded to tell anyone.
???
>>, which loader running,
>grub of course i told that in very first post, read it back.
>> contents of new/old grug stanza,
>what do you mean by stanza? state?
>> what did not work,
>you're really lacking of brain! tha's really astonishing you're still on.
>I'm not offending you here, but that's really what I feel
>look, i'm summarizing the issue here again:
Good. Precisely what you need to do.
>1.I rsynced (with a live linux) a logical partition data (a linux) on a
>newly created partition on the same primary partition (all ext3).
>you get it?
No. That sentence does not really make gramatical sense. Do you mean you
rsynced the contents of one linux partition onto a new partition?
>IOW:
>I have a computer on which there is (among others) a primary partition
You eitehr have primary or logical. Or did you mean you had an extended
partition on which was a logical partition?
>with a logical one in it which holds a linux. I created a new logical
>partition in the same primary partition. both are ext3. Then I
partition on the same partition? Or again did you mean on the same extended
partition?
>synchronised the data of the new partition with the old one holding a
>linux with a live linux and rsync.
What is a linus with a live linux and rsync? Or did you mean you booted
from a live CD, and from there used rsync to copy the old partition
contents to the new partition?
>now you got it!??? :-|
No I am not at all sure I got it. I have had to try to disentable your grammer and have no faith I have done so accurately.
>2.The boot loader is Grub. I have never ever used it before, not even have
>smelled it. ok?
So why not use a bootloader you do know?
>my request: give me some straigh foreward instructions to make grub
Do you mean straight-forward?
>loading the linux on the new logical partition instead of the old one.
You mean you want to boot from teh new partition?
>that's all. extra information is unneeded. anyway if any wanted, he should
" I have no idea what I am doing but I know what information others need to
help me." Sheesh.
>have asked.
>extra comments: I emphasized that i was using logical partitions because
>at my knowledge some boot loaders can only load one logical partition in a
>primary one and only the first one in it.
No boot loader under linux does that. Maybe windows does.
Except I believe Windows can only boot from a primary partition not a
logical one.
>ALA I didn't mention here any detail about the grub config file or
>anything else you should assume that everything is working well with the
>old partition. So you don't need to ask whether it's sunny or not or
>whether the grass is growing or not.
Do you want help or do you just want to bluster and yell at people who are
trying to help you?
>Also don't ask why i rsynced a linux to a new logical partition on the
>same primary one because, first, you don't need to know, second, it's a
>bit too long to me to explain.
>It's seems quite clear to me. You should take rest.
Good. Then you do not need help. It is clear to you so go off and do it,
and stop bothering people here.
>> If Mandriva Linux, I would point you to the Mandriva Control Center's
>> Boot section.
>you should go back to MSwin
>>It would make changes to grub's config file and update the
>> mbr. No sweat.
>>
>with lilo I always touch the lilo.conf and run lilo, and never sweated.
So. Use lilo. Mandriva contains lilo.
>>
>> Yes, but tells us nothing. We have no idea what you did, if you did it
>> right,
>don't worry about that.
we are not. we are trying to help. You apparently do not want help.
>Do you wonder everyday whether the postman's bicycle is OK so he can
>deliver you your mails.
If he asks for my help, I may. If he does not then I do not care. You ask
for help and then yell at people who try to give you help.
>man, ALA i didn't mention any problem you worry for nothing.
>> With no error message
>why the hell you want error messages????
>go straigh into a concrete wall and knock your head, then you'll get error
>messages straight in your brain.
Goodbye. I sure do not want to help you.
>>>> Install grub in the mbr.
>>>>
>>>>
>> All right, you finally provide ONE piece of required information.
>that's seems to me quite obvious.
>> Glad to hear that. :-D
>forget about it, just be glad you're alive. With so damaged brain that's
>really lucky.
>>> FIRST try to understand my question.
>>
>> I understood your question,
>you're too off to do.
>> I just do not know exactly what your problem
>find out your problem first.
>> is. With this last post, I think you are telling me you cannot boot the
>> new partition using the current grub boot loader.
>>
>no, you're really damaged.
>> I do not know if it is a grub problem, or problem in the new partition.
>>
>shut up
>...
Fine. You are now in my killfile.