Ask Your Question

afyr's profile - activity

2015-12-03 16:47:08 -0500 received badge  Supporter (source)
2015-11-24 10:53:37 -0500 received badge  Self-Learner (source)
2015-11-24 10:33:34 -0500 answered a question Is it possible to add quickly add persistent net rules to Fedora 22?

Installing the following files from Fedora 15 (with a few tweaks described below) helped me regenerate 70-persistent-net.rules in Fedora 22:

/lib/udev/rules.d/75-persistent-net-generator.rules
/lib/udev/write_net_rules
/lib/udev/rule_generator.functions

In /lib/udev/rule_generator.functions:

RUNDIR=$(udevadm info --run)

Changed to:

RUNDIR=/run/udev

Since --run is no longer defined.

In /lib/udev/write_net_rules, commented out:

match="$match, KERNEL==\"$basename*\""

Since the name may be the old-style eth* or new style en. Fedora uses eth names and, per their documentation, its use is discouraged in rules files. So I initially name the interfaces with the prefix lan* and then rename them using the service described here. Also, added this short if block after basename assignment:

basename=${INTERFACE%%[0-9]*}
# Re-map new basename (en, wl, etc) to old style (eth, wlan)
if [[ $basename == "en"* ]]; then # If installed before boot   
  basename=lan
  INTERFACE=lan0
elif [[ $basename == "eth"* ]]; then # If installed after boot
   basename=lan
   INTERFACE=lan0
elif [[ $basename == "wl"* ]]; then
   basename=wlan
   INTERFACE=wlan0
fi
2015-11-20 11:25:23 -0500 commented question Is it possible to add quickly add persistent net rules to Fedora 22?

I would like to use the old style ethernet names (eth0...ethN). The whole problem is I don't have a rules file, but I would like to use the one that was generated in previous versoins of Linux. I appreciate any advice you have may have.

2015-11-19 14:21:44 -0500 asked a question Is it possible to add quickly add persistent net rules to Fedora 22?

Is it possible to add something equivalent to 75-persistent-net-generator.rules//lib/udev/write_net_rules to Fedora 22? We have systems that are currently using /etc/udev/rules.d/70-persistent-net.rules which is dependent on 75-persistent-net-generator.rules to get generated. Of course we could update everything to use biosdevname or net.ifnames, but a lot of systems would have to change and it would get messy.

2015-10-26 11:14:12 -0500 commented answer livecd-creator using the wrong Fedora version

No there weren't. Only the lines that said to include those other files. All I did was move the repo line above from fedora-repo-not-rawhide.ks to fedora-live-base.ks

2015-10-21 02:39:06 -0500 received badge  Self-Learner (source)
2015-10-20 11:26:53 -0500 received badge  Scholar (source)
2015-10-20 11:26:27 -0500 answered a question livecd-creator using the wrong Fedora version

Replacing:

%include fedora-repo.ks

in fedora-live-base.ks with:

repo --name=fedora --mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-22&arch=$basearch

and removing fedora-repo.ks and fedora-repo-not-rawhide.ks resolved the issue.

2015-10-20 10:53:55 -0500 commented question livecd-creator using the wrong Fedora version

Yes, it is the complete output. There are no other repo= lines. This link https://paste.fedoraproject.org/28154... includes -v -d options for more verbose messages,

2015-10-19 15:51:53 -0500 commented question livecd-creator using the wrong Fedora version

hedayat, thanks for your help! I provided the command and uploaded the output.

2015-10-19 12:13:59 -0500 asked a question livecd-creator using the wrong Fedora version

I'm trying to create a Fedora 22 livecd, but livecd-creator is creating a Fedora 24 livecd. Here is the repo statement in my kickstart file:

repo --name=fedora --mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-22&arch=$basearch

I tried passing the releasever option to livecd-creator on the command line:

 livecd-creator --config=workspace/tt_000000_l_tester_f22_os/kickstart.virgin.mate/fedora-live-mate_compiz.ks --fslabel=virgin.mate --releasever=22 -v -d

The full text output is here. What am I doing wrong?

2015-06-13 21:34:46 -0500 received badge  Teacher (source)
2015-06-13 21:34:46 -0500 received badge  Self-Learner (source)
2015-06-13 21:34:44 -0500 received badge  Student (source)
2015-06-11 19:31:49 -0500 answered a question Fedora Disable Home Partition in Kickstart

I put the below commands in a script which runs on the first boot after installation at run level 3 (at run level 5 there are issues with gnome using /home and some commands will fail):

<backup home directory to temp>
umount /home
lvremove -vf --autobackup n /dev/mapper/VolGroup-lv_home
pvresize /dev/sda2      
lvextend /dev/mapper/VolGroup-lv_root -l+100%FREE
resize2fs /dev/mapper/VolGroup-lv_root
<restore home directory from temp>

Source: http://serverfault.com/questions/4246...

2015-06-09 18:33:30 -0500 commented answer Fedora Disable Home Partition in Kickstart

It's a long story, but we're stuck on 15 for the driver support from our 3rd party vendor. In general, I agree.

2015-06-09 01:10:07 -0500 commented answer Fedora Disable Home Partition in Kickstart

Thanks for the answer. I should clarify that this installation is a custom livecd and I'm trying to automate as much as I can as it will be used on hundreds of laptops. Also those performing the installation aren't very savvy with such things which is all the more reason to automate the process.

2015-06-08 16:39:35 -0500 asked a question Fedora Disable Home Partition in Kickstart

As described here: https://ask.fedoraproject.org/en/ques... Fedora 15 creates a / and /home partition by default.

I would like to disable this so /home resides on the / partition. I've tried to specify / as follows: part / --size 4096 --grow --fstype ext4

but how do you specify no /home partition in an automated fasion?

Will 'part' commands be used if the user specifies 'Use all space' from the 'Install to Hard Drive' GUI?