search for: machine_ids

Hi, I have the following example: it ''should have a form with an action attribute'' do response.should have_tag( "form[action=?]", ''/users/1/machines/1/trouble_tickets'') end for a form like so: <% form_for( :trouble_ticket, :url => { :action => ''create'', :user_id => @machine.current_owner,

Another machine-id file, used by D-Bus. --- sysprep/sysprep_operation_machine_id.ml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/sysprep/sysprep_operation_machine_id.ml b/sysprep/sysprep_operation_machine_id.ml index 190ca5b..dbf8ce2 100644 --- a/sysprep/sysprep_operation_machine_id.ml +++ b/sysprep/sysprep_operation_machine_id.ml @@ -24,7 +24,8 @@ module G = Guestfs let

Instead of rm + touch, just truncate the file if existing. In case there was no file previously, now nothing is created, as most probably the system was fine even without it. Also, turn the single path into a list, so more machine-id files can be handled at once. --- sysprep/sysprep_operation_machine_id.ml | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git

Modern distributions are moving toward a common boot scheme called "The Boot Loader Specification". This patch enables syslinux's (vesa)menu.c32 modules to parse the drop-in files that are defined by this new specification. Link to The Boot Loader Specification: https://systemd.io/BOOT_LOADER_SPECIFICATION Link to demonstration bootdisk image (82MB gzipped):

Commit a6330e9d3af0f5286f1d53d909fd868387b67f69 enabled /run for systemd-tmpfiles: while this works fine in most of the cases, there are few tmpfiles configurations that still references /var/run instead of /run. As result, include also /var/run in the systemd-tmpfiles execution. --- appliance/init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appliance/init

On Sat, May 25, 2019 at 3:42 PM Sebastian Herbszt <herbszt at gmx.de> wrote: > > Gregory Lee Bartholomew wrote: > > Modern distributions are moving toward a common boot scheme called > > "The Boot Loader Specification". > > Which distributions are using this yet? > > > This patch enables syslinux's > > (vesa)menu.c32 modules to parse the

Gregory Lee Bartholomew wrote: > Modern distributions are moving toward a common boot scheme called > "The Boot Loader Specification". Which distributions are using this yet? > This patch enables syslinux's > (vesa)menu.c32 modules to parse the drop-in files that are defined by > this new specification. Any reason why you don't try to implement this in syslinux

I know this has been rehashed many times, but I don''t get it. I can''t find it documented to were I understand all the parts. I can make this work using Rails database design conventions, but in this case I am not able to do that. I find examples, but the ones I find do not follow the conventions. They also do not give enough information to understand what is going on. In

Hi, this series improves the way LVM is used in the appliance: in particular, now lvmetad can eventually run at all, and with the correct configuration. Also improve the listing strategies. Changes in v2: - dropped patch #5, will be sent separately - move lvmetad statup in own function (patch #2) Thanks, Pino Toscano (4): daemon: lvm-filter: set also global_filter daemon: lvm-filter:

Modern distributions are moving toward a common boot scheme called "The Boot Loader Specification". This patch enables syslinux to parse the drop-in files that are defined by this new specification. Link to documentation of the options added to syslinux by this patch: https://drive.google.com/uc?export=download&id=1nuRISVJeE1whYggFURywoQFpPzc6s1MC MD5 (syslinux-bls1.txt) =

Gregory Bartholomew wrote: > On Sat, May 25, 2019 at 3:42 PM Sebastian Herbszt <herbszt at gmx.de> > wrote: > > > > Gregory Lee Bartholomew wrote: > > > Modern distributions are moving toward a common boot scheme called > > > "The Boot Loader Specification". > > > > Which distributions are using this yet? [copy & paste from other

Setup the volatile /run in the appliance also with the tmpfiles configurations available. In particular, setting up correctly the lvm bits allow lvmetad to run. --- appliance/init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appliance/init b/appliance/init index d440007..e678e42 100755 --- a/appliance/init +++ b/appliance/init @@ -88,7 +88,7 @@ machine_id=$(dd

Setup the volatile /run in the appliance also with the tmpfiles configurations available. In particular, setting up correctly the lvm bits allow lvmetad to run. --- appliance/init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appliance/init b/appliance/init index d440007..e678e42 100755 --- a/appliance/init +++ b/appliance/init @@ -88,7 +88,7 @@ machine_id=$(dd

Hi, this series improves the way LVM is used in the appliance: in particular, now lvmetad can eventually run at all, and with the correct configuration. Also improve the listing strategies. Thanks, Pino Toscano (5): daemon: lvm-filter: set also global_filter daemon: lvm-filter: start lvmetad better daemon: lvm: improve filter for LVs with activationskip flag set daemon: lvm: list

Remove hostname from network interface configuration. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- po/POTFILES-ml | 1 + sysprep/Makefile.am | 1 + sysprep/sysprep_operation_net_hostname.ml | 58 +++++++++++++++++++++++++++++++ 3 files changed, 60 insertions(+) create mode 100644 sysprep/sysprep_operation_net_hostname.ml

We just remove the process accounting files previously without touch a empty file, this will cause psacct runs error. Restart the service can't help us create this file auto. couldn't open file '/var/account/pacct': No such file or directory Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- po/POTFILES-ml | 1 + sysprep/Makefile.am

This new operation removes the Kerberos /etc/krb5.keytab file from the guest. Thanks to Christian Heimes and François Cami for the hints. Related to RHBZ#1789592. --- sysprep/Makefile.am | 1 + .../sysprep_operation_kerberos_hostkeytab.ml | 38 +++++++++++++++++++ 2 files changed, 39 insertions(+) create mode 100644 sysprep/sysprep_operation_kerberos_hostkeytab.ml

Hi, The use-case is deploying C7 VMs with a pre-set machine-id and default-duid based on the machine-id to facilitate static DHCP with IPv6. The default-duid is found in dhclient6-<value>-eth0.lease and IPv6 DHCP uses default-duid like IPv4 DHCP uses MAC addresses for static DHCP. How does one convert /etc/machine-id to a default-duid (in bash)? 1) /etc/machine-id -> DUID: <read

I have a problem logging into 3.0.6 with an XP SP2 machine. I'm not sure where this problem has arisen from as I have been testing XP SP2 on a few machines and during this process I've done a clean install of 3.0.6. I started testing a laptop and found that while logged in locally I could access domain files as expected. When I tried to log into the domain I was presented with

...c info ### I''ve got following model associations: Customer has_many :inquiries attr_accessible :inquiry_ids accepts_nested_attributes_for :inquiries Inquiry belongs_to :customer has_and_belongs_to_many :machines accepts_nested_attributes_for :machines attr_accessible :machine_ids Machine has_and_belongs_to_many :inquiries I''m on Rails 2.3.5 and formtastic 0.9.7 ### What I want ### I wanted to build a nested form (using formtastic + haml), so a User could enter his data and create an inquiry regarding several machines (he put into a cart in advance) so I set...