Send plymouth mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freedesktop.org/mailman/listinfo/plymouth
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of plymouth digest..."
Today's Topics:
1. Re: Keyboard input / init + questions (Jerome Martin)
2. Re: Keyboard input / init + questions (Jerome Martin)
3. Re: Keyboard input / init + questions (Ray Strode)
4. Re: Keyboard input / init + questions (Ray Strode)
5. Re: Keyboard input / init + questions (Charlie Brej)
----------------------------------------------------------------------
Message: 1
Date: Mon, 27 Sep 2010 17:54:57 +0200
From: Jerome Martin <[email protected]>
Subject: Re: Keyboard input / init + questions
To: Ray Strode <[email protected]>
Cc: plymouth <[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
Mmmhh. I am not familiar with these options so I blindly copied them, but it
does not work. Only the kernel logs in dmesg, and same as before /dev/vcs1.
Here is my full commandline (tried both with and without plymouth:debug as I
suspect it might be redundant with plymouth.debug= ). An echo in /dev/kmsg
does show up in dmesg ok. I also tried moving the options on the line, still
no cigar.
[ 0.000000] Command line: initrd=/live/initrd.img boot=live noprompt
nouser splash vga=0x311 plymouth:debug plymouth.debug=file:/dev/kmsg
printk.time log_bug_len=1M BOOT_IMAGE=/live/vmlinuz
On Mon, Sep 27, 2010 at 4:18 PM, Ray Strode <[email protected]> wrote:
> Hi,
>
> On Mon, Sep 27, 2010 at 3:13 AM, Jerome Martin
> <[email protected]> wrote:
> > Fred here is using a patch very similar to my own, basically moving
> > the TIOCSCTTY of init out of plymouth's way.
> > As for the logs, I use a much stripped down system environment, with a ro
> > root and a COW on top of it that does not get mounted right away, so that
> > might explain the log issues.
> Oh, okay. So, if the file system might be read-only at the time
> plymouth quits, then you should be able to boot with
>
> plymouth.debug=file:/dev/kmsg printk.time log_bug_len=1M
>
> on your kernel command line and the debug output will go to "dmesg"
> along wth nice timestamps. Then you can just
>
> dmesg > output.txt
>
> and post it here.
>
> --Ray
>
--
J?r?me Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/plymouth/attachments/20100927/187de8da/attachment-0001.htm>
------------------------------
Message: 2
Date: Mon, 27 Sep 2010 18:13:06 +0200
From: Jerome Martin <[email protected]>
Subject: Re: Keyboard input / init + questions
To: Ray Strode <[email protected]>
Cc: plymouth <[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
OK, I removed my patches to get access to detail mode again and the tty is
filling with "couldn't write a log entry; log text too long" messages, but
there is also some other output that scrolls past too fast for me to get it.
On Mon, Sep 27, 2010 at 5:54 PM, Jerome Martin
<[email protected]>wrote:
> Mmmhh. I am not familiar with these options so I blindly copied them, but
> it does not work. Only the kernel logs in dmesg, and same as before
> /dev/vcs1. Here is my full commandline (tried both with and without
> plymouth:debug as I suspect it might be redundant with plymouth.debug= ). An
> echo in /dev/kmsg does show up in dmesg ok. I also tried moving the options
> on the line, still no cigar.
>
> [ 0.000000] Command line: initrd=/live/initrd.img boot=live noprompt
> nouser splash vga=0x311 plymouth:debug plymouth.debug=file:/dev/kmsg
> printk.time log_bug_len=1M BOOT_IMAGE=/live/vmlinuz
>
>
> On Mon, Sep 27, 2010 at 4:18 PM, Ray Strode <[email protected]> wrote:
>
>> Hi,
>>
>> On Mon, Sep 27, 2010 at 3:13 AM, Jerome Martin
>> <[email protected]> wrote:
>> > Fred here is using a patch very similar to my own, basically moving
>> > the TIOCSCTTY of init out of plymouth's way.
>> > As for the logs, I use a much stripped down system environment, with a
>> ro
>> > root and a COW on top of it that does not get mounted right away, so
>> that
>> > might explain the log issues.
>> Oh, okay. So, if the file system might be read-only at the time
>> plymouth quits, then you should be able to boot with
>>
>> plymouth.debug=file:/dev/kmsg printk.time log_bug_len=1M
>>
>> on your kernel command line and the debug output will go to "dmesg"
>> along wth nice timestamps. Then you can just
>>
>> dmesg > output.txt
>>
>> and post it here.
>>
>> --Ray
>>
>
>
>
> --
> J?r?me Martin
>
--
J?r?me Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/plymouth/attachments/20100927/fe78c559/attachment.htm>
------------------------------
Message: 3
Date: Mon, 27 Sep 2010 12:32:57 -0400
From: Ray Strode <[email protected]>
Subject: Re: Keyboard input / init + questions
To: Jerome Martin <[email protected]>
Cc: plymouth <[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=UTF-8
Hi,
On Mon, Sep 27, 2010 at 12:13 PM, Jerome Martin
<[email protected]> wrote:
> OK, I removed my patches to get access to detail mode again and the tty is
> filling with "couldn't write a log entry; log text too long" messages, but
> there is also some other output that scrolls past too fast for me to get it.
That's interesting. That suggests it's spewing *a lot* of text in one
ply_trace call (like more than 4k).
--Ray
------------------------------
Message: 4
Date: Mon, 27 Sep 2010 12:28:26 -0400
From: Ray Strode <[email protected]>
Subject: Re: Keyboard input / init + questions
To: Jerome Martin <[email protected]>
Cc: plymouth <[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=UTF-8
Hi,
On Mon, Sep 27, 2010 at 11:54 AM, Jerome Martin
<[email protected]> wrote:
> Mmmhh. I am not familiar with these options so I blindly copied them, but it
> does not work. Only the kernel logs in dmesg, and same as before /dev/vcs1.
> Here is my full commandline (tried both with and without plymouth:debug as I
> suspect it might be redundant with plymouth.debug= ). An echo in /dev/kmsg
> does show up in dmesg ok. I also tried moving the options on the line, still
> no cigar.
Oh sorry about the confusion. plymouth:debug and plymouth.debug are the same.
The former is what we use in 0.8.3 and earlier, the latter is the "new
format". I changed it to match closer with the kernel and other
things that touch kernel command line.
It just automatically turns ":" into "." before processing options.
If you don't specify an argument to plymouth debug it defaults to
/var/log/plymouth-debug.log. So you don't need or want both entries,
just the one with the file: argument.
I think i know why you aren't getting a log file. I just realized you
probably aren't ever "quitting" plymouthd since you're using it for
your menu thing. The log file isn't written out until exit time.
If you could run "plymouth quit" (as root) then it should dump things
to dmesg afterward.
--Ray
------------------------------
Message: 5
Date: Mon, 27 Sep 2010 19:01:43 +0100
From: Charlie Brej <[email protected]>
Subject: Re: Keyboard input / init + questions
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Sorry about the delay. I'll try and answer as many questions aimed for
me as I find, but I will probably have missed some.
On 09/25/2010 11:50 AM, Jerome Martin wrote:
> - Is there a way to call up an external binary from plymouth, like a
> system() function ? If not, I guess this would not be much to add, I can
> do it if you give me a proper pointer in your code (hints on the proper
> parse token to use, etc.).
Yes possible, although I would recommend using the on keystroke execute
command feature rather than letting a plugin run anything it likes. At
least that way you can be sure what state the system is in.
> - I desperately miss a couple of possibilities regarding strings, like
> determining a string length, and addressing strings as lists
> (a="foobar"; c=a[2]), thus making it possible to do strings
> transformations, iterate on strings, etc. Did I miss something ? Would
> that be hard to implement ?
Ah! So there are two functions that do this. "CharAt" and "SubString".
Somehow, I forgot to add these to the wiki.
"String".CharAt(2) => "r"
"String".SubString(2, 4) => "rin"
I think it is indexed starting at zero and the SubString takes inclusive
start and end pointers.
> - Last, but related to the previous, I currently keep an index on lists
> I create to knopw their length before iterating on them, but it would be
> nice to have a mylist.Len() method.
Are you just appending to a list by adding elements at increasing
indices? list[0] = "blah", list[1]="sdf"...
In which case you can just add a length element and keep that up to date
when you add/remove elements. (list.length++ or list["length"]++)
> Can any of the two previous points be done with a "list | []" method of
> sorts ?
Not really. That's a rather complex one to explain.
> Things using "\033"
There is no escaping supported in the scripted system apart from \n \"
and \0.
Ok, sorry, just found your patch. I'm split between \123 and \x123.
Are there other questions I have missed?
------------------------------
_______________________________________________
plymouth mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/plymouth
End of plymouth Digest, Vol 23, Issue 10
****************************************
