On 04/25/2014 04:13 AM, Bruce Dubbs wrote:
Ken Moffat wrote:
On Thu, Apr 24, 2014 at 08:02:58PM -0500, Bruce Dubbs wrote:
Ken Moffat wrote:
Thanks for the pointer (I have not built systemd at the moment,
still trying to sort out enough details for me to have a chance of
getting the whole
On Wed, Apr 23, 2014 at 12:09:26AM -0500, Bruce Dubbs wrote:
Ken Moffat wrote:
On Sun, Apr 20, 2014 at 03:19:45PM -0500, Bruce Dubbs wrote:
Last night I was trying to figure out how to set the dmesg log level in
systemd. It turns out that it can be done with sysctl and set:
Ken Moffat wrote:
On Wed, Apr 23, 2014 at 12:09:26AM -0500, Bruce Dubbs wrote:
Ken Moffat wrote:
On Sun, Apr 20, 2014 at 03:19:45PM -0500, Bruce Dubbs wrote:
Last night I was trying to figure out how to set the dmesg log level in
systemd. It turns out that it can be done with sysctl and
On Thu, Apr 24, 2014 at 08:02:58PM -0500, Bruce Dubbs wrote:
Ken Moffat wrote:
Thanks for the pointer (I have not built systemd at the moment,
still trying to sort out enough details for me to have a chance of
getting the whole thing working). But your use of sysctl looks
Ken Moffat wrote:
On Thu, Apr 24, 2014 at 08:02:58PM -0500, Bruce Dubbs wrote:
Ken Moffat wrote:
Thanks for the pointer (I have not built systemd at the moment,
still trying to sort out enough details for me to have a chance of
getting the whole thing working). But your use of sysctl
On Sun, Apr 20, 2014 at 03:19:45PM -0500, Bruce Dubbs wrote:
Last night I was trying to figure out how to set the dmesg log level in
systemd. It turns out that it can be done with sysctl and set:
kernel.printk = 4 4 1 7
where the numbers are console_loglevel, default_message_loglevel,
Ken Moffat wrote:
On Sun, Apr 20, 2014 at 03:19:45PM -0500, Bruce Dubbs wrote:
Last night I was trying to figure out how to set the dmesg log level in
systemd. It turns out that it can be done with sysctl and set:
kernel.printk = 4 4 1 7
where the numbers are console_loglevel,
Le 20/04/2014 23:26, Ken Moffat a écrit :
I've no idea what that refers to, but it doesn't matter. I know
that (at least) you and Pierre use jhalfs, and for me that is
unusable (/scratch is an nfs mount on/from my server, I _really_ do
not want to try to build there - by the same token, I
Pierre Labastie wrote:
Le 20/04/2014 23:26, Ken Moffat a écrit :
I've no idea what that refers to, but it doesn't matter. I know
that (at least) you and Pierre use jhalfs, and for me that is
unusable (/scratch is an nfs mount on/from my server, I _really_ do
not want to try to build
Le 21/04/2014 20:49, Bruce Dubbs a écrit :
Pierre Labastie wrote:
Le 20/04/2014 23:26, Ken Moffat a écrit :
I've no idea what that refers to, but it doesn't matter. I know
that (at least) you and Pierre use jhalfs, and for me that is
unusable (/scratch is an nfs mount on/from my server,
On Mon, Apr 21, 2014 at 03:28:01PM -0500, Bruce Dubbs wrote:
Pierre Labastie wrote:
Le 21/04/2014 20:49, Bruce Dubbs a écrit :
Pierre Labastie wrote:
Le 20/04/2014 23:26, Ken Moffat a écrit :
For convenience I also have scripts to mount and unmount virtual file
systems and to clean up
Ken Moffat wrote:
There is also a deeper difference - jhalfs was originally a tool for
builders. As an editor, my preference is to look at a new package
version on a completed system [ normally, just a DESTDIR ], see what
options I want to use [ e.g. omit static libs even in LFS, unless
BLFS Trac wrote:
Comment (by ken@…):
At the moment I'm still trying to absorb the systemd changes in LFS - my
own scripts now build a working LFS with eudev and _current_ LFS
bootscripts, and I'm fairly confident that the systemv-on-systemd build
will work when I test it. But I'm
On Sun, Apr 20, 2014 at 03:19:45PM -0500, Bruce Dubbs wrote:
BLFS Trac wrote:
Comment (by ken@…):
At the moment I'm still trying to absorb the systemd changes in LFS - my
own scripts now build a working LFS with eudev and _current_ LFS
bootscripts, and I'm fairly confident that
Em 20-04-2014 18:26, Ken Moffat escreveu:
On Sun, Apr 20, 2014 at 03:19:45PM -0500, Bruce Dubbs wrote:
BLFS Trac wrote:
My objective is to allow users that do not want to consider or even try
systemd to continue to do what they are already doing.
And you appear to be achieving that. I
Ken Moffat wrote:
On Sun, Apr 20, 2014 at 03:19:45PM -0500, Bruce Dubbs wrote:
My point was that _many_ people who build
LFS-svn will either copy and paste, or will already have their own
scripts. As you said (paraphrasing), this is a major change - those
of us with our own scripts will
On Sun, Apr 20, 2014 at 05:19:22PM -0500, Bruce Dubbs wrote:
Ken Moffat wrote:
Really, the only thing that's different through the end of Chapter 6 is
adding new packages. Skipping systemd and adding eudev is all that is
needed to do a straight traditional build (with a few packages from
Ken Moffat wrote:
On Sun, Apr 20, 2014 at 05:19:22PM -0500, Bruce Dubbs wrote:
Ken Moffat wrote:
Really, the only thing that's different through the end of Chapter 6 is
adding new packages. Skipping systemd and adding eudev is all that is
needed to do a straight traditional build (with a
On Sun, Apr 20, 2014 at 06:00:51PM -0500, Bruce Dubbs wrote:
Ken Moffat wrote:
On Sun, Apr 20, 2014 at 05:19:22PM -0500, Bruce Dubbs wrote:
However there is a method to their madness and
LFSers should be able to pick it up relatively quickly.
Don't get me started on what that
Ken Moffat wrote:
On Sun, Apr 20, 2014 at 06:00:51PM -0500, Bruce Dubbs wrote:
Ken Moffat wrote:
On Sun, Apr 20, 2014 at 05:19:22PM -0500, Bruce Dubbs wrote:
However there is a method to their madness and
LFSers should be able to pick it up relatively quickly.
Don't get me started
20 matches
Mail list logo
