2 p.m.
I heard that it could happen in FC5, or FC6, but is there some more
official timeframe?
5:41 p.m.
Paul Howarth wrote:
On Sun, 2005-09-11 at 14:00 -0500, Reshat Sabiq wrote:
>I heard that it could happen in FC5, or FC6, but is there some more
>official timeframe?
>
>
It's be in FC shortly after it makes it into the mainstream kernel I
should think.
Paul.
I thought it's already included with kernel.org kernels. Isn't it?
5:48 p.m.
Reshat Sabiq wrote:
Paul Howarth wrote:
>On Sun, 2005-09-11 at 14:00 -0500, Reshat Sabiq wrote:
>
>
>>I heard that it could happen in FC5, or FC6, but is there some more
>>official timeframe?
>>
>>
>
>It's be in FC shortly after it makes it into the mainstream kernel I
>should think.
>
>Paul.
>
>
I thought it's already included with kernel.org kernels. Isn't it?
No. The in kernel implementation is a different one and is already
enabled in the development version of Fedora
regards
Rahul
10:02 p.m.
Rahul Sundaram wrote:
No. The in kernel implementation is a different one and is already
enabled in the development version of Fedora
regards
Rahul
Are you referring to suspend1? Are you referring to FC5 development
pipeline? I'd be happy w/ that one too, as long as works. ;)
Thanks.
10:02 p.m.
Reshat Sabiq wrote:
Rahul Sundaram wrote:
> No. The in kernel implementation is a different one and is already
> enabled in the development version of Fedora
>
> regards
> Rahul
Are you referring to suspend1? Are you referring to FC5 development
pipeline? I'd be happy w/ that one too, as long as works. ;)
Thanks.
Yes and yes but the development version requires more testing for it to
be enabled in the final FC5 release. Hop in and participate if you have
time
regards
Rahul
1:58 p.m.
Rahul Sundaram wrote:
Yes and yes but the development version requires more testing for it
to be enabled in the final FC5 release. Hop in and participate if you
have time
regards
Rahul
I'm not sure if i'll have time for that. But hypothetically speaking,
how does one go about installing the development release? I'm not seeing
isos for download. Do people install FC4, and then run yum from specific
Development sources?
Also, testing suspend to disk shouldn't be very dangerous for my
harddrive, i guess. The worst thing that could happen is a crash during
re-boot, which one should be able to fix by running a rescue CD, correct?
Thanks.
2:21 p.m.
Reshat Sabiq wrote:
Rahul Sundaram wrote:
> Yes and yes but the development version requires more testing for it
> to be enabled in the final FC5 release. Hop in and participate if
> you have time
>
> regards
> Rahul
I'm not sure if i'll have time for that. But hypothetically speaking,
how does one go about installing the development release? I'm not
seeing isos for download. Do people install FC4, and then run yum from
specific Development sources?
See http://fedoraproject.org/wiki/Docs/Drafts/TestersGuide
Also, testing suspend to disk shouldn't be very dangerous for my
harddrive, i guess. The worst thing that could happen is a crash
during re-boot, which one should be able to fix by running a rescue
CD, correct?
It shouldnt cause any hardware problems. Use a dedicated system.
subscribe to the fedora-test list, read the archives and post queries
there. Alternatively there is a third party website providing software
suspend enabled kernels which was recently referred in the
fedora-desktop list. This might work for you. You are on your own with
this one though
http://mhensler.de/swsusp/index_en.php
regards
Rahul
10:48 p.m.
Rahul Sundaram wrote:
Reshat Sabiq wrote:
> Rahul Sundaram wrote:
>
>> Yes and yes but the development version requires more testing for it
>> to be enabled in the final FC5 release. Hop in and participate if
>> you have time
>>
>> regards
>> Rahul
>
> I'm not sure if i'll have time for that. But hypothetically speaking,
> how does one go about installing the development release? I'm not
> seeing isos for download. Do people install FC4, and then run yum
> from specific Development sources?
See http://fedoraproject.org/wiki/Docs/Drafts/TestersGuide
Tried it out on my new laptop: both suspend and hibernate hang while
shutting down. I'll try to check the logs some time.
I'm hesitant to spend any time on suspend1, cause i have the impression
that it's gonna get overwritten by suspend2 within about a year. Is that
correct? If so, it might be worse just sitting it out, in my case anyway.
> Also, testing suspend to disk shouldn't be very dangerous for
my
> harddrive, i guess. The worst thing that could happen is a crash
> during re-boot, which one should be able to fix by running a rescue
> CD, correct?
It shouldnt cause any hardware problems. Use a dedicated system.
subscribe to the fedora-test list, read the archives and post queries
there. Alternatively there is a third party website providing software
suspend enabled kernels which was recently referred in the
fedora-desktop list. This might work for you. You are on your own with
this one though
http://mhensler.de/swsusp/index_en.php
Yes, i am aware of it, just don't trust the guy. I'm kidding. :)
9:22 a.m.
on my thinkpad r51 swsusp2 works great.
2005/10/25, Reshat Sabiq <sabiq(a)csociety.org>:
Rahul Sundaram wrote:
> Reshat Sabiq wrote:
>
>> Rahul Sundaram wrote:
>>
>>> Yes and yes but the development version requires more testing for it
>>> to be enabled in the final FC5 release. Hop in and participate if
>>> you have time
>>>
>>> regards
>>> Rahul
>>
>> I'm not sure if i'll have time for that. But hypothetically speaking,
>> how does one go about installing the development release? I'm not
>> seeing isos for download. Do people install FC4, and then run yum
>> from specific Development sources?
>
>
> See http://fedoraproject.org/wiki/Docs/Drafts/TestersGuide
Tried it out on my new laptop: both suspend and hibernate hang while
shutting down. I'll try to check the logs some time.
I'm hesitant to spend any time on suspend1, cause i have the impression
that it's gonna get overwritten by suspend2 within about a year. Is that
correct? If so, it might be worse just sitting it out, in my case anyway.
>> Also, testing suspend to disk shouldn't be very dangerous for my
>> harddrive, i guess. The worst thing that could happen is a crash
>> during re-boot, which one should be able to fix by running a rescue
>> CD, correct?
>
>
>
> It shouldnt cause any hardware problems. Use a dedicated system.
> subscribe to the fedora-test list, read the archives and post queries
> there. Alternatively there is a third party website providing software
> suspend enabled kernels which was recently referred in the
> fedora-desktop list. This might work for you. You are on your own with
> this one though
>
> http://mhensler.de/swsusp/index_en.php
Yes, i am aware of it, just don't trust the guy. I'm kidding. :)
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
12:58 a.m.
New subject: Files for a tar (FC3)
For a few days i've trying to figure out how to make backup of my machine.
Since i have to duplicate it, i thought on tar'ing directories so i can
store untar them on the other mahcine, (wich is far away from this one) and
store it to have a safe copy.
But i still cannot tar var directory. In particular i have lots of problems
with /var/named/chroot/proc wich is filled with an incredible ammount of
stuff, like:
dr-xr-xr-x 5 root root 0 sep 12 01:15 1
dr-xr-xr-x 5 root root 0 sep 12 01:15 12
dr-xr-xr-x 5 root root 0 sep 12 01:15 1407
dr-xr-xr-x 5 root root 0 sep 12 01:15 14559
dr-xr-xr-x 5 root root 0 sep 12 01:15 14561
dr-xr-xr-x 5 cyrus mail 0 sep 12 01:15 14833
dr-xr-xr-x 5 cyrus mail 0 sep 12 01:15 14866
dr-xr-xr-x 5 named named 0 sep 12 01:15 15099
dr-xr-xr-x 5 root root 0 sep 12 01:15 154
dr-xr-xr-x 5 root root 0 sep 12 01:15 155
dr-xr-xr-x 5 root root 0 sep 12 01:15 156
dr-xr-xr-x 5 root root 0 sep 12 01:15 157
dr-xr-xr-x 5 root root 0 sep 12 01:15 158
dr-xr-xr-x 5 cyrus mail 0 sep 12 01:15 15956
dr-xr-xr-x 5 cyrus mail 0 sep 12 01:15 15985
dr-xr-xr-x 5 cyrus mail 0 sep 12 01:15 16018
dr-xr-xr-x 5 root root 0 sep 12 01:15 19742
dr-xr-xr-x 5 apache apache 0 sep 12 01:15 19821
dr-xr-xr-x 5 apache apache 0 sep 12 01:15 19822
dr-xr-xr-x 5 apache apache 0 sep 12 01:15 19823
dr-xr-xr-x 5 apache apache 0 sep 12 01:15 19824
dr-xr-xr-x 5 apache apache 0 sep 12 01:15 19825
dr-xr-xr-x 5 apache apache 0 sep 12 01:15 19826
dr-xr-xr-x 5 apache apache 0 sep 12 01:15 19827
dr-xr-xr-x 5 apache apache 0 sep 12 01:15 19828
dr-xr-xr-x 5 root root 0 sep 12 00:08 2
dr-xr-xr-x 5 root root 0 sep 12 01:15 2036
dr-xr-xr-x 5 root root 0 sep 12 01:15 21280
dr-xr-xr-x 5 root root 0 sep 12 01:15 21282
dr-xr-xr-x 5 root root 0 sep 12 01:15 21324
dr-xr-xr-x 5 smmsp smmsp 0 sep 12 01:15 21332
dr-xr-xr-x 5 cyrus mail 0 sep 12 01:15 22796
dr-xr-xr-x 5 root root 0 sep 12 01:15 22805
dr-xr-xr-x 5 root root 0 sep 12 01:15 22806
dr-xr-xr-x 5 root root 0 sep 12 01:15 22807
dr-xr-xr-x 5 root root 0 sep 12 01:15 22808
dr-xr-xr-x 5 root root 0 sep 12 01:15 22809
dr-xr-xr-x 5 root root 0 sep 12 01:15 245
(resumed)
-r--r--r-- 1 root root 0 sep 12 01:15 buddyinfo
dr-xr-xr-x 5 root root 0 sep 1 15:29 bus
-r--r--r-- 1 root root 0 sep 12 01:15 cmdline
-r--r--r-- 1 root root 0 sep 12 01:15 cpuinfo
-r--r--r-- 1 root root 0 sep 12 01:15 crypto
-r--r--r-- 1 root root 0 sep 12 01:15 devices
-r--r--r-- 1 root root 0 sep 12 01:15 diskstats
-r--r--r-- 1 root root 0 sep 12 01:15 dma
dr-xr-xr-x 2 root root 0 sep 12 01:15 driver
-r--r--r-- 1 root root 0 sep 12 01:15 execdomains
-r--r--r-- 1 root root 0 sep 12 01:15 fb
-r--r--r-- 1 root root 0 sep 12 01:15 filesystems
dr-xr-xr-x 3 root root 0 sep 12 01:15 fs
dr-xr-xr-x 4 root root 0 sep 12 01:15 ide
-r--r--r-- 1 root root 0 sep 12 01:15 interrupts
-r--r--r-- 1 root root 0 sep 12 01:15 iomem
-r--r--r-- 1 root root 0 sep 12 01:15 ioports
dr-xr-xr-x 23 root root 0 sep 12 01:15 irq
-r--r--r-- 1 root root 0 sep 12 01:15 kallsyms
-r-------- 1 root root 536285184 sep 12 01:15 kcore
-r--r--r-- 1 root root 0 sep 12 01:15 keys
-r--r--r-- 1 root root 0 sep 12 01:15 key-users
-r-------- 1 root root 0 sep 1 19:29 kmsg
-r--r--r-- 1 root root 0 sep 12 01:15 loadavg
-r--r--r-- 1 root root 0 sep 12 01:15 locks
-r--r--r-- 1 root root 0 sep 12 01:15 mdstat
-r--r--r-- 1 root root 0 sep 12 01:15 meminfo
-r--r--r-- 1 root root 0 sep 12 01:15 misc
-r--r--r-- 1 root root 0 sep 12 01:15 modules
lrwxrwxrwx 1 root root 11 sep 12 01:15 mounts -> self/mounts
-rw-r--r-- 1 root root 0 sep 1 15:29 mtrr
dr-xr-xr-x 5 root root 0 sep 2 00:58 net
-r--r--r-- 1 root root 0 sep 12 01:15 partitions
-r--r--r-- 1 root root 0 sep 12 01:15 pci
lrwxrwxrwx 1 root root 64 sep 11 23:45 self -> 22809
-rw-r--r-- 1 root root 0 sep 12 01:15 slabinfo
-r--r--r-- 1 root root 0 sep 12 01:15 stat
-r--r--r-- 1 root root 0 sep 12 01:45 swaps
dr-xr-xr-x 9 root root 0 sep 1 19:29 sys
--w------- 1 root root 0 sep 12 01:45 sysrq-trigger
dr-xr-xr-x 2 root root 0 sep 12 01:45 sysvipc
dr-xr-xr-x 4 root root 0 sep 12 01:45 tty
-r--r--r-- 1 root root 0 sep 12 01:45 uptime
-r--r--r-- 1 root root 0 sep 12 01:45 version
-r--r--r-- 1 root root 0 sep 12 01:45 vmstat
The question is, is there any of this files-directories that i can erase to
make a tar? by now im having problems with some files from the -number-
directories like:
lrwxrwxrwx 1 root root 0 sep 12 01:57 exe
wich is not linked to anything
what can i do?
1:13 a.m.
New subject: Files for a tar (FC3)
On Monday 12 September 2005 01:58, Daniel Vogel wrote:
For a few days i've trying to figure out how to make backup of my
machine.
Since i have to duplicate it, i thought on tar'ing directories so i can
store untar them on the other mahcine, (wich is far away from this one) and
store it to have a safe copy.
But i still cannot tar var directory. In particular i have lots of problems
with /var/named/chroot/proc wich is filled with an incredible ammount of
stuff, like:
<snip>
The question is, is there any of this files-directories that i can
erase to
make a tar? by now im having problems with some files from the -number-
directories like:
lrwxrwxrwx 1 root root 0 sep 12 01:57 exe
wich is not linked to anything
what can i do?
Do you have a copy of proc mounted under /var/named/chroot/proc? It
sounds
like you're running a chrooted setup for bind?
Anyway, you can use the -X option in tar, point it to a file that contains all
unwanted directories... /var/spool /var/cache /var/lock /var/tmp are probably
some others you won't need on most boxes...
Peter.
1:22 a.m.
New subject: Files for a tar (FC3)
Peter Arremann wrote:
...
Anyway, you can use the -X option in tar, point it to a file that
contains all
unwanted directories... /var/spool /var/cache /var/lock /var/tmp are probably
some others you won't need on most boxes...
/var/spool/mail contains unread mails on a mailserver, not the best
candidate for the -X option...
/var/cache/samba contains important information for samba,
at least if it runs as a domain controller. Not a good
candidate either.
Mogens
--
Mogens Kjaer, Carlsberg A/S, Computer Department
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
Email: mk(a)crc.dk Homepage: http://www.crc.dk
1:18 a.m.
New subject: Files for a tar (FC3)
Daniel Vogel wrote:
For a few days i've trying to figure out how to make backup of my
machine.
Since i have to duplicate it, i thought on tar'ing directories so i can
store untar them on the other mahcine, (wich is far away from this one)
and store it to have a safe copy.
But i still cannot tar var directory. In particular i have lots of
problems with /var/named/chroot/proc wich is filled with an incredible
ammount of stuff, like:
...
The question is, is there any of this files-directories that i can erase
to make a tar? by now im having problems with some files from the
-number- directories like:
lrwxrwxrwx 1 root root 0 sep 12 01:57 exe
wich is not linked to anything
what can i do?
It looks like the /proc file system, don't try to back up this!
Make a backup of one file system at a time, e.g. separate backups
of /boot and /.
Use the "-l" option to tar to make it stay in the same file system:
tar cvlSf /dev/nrtape /boot
tar cvlSf /dev/nrtape /
etc.
It will complain about the leading /, this can be ignored.
The "-S" option makes tar handle sparse files more efficiently,
the file /var/log/lastlog is an example of this:
# tar cf /tmp/test1.tar /var/log/lastlog
# tar cSf /tmp/test2.tar /var/log/lastlog
# ls -l /tmp/test*.tar
-rw-r--r-- 1 root root 603996160 Sep 12 08:17 /tmp/test1.tar
-rw-r--r-- 1 root root 10240 Sep 12 08:17 /tmp/test2.tar
Mogens
PS: Don't steal another thread when sending mails to
a mailing list.
--
Mogens Kjaer, Carlsberg A/S, Computer Department
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
Email: mk(a)crc.dk Homepage: http://www.crc.dk
6817
days inactive
6862
days old
13 comments
7 participants
participants (7)
-
Daniel Vogel -
Mogens Kjaer -
Paul Howarth -
Peter Arremann -
Rahul Sundaram -
Reshat Sabiq -
Rudolf Kastl