Re: making more room in root partition for distribution upgrade

[Andy Smith]

Hello,

On Sun, May 20, 2018 at 07:59:48PM -0400, songbird wrote:
> Pascal Hambourg wrote:
> > Then LVM is your friend. You can create as many logical volumes as you 
> > like with minimal sizes and easily extend them when needed. This way you 
> > don't waste space in overprovisioning.
> 
>   added complexity for a simple system such as mine
> is rather pointless.

I hear that a lot from people who later find themselves doing
cosmetic surgery on their partition table because they weren't able
to initially size things properly.

It's quite a manageable bit of learning that pays dividends for the
whole rest of your time.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Please consider the environment before reading this e-mail.
 — John Levine

Re: making more room in root partition for distribution upgrade

[Richard Hector]

On 21/05/18 02:19, Abdullah Ramazanoğlu wrote:
> LVM greatly simplifies the partitioning part of the chore. But you still need
> to do the content management part[*] before shrinking / after enlarging an LV,
> don't you?
> 
> [*] backup, umount/swapoff, resize2fs/mkswap, mount/swapon, (unlikely but
> possibly: restore)

How much risk is there really these days in resizing a filesystem? I
don't think I've ever had a problem (that required restoring from
backup) in ~15 years. I usually use xfs for anything beyond the root fs.

The most significant problem I think I had was trying to take LVM
snapshots of an xfs filesystem - I don't know for sure if it was that
combination that was the problem, or if it was, whether it still is.

Richard



signature.asc
Description: OpenPGP digital signature

Re: lightdm (testing): Long waiting time after login

[Ben Caradoc-Davies]

On 19/05/18 13:07, Ben Caradoc-Davies wrote:

On 19/05/18 11:28, Ben Caradoc-Davies wrote:

The cause is xfce4-session. I will file a bug report.

Bug#899080: xfce4-session hangs in getrandom if crng not ready
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899080
I think this is a symptom of Bug#898088 in libbsd0:
Bug#898088: arc4random_buf() may block for a long time
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898088
xfce4-session uses IceGenerateMagicCookie and thus arc4random_buf to 
generate MIT-MAGIC-COOKIE-1.


Fixed in libbsd/0.8.7-1.1 on unstable:
https://tracker.debian.org/news/958795/accepted-libbsd-087-11-source-into-unstable/
"Switch Linux getrandom() usage to non-blocking mode, continuing to use 
fallback mechanims if unsuccessful. Closes: #898088"


I installed libbsd0_0.8.7-1.1_amd64.deb on a buster VM and it no longer 
hangs after lightdm credentials are entered (the xfce4-session hang 
reported in #899080):

http://ftp.debian.org/debian/pool/main/libb/libbsd/libbsd0_0.8.7-1.1_amd64.deb

Packages for other architectures here:
http://ftp.debian.org/debian/pool/main/libb/libbsd

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: making more room in root partition for distribution upgrade

[songbird]

Pascal Hambourg wrote:
> Le 20/05/2018 à 14:33, songbird a écrit :
>> 
>>in my last system i had many different partitions like that but
>> with the new system i decided that was wasting too much space and
>
> Then LVM is your friend. You can create as many logical volumes as you 
> like with minimal sizes and easily extend them when needed. This way you 
> don't waste space in overprovisioning.

  added complexity for a simple system such as mine
is rather pointless.

  i don't need to learn yet another layer for dealing 
with space issues.  i've already got it going, everything 
works as desired.

  if for some reason i do need such complexity i do
know where to find it.


  songbird

Re: Correct: System Thinks Hardware Clock is UTC

[Patrick Bartek]

On Sun, 20 May 2018 22:42:24 +0300 Abdullah Ramazanoğlu
 wrote:

> On Sun, 20 May 2018 12:10:01 -0700 Patrick Bartek said:
> 
> > On Sat, 19 May 2018 03:52:27 +0300 Abdullah Ramazanoğlu
> >  wrote:
> > 
> > > On Fri, 18 May 2018 17:13:07 -0700 Patrick Bartek said:
> > >   
> > > > I could use hwclock --set --date= with the
> > > > --localtime option, etc., to correct this but is there an
> > > > easier way?  
> > > 
> > > # dpkg-reconfigure tzdata
> > > 
> > > should do it, I think.  
> > 
> > tzdata sets the local time zone. Mine is correctly set  The
> > problem is the system "thinks" the hardware clock is set to UTC when
> > It's really set to local time. So, the time shown for my local time
> > zone is incorrect.
> > 
> > Anyway, thanks for your suggestion.
> 
> You are welcome. :)
> 
> So, your original idea of using "hwclock --set --date --localtime"
> seems to be the best way.

Simpliest fix.

> Alternatively, you might try replaying the question-answer sequence
> regarding RTC at install time.

Considered this, but just using hwclock was easier.

> ~$ dpkg -S /sbin/hwclock
> util-linux: /sbin/hwclock
> 
> Perhaps "dpkg-reconfigure util-linux" might cause the same
> install-time question be asked again (presumably along with other
> questions).

Thanks

B

Re: Correct: System Thinks Hardware Clock is UTC

[Steve McIntyre]

Patrick Bartek wrote:
>On Fri, 18 May 2018 20:59:25 -0500 David Wright
> wrote:
>
>> On Fri 18 May 2018 at 17:13:07 (-0700), Patrick Bartek wrote:
>> > Okay, it's my fault: I admit it. During the Base Only, Terminal-only
>> > install of Stretch, I clicked UTC instead of Local for the hardware
>> > clock time. Honestly, I thought the clock was set to UTC. Haven't
>> > installed any other OS on this system since Wheezy 5 years ago. So,
>> > now system time on Stretch is 7 hours earlier than it should be --
>> > difference between my time zone and Greenwich.
>> 
>> You could reboot and set the hardware clock in the CMOS/BIOS
>> to UTC time (coming up to 02:00 Saturday as I send this).
>
>Unfortunately, I have other OSes on this system and they are configured
>for the hardware clock set to local time. I need to keep it that way.
>
>Thanks, anyway.

The code in the Debian installer that deals with this [1] is:

---
# Update target system configuration for utc/localtime selection
utcfile=/target/etc/default/rcS

db_get clock-setup/utc
if [ "$RET" = true ]; then
if [ -e $utcfile ]; then
sed -i -e 's:^UTC="no":UTC="yes":' -e 's:^UTC=no:UTC=yes:' 
$utcfile
fi
if [ -e /target/etc/adjtime ]; then
sed -i -e 's:^LOCAL$:UTC:' /target/etc/adjtime
fi
OPT="--utc"
else
if [ -e $utcfile ]; then
sed -i -e 's:^UTC="yes":UTC="no":' -e 's:^UTC=yes:UTC=no:' 
$utcfile
fi
if [ -e /target/etc/adjtime ]; then
sed -i -e 's:^UTC$:LOCAL:' /target/etc/adjtime
fi
OPT="--localtime"
fi
---

If you're using systemd, then /etc/default/rcS is not likely to do
much. However, you may want to check in /etc/adjtime. My machine has
the following:

0.00 1521991744 0.00
1521991744
UTC

If yours is saying "UTC" there, then try "LOCAL" instead.

HTH!

[1] 
https://salsa.debian.org/installer-team/clock-setup/blob/master/finish-install.d/10clock-setup#L118

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Further comment on how I feel about IBM will appear once I've worked out
 whether they're being malicious or incompetent. Capital letters are forecast."
 Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html

Proposta de trobada el juny del 2018.

[Mònica Ramírez Arceda]

Hola,

A partir de la idea de l'Adrià de fer una trobada alternativa al SunCamp hem 
pogut concretar diverses propostes.

Aquí teniu l'enquesta per tal digueu quin/s format i dates us va bé: 
https://dudle.inf.tu-dresden.de/debian-cat-alt-suncamp-18-finalistes/

Per més informació sobre les propostes podeu consultar el wiki: 
https://wiki.debian.org/LocalGroups/DebianCat/201806altSunCamp

La data límit per contestar és el proper diumenge 27 de maig.

Vinga, animeu-vos!

Salut!

Re: making more room in root partition for distribution upgrade

[Pascal Hambourg]

Le 20/05/2018 à 21:34, Reco a écrit :

On Sun, May 20, 2018 at 08:48:05PM +0200, Pascal Hambourg wrote:

Le 20/05/2018 à 17:23, Reco a écrit :


On Sun, May 20, 2018 at 10:30:26AM -0400, Stefan Monnier wrote:


  lvextend --resizefs ...

will work without you needing to unmount the file-system.


You forgot to add 'unless you try to shrink the filesystem, or still use
reiserfs'.


Or use btrfs which supports online shrinking.


Two questions:

1) lvextend uses fsadm, fsadm does not know anything about brtfs.
How it's supposed to work?


Well then, until it does, use "btrfs filesystem resize" instead.
The important thing is that you do not have to unmount the filesystem.


2) Why does anyone would want to create btrfs inside the Logical Volume?


For the same reasons as any other type of contents.
Why not ? Some features of LVM and btrfs may appear redundant, but they 
do not operate at the same layer.

Re: Correct: System Thinks Hardware Clock is UTC

[Abdullah Ramazanoğlu]

On Sun, 20 May 2018 12:10:01 -0700 Patrick Bartek said:

> On Sat, 19 May 2018 03:52:27 +0300 Abdullah Ramazanoğlu
>  wrote:
> 
> > On Fri, 18 May 2018 17:13:07 -0700 Patrick Bartek said:
> >   
> > > I could use hwclock --set --date= with the --localtime
> > > option, etc., to correct this but is there an easier way?  
> > 
> > # dpkg-reconfigure tzdata
> > 
> > should do it, I think.  
> 
> tzdata sets the local time zone. Mine is correctly set  The
> problem is the system "thinks" the hardware clock is set to UTC when
> It's really set to local time. So, the time shown for my local time
> zone is incorrect.
> 
> Anyway, thanks for your suggestion.

You are welcome. :)

So, your original idea of using "hwclock --set --date --localtime" seems to be
the best way.

Alternatively, you might try replaying the question-answer sequence regarding
RTC at install time.

~$ dpkg -S /sbin/hwclock
util-linux: /sbin/hwclock

Perhaps "dpkg-reconfigure util-linux" might cause the same install-time
question be asked again (presumably along with other questions).

Regards
-- 
Abdullah Ramazanoğlu

Re: Correct: System Thinks Hardware Clock is UTC

[Patrick Bartek]

On Sat, 19 May 2018 10:37:39 +1000 Ben Finney 
wrote:

> Patrick Bartek  writes:
> 
> > I could use hwclock --set --date= with the --localtime
> > option, etc., to correct this but is there an easier way?
> 
> There is only one clock involved in this: the hardware clock.
> 
> By telling the operating system that your hardware clock is set to
> UTC, you have told the operating system how to *render* the hardware
> clock's time for your local time zone.
> 
> Setting the clock will set the hardware clock. By using a “set the
> clock” tool, you will set the hardware clock — but the clock-setting
> tool will take care of converting the time zone correctly.
>
> I think the generally-applicable advice is correct: tell the OS that
> your clock is set to UTC, and leave it to the operating system to
> figure out the weirdness of time zones.

Actually, the hardware clock has always been set to local time.  Had
to: Used to have Windows XP installed (this box is 11+ years old) as a
multi-boot with Linux, and as you know Windows needs the hardware
clock set to local to work correctly.  I've just keep it that way. .  

> So I think you've done the right thing: tell the OS to keep the
> hardware clock at UTC. Now you just need to tell it what the time
> is :-)

Actually, it's the other way around. hardware clock is local time, but
Stretch thinks it's UTC. (I have Wheezy on here to, but it's configured
correctly.)

Just going to use hwclock and the --localtime option to reset it.
Haven't been able to find any other way to do so.

> Assuming your machine is internet-connected, tell the operating system
> to keep your hardware clock in sync with the Network Time Protocol, by
> installing an NTP server. I can't recall what the default is; I use
> the ‘chrony’ package.

I alway install ntp, but I want everything timewise configured
appropriately before I do so.

Thanks for you advice.

B

Re: making more room in root partition for distribution upgrade

[Reco]

On Sun, May 20, 2018 at 08:48:05PM +0200, Pascal Hambourg wrote:
> Le 20/05/2018 à 17:23, Reco a écrit :
> > 
> > On Sun, May 20, 2018 at 10:30:26AM -0400, Stefan Monnier wrote:
> > > 
> > >  lvextend --resizefs ...
> > > 
> > > will work without you needing to unmount the file-system.
> > 
> > You forgot to add 'unless you try to shrink the filesystem, or still use
> > reiserfs'.
> 
> Or use btrfs which supports online shrinking.

Two questions:

1) lvextend uses fsadm, fsadm does not know anything about brtfs.
How it's supposed to work?

2) Why does anyone would want to create btrfs inside the Logical Volume?

Reco

Re: Correct: System Thinks Hardware Clock is UTC

[Patrick Bartek]

On Fri, 18 May 2018 20:59:25 -0500 David Wright
 wrote:

> On Fri 18 May 2018 at 17:13:07 (-0700), Patrick Bartek wrote:
> > Okay, it's my fault: I admit it. During the Base Only, Terminal-only
> > install of Stretch, I clicked UTC instead of Local for the hardware
> > clock time. Honestly, I thought the clock was set to UTC. Haven't
> > installed any other OS on this system since Wheezy 5 years ago. So,
> > now system time on Stretch is 7 hours earlier than it should be --
> > difference between my time zone and Greenwich.
> 
> You could reboot and set the hardware clock in the CMOS/BIOS
> to UTC time (coming up to 02:00 Saturday as I send this).

Unfortunately, I have other OSes on this system and they are configured
for the hardware clock set to local time. I need to keep it that way.

Thanks, anyway.

B

Re: Correct: System Thinks Hardware Clock is UTC

[Patrick Bartek]

On Sat, 19 May 2018 03:52:27 +0300 Abdullah Ramazanoğlu
 wrote:

> On Fri, 18 May 2018 17:13:07 -0700 Patrick Bartek said:
> 
> > I could use hwclock --set --date= with the --localtime
> > option, etc., to correct this but is there an easier way?
> 
> # dpkg-reconfigure tzdata
> 
> should do it, I think.

tzdata sets the local time zone. Mine is correctly set  The
problem is the system "thinks" the hardware clock is set to UTC when
It's really set to local time. So, the time shown for my local time
zone is incorrect.

Anyway, thanks for your suggestion.

B

Re: making more room in root partition for distribution upgrade

[Pascal Hambourg]

Le 20/05/2018 à 17:23, Reco a écrit :


On Sun, May 20, 2018 at 10:30:26AM -0400, Stefan Monnier wrote:


 lvextend --resizefs ...

will work without you needing to unmount the file-system.


You forgot to add 'unless you try to shrink the filesystem, or still use
reiserfs'.


Or use btrfs which supports online shrinking.

Re: making more room in root partition for distribution upgrade

[Pascal Hambourg]

Le 20/05/2018 à 16:19, Abdullah Ramazanoğlu a écrit :

On Sun, 20 May 2018 15:03:37 +0200 Pascal Hambourg said:

Le 20/05/2018 à 14:33, songbird a écrit :


in my last system i had many different partitions like that but
with the new system i decided that was wasting too much space and


Then LVM is your friend. You can create as many logical volumes as you
like with minimal sizes and easily extend them when needed. This way you
don't waste space in overprovisioning.


LVM greatly simplifies the partitioning part of the chore. But you still need
to do the content management part[*] before shrinking / after enlarging an LV,
don't you?

[*] backup, umount/swapoff, resize2fs/mkswap, mount/swapon, (unlikely but
possibly: restore)


Most common filesystems such as ext2/3/4, xfs or btrfs can be extended 
online while mounted. Extend the logical volume, then resize the 
filesystem, that's it. A swap cannot be extended while in use [*], but 
you can create and add a new swap instead. If you install with minimal 
logical volume sizes and leave plenty of free space in the volume group 
for future logical volume growth, you do not need to reduce existing 
logical volumes to gain free space.


[*] Actually it cannot be resized even when not in use, but it can be 
recreated with the same UUID and/or label, which provides about the same 
result as offline resizing would.

Re: Montar carpeta compartida automáticamente

[Javier ArgentinaBBAR]

Creo que ya encontré lo que buscaba:  autofs

http://web.mit.edu/rhel-doc/3/rhel-sag-es-3/s1-nfs-mount.html

El día 20 de mayo de 2018, 12:38, Javier Debian
 escribió:
>
>
> El 20/05/18 a las 02:07, remgasis remgasis escribió:
>>
>> El 19 de mayo de 2018, 14:53, Javier Debian > > escribió:
>>
>> Estimados:
>>
>> El entorno de escritorio que estoy usando es KDE Plasma 5 en la
>> computadora de casa.
>> He instalado otra, que quiero que, para cada usuario, poner en su
>> escritorio un ícono o algo, que acceda a la máquina principal, donde
>> tienen sus archivos.
>>
>> Ambos sistemas son Debian, y quiero hacerlo por NFS.
>>
>> La solución que se me ocurre es modificat en la máquina cliente
>> /etc/fstab para montarle a cada uno su carpèta remota.
>>
>> Pero lo que estoy pensando es que eso no se haga con todos al
>> inicio, si no sólo cuando un usuario inicie su sesión, se monte sólo
>> su carpeta remota.
>> Y se desmonte al cerrar la sesión.
>>
>> Éso es lo que no se me ocurre.
>>
>> Si alguno tiene una idea, se agradece.
>>
>> Gracias en adelanto.
>>
>> JAP
>>
>>
>> Todo lo que dices lo puedes hacer "y se ejecuta", no entiendo cuál es tu
>> duda.
>>
>
> A ver si se entiende:
>
> Si hago lo que sé hacer, que es poner en fstab un enlace a todas las
> carpetas de usuario remotas, la misma se montan, TODAS, al inicio del
> sistema.
>
> Lo que quiero, es que al arrancar el sistema, no se monte NINGUNA.
> Sólo lo haga la del usuario que en un momento dado se identifique, y monte
> SÓLO LA CARPETA REMOTA DE ÉL. Y si al cerrar la sesión, se desmonta, mejor.
>
> JAP

Re: Montar carpeta compartida automáticamente

[Javier Debian]

El 20/05/18 a las 02:07, remgasis remgasis escribió:
El 19 de mayo de 2018, 14:53, Javier Debian 
> 
escribió:


Estimados:

El entorno de escritorio que estoy usando es KDE Plasma 5 en la
computadora de casa.
He instalado otra, que quiero que, para cada usuario, poner en su
escritorio un ícono o algo, que acceda a la máquina principal, donde
tienen sus archivos.

Ambos sistemas son Debian, y quiero hacerlo por NFS.

La solución que se me ocurre es modificat en la máquina cliente
/etc/fstab para montarle a cada uno su carpèta remota.

Pero lo que estoy pensando es que eso no se haga con todos al
inicio, si no sólo cuando un usuario inicie su sesión, se monte sólo
su carpeta remota.
Y se desmonte al cerrar la sesión.

Éso es lo que no se me ocurre.

Si alguno tiene una idea, se agradece.

Gracias en adelanto.

JAP



> Todo lo que dices lo puedes hacer "y se ejecuta", no entiendo cuál es tu
> duda.
>

A ver si se entiende:

Si hago lo que sé hacer, que es poner en fstab un enlace a todas las 
carpetas de usuario remotas, la misma se montan, TODAS, al inicio del 
sistema.


Lo que quiero, es que al arrancar el sistema, no se monte NINGUNA.
Sólo lo haga la del usuario que en un momento dado se identifique, y 
monte SÓLO LA CARPETA REMOTA DE ÉL. Y si al cerrar la sesión, se 
desmonta, mejor.


JAP

Re: making more room in root partition for distribution upgrade

[Reco]

Hi.

On Sun, May 20, 2018 at 10:30:26AM -0400, Stefan Monnier wrote:
> > [*] backup, umount/swapoff, resize2fs/mkswap, mount/swapon, (unlikely but
> > possibly: restore)
> 
> lvextend --resizefs ...
> 
> will work without you needing to unmount the file-system.

You forgot to add 'unless you try to shrink the filesystem, or still use
reiserfs'.

Reco

Re: making more room in root partition for distribution upgrade

[Stefan Monnier]

> [*] backup, umount/swapoff, resize2fs/mkswap, mount/swapon, (unlikely but
> possibly: restore)

lvextend --resizefs ...

will work without you needing to unmount the file-system.


Stefan

Re: making more room in root partition for distribution upgrade

[Abdullah Ramazanoğlu]

On Sun, 20 May 2018 15:03:37 +0200 Pascal Hambourg said:
> Le 20/05/2018 à 14:33, songbird a écrit :
>> 
>>in my last system i had many different partitions like that but
>> with the new system i decided that was wasting too much space and  
> 
> Then LVM is your friend. You can create as many logical volumes as you 
> like with minimal sizes and easily extend them when needed. This way you 
> don't waste space in overprovisioning.

LVM greatly simplifies the partitioning part of the chore. But you still need
to do the content management part[*] before shrinking / after enlarging an LV,
don't you?

[*] backup, umount/swapoff, resize2fs/mkswap, mount/swapon, (unlikely but
possibly: restore)

Regards
-- 
Abdullah Ramazanoğlu

Re: making more room in root partition for distribution upgrade

[Pascal Hambourg]

Le 20/05/2018 à 14:33, songbird a écrit :


   in my last system i had many different partitions like that but
with the new system i decided that was wasting too much space and


Then LVM is your friend. You can create as many logical volumes as you 
like with minimal sizes and easily extend them when needed. This way you 
don't waste space in overprovisioning.

Re: making more room in root partition for distribution upgrade

[songbird]

Charlie S wrote:
> On Sat, 19 May 2018 09:16:43 -0500 ntrfug sent:
>
>> More than 20 years ago I began saving personal files to a different
>> partition than the OS.
>> 
>> I've used this system for Windows (when I started) and for more
>> flavors of Linux than I can remember. I did this so I could wipe the
>> root partition and reinstall without destroying my personal files.
>> 
>> I call it "files" and mount it on /home/ntrfug/Documents at boot.
>
>
>
>   After contemplation, my reply is:
>
> I thought that's what everyone did?
>
> Have a root, a home, a usr, a var, a tmp, graphics, etc etc.. partition.
>
> If ever there is a problem with the O/S and in the event it needs
> reinstallation. Install what O/S is desired and allow all the other
> partitions to be used, but not formatted.

...

  in my last system i had many different partitions like that but
with the new system i decided that was wasting too much space and
so with the new one i've gone to keeping everything in one 
partition per version i'm booting.

  that way i'm not wasting much space.  i have four partitions,
boot/efi, root for testing, root for stable and then swap.  i'm
not doing RAID or LVM or encryption as nothing i do is that
critical (i do have a separate backup device).

  i think the main point to consider though is what the system
is being used for.  in a production system where you may have
large areas of data, pictures, etc. which are apart from user
files and the OS then it makes sense to have things split apart
but for most people doing things on a home system maybe you 
don't need that complexity?

  for me the gain in space moving to the new system was great.
if i need to reorganize later chances are pretty good i'll just
buy an additional SSD as capacity should continue to improve
for about the same price.  i may not really have to buy a new
system again until this one burns out completely.  the SSDs
can be leapfrogged easily enough as time goes on if i run out
of SATA connections or slots.


  songbird

Re: CD Burning Software

[Joe]

On Sat, 19 May 2018 22:10:04 +0300
Abdullah Ramazanoğlu  wrote:

> On Sat, 19 May 2018 11:36:35 -0700 Herb Garcia said:
> 
> > I'm running Mate on my laptop. I don't see a CD/DVD burning software
> > that came with the build. Any suggestions?  
> 
> But beware of k3b's KDE dependencies.
> 

I was going to mention that, though it varies according to what you
have already. I like k3b, and also like konqueror as a backup browser,
so on my desktop machine I'm willing to tolerate the KDE stuff that
comes with them that I never use.

-- 
Joe

Re: Montar carpeta compartida automáticamente

[Galvatorix Torixgalva]

CREO que lo que necesitas es esto http://nfs.sourceforge.net/
​

Re: making more room in root partition for distribution upgrade

[Pascal Hambourg]

Le 18/05/2018 à 02:05, Mark Copper a écrit :



There was a day when a 10 gb partition seemed like plenty of space to leave
for the system but now it's not. An upgrade to Stretch appears to need more.


How do you know ?


Device BootStart   End   Sectors   Size Id Type
/dev/sda1  *2048  19531775  19529728   9.3G 83 Linux
/dev/sda2   19533822 312580095 293046274 139.8G  5 Extended
/dev/sda5   19533824  27578367   8044544   3.9G 82 Linux swap / Solaris
/dev/sda6   27580416 312580095 284999680 135.9G 83 Linux

$ cat /etc/fstab
# / was on /dev/sda1 during installation
# /home was on /dev/sda6 during installation
# swap was on /dev/sda5 during installation



This must be a FAQ. But there appear to be two ways forward.

1. Back-up /home, enlarge / partition, copy back-up back to new, smaller
/home partition (because /home will then start on a different cylinder so
data will be lost).


You will have to move/delete and re-create the swap too.
Gparted allows to resize and move an unused partition. Better have a 
backup though.



2. Carve out a new partition for /usr at end of disk which will free up
over 6 gb.


The Debian initramfs supports a separate /usr since Jessie.


$ du -h /var
...
598M/var

but

$ du -h /usr
...
4.2G/usr/share
6.5G/usr


What about the rest ? How much free space is available ?
Maybe the upgrade requires more space in order to download and store the 
new packages. Have you considered moving /var/cache/apt/archives to the 
/home partition (through a symlink or bind mount) so that downloaded 
packages do not use space in the / filesystem ?

Re: filter network traffic of KVM guests.

[Chris]

On Sun, 20 May 2018 00:15:12 +0300
Reco wrote:

> Not your only option (had my share of openvswitch, ditched the thing
> recently). I fact, I count four possible ways of doing it (and that's
> without the external hardware):

Thank you Reco!

Your replies were very helpful. I really appreciate them.

Chris

-- 
Papst Franziskus ruft zum Kampf gegen Fake News auf. Wir finden, der
Mann, der sich als Stellvertreter Christi ausgibt, von dem er
behauptet, dessen Mutter sei zeitlebens Jungfrau gewesen, er hätte über
Wasser gehen und selbiges in Wein verwandeln können, hat vollkommen
recht.

Re: installation "propre" sur portable installé en win10 ?

[Pierre L.]

Le 19/05/2018 à 00:22, Yann Serre a écrit :
> Le 18/05/2018 à 23:53, Jérôme a écrit :
>> Ben justement, la première chose a faire est de fabriquer un media
>> recovery (une clé usb de qualité ? Des DVD ?). Ça peut servir si un
>> jour elle
>> veut revendre son engin.
>
> C'est pour ça que mettre un disque neuf et d'archiver le disque
> d'origine avec les docs est le plus simple :) Même si ce HD d'origine
> est en parfaite condition, ce sera du temps de gagné et plus besoin de
> se prendre la tête sur un driver W10 absent...
>
Un bon vieux fichier Clonezilla du disque d'origine qui serait stocké
sur un disque externe ? Ca fonctionnerait avec ces histoires de EFI et
autres joyeusetés de maintenant ?



signature.asc
Description: OpenPGP digital signature