| 1 |
Peter Davoust wrote: |
| 2 |
> I don't know if this helps, but I usually run emerge <package> && init |
| 3 |
> 0 so it shuts off after it's finished (it would be nice if portage had |
| 4 |
> an --shutdownafter option, but oh well). The only problem is that if |
| 5 |
> there's an error in portage it won't shut down. |
| 6 |
|
| 7 |
Try "emerge foo; shutdown -h now" instead, that won't break if there is |
| 8 |
an error during the emerge and will shut down the computer. Of yourse |
| 9 |
you need to check if all packages really emerged the next day. |
| 10 |
|
| 11 |
> On 11/23/06, Thomas Rösner <Thomas.Roesner@××××××××××××××.de> wrote: |
| 12 |
>> |
| 13 |
>> ^Z and suspend-to-disk? |
| 14 |
>> |
| 15 |
|
| 16 |
No need for ^Z, suspend should be able to handle suspending during a |
| 17 |
running emerge and resume at the same point when coming back up. I've |
| 18 |
done this several times with suspend2 and it works just fine. |
Archives