Re: F23 install from hard disk

On Wed, 2016-04-06 at 22:07 -0700, Samuel Sieb wrote: > If you tell the installer to get the stage2 from an iso file, the > installer will remove the entire drive (not just the partition) > containing the file from the install options. What a major fuck-up in design. Nup, I'm not going to

Re: Changing partition sizes on dual boot disks.

On 04/07/2016 09:34 PM, jd1008 wrote: Can parted handle 1. shrinking partition 3 (i.e. starts at a numerically higher block number) This will be two steps. Shrink partition, then move it. Gparted would let you set it up as one step, but it is done in two. 2. fixing the

Re: Changing partition sizes on dual boot disks.

On 04/07/16 23:34, jd1008 wrote: > Hi all. > I have a dos partitioned drive. > partition 1 has windoze > there is no partition 2 (it was deleted and it's space added to partition 1, > using the old software called "Partition Magic". > partition 3 is fedora > partition 4 is fedora's swap. > >

Changing partition sizes on dual boot disks.

Hi all. I have a dos partitioned drive. partition 1 has windoze there is no partition 2 (it was deleted and it's space added to partition 1, using the old software called "Partition Magic". partition 3 is fedora partition 4 is fedora's swap. Fedora partition is only using 3% of it's available

Re: F23 install from hard disk

On 04/07/2016 07:01 PM, Amadeus W.M. wrote: Yes, that's the procedure I remember. The magic you put in grub is essential. This should be documented as a FAQ or actually in the official docs. It used to be, I don't know why it isn't anymore. It's a "green" method, it saves time and dvds. I

Re: forcing mplayer to use available .srt file

On 04/02/2016 09:07 PM, Ed Greshko wrote: On 04/03/16 10:45, jd1008 wrote: Tried to make mplayer to use english subtitles like so: mplayer -sub-paths ./en.srt -slang en The_Brain.mkv but it does not display the english subs. -sub-paths is parameter specifying a directory. A directory

Re: F23 install from hard disk

On Tue, 05 Apr 2016 08:19:55 +1000, Stephen Morris wrote: > On 05/04/16 08:04, Samuel Sieb wrote: >> On 04/04/2016 02:49 PM, Stephen Morris wrote: >>> On 04/04/16 10:30, Amadeus W.M. wrote: I haven't upgraded my machines in a while and I couldn't find any reference on how to install

[389-users] Re: ldap-ping with 389-ds version

On 04/07/2016 10:45 AM, ghiureai wrote: Hello Gurus, I was searching the web for some scripts to monitor DS performance , and found the Open Ldap: ldap-ping.pl script, I wonder if there is a version for 389-DS or if are other similar performance measure scripts available for 389-ds? Looks

Re: F23 install from hard disk

On Tue, 05 Apr 2016 16:32:26 -0700, Samuel Sieb wrote: > On 04/04/2016 02:34 PM, Amadeus W.M. wrote: >> I used to - mount the iso on some empty directory, >> - extract vmlinuz and the initramfs image for the new distribution and >> put them in /boot - modify grub.conf accordingly, write it to

[389-users] Re: Create 389 directory server secure connections

Hello William, The slapd was down by itself for some reason. Below is from error file this afternoon. [07/Apr/2016:13:36:33 -0400] - slapd started. Listening on All Interfaces port 389 for LDAP requests [07/Apr/2016:13:36:33 -0400] - Listening on All Interfaces port 636 for LDAPS requests

Re: F23 dracut can't find disk

On 04/07/16 05:56 PM, Rick Stevens wrote: > Glad to help. Did the rebuild of the ramdisk work? Are you running > the new kernel? Just curious as this may happen on the next update, > too. I hope to have time for that tomorrow. -- Dave Close -- users mailing list users@lists.fedoraproject.org To

Re: F23 dracut can't find disk

On 04/07/2016 05:21 PM, CLOSE Dave wrote: I wrote: I have five machines which were fresh-installed with F23 back in February and all have been booted successfully a few times since. Today, booting of all of them fails in exactly the same way: dracut says it can't find the disk filesystems. The

Re: F23 dracut can't find disk

I wrote: > I have five machines which were fresh-installed with F23 back in > February and all have been booted successfully a few times since. > Today, booting of all of them fails in exactly the same way: dracut > says it can't find the disk filesystems. The kernel boots as it > should, and of

Re: F23 dracut can't find disk

On 04/07/2016 04:50 PM, CLOSE Dave wrote: I have five machines which were fresh-installed with F23 back in February and all have been booted successfully a few times since. Today, booting of all of them fails in exactly the same way: dracut says it can't find the disk filesystems. The kernel

Re: converting to btrfs

On 04/07/2016 04:00 PM, Jeffrey Ross wrote: I had an raid1 partition with ext4 on it which was empty. it was /dev/md124 which was made up of /dev/sda1 and /dev/sdb1, I decided to change this to be a btrfs partition. Initially I figured I'd simply unmount /dev/md124 and simply do a "mkfs.btrfs

F23 dracut can't find disk

I have five machines which were fresh-installed with F23 back in February and all have been booted successfully a few times since. Today, booting of all of them fails in exactly the same way: dracut says it can't find the disk filesystems. The kernel boots as it should, and of course that

converting to btrfs

I had an raid1 partition with ext4 on it which was empty. it was /dev/md124 which was made up of /dev/sda1 and /dev/sdb1, I decided to change this to be a btrfs partition. Initially I figured I'd simply unmount /dev/md124 and simply do a "mkfs.btrfs -f -L home2 /dev/md124" and remount the

[389-users] Re: Change of /etc/selinux/config's SELINUX causes port389 fail to start

On Thu, 2016-04-07 at 15:27 -0700, Gordon Messmer wrote: > On 04/07/2016 03:15 PM, William Brown wrote: > > > > When you change from permissive to enforcing, you often need to re-label to > > make > > sure the system is consistent. >  From "permissive"?  I know that's true if a system is set to

[389-users] Re: Change of /etc/selinux/config's SELINUX causes port389 fail to start

On 04/07/2016 08:35 AM, Lutz Berger wrote: Changing the SELINUX setting from "permissive" to "enforcing" and rebooting afterwards causes port389 DS fail to start due to a permission problem of /var/run/dirsrv Interestingly, the ownership of /var/run/dirsrv changed from port389:port389 to

[389-users] Re: Change of /etc/selinux/config's SELINUX causes port389 fail to start

On 04/07/2016 03:15 PM, William Brown wrote: When you change from permissive to enforcing, you often need to re-label to make sure the system is consistent. From "permissive"? I know that's true if a system is set to enforcing from "disabled" but I've never seen an indication that switching

[389-users] Re: Create 389 directory server secure connections

> ldap_connect_to_host: Trying 127.0.0.1:389 > ldap_pvt_connect: fd: 3 tm: -1 async: 0 > ldap_close_socket: 3 > ldap_err2string > ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1) > It appears that when admin server TLS change takes effect but when the instance TLS wasn't in effect, then

[389-users] Re: ldap-ping with 389-ds version

On Thu, 2016-04-07 at 09:45 -0700, ghiureai wrote: > Hello Gurus, > I was searching the web for some scripts to monitor DS performance , and  > found the Open Ldap:  ldap-ping.pl script, >   I wonder if there is a version for 389-DS or  if are other similar  > performance measure scripts available

[389-users] Re: Change of /etc/selinux/config's SELINUX causes port389 fail to start

On Thu, 2016-04-07 at 17:35 +0200, Lutz Berger wrote: > Hi, > > IHAC who wants to use ( under RHEL 7.2 ): > > /etc/selinux/config with > SELINUX=enforcing > > > Changing the SELINUX setting from "permissive" to "enforcing" and > rebooting afterwards causes port389 DS fail to start due to > a

[389-users] Create 389 directory server secure connections

Hello All, I screwed up my 389 directory server console authentication today because I need to set up TLS secure connections. I first started reading this document: http://directory.fedoraproject.org/docs/389ds/howto/howto-ssl.html. The document refers to a nice shell script from github:

[389-users] Configure the behavior of the creation of some attributes

Hi, When using the 389DS console to create a new user, can we configure the behavior of the creation of some attributes? for example, for our mailing service the user's uid is of the form : *lastname.firstname* and the email address is of the form : *lastname.firstn...@example.com

[389-users] ldap-ping with 389-ds version

Hello Gurus, I was searching the web for some scripts to monitor DS performance , and found the Open Ldap: ldap-ping.pl script, I wonder if there is a version for 389-DS or if are other similar performance measure scripts available for 389-ds? Thank you -- 389 users mailing list

[389-users] Change of /etc/selinux/config's SELINUX causes port389 fail to start

Hi, IHAC who wants to use ( under RHEL 7.2 ): /etc/selinux/config with SELINUX=enforcing Changing the SELINUX setting from "permissive" to "enforcing" and rebooting afterwards causes port389 DS fail to start due to a permission problem of /var/run/dirsrv Interestingly, the ownership of

[389-users] Re: admin and Directory Manager accounts cannot log into 389-console

On 04/07/2016 10:45 AM, Mark Reynolds wrote: On 04/07/2016 10:34 AM, Mark Reynolds wrote: On 04/07/2016 09:50 AM, Warron French wrote: Mr. Brown, As much as I can now log into 389-console to access the Directory Server and the Admin Server entities through the GUI console, and I can

[389-users] Re: admin and Directory Manager accounts cannot log into 389-console

On 04/07/2016 10:34 AM, Mark Reynolds wrote: On 04/07/2016 09:50 AM, Warron French wrote: Mr. Brown, As much as I can now log into 389-console to access the Directory Server and the Admin Server entities through the GUI console, and I can also perform ldapsearch successfully, I am

[389-users] Re: admin and Directory Manager accounts cannot log into 389-console

On 04/07/2016 09:50 AM, Warron French wrote: Mr. Brown, As much as I can now log into 389-console to access the Directory Server and the Admin Server entities through the GUI console, and I can also perform ldapsearch successfully, I am still having one irksome problem. I still cannot

[389-users] Re: admin and Directory Manager accounts cannot log into 389-console

Mr. Brown, As much as I can now log into 389-console to access the Directory Server and the Admin Server entities through the GUI console, and I can also perform ldapsearch successfully, I am still having one irksome problem. I still cannot log into the 389-console with the account

any simpler option to overlaying header file dirs than funionfs?

a project i was recently introduced to uses, quite heavily, the notion of overlaying header file directories with the now-obsolete gcc "-I-" option, and i'm curious if there are equivalent solutions that don't use that feature. summary: sizable C (and possibly, not sure, some C++) code base

[389-users] Re: admin and Directory Manager accounts cannot log into 389-console

Mr. Brown, you sort of lead me down the path; thank you. It turns out that I needed to use the certutil (something I didn't know how to use properly for this problem to diagnose or FIX the problem with) to remove the OLD wsf-LabLDAP.crt, Then I needed to add the NEW wsf-LabLDAP.crt (from the

[389-users] Re: admin and Directory Manager accounts cannot log into 389-console

Hello Mr. Brown, the problem is still not resolved. I ran, as you suggested: root@wsf-LabLDAP:/etc/openldap/cacerts> certutil -L -d /etc/dirsrv/slapd-E2WAN/ -n wsf-LabCA.lab.aero.org -a > wsf-LabCA.lab.aero.org.pem Then I ran the cacertdir_hash command (not realizing I needed to provide a

Re: cpio Digest mismatch error?

On 6 Apr 2016 22:12, "Tom Horsley" wrote: > > On Wed, 06 Apr 2016 12:55:04 -0700 > Doug H. wrote: > > > So my guess is that there is a digest file that is being checked by > > default in fedora but not checked on centos. > > But I'd really like to know why it says it has a