On 04/26/2014 10:32 AM, akhiezer wrote:
> Hi,
>
> Armin, are you (or anyone) going to be continuing to maintain the
> pure-systemd lfs book?
>
It wouldn't be hard to merge stuff from main to systemd branch if that's
needed.
> Or are you (Armin) 'just' going to contrib directly to main mixed(-up)
On 04/26/2014 05:15 AM, Ken Moffat wrote:
> I've now got to section 8.3, and as-expected I need to change my
> kernel config from what I've been using, if I hope it will support
> booting with systemd. But I'd like to query if a few of these
> settings really are necessary, and also to suggest th
2014-04-26 16:32 GMT+08:00 akhiezer :
> Hi,
>
> Armin, are you (or anyone) going to be continuing to maintain the
> pure-systemd lfs book?
I'm using a rough patch for jhalfs build.
>
> Or are you (Armin) 'just' going to contrib directly to main mixed(-up)-lfs
> from now on?
>
> (Apols if have misse
Ken Moffat wrote:
> On Fri, Apr 25, 2014 at 10:35:11PM -0500, Bruce Dubbs wrote:
>>
>> Does this help?
>>
>> http://wiki.gentoo.org/wiki/Systemd#Kernel
>>
>> -- Bruce
>
> No ;-)
>
> They show "open by fhandle syscalls" as required, so I start to
> believe there is no choice for that. But t
On Fri, Apr 25, 2014 at 10:35:11PM -0500, Bruce Dubbs wrote:
>
> Does this help?
>
> http://wiki.gentoo.org/wiki/Systemd#Kernel
>
>-- Bruce
No ;-)
They show "open by fhandle syscalls" as required, so I start to
believe there is no choice for that. But the other items I queried,
as well
Ken Moffat wrote:
> I've now got to section 8.3, and as-expected I need to change my
> kernel config from what I've been using, if I hope it will support
> booting with systemd. But I'd like to query if a few of these
> settings really are necessary, and also to suggest that we ought to
> distin
On 2014-04-25 14:16, Gerard Beekmans wrote:
> On 2014-04-25 14:14, Gerard Beekmans wrote:
>> This weekend I'm going to spend some time migrating the LFS mailinglists
>>
> I forgot to mention: the archives will be re-instated. New server
> hosting allows 16 TB/month tran
On 2014-04-25 14:14, Gerard Beekmans wrote:
> This weekend I'm going to spend some time migrating the LFS mailinglists
>
I forgot to mention: the archives will be re-instated. New server
hosting allows 16 TB/month transfer (old host only 100 GB/month which is
why we took the archi
On 2014-04-24 07:15, Gerard Beekmans wrote:
> On 2014-04-23 15:53, Gerard Beekmans wrote:
>> Hosting company (Linode) has changed price plans and how offers
>> additional resources for same monthly cost.
>>
>> This upgrade for us includes:
>>
>> * RAM from 8 GB to 16 GB
>> * Shared outgoing bandwid
On 2014-04-23 15:53, Gerard Beekmans wrote:
> Hosting company (Linode) has changed price plans and how offers
> additional resources for same monthly cost.
>
> This upgrade for us includes:
>
> * RAM from 8 GB to 16 GB
> * Shared outgoing bandwidth from 250 Mbps to 2 Gbps
>
> I'll follow-up later w
On 04/23/2014 12:05 PM, Fernando de Oliveira wrote:
> Em 23-04-2014 02:39, Bruce Dubbs escreveu:
>> Ken Moffat wrote:
>
>
>>> I've had a users group in my own builds for years, probably derived
>>> from fedora, and it has always been 1000. Shadow is now maintained
>>> by debian, no ? So the f
Em 23-04-2014 02:39, Bruce Dubbs escreveu:
> Ken Moffat wrote:
>> I've had a users group in my own builds for years, probably derived
>> from fedora, and it has always been 1000. Shadow is now maintained
>> by debian, no ? So the fact that it too uses 1000 implies many
>> people will already
Ken Moffat wrote:
> On Sun, Apr 20, 2014 at 09:27:55PM -0500, Bruce Dubbs wrote:
>> Ken Moffat wrote:
>>>I'm just looking in more detail at the set-systemd and set-sysv
>>> scripts in section 7.1.
>>>
>>>Two questions:
>>>
>>> 1. set-systemd ends with
>>> echo "Now reboot with /sbin/reboot-
Ken Moffat wrote:
> On Tue, Apr 22, 2014 at 11:28:32AM -0700, bdu...@higgs.linuxfromscratch.org
> wrote:
>> Author: bdubbs
>> Date: Tue Apr 22 11:28:32 2014
>> New Revision: 10546
>>
>> Log:
>> Update users so all acl tests pass
>>
>
>>
>> Modified: trunk/BOOK/chapter06/shadow.xml
>> =
Ken Moffat wrote:
> I'm trying to guess what I need here, but the details seem to be
> sparse.
>
> 1. FONT_MAP and FONT_UNIMAP : I haven't found any relevant examples
> yet, but I assume those of use using UTF-8 throughout our system do
> not need to specify anything ? I saw an example of FONT_M
On Tue, Apr 22, 2014 at 11:28:32AM -0700, bdu...@higgs.linuxfromscratch.org
wrote:
> Author: bdubbs
> Date: Tue Apr 22 11:28:32 2014
> New Revision: 10546
>
> Log:
> Update users so all acl tests pass
>
>
> Modified: trunk/BOOK/chapter06/shadow.xml
> ===
On Sun, Apr 20, 2014 at 09:27:55PM -0500, Bruce Dubbs wrote:
> Ken Moffat wrote:
> > I'm just looking in more detail at the set-systemd and set-sysv
> > scripts in section 7.1.
> >
> > Two questions:
> >
> > 1. set-systemd ends with
> > echo "Now reboot with /sbin/reboot-sysv"
> > and set-sys
Sebastian Plotz wrote:
> Am 21.04.2014 23:46, schrieb Bruce Dubbs:
>> I have reorganized and rewritten Chapter 7. I'd appreciate feedback.
>> Thanks.
>>
>> -- Bruce
>
> It looks really good. I have only three minor things to mention:
>
> 1)
>
> Unfortunately some (in my opinion) interesting d
Am 21.04.2014 23:46, schrieb Bruce Dubbs:
> I have reorganized and rewritten Chapter 7. I'd appreciate feedback.
> Thanks.
>
> -- Bruce
It looks really good. I have only three minor things to mention:
1)
Unfortunately some (in my opinion) interesting documentation got lost:
- |description
Ken Moffat wrote:
> I'm just looking in more detail at the set-systemd and set-sysv
> scripts in section 7.1.
>
> Two questions:
>
> 1. set-systemd ends with
> echo "Now reboot with /sbin/reboot-sysv"
> and set-sysv ends with
> echo "Now reboot with /sbin/reboot-systemd"
> Are these swappe
On Apr 19, 2014, at 4:00 AM, Pontus Karlsson wrote:
> 2. Read the archlibexp and use that path instead:
> mkdir -pv $(grep archlibexp lib/Config.pm | cut -d"'" -f2)
> cp -Rv lib/* $(grep archlibexp lib/Config.pm | cut -d"'" -f2)
>
...
>
> But as long as no Perl modules are required while
I copied the example from
http://www.freedesktop.org/software/systemd/man/systemd.link.html.
Here is the full example:
[Match]
MACAddress=12:34:56:78:9a:bc
Driver=brcmsmac
Path=pci-:02:00.0-*
Type=wlan
Virtualization=no
Host=my-laptop
Architecture=x86-64
[Link]
Name=wireless0
MTUBytes=1450
Sebastian Plotz wrote:
> Am 15.04.2014 05:37, schrieb Bryan Kadzban:
>> Also, does it work to match NICs by device path instead of MAC
>> address,
>
> Yes. Have a look at "|Path=pci-:02:00.0-*":|
Huh. OK, that's unexpected. :-)
However, while this:
> |[Match]
> Driver=brcmsmac
> Path=pci
Am 15.04.2014 05:37, schrieb Bryan Kadzban:
> Why the duplication? If I create a file named 10-eth1.link and it has
> Name="eth0" in it, what interface name is created when the address
> matches? (Wouldn't it be better to have *one* source of truth for
> renames like this?)
It would create the
Bruce Dubbs wrote:
> Bruce Dubbs wrote:
>> Sebastian Plotz wrote:
>>> This assignes the name eth0 to the interface with the MAC address
>>> 12:34:56:78:9a:bc. The file name is important: if there would be a
>>> second file (for example 10-eth1.link) with "Name=eth1"instead of
>>> "Name=eth0" the
Bruce Dubbs wrote:
> Sebastian Plotz wrote:
>> Am 14.04.2014 21:52, schrieb Bruce Dubbs:
>>> I've thought about it, but my experience with systemd is limited. Do
>>> you have specific instructions I can test with LFS? -- Bruce
>>
>> Ok, I'll try to give a starting point.
>>
>> 1.) First of all we n
Sebastian Plotz wrote:
> Am 14.04.2014 21:52, schrieb Bruce Dubbs:
>> I've thought about it, but my experience with systemd is limited. Do
>> you have specific instructions I can test with LFS? -- Bruce
>
> Ok, I'll try to give a starting point.
>
> 1.) First of all we need to create a .link file (
Am 14.04.2014 21:52, schrieb Bruce Dubbs:
> I've thought about it, but my experience with systemd is limited. Do
> you have specific instructions I can test with LFS? -- Bruce
Ok, I'll try to give a starting point.
1.) First of all we need to create a .link file (for example
15-eth0.link) in /us
On 04/14/2014 09:52 PM, Bruce Dubbs wrote:
> Sebastian Plotz wrote:
>> What about using systemd to bring up the network interfaces?
>>
>> There was already a discussion about this topic before:
>>
>> https://www.mail-archive.com/lfs-dev@linuxfromscratch.org/msg19837.html
>>
>> The systemd version w
Sebastian Plotz wrote:
> What about using systemd to bring up the network interfaces?
>
> There was already a discussion about this topic before:
>
> https://www.mail-archive.com/lfs-dev@linuxfromscratch.org/msg19837.html
>
> The systemd version wouldn't need the LFS-Network-Scripts anymore.
> The
Em 13-04-2014 19:32, Ken Moffat escreveu:
> On Sun, Apr 13, 2014 at 12:06:54PM -0500, Bruce Dubbs wrote:
>> I would like to get the opinion of the community. Right now we have
>> four tickets:
>>
>> #3537 MPFR-3.1.2 Patchlevel 5
>> #3536 Fix BC-1.06.95 bug
>> #3532 Readline-6.3 patchlevel 3
>> #3
On Sun, Apr 13, 2014 at 3:32 PM, Ken Moffat wrote:
> On Sun, Apr 13, 2014 at 12:06:54PM -0500, Bruce Dubbs wrote:
>> I would like to get the opinion of the community. Right now we have
>> four tickets:
>>
>> #3537 MPFR-3.1.2 Patchlevel 5
>> #3536 Fix BC-1.06.95 bug
>> #3532 Readline-6.3 patchleve
On Sun, Apr 13, 2014 at 12:06:54PM -0500, Bruce Dubbs wrote:
> I would like to get the opinion of the community. Right now we have
> four tickets:
>
> #3537 MPFR-3.1.2 Patchlevel 5
> #3536 Fix BC-1.06.95 bug
> #3532 Readline-6.3 patchlevel 3
> #3532 Bash-4.3 patchlevel 8
>
> All of these call f
Le 13/04/2014 19:06, Bruce Dubbs a écrit :
> I would like to get the opinion of the community. Right now we have
> four tickets:
>
> #3537 MPFR-3.1.2 Patchlevel 5
> #3536 Fix BC-1.06.95 bug
> #3532 Readline-6.3 patchlevel 3
> #3532 Bash-4.3 patchlevel 8
>
> All of these call for adding patches
>
>> I have used lfs-bootscripts-20140321.
>
> That's been updated. Welcome to the joys of -dev.
>
>-- Bruce
>
Thank you Bruce, for checking and pointing this out.
It works perfectly, after updating to lfs-bootscripts-20140404.
Magnus
--
http://linuxfromscratch.org/mailman/listinfo/lf
Magnus Larsson wrote:
> On 2014-04-12 23:04, Bruce Dubbs wrote:
>> Magnus Larsson wrote:
>>> (resend with correct subject title)
>>> Magnus
>>>
>>> dearlfs-...@linuxfromscratch.org,
>>>
>>> LFS : SVN : "/lib/udev/devices does not exist" and "/dev/pts does not
>>> exist"
>>>
>>> === my lfs system ==
On 2014-04-12 23:04, Bruce Dubbs wrote:
> Magnus Larsson wrote:
>> (resend with correct subject title)
>> Magnus
>>
>> dearlfs-...@linuxfromscratch.org,
>>
>> LFS : SVN : "/lib/udev/devices does not exist" and "/dev/pts does not
>> exist"
>>
>> === my lfs system ===
>>
>> I built SVN circa 140331-1
Magnus Larsson wrote:
> (resend with correct subject title)
> Magnus
>
> dearlfs-...@linuxfromscratch.org,
>
> LFS : SVN : "/lib/udev/devices does not exist" and "/dev/pts does not
> exist"
>
> === my lfs system ===
>
> I built SVN circa 140331-140408. I can boot the system and log in as
> root. It
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
Le 07/04/2014 13:50, Christer Solskogen a écrit :
> Pierre Labastie neuf.fr> writes:
>
>>
>> Le 03/04/2014 10:36, Christer Solskogen a écrit :
>>> Hi!
>>>
>>> I'm hoping to create a LFS system with as few patches as necessary. Some
> of
>>> the patches that are in use for both CLFS and LFS are.
Pierre Labastie neuf.fr> writes:
>
> Le 03/04/2014 10:36, Christer Solskogen a écrit :
> > Hi!
> >
> > I'm hoping to create a LFS system with as few patches as necessary. Some
of
> > the patches that are in use for both CLFS and LFS are. For instance the
use
> > of
> > #undef STANDARD_STARTFIL
thomas wrote:
> Am Samstag, den 05.04.2014, 19:17 -0500 schrieb Bruce Dubbs:
>> Armin K. wrote:
>>> On 04/06/2014 01:19 AM, thomas wrote:
Am Samstag, den 05.04.2014, 16:41 -0500 schrieb Bruce Dubbs:
> Working with systemd, there seem to be lots of "learning" issues.
>
> I was tryin
Am Samstag, den 05.04.2014, 19:17 -0500 schrieb Bruce Dubbs:
> Armin K. wrote:
> > On 04/06/2014 01:19 AM, thomas wrote:
> >> Am Samstag, den 05.04.2014, 16:41 -0500 schrieb Bruce Dubbs:
> >>> Working with systemd, there seem to be lots of "learning" issues.
> >>>
> >>> I was trying to watch the bo
Armin K. wrote:
> On 04/06/2014 01:19 AM, thomas wrote:
>> Am Samstag, den 05.04.2014, 16:41 -0500 schrieb Bruce Dubbs:
>>> Working with systemd, there seem to be lots of "learning" issues.
>>>
>>> I was trying to watch the boot sequence and the screen clears and I get
>>> a login prompt. How to d
On 04/06/2014 01:25 AM, Armin K. wrote:
> On 04/05/2014 11:41 PM, Bruce Dubbs wrote:
>> Now I come to setting up udev and networking. I have the rule:
>>
>> /etc/udev/rules.d/70-persistent-net.rules
>>
>> The contents are
>>
>> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
>> ATTR{address}=="
On 04/06/2014 01:19 AM, thomas wrote:
> Am Samstag, den 05.04.2014, 16:41 -0500 schrieb Bruce Dubbs:
>> Working with systemd, there seem to be lots of "learning" issues.
>>
>> I was trying to watch the boot sequence and the screen clears and I get
>> a login prompt. How to disable clearing the sc
On 04/05/2014 11:41 PM, Bruce Dubbs wrote:
> Working with systemd, there seem to be lots of "learning" issues.
>
> I was trying to watch the boot sequence and the screen clears and I get
> a login prompt. How to disable clearing the screen? Well that's simple
> enough:
>
> mkdir -p /etc/syste
Am Samstag, den 05.04.2014, 16:41 -0500 schrieb Bruce Dubbs:
> Working with systemd, there seem to be lots of "learning" issues.
>
> I was trying to watch the boot sequence and the screen clears and I get
> a login prompt. How to disable clearing the screen? Well that's simple
> enough:
>
> m
xinglp wrote:
> 2014-04-05 19:50 GMT+08:00 Armin K. :
>> On 04/05/2014 05:50 AM, Bruce Dubbs wrote:
>>> xinglp wrote:
2014-04-05 11:04 GMT+08:00 Bruce Dubbs :
> xinglp wrote:
>> When boot into systemd, got the below message:
>
> Lets work the problems one at a time.
>>>
>>
Armin K. wrote:
> On 04/05/2014 05:50 AM, Bruce Dubbs wrote:
>> xinglp wrote:
>>> 2014-04-05 11:04 GMT+08:00 Bruce Dubbs :
xinglp wrote:
> When boot into systemd, got the below message:
Lets work the problems one at a time.
>>
> [/usr/lib/tmpfiles.d/systemd.conf:25] Unknown g
2014-04-05 19:50 GMT+08:00 Armin K. :
> On 04/05/2014 05:50 AM, Bruce Dubbs wrote:
>> xinglp wrote:
>>> 2014-04-05 11:04 GMT+08:00 Bruce Dubbs :
xinglp wrote:
> When boot into systemd, got the below message:
Lets work the problems one at a time.
>>
> [/usr/lib/tmpfiles.d/syst
On 04/05/2014 05:50 AM, Bruce Dubbs wrote:
> xinglp wrote:
>> 2014-04-05 11:04 GMT+08:00 Bruce Dubbs :
>>> xinglp wrote:
When boot into systemd, got the below message:
>>>
>>> Lets work the problems one at a time.
>
[/usr/lib/tmpfiles.d/systemd.conf:25] Unknown group 'systemd-journal'.
>
On 04/05/2014 03:50 AM, Bruce Dubbs wrote:
> http://lkml.iu.edu//hypermail/linux/kernel/1404.0/01327.html
>
>-- Bruce
>
>From what I've read past few days the thread isn't about systemd but one
of its devs (behaviour), FYI, it was Kay who rejected my compat patch
and I didn't want to argue w
> Date: Sat, 05 Apr 2014 10:52:09 +0100
> From: lf...@cruziero.com (akhiezer)
> To: LFS Developers Mailinglist
> Subject: Re: [lfs-dev] An interesting thread about systemd
>
- et seq ...
... https://plus.google.com/111049168280159033135/posts/Kd57G8s1cTD
Akhiezer
> Date: Fri, 04 Apr 2014 21:16:01 -0700
> From: Bryan Kadzban
> To: LFS Developers Mailinglist
> Subject: Re: [lfs-dev] Major changes in -dev
>
>
>
> Bruce Dubbs wrote:
> > I did have a private email with a volunteer to write a hint. If I get
> > that, I&
> Date: Fri, 04 Apr 2014 20:50:23 -0500
> From: Bruce Dubbs
> To: LFS Developers Mailinglist
> Subject: [lfs-dev] An interesting thread about systemd
>
> http://lkml.iu.edu//hypermail/linux/kernel/1404.0/01327.html
>
- ha, and I didn't refer to that yesterday at various points, going a
bit ea
Bruce Dubbs wrote:
> Bryan Kadzban wrote:
>> However, if someone (like me...) *really really* doesn't want systemd,
>> and knows it from the get-go, shouldn't they avoid building all the other
>> junk like libacl / libattr / expat / *dbus* / etc., too? The current
>> list of packages that are only
Bryan Kadzban wrote:
> Bruce Dubbs wrote:
>> I did have a private email with a volunteer to write a hint. If I get
>> that, I'll add a note in the systemd section that points there.
>
> I saw a commit mail to -book that added the hint link.
>
> However, if someone (like me...) *really really* does
Bruce Dubbs wrote:
> I did have a private email with a volunteer to write a hint. If I get
> that, I'll add a note in the systemd section that points there.
I saw a commit mail to -book that added the hint link.
However, if someone (like me...) *really really* doesn't want systemd, and
knows it
xinglp wrote:
> 2014-04-05 10:59 GMT+08:00 William Harrington :
>>
>> On Apr 4, 2014, at 9:44 PM, xinglp wrote:
>>
>>> [FAILED] Failed to start Create Volatile Files and Directories.
>>> See 'systemctl status systemd-tmpfiles-setup.service' for details.
>>
>> View the README in the systemd-xxx/ sou
xinglp wrote:
> 2014-04-05 11:04 GMT+08:00 Bruce Dubbs :
>> xinglp wrote:
>>> When boot into systemd, got the below message:
>>
>> Lets work the problems one at a time.
>>> [/usr/lib/tmpfiles.d/systemd.conf:25] Unknown group 'systemd-journal'.
>>
>> Something else I forgot. What happens if you ad
2014-04-05 10:59 GMT+08:00 William Harrington :
>
> On Apr 4, 2014, at 9:44 PM, xinglp wrote:
>
>> [FAILED] Failed to start Create Volatile Files and Directories.
>> See 'systemctl status systemd-tmpfiles-setup.service' for details.
>
> View the README in the systemd-xxx/ source directory or at /us
2014-04-05 10:59 GMT+08:00 William Harrington :
>
> On Apr 4, 2014, at 9:44 PM, xinglp wrote:
>
>> [FAILED] Failed to start Create Volatile Files and Directories.
>> See 'systemctl status systemd-tmpfiles-setup.service' for details.
>
> View the README in the systemd-xxx/ source directory or at /us
2014-04-05 11:04 GMT+08:00 Bruce Dubbs :
> xinglp wrote:
>> When boot into systemd, got the below message:
>
> Lets work the problems one at a time.
>
>> [FAILED] Failed to start Create Volatile Files and Directories.
>> See 'systemctl status systemd-tmpfiles-setup.service' for details.
>>
xinglp wrote:
> When boot into systemd, got the below message:
Lets work the problems one at a time.
> [FAILED] Failed to start Create Volatile Files and Directories.
> See 'systemctl status systemd-tmpfiles-setup.service' for details.
> ---split---
> root [ ~ ]# systemctl status
On Apr 4, 2014, at 9:44 PM, xinglp wrote:
> [FAILED] Failed to start Create Volatile Files and Directories.
> See 'systemctl status systemd-tmpfiles-setup.service' for details.
View the README in the systemd-xxx/ source directory or at /usr/share/
systemd-xxx/README and make sure your kernel op
When boot into systemd, got the below message:
[FAILED] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
---split---
root [ ~ ]# systemctl status systemd-tmpfiles-setup.service
systemd-tmpfiles-setup.service -
On Thu, Apr 03, 2014 at 08:35:34PM -0500, Bruce Dubbs wrote:
> Ken Moffat wrote:
> >
> > I'm now sufficiently interested by this to try a _minimal_ build
> > (i.e. LFS and not much else - many of the things I normally build
> > before rebooting have their own local bootscripts, which will
> > pro
On Fri, Apr 04, 2014 at 08:44:22PM +0200, Denis Mugnier wrote:
> On 04/04/2014 18:41, Bruce Dubbs wrote:
> > Denis Mugnier wrote:
> >>
> >> It is possible to integrate eudev on the BLFS book to provide a solution
> >> without the systemd package?
> > Not without changing the flow. I understand the
On Fri, Apr 04, 2014 at 11:49:14AM -0500, Bruce Dubbs wrote:
> Ken Moffat wrote:
>
> >> The scripts to reconfigure are in /usr/local/sbin and are named
> >> set-systemd and set-sysv. I recommend re-reading Chapter 7 as there are
> >> a lot of changes there.
>
On 04/04/2014 18:41, Bruce Dubbs wrote:
> Denis Mugnier wrote:
>> Hi
>>
>> On 04/04/2014 02:02, Ken Moffat wrote:
>>> I'm sorry to see eudev disappear from the book after its brief
>>> appearance, but more power to your elbow for providing the two
>>> alternative init systems.
>> I'm sorry too.
Ken Moffat wrote:
>> The scripts to reconfigure are in /usr/local/sbin and are named
>> set-systemd and set-sysv. I recommend re-reading Chapter 7 as there are
>> a lot of changes there.
>
> Why /usr/local ? They will be an intrinsic part of LFS if this all
Denis Mugnier wrote:
> Hi
>
> On 04/04/2014 02:02, Ken Moffat wrote:
>>I'm sorry to see eudev disappear from the book after its brief
>> appearance, but more power to your elbow for providing the two
>> alternative init systems.
> I'm sorry too.
>
> It is possible to integrate eudev on the BLFS
Pierre Labastie wrote:
>> -- Bruce
> Built using jhalfs, with all final testsuites:
> Errors (FWIW):
> - glibc : 2 errors (+ 2 ignored), seems as usual
> - coreutils : 1 error (test/misc/nohup)
> - bash (a few, not sure, seems similar to usual)
> - bc (a few, similar to usual)
> - systemd : 2
Hi
On 04/04/2014 02:02, Ken Moffat wrote:
> I'm sorry to see eudev disappear from the book after its brief
> appearance, but more power to your elbow for providing the two
> alternative init systems.
I'm sorry too.
It is possible to integrate eudev on the BLFS book to provide a solution
withou
/usr/local/sbin and are named
> set-systemd and set-sysv. I recommend re-reading Chapter 7 as there are
> a lot of changes there.
>
> The lfs-bootscripts now also install the needed systemd unit for
> bringing up the network.
>
> I've done a render of the book on the
ool}-systemd /sbin/${tool}
> should be
> ln -sfvn ${tool}-systemd /sbin/${tool}
Also fixed at revision 10521.
I've re-rendered the book on the website. Grab the new wget-list,
md5sums, and lfs-bootscripts-20140404.tar.bz2.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
akhiezer wrote:
>> Date: Thu, 03 Apr 2014 17:11:10 -0500
>> From: Bruce Dubbs
>> To: LFS Developers Mailinglist
>> Subject: [lfs-dev] Major changes in -dev
>>
>> I've committed a major change to the -dev version of LFS.
>>
>> The new version installs systemd and System V side-by-side with the
>>
xinglp wrote:
> 2014-04-04 6:11 GMT+08:00 Bruce Dubbs :
>> I'm sure there are still latent bugs in the current commit, whether they
>> be in scripts, build instructions, or text. Please test this out and
>> let me know of needed changes.
>
> set-systemd line 7
> ln -sfvn $(tool}-systemd /sbin/$
xinglp wrote:
> Some error messages during boot，sysv
> Mounting virtual file systems: /runcp: cannot stat
> '/lib/udev/devices/*': No such file or directory
Hmm. I didn't see this. The command is:
cp -a /lib/udev/devices/* /dev
and I do not appear to have the /lib/udev/devices directory at al
> Date: Thu, 03 Apr 2014 17:11:10 -0500
> From: Bruce Dubbs
> To: LFS Developers Mailinglist
> Subject: [lfs-dev] Major changes in -dev
>
> I've committed a major change to the -dev version of LFS.
>
> The new version installs systemd and System V side-by-side with the
> ability to reconfigure a
2014-04-04 6:11 GMT+08:00 Bruce Dubbs :
> I'm sure there are still latent bugs in the current commit, whether they
> be in scripts, build instructions, or text. Please test this out and
> let me know of needed changes.
set-systemd line 7
ln -sfvn $(tool}-systemd /sbin/${tool}
should be
ln -sfv
ocal/sbin and are named
> set-systemd and set-sysv. I recommend re-reading Chapter 7 as there are
> a lot of changes there.
>
> The lfs-bootscripts now also install the needed systemd unit for
> bringing up the network.
>
> I've done a render of the book on the website, s
Ken Moffat wrote:
> As to the size in the foreword - I think you are probably correct.
Perhaps you mean the Preface. The first place I see size mentioned is
in the target architectures. My, things gave grown since LFS 6.5.
The size for 7.5 (64-bit) is 1.5G. We have increased the minimum
MENGUAL Jean-Philippe wrote:
> Hi,
>
> OK so LFS doesn't use anymore sysvinit, but Systemd.
Incorrect. You have a choice. We install both and you can test them
out and choose the one you like best.
I thought the book
> 9ould use an approach like the CLFS one: one chapter if you use Systemd;
t; Meantime, two brief comments -
>
>> The scripts to reconfigure are in /usr/local/sbin and are named
>> set-systemd and set-sysv. I recommend re-reading Chapter 7 as there are
>> a lot of changes there.
>
> Why /usr/local ? They will be an intrinsic part of LFS if th
On Fri, Apr 04, 2014 at 02:46:13AM +0200, MENGUAL Jean-Philippe wrote:
> Hi,
>
> OK so LFS doesn't use anymore sysvinit, but Systemd. I thought the book
> 9ould use an approach like the CLFS one: one chapter if you use Systemd;
> one if sysvinit (in CLFS: if you chroot; if you reboot). Given tha
/sbin and are named
> set-systemd and set-sysv. I recommend re-reading Chapter 7 as there are
> a lot of changes there.
>
> The lfs-bootscripts now also install the needed systemd unit for
> bringing up the network.
>
> I've done a render of the book on the website, so
/usr/local/sbin and are named
> set-systemd and set-sysv. I recommend re-reading Chapter 7 as there are
> a lot of changes there.
Why /usr/local ? They will be an intrinsic part of LFS if this all
works out. Some of us occasionally try things in /usr/local, and
then wipe it all out. [
Le 03/04/2014 10:36, Christer Solskogen a écrit :
> Hi!
>
> I'm hoping to create a LFS system with as few patches as necessary. Some of
> the patches that are in use for both CLFS and LFS are. For instance the use
> of
> #undef STANDARD_STARTFILE_PREFIX_1
> #undef STANDARD_STARTFILE_PREFIX_2
> #def
Ken Moffat wrote:
> On Wed, Apr 02, 2014 at 02:00:29PM -0500, Bruce Dubbs wrote:
>> I've been trying to figure out whether we need the lfs udev rules when
>> transitioning to udev from systemd-211.
>>
>> 83-cdrom-symlinks.rules needs write_cd_rules, so those go together.
>>
> Taking a quick look
On Wed, Apr 02, 2014 at 02:00:29PM -0500, Bruce Dubbs wrote:
> I've been trying to figure out whether we need the lfs udev rules when
> transitioning to udev from systemd-211.
>
> 83-cdrom-symlinks.rules needs write_cd_rules, so those go together.
>
Taking a quick look at them, I admit I don't
1 - 100 of 16904 matches
Mail list logo
