On Jun 14 2019, Finn Thain <fth...@telegraphics.com.au> wrote: > On Thu, 13 Jun 2019, Andreas Schwab wrote: > >> On Jun 13 2019, Finn Thain <fth...@telegraphics.com.au> wrote: >> >> > IMHO these log messages are a bit silly -- >> > >> > [ **] (3 of 3) A start job is running for /dev/sda4 (1min 5s / 1min 36s) >> > ... >> > [ TIME ] Timed out waiting for device /dev/sda4. >> > [DEPEND] Dependency failed for /dev/sda4. >> > [DEPEND] Dependency failed for Swap. >> > ... >> > Activating swap /dev/sda4... >> > ... >> > [ 450.650000] Adding 524284k swap on /dev/sda4. Priority:-2 extents:1 >> > across:524284k FS >> > ... >> > [ OK ] Activated swap /dev/sda4. >> >> That just means that the timeout is maybe too short, > > Adding swap isn't that complicated.
It's not about adding swap, it's about adding the device node. You cannot run swapon until the device node exists. > The device isn't late, swapon() is late (compared to Debian 3 or Debian > 4). No, the device node shows up late. That's a user-space operation, carried out by udev. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
