| pmjdebru1jn | hi guys | 09:11 |
|---|---|---|
| pmjdebru1jn | I have a Ubuntu Precise system running in a large ramdisk (so no initrd/pivotroot construct) | 09:12 |
| pmjdebru1jn | the ramdisk is the main system | 09:12 |
| pmjdebru1jn | now when booting I get | 09:12 |
| pmjdebru1jn | init: Failed to create pty - disabling logging for job | 09:12 |
| pmjdebru1jn | from what I rather this is because /dev/pts probably isn't mounted yet (since this would usually be done by the initrd) | 09:12 |
| pmjdebru1jn | the question is what would be the best point to mount /dev/pts | 09:13 |
| pmjdebru1jn | I could create my on job | 09:13 |
| pmjdebru1jn | though on what event should it be started, what is most wise? | 09:13 |
| pmjdebru1jn | btw | 09:19 |
| pmjdebru1jn | the /dev/pts filesystem is mounted on this system | 09:19 |
| pmjdebru1jn | though I don't see where it gets mounted | 09:19 |
| jodh | pmjdebru1jn: this is a known limitation. /dev/pts is probably being mounted by mountalls built-in fstab (/lib/init/fstab). | 12:54 |
| pmjdebru1jn | ok | 13:11 |
| pmjdebru1jn | is there a way to workaround this? | 13:12 |
| pmjdebru1jn | by creating my own upstart job to mount /dev/pts? | 13:12 |
| pmjdebru1jn | at an earlier stage | 13:12 |
| jodh | mountall already starts as early as possible. The simplest solution is to boot with '--no-log' to disable job logging, since this is that part of Upstart that requires /dev/pts. | 13:20 |
| pmjdebru1jn | jodh: I read about that | 16:44 |
| pmjdebru1jn | just wondered if there was a way to deal with it differently | 16:44 |
| pmjdebru1jn | jodh: anyhow, thanks for your time | 16:44 |
| pmjdebru1jn | I'll go with --no-log then | 16:45 |
| JanC | I guess you could use alternative ways to run something before upstart | 17:46 |
| JanC | actually, it's quite easy to start a job before all other jobs, including mountall etc. | 17:58 |
| JanC | if that would be helpful... | 17:59 |
| JanC | pmjdebru1jn: ^^^ | 18:13 |
| pmjdebru1jn | well if mountall is already among the first job to start I guess it probably won't make a difference | 18:14 |
| pmjdebru1jn | still thanks for the thought | 18:14 |
| JanC | I never tried a setup like yours, but does it prevent loging for all jobs, or only for jobs started before /dev/pts is mounted? | 18:15 |
| pmjdebru1jn | I think only the first few | 18:15 |
| pmjdebru1jn | but I'd have to investigate to be sure | 18:15 |
| JanC | okay, then you could add "--startup-event pre-startup" to the kernel commandline and add a job that starts on the 'pre-startup' event which mounts /dev/pts (and maybe does other things?) and then emits the 'startup' event (which is the default event emitted on boot, so it should start whatever would normally be started) | 18:19 |
| JanC | that way, only this "pre-startup job" would not be logged | 18:19 |
| JanC | I think | 18:19 |
| JanC | ;) | 18:19 |
| JanC | mountall is started in parallel with other jobs, so it's normall some of them start before mountall has the chance to mount /dev/pts | 18:23 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!