On Apr 8, 2014, at 10:42 PM, xinglp wrote:
> wpa_supplicant support systemd already.
Yeah, I had it going with systemd long ago, but without systemd-
networkd. Looks like as long as you have all the configuration setup
properly it will work fine.
I haven't tried it with systemd-networkd, yet.
2014-04-09 10:12 GMT+08:00 William Harrington :
>
> On Apr 8, 2014, at 8:00 PM, xinglp wrote:
>
>>> Wouldn't it be the easiest way to let systemd configure the network
>>> interfaces?
>> It works well for my problemed vmware. I think we don't need ifup
>> ifdown script for systemd now.
>
> It's be
On Apr 8, 2014, at 8:00 PM, xinglp wrote:
>> Wouldn't it be the easiest way to let systemd configure the network
>> interfaces?
> It works well for my problemed vmware. I think we don't need ifup
> ifdown script for systemd now.
It's best to let systemd's networkd deal with all of the network.
2014-04-08 22:50 GMT+08:00 Sebastian Plotz :
> Am 08.04.2014 16:40, schrieb xinglp:
>> $ journalctl -b|grep enp
>> Apr 08 22:37:25 vm1 ifup[123]: Adding IPv4 address 192.168.3.1 to the
>> enp4s0 interface...Cannot find device "enp4s0"
>> Apr 08 22:37:26 vm1 systemd-udevd[173]: renamed network inter
2014-04-09 0:07 GMT+08:00 Bruce Dubbs :
> xinglp wrote:
>> $ journalctl -b|grep enp
>> Apr 08 22:37:25 vm1 ifup[123]: Adding IPv4 address 192.168.3.1 to the
>> enp4s0 interface...Cannot find device "enp4s0"
>> Apr 08 22:37:26 vm1 systemd-udevd[173]: renamed network interface eth0 to
>> enp4s0
>>
>
2014-04-08 22:50 GMT+08:00 Sebastian Plotz :
> Am 08.04.2014 16:40, schrieb xinglp:
>> $ journalctl -b|grep enp
>> Apr 08 22:37:25 vm1 ifup[123]: Adding IPv4 address 192.168.3.1 to the
>> enp4s0 interface...Cannot find device "enp4s0"
>> Apr 08 22:37:26 vm1 systemd-udevd[173]: renamed network inter
2014-04-09 0:07 GMT+08:00 Bruce Dubbs :
> xinglp wrote:
>> $ journalctl -b|grep enp
>> Apr 08 22:37:25 vm1 ifup[123]: Adding IPv4 address 192.168.3.1 to the
>> enp4s0 interface...Cannot find device "enp4s0"
>> Apr 08 22:37:26 vm1 systemd-udevd[173]: renamed network interface eth0 to
>> enp4s0
>>
>
xinglp wrote:
> $ journalctl -b|grep enp
> Apr 08 22:37:25 vm1 ifup[123]: Adding IPv4 address 192.168.3.1 to the
> enp4s0 interface...Cannot find device "enp4s0"
> Apr 08 22:37:26 vm1 systemd-udevd[173]: renamed network interface eth0 to
> enp4s0
>
> So it won't startup network.
Are you using /et
Am 08.04.2014 16:40, schrieb xinglp:
> $ journalctl -b|grep enp
> Apr 08 22:37:25 vm1 ifup[123]: Adding IPv4 address 192.168.3.1 to the
> enp4s0 interface...Cannot find device "enp4s0"
> Apr 08 22:37:26 vm1 systemd-udevd[173]: renamed network interface eth0 to
> enp4s0
>
> So it won't startup netw
$ journalctl -b|grep enp
Apr 08 22:37:25 vm1 ifup[123]: Adding IPv4 address 192.168.3.1 to the
enp4s0 interface...Cannot find device "enp4s0"
Apr 08 22:37:26 vm1 systemd-udevd[173]: renamed network interface eth0 to enp4s0
So it won't startup network.
--
http://linuxfromscratch.org/mailman/listin
matthew wrote:
> It's been a while since I looked at it, but which of systemd's
> utilities doesn't adhere to the 'do one job and do it well'
> philosophy?
I've already removed that verbage, but see below.
> I see systemd as a collection of utilities much like
> coreutils and util-linux. I'd agre
To: LFS Developers Mailinglist
Subject: [lfs-dev] systemd vs system V
I've been working on rewriting Chapter 7 to incorporate systemd. I've
come up with the following text in the introduction and would like
feedback. Thanks,
-- Bruce
7.1.1. System V
System V is the classic boot proc
Ken Moffat wrote:
> On Mon, Mar 31, 2014 at 01:26:46PM -0500, Bruce Dubbs wrote:
>>
>> The init program is controlled by the /etc/inittab file and is organized
>> into run levels that can be run by the user:
>>
>> 0 — halt
>> 1 — Single user mode
>> 2 — Multiuser, without networki
On Mon, Mar 31, 2014 at 01:26:46PM -0500, Bruce Dubbs wrote:
>
> The init program is controlled by the /etc/inittab file and is organized
> into run levels that can be run by the user:
>
> 0 — halt
> 1 — Single user mode
> 2 — Multiuser, without networking
> 3 — Full multiuse
Hello Bruce,
>> - Serial processing of boot tasks. This is related to the previous
> >> point. A delay in any process such as a file system check, will deleay
> >> the entire boot process.
>
Typo in the second line above. "will deleay" should read "will delay".
Regards
Nii Nai
--
http://li
On 03/31/2014 09:20 PM, Pierre Labastie wrote:
> Le 31/03/2014 20:26, Bruce Dubbs a écrit :
>> I've been working on rewriting Chapter 7 to incorporate systemd. I've
>> come up with the following text in the introduction and would like
>> feedback. Thanks,
>>
>>-- Bruce
>>
>> 7.1.1. System V
Le 31/03/2014 20:26, Bruce Dubbs a écrit :
> I've been working on rewriting Chapter 7 to incorporate systemd. I've
> come up with the following text in the introduction and would like
> feedback. Thanks,
>
>-- Bruce
>
> 7.1.1. System V
>
> System V is the classic boot process that has be
I've been working on rewriting Chapter 7 to incorporate systemd. I've
come up with the following text in the introduction and would like
feedback. Thanks,
-- Bruce
7.1.1. System V
System V is the classic boot process that has been used in Unix and
Unix-like systems such as Linux since ab
>> Can I try your patch please?
>>
>
> Archlinux also enables compat-libs, but as I said, they're useless on
> LFS since you don't actually link against them - they're necessary if
> you have programs linked to it and are going through a transition to the
> new lib.
>
> http://www.linuxfromscratch.
On 03/08/2014 01:04 AM, John Burrell wrote:
>>>
>>
>> systemd version of lfs has systemd-208. 210 is in terrible shape.
>> systemd-209 merged those libraries into one library - libsystemd.so and
>> all apps now link against it. --enable-compat-libs enable those
>> libraries and their pkg-config fil
>>
>
> systemd version of lfs has systemd-208. 210 is in terrible shape.
> systemd-209 merged those libraries into one library - libsystemd.so and
> all apps now link against it. --enable-compat-libs enable those
> libraries and their pkg-config files, but those libraries shouldn't be
> linked agai
On 03/07/2014 11:54 PM, John Burrell wrote:
> As 210 is the latest version, I thought I'd try it in the systemd version of
> LFS.
>
> Without gudev it doesn't install:
>
> /usr/lib/pkgconfig/libsystemd-daemon.pc
> /usr/lib/pkgconfiglibsystemd-journal.pc
> /usr/lib/pkgconfig/libsystemd-login.pc
>
As 210 is the latest version, I thought I'd try it in the systemd version of
LFS.
Without gudev it doesn't install:
/usr/lib/pkgconfig/libsystemd-daemon.pc
/usr/lib/pkgconfiglibsystemd-journal.pc
/usr/lib/pkgconfig/libsystemd-login.pc
Without these files dbus-1.8.0 won't recognise that systemd
On 01/04/2014 03:05 AM, Ivan Wagner wrote:
> On Fri, Jan 03, 2014 at 08:49:42PM +0100, Armin K. wrote:
>> Systemd branch doesn't yet have libcap-2.23 because of that reason. I
>> was waiting for fix to land in BLFS before I could merge the changes.
>> Revert to 2.22 or use patch from BLFS to fix th
On Fri, Jan 03, 2014 at 08:49:42PM +0100, Armin K. wrote:
> Systemd branch doesn't yet have libcap-2.23 because of that reason. I
> was waiting for fix to land in BLFS before I could merge the changes.
> Revert to 2.22 or use patch from BLFS to fix the issue.
>
> Also, Follow book, book good.
Wha
>
> Systemd branch doesn't yet have libcap-2.23 because of that reason. I
> was waiting for fix to land in BLFS before I could merge the changes.
> Revert to 2.22 or use patch from BLFS to fix the issue.
>
> Also, Follow book, book good.
>
Yes, but have to go off-piste for the real excitement - an
On 01/03/14 14:47, John Burrell wrote:
> I'm building the systemd version of LFS
>
> When I configure systemd-208 with libcap-2.23 I get:
>
> checking sys/capability.h usability... no
> checking sys/capability.h presence... no
> checking for sys/capability.h... no
> configure: error: *** POSIX caps
On 01/03/2014 08:47 PM, John Burrell wrote:
> I'm building the systemd version of LFS
>
> When I configure systemd-208 with libcap-2.23 I get:
>
> checking sys/capability.h usability... no
> checking sys/capability.h presence... no
> checking for sys/capability.h... no
> configure: error: *** POS
I'm building the systemd version of LFS
When I configure systemd-208 with libcap-2.23 I get:
checking sys/capability.h usability... no
checking sys/capability.h presence... no
checking for sys/capability.h... no
configure: error: *** POSIX caps headers not found
The file /usr/include/sys/capabil
.
>>>
>>> You can clone lfs-systemd book using svn co
>>> svn://svn.linuxfromscratch.org/LFS/branches/systemd
>>
>> A small request re. the svn cloning -
>>
>> When the book is downloaded using svn, it creates systemd/BOOK
>> which contains all the files except one dir.
>>
>> The directory .svn doe
John Burrell wrote:
> A small request re. the svn cloning -
>
> When the book is downloaded using svn, it creates systemd/BOOK
> which contains all the files except one dir.
>
> The directory .svn doesn't sit under BOOK, it's under systemd.
>
> Would you change it please so that .svn is under BOOK
On 12/24/2013 07:39 PM, John Burrell wrote:
>> Hello there,
>>
>> After many months since lfs systemd branch was created, I am pleased to
>> announce that I consider it being usable for everyone that wants to use it.
>>
>> I've managed to add missing bits to the branch today and doing that I've
>>
> Hello there,
>
> After many months since lfs systemd branch was created, I am pleased to
> announce that I consider it being usable for everyone that wants to use it.
>
> I've managed to add missing bits to the branch today and doing that I've
> finished what it was necessarry to bring it up to p
>On Sat, 21 Dec 2013 21:55:30 +0100
>"Armin K." wrote:
>
> Hello there,
>
> After many months since lfs systemd branch was created, I am pleased
> to announce that I consider it being usable for everyone that wants
> to use it.
>
> I've managed to add missing bits to the branch today and doing t
Le 21/12/2013 21:55, Armin K. a écrit :
> Hello there,
>
> After many months since lfs systemd branch was created, I am pleased to
> announce that I consider it being usable for everyone that wants to use it.
>
> I've managed to add missing bits to the branch today and doing that I've
> finished
Le 21/12/2013 22:27, Bruce Dubbs a écrit :
> Armin K. wrote:
>> Hello there,
>>
>> After many months since lfs systemd branch was created, I am pleased to
>> announce that I consider it being usable for everyone that wants to use it.
>>
>> I've managed to add missing bits to the branch today and do
On 12/21/2013 10:27 PM, Bruce Dubbs wrote:
[the very long post]
>
> Thanks for that Armin. One question. Do you know if it will build with
> jhalfs? I suspect one would only need to change the 'Loc of working
> copy', but I haven't tried it.
>
>-- Bruce
I don't know about jhalfs since
On 12/21/2013 02:55 PM, Armin K. wrote:
> Hello there,
>
> After many months since lfs systemd branch was created, I am pleased to
> announce that I consider it being usable for everyone that wants to use it.
>
> I've managed to add missing bits to the branch today and doing that I've
> finished wh
Armin K. wrote:
> Hello there,
>
> After many months since lfs systemd branch was created, I am pleased to
> announce that I consider it being usable for everyone that wants to use it.
>
> I've managed to add missing bits to the branch today and doing that I've
> finished what it was necessarry to
Hello there,
After many months since lfs systemd branch was created, I am pleased to
announce that I consider it being usable for everyone that wants to use it.
I've managed to add missing bits to the branch today and doing that I've
finished what it was necessarry to bring it up to par with curr
I actually largely agree with you technically. Though if sysd is being
modularized, taking it into LFS and experimenting with that might be
interesting.
The ad hominem attacks just aren't helping your argument. And I don't
really think they do much to encourage real technical discussions about a
c
> Date: Fri, 13 Dec 2013 21:06:17 +
> From: Kevin Lyda
> To: LFS Developers Mailinglist
> Subject: [lfs-dev] systemd discussions
>
> Dear children,
>
> I for one would appreciate it if the discussions about systemd would be
> solely about the technical issues and n
On Dec 13, 2013 2:06 PM, "Kevin Lyda" wrote:
>
> Dear children,
>
> I for one would appreciate it if the discussions about systemd would be
solely about the technical issues and not a contest to see who can be the
biggest prat.
>
> With much love and affection,
>
> Kevin
Reminds me of Linux 2.4
On Fri, Dec 13, 2013 at 09:06:17PM +, Kevin Lyda wrote:
> Dear children,
>
> I for one would appreciate it if the discussions about systemd would be
> solely about the technical issues and not a contest to see who can be the
> biggest prat.
>
> With much love and affection,
>
> Kevin
That
Dear children,
I for one would appreciate it if the discussions about systemd would be
solely about the technical issues and not a contest to see who can be the
biggest prat.
With much love and affection,
Kevin
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscr
akhiezer wrote:
> Hmmm. Wasn't gnome one of the main causes of blfs getting itself into a
> never-coherent-enough-for-release tailspin:
No, it was just a volume of changes and available editor time problem.
Even now, BLFS needs to update, on average, 4 packages a day. LFS has a
lot less churn a
> Date: Wed, 11 Dec 2013 17:14:45 -0600
> From: Bruce Dubbs
> To: LFS Developers Mailinglist
> Subject: Re: [lfs-dev] Systemd branch is alive
>
> Armin K. wrote:
> > On 12/11/2013 11:33 PM, Matt Burgess wrote:
> >> Hi all,
> >>
> >> Those of
> Date: Thu, 12 Dec 2013 23:45:50 -0800
> From: Nathan Coulson
> To: LFS Developers Mailinglist
> Subject: Re: [lfs-dev] Systemd branch is alive
>
.
.
> to systemd when you were previously working on it (Although sortof a
> love/hate relationship with it. I
On Wed, Dec 11, 2013 at 2:52 PM, Armin K. wrote:
> On 12/11/2013 11:33 PM, Matt Burgess wrote:
>> Hi all,
>>
>> Those of you who follow lfs-book will have seen some commits fly by from
>> Armin, who asked to be granted access to work on the systemd branch. As
>> I've been lacking time recently, a
Em 11-12-2013 20:14, Bruce Dubbs escreveu:
> Armin K. wrote:
>> On 12/11/2013 11:33 PM, Matt Burgess wrote:
>>> Hi all,
>>>
>>> Those of you who follow lfs-book will have seen some commits fly by from
>>> Armin, who asked to be granted access to work on the systemd branch. As
>>> I've been lacking
On Wednesday 11 December 2013 23:52:45 Armin K. wrote:
> For those that don't know, you can read systemd version of the book
> online at [1].
>
> Please note that I've just applied systemd specific changes to lfs
> development book which was the most current at the time, but didn't yet
> run any t
Armin K. wrote:
> On 12/11/2013 11:33 PM, Matt Burgess wrote:
>> Hi all,
>>
>> Those of you who follow lfs-book will have seen some commits fly by from
>> Armin, who asked to be granted access to work on the systemd branch. As
>> I've been lacking time recently, and lost a bit of motivation for
>>
On 12/11/2013 11:33 PM, Matt Burgess wrote:
> Hi all,
>
> Those of you who follow lfs-book will have seen some commits fly by from
> Armin, who asked to be granted access to work on the systemd branch. As
> I've been lacking time recently, and lost a bit of motivation for
> maintaining the branch
Hi all,
Those of you who follow lfs-book will have seen some commits fly by from
Armin, who asked to be granted access to work on the systemd branch. As
I've been lacking time recently, and lost a bit of motivation for
maintaining the branch myself, I was happy to accept the offer of help.
Welco
Christoph Vigano wrote:
> Hello guys,
>
> I just found the systemd version of the LFS guide the other day and I
> like the idea of providing this alternative init system in a separate guide.
>
> But it seems - so the IRC channel told me - that this guide won't be
> maintained anytime soon.
>
> As I
Hello guys,
I just found the systemd version of the LFS guide the other day and I
like the idea of providing this alternative init system in a separate guide.
But it seems - so the IRC channel told me - that this guide won't be
maintained anytime soon.
As I am using systemd actively under Arch L
Took me a while to figure out, but to enable a interface on startup
you need to enable it as so:
systemctl enable ifupdown@br0
But it also has the following in the ifupdown@service:
Requires=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
As br0 (Bridged device) is
All this dependencies, it's amazing and still it seems to be some missing.
I did not found any man page for example for systemd.
2013/5/27 Pierre Labastie
> Le 27/05/2013 11:45, Thierry Nuttens a écrit :
> > Hello Pierre,
> >
> > I did a try of your systemd based LFS. It's working quite impres
Le 27/05/2013 11:45, Thierry Nuttens a écrit :
> Hello Pierre,
>
> I did a try of your systemd based LFS. It's working quite impressive.
> Meanwhile I have a big question in my face. Do we really want that
> systemd is crawling everywhere. It's really a strange feeling I have
> to say. A lot of h
Hello Pierre,
I did a try of your systemd based LFS. It's working quite impressive.
Meanwhile I have a big question in my face. Do we really want that systemd
is crawling everywhere. It's really a strange feeling I have to say. A lot
of habits are change.
Have a nice day
Thierry
2013/5/19 Pier
Le 19/05/2013 19:39, Armin K. a écrit :
> On 05/19/2013 06:41 PM, Pierre Labastie wrote:
>> on the systemd page, there are configure options
>> --with-kbd-loadkeys=/bin/loadkeys \
>> --with-kbd-setfont=/bin/setfont \
>
> I have removed that yesterday iirc.
Right, sorry.
On 05/19/2013 06:41 PM, Pierre Labastie wrote:
> Hi,
>
> Don't know whether I should raise a ticket for the
> systemd branch. For now, I make this message about my
> last build (using tweaked jhalfs, which I'll commit soon, but I
> need a few more tests).
>
> I found 4 issues, the first one being e
On Sun, 2013-05-19 at 18:41 +0200, Pierre Labastie wrote:
> Hi,
>
> Don't know whether I should raise a ticket for the
> systemd branch. For now, I make this message about my
> last build (using tweaked jhalfs, which I'll commit soon, but I
> need a few more tests).
Hi Pierre,
Could you raise ti
Hi,
Don't know whether I should raise a ticket for the
systemd branch. For now, I make this message about my
last build (using tweaked jhalfs, which I'll commit soon, but I
need a few more tests).
I found 4 issues, the first one being easy to fix:
on the systemd page, there are configure options
Hi,
When building the systemd branch of LFS, one of the coreutils
tests fails:
FAIL: tests/df/skip-rootfs.sh
That test is skipped if `df' exits with nonzero code. This is
what happens on trunk LFS, because /etc/mtab is empty.
Now, on systemd branch, /etc/mtab is a symbolic link to
/proc/self/moun
On Tue, 2013-03-05 at 23:39 +0100, Pierre Labastie wrote:
> I guess the /etc/localtime link should be the other way around:
> ln -s /usr/share/zoneinfo/ /etc/localtime
>
> (and also could be ln -sv)
Thanks again! Fixed in r10196.
Regards,
Matt.
--
http://linuxfromscratch.org/mailman/listinf
I guess the /etc/localtime link should be the other way around:
ln -s /usr/share/zoneinfo/ /etc/localtime
(and also could be ln -sv)
Regards
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
On Sun, 2013-03-03 at 11:14 -0600, Randy McMurchy wrote:
> I agree completely with Pierre on this one. There really is no reason
> I can think of that XML::Parser cannot have its own page for package
> management simplicity.
I agree with Randy, Bruce, and half-with, half-against Pierre :-)
I thi
Armin K. wrote these words on 03/02/13 11:28 CST:
> Dana 2.3.2013 18:14, Pierre Labastie je napisao:
>> I do not understand why the above has been done.
>> I understand XML::Parser is a Perl module.
>> But glibc (for example) is a C library, and we do not
>> put it on the same page as GCC...
I agr
On Sat, 2013-03-02 at 20:29 +0100, Pierre Labastie wrote:
> There are (at least) to places in the systemd book
> where post install instructions are inside a
> tag.
>
> for dbus:
> dbus-uuidgen --ensure
>
> for systemd:
> systemd-machine-id-setup
>
> I suggest they are moved to a remap="config
Hi again,
Still trying to sort out issues with jhalfs
package management...
There are (at least) to places in the systemd book
where post install instructions are inside a
tag.
for dbus:
dbus-uuidgen --ensure
for systemd:
systemd-machine-id-setup
I suggest they are moved to a remap="configura
Le 02/03/2013 18:28, Armin K. a écrit :
> Dana 2.3.2013 18:14, Pierre Labastie je napisao:
>> Date: Fri Feb 15 10:17:18 2013
>> New Revision: 10154
>>
>> Log:
>> Merge XML::Parser into Perl page.
>>
>> Hi,
>>
>> I do not understand why the above has been done.
>> I understand X
Dana 2.3.2013 18:14, Pierre Labastie je napisao:
> Date: Fri Feb 15 10:17:18 2013
> New Revision: 10154
>
> Log:
> Merge XML::Parser into Perl page.
>
> Hi,
>
> I do not understand why the above has been done.
> I understand XML::Parser is a Perl module.
> But glibc (for exampl
Date: Fri Feb 15 10:17:18 2013
New Revision: 10154
Log:
Merge XML::Parser into Perl page.
Hi,
I do not understand why the above has been done.
I understand XML::Parser is a Perl module.
But glibc (for example) is a C library, and we do not
put it on the same page as GCC...
M
Dana 1.3.2013 22:34, John Burrell je napisao:
>>
>> $ cat /lib/systemd/system/mysqld.service
>> [Unit]
>> Description=MySQL Server
>> After=network.target
>>
>> [Service]
>> User=mysql
>> Group=mysql
>> ExecStart=/usr/bin/mysqld --pid-file=/var/run/mysqld/mysqld.pid
>> Restart=always
>> PrivateTmp=
>
> $ cat /lib/systemd/system/mysqld.service
> [Unit]
> Description=MySQL Server
> After=network.target
>
> [Service]
> User=mysql
> Group=mysql
> ExecStart=/usr/bin/mysqld --pid-file=/var/run/mysqld/mysqld.pid
> Restart=always
> PrivateTmp=true
>
> [Install]
> WantedBy=multi-user.target
>
> $ cat
On 03/01/2013 08:00 PM, John Burrell wrote:
> I installed lfs with systemd and encountered no problems at all - to my mild
> surprise.
>
> Encouraged by this, I've been adding blfs packages and have now come up
> against the question of starting various daemons.
>
> For example, I installed mysql
I installed lfs with systemd and encountered no problems at all - to my mild
surprise.
Encouraged by this, I've been adding blfs packages and have now come up against
the question of starting various daemons.
For example, I installed mysql and used the mysql.service file from Arch-Linux
as a g
Yeah, I think there were a couple of things out of place or missing. It's
been a while since I compiled LFS so was sort of fuddling through it
anyway. The post-LFS hint the and how-to someone posted in the blfs
mailing list helped a lot.
I'm about to try it again, this time in 32-bit. I'll write
On 02/15/2013 05:31 AM, cybertao wrote:
> I just finished building this, ironed out my mistakes (journald barfing
> because there's no machine-id is a good one!), and couldn't be more
> pleased with myself. And immensely grateful for all the work that went
> into this.
>
> Thanks.
>
>
I'm glad I'
On Fri, 15 Feb 2013 17:31:05 +1300, cybertao wrote:
> I just finished building this, ironed out my mistakes (journald barfing
> because there's no machine-id is a good one!), and couldn't be more
> pleased
> with myself. And immensely grateful for all the work that went into this.
Thanks for the
I just finished building this, ironed out my mistakes (journald barfing
because there's no machine-id is a good one!), and couldn't be more pleased
with myself. And immensely grateful for all the work that went into this.
Thanks.
On 6 February 2013 10:34, Matt Burgess wrote:
> Hi all,
>
> I'v
Matt Burgess wrote:
> On Wed, 2013-02-13 at 15:28 -0600, Bruce Dubbs wrote:
>> Matt Burgess wrote:
>>
>>>
>>> I think that's the problem. My host (Fedora 18) calls my eth0 device
>>> p5p1.
>>
>> What on earth are they doing? The link
>> http://www.freedesktop.org/wiki/Software/systemd/Predictable
On Wed, 2013-02-13 at 15:28 -0600, Bruce Dubbs wrote:
> Matt Burgess wrote:
>
> >
> > I think that's the problem. My host (Fedora 18) calls my eth0 device
> > p5p1.
>
> What on earth are they doing? The link
> http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
>
Matt Burgess wrote:
>
> I think that's the problem. My host (Fedora 18) calls my eth0 device
> p5p1.
What on earth are they doing? The link
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
indicates names starting with en. Without the en, it doesn't make
th
On Wed, 2013-02-13 at 14:03 -0600, Bruce Dubbs wrote:
> Armin K. wrote:
> > On 02/13/2013 08:46 PM, Bruce Dubbs wrote:
> >> Armin K. wrote:
> >>> lfs net-rules are prefixed with 70 while systemd net rules are prefixed
> >>> with 80. systemd net rules are ran *after* lfs ones and they basicaly
> >>>
Armin K. wrote:
> On 02/13/2013 08:46 PM, Bruce Dubbs wrote:
>> Armin K. wrote:
>>> lfs net-rules are prefixed with 70 while systemd net rules are prefixed
>>> with 80. systemd net rules are ran *after* lfs ones and they basicaly
>>> overwrite them.
>>
>> But 80-net-name-slot.rules is skipped inter
On 02/13/2013 08:46 PM, Bruce Dubbs wrote:
> Armin K. wrote:
>> lfs net-rules are prefixed with 70 while systemd net rules are prefixed
>> with 80. systemd net rules are ran *after* lfs ones and they basicaly
>> overwrite them.
>
> But 80-net-name-slot.rules is skipped internally if NAME!="" and we
Armin K. wrote:
> On 02/13/2013 08:16 PM, Matt Burgess wrote:
>> On Wed, 2013-02-13 at 13:01 -0600, Bruce Dubbs wrote:
>>> Thomas Trepl wrote:
Hi all,
you may have noticed or probably read in other articles that systemd
introduced a new device naming scheme starting with version
On 02/13/2013 08:16 PM, Matt Burgess wrote:
> On Wed, 2013-02-13 at 13:01 -0600, Bruce Dubbs wrote:
>> Thomas Trepl wrote:
>>> Hi all,
>>>
>>> you may have noticed or probably read in other articles that systemd
>>> introduced a new device naming scheme starting with version 197. Doing
>>> nothing
Matt Burgess wrote:
> On Wed, 2013-02-13 at 13:01 -0600, Bruce Dubbs wrote:
>> Thomas Trepl wrote:
>>> Hi all,
>>>
>>> you may have noticed or probably read in other articles that systemd
>>> introduced a new device naming scheme starting with version 197. Doing
>>> nothing
>>> will result in devi
On Wed, 2013-02-13 at 13:01 -0600, Bruce Dubbs wrote:
> Thomas Trepl wrote:
> > Hi all,
> >
> > you may have noticed or probably read in other articles that systemd
> > introduced a new device naming scheme starting with version 197. Doing
> > nothing
> > will result in device names like enp5s0 in
Thomas Trepl wrote:
> Hi all,
>
> you may have noticed or probably read in other articles that systemd
> introduced a new device naming scheme starting with version 197. Doing nothing
> will result in device names like enp5s0 instead of eth0.
It depends on the BIOS. Older systems will not produce
Hi all,
you may have noticed or probably read in other articles that systemd
introduced a new device naming scheme starting with version 197. Doing nothing
will result in device names like enp5s0 instead of eth0.
A simple way to prevent systemd (the udev part of it) to rename devices is to
cre
On Tue, Feb 5, 2013 at 1:34 PM, Matt Burgess
wrote:
> Hi all,
>
> I've just created a systemd branch for LFS. The intention behind this
> is to provide a version of the book with systemd fully integrated,
> without the need for post-lfs changes. This in no way means that
> systemd will make it i
Hi all,
I've just created a systemd branch for LFS. The intention behind this
is to provide a version of the book with systemd fully integrated,
without the need for post-lfs changes. This in no way means that
systemd will make it into the book at any point, but it should help
folks out that wan
Aleksey Rybalkin wrote:
> Hi Bruce.
>
> I suggest to move `udevadm hwdb --update` up to the chapter in the book
> (from Makefile.lfs). With that change fakeroot/DESTDIR folks can easily
> move that line to their post-upgrades/post-installs.
>
> Right now `make DESTDIR= -f udev-lfs-196/Makefile.lfs
Hi Bruce.
I suggest to move `udevadm hwdb --update` up to the chapter in the book
(from Makefile.lfs). With that change fakeroot/DESTDIR folks can easily
move that line to their post-upgrades/post-installs.
Right now `make DESTDIR= -f udev-lfs-196/Makefile.lfs install`
does not work with that ins
Bruce Dubbs wrote:
> Bryan Kadzban wrote:
>
>> *Presumably* (without having actually looked at it) this database would
>> be mapping from hardware IDs (vendor/device pairs, etc.) to human
>> readable description strings, so I'd be surprised if 105 bytes was
>> sufficient, yeah. Is there anything r
Am 21.11.2012 18:21, schrieb Bruce Dubbs:
> I've been testing udev from systemd-196. I have been able to build and
> install it with some changes to the LFS Makefile. One new capability is
> that it has it's own hw database instead of lspci and lsusb.
udev/systemd gets uglier with each release...
1 - 100 of 152 matches
Mail list logo
