Re: [gentoo-user] Re: Fresh gen too install - unsuccesful
On 2014-12-20 00:57, German wrote: Just a follow up to my original question. I've installed grub on /dev/SDA literally following the quide. And I just realized why I made /dev/sda1 partition obviously designed for grub? Should I have been install grub into /dev/sda1? I also have uefi system and I think it matters. Thanks everyone for clarifications German wrote: Is anyone can advice on where to dig. It seems that grub isn't installed because I can't access it pressing ESC key and I return to bios. During installation there were no errors reported, the system installed grub just fine. Also grub.cfg found all my kernels and ramdisks? Thanks for any suggestion. What would you do? If you have your /dev/sda only for Gentoo, you would install grub into /dev/sda and have /dev/sda1 for /boot, for example: /dev/sda1: /boot /dev/sda2: / The bios will load grub from mbr of /dev/sda and since you specify that grub can find it's stuff on /dev/sda1 (root), it can continue to find the kernel, etc.. Once found, it can load the kernel and mount root, because it's the kernel parameter. For example: root(hd0,0) setup (hd0) Check out http://www.gnu.org/software/grub/manual/legacy/grub.html#Installing-GRUB-natively Or for grub2: http://wiki.gentoo.org/wiki/GRUB2 https://wiki.gentoo.org/wiki/Handbook:X86/Installation/Bootloader http://wiki.gentoo.org/wiki/GRUB http://wiki.gentoo.org/wiki/GRUB2_Quick_Start You can also have your /boot and / on the same partition.
Re: [gentoo-user] New PC, new boot concepts
On Fri, Dec 19, 2014 at 9:03 PM, Sid S wrote: > > Anyway, I am kind of surprised people are still having problems with UEFI. > It's necessary to turn SecureBoot off, but otherwise I just got everything to > work. > I've yet to do an EFI install, but presumably you could either sign the kernel or bootloader and load the key you used into the firmware (which is required to be supported for Microsoft compliance, so if it doesn't work you might consider mentioning it to Microsoft in the hope that they yank the Windows logo from the machine), or you could load an MS-signed shim which I believe exists. The latter is probably preferable as it basically gives you a secondary bootloader which makes the system a bit more flexible, but it still protects you from boot manipulation since the shim requires physical keyboard presence to change the boot config. I wouldn't completely discount secure boot - if you can configure it then it actually can be a powerful tool to give you more control over your own machine, much like a TPM. -- Rich
Re: [gentoo-user] New PC, new boot concepts
> I still use GRUB to boot ISO images, and have a sysrescd image in /boot > for this. With UEFI, you can have more than one bootloader installed. I > hadn't considered the possibility of UEFI booting to an ISO directly, I'd > be interested to know if it is possible. Typically one takes the contents of the iso, places that on a partition, and then makes it bootable with grub. I'm not sure you can boot the iso directly. >> Finally, what's your opinion on 'secure boot'? > > That the main security is is aimed at is job security for MS employees. I > turn it off straight away. It is not a completely stupid idea. When it is adequately supported it is something I intend to use. It is possible (unless I misunderstood something) to provide your own keys and sign your own OS partition. Anyway, I am kind of surprised people are still having problems with UEFI. It's necessary to turn SecureBoot off, but otherwise I just got everything to work.
Re: [gentoo-user] Re: Fresh gen too install - unsuccesful
Am Samstag, 20.12.2014 um 03:57 schrieb German : > Just a follow up to my original question. I've installed grub > on /dev/SDA literally following the quide. And I just realized why I I think the MBR of your first drive (/dev/sda) is usually the right place for grub if you only have one OS (gentoo) installed. > made /dev/sda1 partition obviously designed for grub? Should I have > been install grub into /dev/sda1? I also have uefi system and I think > it matters. Thanks everyone for clarifications You really should share more information. What version of grub do you have installed? How do you have it installed (commands and parameters). And of course you should post the config file. How many drives do you have you attached to your computer? Sometimes a connected USB-Stick or eSATA drive confuses the drive order so that grub can't boot or even has been installed at another place than you intended. I don't have a clue about UEFI and I never used grub2. But I think someone else could help you in that case, if you give enough infos. Regards wabe > German wrote: > > >Is anyone can advice on where to dig. It seems that grub isn't > >installed because I can't access it pressing ESC key and I return to > >bios. During installation there were no errors reported, the system > >installed grub just fine. Also grub.cfg found all my kernels and > >ramdisks? Thanks for any suggestion. What would you do?
[gentoo-user] Re: Fresh gen too install - unsuccesful
Just a follow up to my original question. I've installed grub on /dev/SDA literally following the quide. And I just realized why I made /dev/sda1 partition obviously designed for grub? Should I have been install grub into /dev/sda1? I also have uefi system and I think it matters. Thanks everyone for clarifications German wrote: >Is anyone can advice on where to dig. It seems that grub isn't installed >because I can't access it pressing ESC key and I return to bios. During >installation there were no errors reported, the system installed grub just >fine. Also grub.cfg found all my kernels and ramdisks? Thanks for any >suggestion. What would you do?
[gentoo-user] [OT emacs-vcs/gnus] movemail failure (on permissions)
Hopefully some emacs/gnus adept will have some idea what's going here. I've hit a snag after deciding to use the gentoo approach to acquiring and tracking a fast moving emacs from bzr sources. I've emerged emacs-vcs and a few required pkgs. After adjusting my emacs init files to suit the new arrangement, when I fire up gnus; I hit failure of `movemail' soon as it tries to check and pull mail. (From *Messages* buffer) , | Reading incoming mail from directory... | Processing mail from ~/.emacs-mail-crash-box... | Reading incoming mail from file... | movemail: Permission denied for /var/spool/mail/harry (1 return). Continue? (y or n) n | Mail source (file :path /var/spool/mail/harry) error (Permission denied for /var/spool/mail/harry). Continue? (y or n) n | Mail source (file :path /var/spool/mail/harry) failed: (error Cannot get new mail) | nnml: Reading incoming mail (no new mail)...done ` Something in those permisssions is set wrong: ls -ld /var/spool/mail drwxr-xr-x 2 mail root 4096 Dec 19 13:30 /var/spool/mail ls -l /var/spool/mail total 4 -rw--- 1 harry nfsu 676 Dec 19 13:30 harry ls -l /usr/libexec/emacs/25.0.50/i686-pc-linux-gnu/ -rwxr-xr-x 1 root root 9552 Dec 19 16:19 hexl -rwxr-xr-x 1 root root 22016 Dec 19 16:19 movemail -rwxr-xr-x 1 root root 5412 Dec 19 16:19 profile -rwxr-xr-x 1 root root 21067 Dec 19 16:19 rcs2log -rwxr-xr-x 1 root root 9636 Dec 19 16:19 update-game-score --- --- ---=--- --- --- On other Linux OSs I vaguely recall something about movemail being setuid or setgid or maybe both perhaps that is the problem. I tried both but the error didn't change
Re: [gentoo-user] Returning to chrooted environment?
On Friday 19 Dec 2014 20:30:07 Alan McKinnon wrote: > On 19/12/2014 21:18, German wrote: > > During installation, just before running genkernel all, pressed something > > by mistake in screen and that got me out of chroot. I have screen split > > up horizontally and now whatever I type appears on two terminals > > simultaneously. How do I enter in a stage where I left off and try to > > finish installation? Thanks a lot > > Repeat your earlier steps in the same order up to the point where you > started installing stuff (you don't need to do that again) and pick up > where you left off. > > The steps you must do are things like copy resolv.conf, mount stuff > inside the chroot and of course run chroot itself Also, to get yourself out of a split screen have a look at these shortcuts: http://www.pixelbeat.org/lkdb/screen.html (or have a look at 'man screen'). -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
On Friday 19 Dec 2014 18:23:36 meino.cra...@gmx.de wrote: > Mick [14-12-19 17:12]: > > On Friday 19 Dec 2014 15:53:53 meino.cra...@gmx.de wrote: > > > Mick [14-12-19 16:52]: > > > > On Friday 19 Dec 2014 15:23:58 meino.cra...@gmx.de wrote: > > > > > Peter Humphrey [14-12-19 16:12]: > > > > > > On Friday 19 December 2014 11:18:34 Mick wrote: > > > > > > > I run fix_libtool_files.sh after a new gcc > > > > > > > is installed, BEFORE I remove the old version. I made a bit of > > > > > > > a habit of this, but I don't know if modern ebuilds of gcc > > > > > > > actually run the same script post install. > > > > > > > > > > > > I've found that emerge -c gcc runs fix_libtool_files.sh > > > > > > automatically. This has been true for quite a while now. > > > > > > > > > > Hi Peter, > > > > > > > > > > that implies that running fix_libtool_files.sh right after > > > > > installing gcc is ok before removing the old gcc. This is the > > > > > opposite from previous mail. > > > > > > > > > > By the way: I could'n find optino "-c" for emerge in the > > > > > manpages... > > > > > > > > Meino, to avoid misunderstandings: > > > > > > > > 1. Emerge the new gcc package. > > > > > > > > 2. Use gcc-config to change to the new gcc version. > > > > > > > > 3. Run 'env-update && source /etc/profile'. > > > > > > > > 4. Run fix_libtool_files.sh, although I would think that this is > > > > redundant these days. > > > > > > > > 5. Unmerge the old gcc version. > > > > > > Hi Mick, > > > > > > thanks for makeing things clear! :) > > > One man - one word - one gcc version! :)) > > > > > > THX! > > > > You're welcome. Peter's right the '--depclean --verbose' options will > > warn you if something you have already installed depends on the old gcc > > version. > > Hi, > > backup done! > > now... > > gcc-4.8.3 is installed, gcc-config points to the new compiler, the > environment is updated (I logged out and in again) and I checked > /etc/env.d/04gcc-armv7a-hardfloat-linux-gnueabi for using the new > compiler. So everything is fine...except... > > If I would remove the old compiler now, my system would again be > broken. > > I run the following little loop (zsh) "(.)" means: "only files"): > > for i in /sbin/*(.) /bin/*(.) /usr/sbin/*(.) /usr/bin/*(.) > do > ldd $i | grep -q -s > '/usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libgcc_s.so.1' if [[ > "$?" == "0" ]] ; then echo $i >> /tmp/gccfiles6.txt ; fi done > > I did find > > 1033 > > executables still linked against > > /usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libgcc_s.so.1 > > and may be there are more being linked against other libs of the old > compiler. > > Should I rebuild Gentoo? > This would take a very very long time on this little system... > > How to proceed now? Well, it would be unwise to uninstall the old version with all these links in your filesystem. What do you get if you run manually 'fix_libtool_files.sh'? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New PC, new boot concepts
On Fri, 19 Dec 2014 15:22:04 +, Mick wrote: > The MoBo is capable of booting in CMS mode, but I am not sure if there > are any benefits in creating a 2MB partition for a conventional MBR > bootloader, or I should forego MBR altogether and go directly with a > GPT FAT32 EFI System Partition (ESP). > > If the latter is the way to go and I forget all things I ever learned > about MBR, does the 550MB FAT32 ESP partition have to be at the > beginning of the drive? Yes, it should be sda1. You can also use this partition as /boot, and should do so if you use Gummiboot. > Is it beneficial to install a Linux boot loader/manager like GRUB2, or > rEFInd, etc., or should I just use the kernel EFI Boot Stub to boot > gentoo with? I use a bootloader, gummiboot, as it makes it easy to select different options when booting. > The PC will single boot in Gentoo, although I may drop in > a sysrescuecd image for recovery purposes and would be nice to be able > to boot this straight off the disk, without having to burn it on a > CDROM. Is it simply a matter of adding the LiveCD iso in the ESP with > a .efi suffix, or will I need to use efibootmgr to inform the UEFI > about *any* kernel images in the ESP other than the default > EFI/BOOT/bootx64.efi? I still use GRUB to boot ISO images, and have a sysrescd image in /boot for this. With UEFI, you can have more than one bootloader installed. I hadn't considered the possibility of UEFI booting to an ISO directly, I'd be interested to know if it is possible. > Finally, what's your opinion on 'secure boot'? That the main security is is aimed at is job security for MS employees. I turn it off straight away. -- Neil Bothwick Top Oxymorons Number 44: Advanced BASIC pgpFULoMpJtVJ.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Fresh gen too install - unsuccesful
141220 German wrote: > It seems that Grub isn't installed, > because I can't access it pressing ESC key and I return to BIOS. > During installation there were no errors reported, > the system installed Grub just fine > & grub.cfg found all my kernels and ramdisks. If you continue to have difficult with Grub, try Lilo instead. It's simpler & quite adequate for ordinary use. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
[gentoo-user] Fresh gen too install - unsuccesful
Is anyone can advice on where to dig. It seems that grub isn't installed because I can't access it pressing ESC key and I return to bios. During installation there were no errors reported, the system installed grub just fine. Also grub.cfg found all my kernels and ramdisks? Thanks for any suggestion. What would you do?
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
meino.cra...@gmx.de wrote: > Dale [14-12-19 17:08]: >> Mick wrote: >>> Meino, to avoid misunderstandings: 1. Emerge the new gcc package. 2. >>> Use gcc-config to change to the new gcc version. 3. Run 'env-update && >>> source /etc/profile'. 4. Run fix_libtool_files.sh, although I would >>> think that this is redundant these days. 5. Unmerge the old gcc version. >> I don't recall ever running fix_libtool_files.sh after switching gcc >> versions. Usually when I see a gcc upgrade, I emerge it, switch to it >> and the usual profile thing, run emerge -e world JUST to be safe, then >> unmerge the old gcc. That's all I usually do here. I have skipped the >> emerge -e world a time or two. >> >> Am I just lucky, not likely as some may know, or does emerge -e world >> catch it or what? Now I'm curious. >> >> Dale >> >> :-) :-) >> >> > Hi Dale, > > I started compiling the new gcc this morning about ~7:00 AM...just a > few minutes ago stage3 finishes. Now ... before doing anything else... > I am makeing a backup of all that, so...if anything fails...I am able > to reinstall the status quo. > > I will keep you informed, what happens to my little embedded system... > > Best > Meino > > That's the thing about slow systems, you want to do it right the first time because it takes to much time to repeat something. Heck, I have a 4 core AMD CPU with 16GBs of ram here and I still would rather do it right the first time. If you have something slow that takes days to do something, you really want plan A to work. I'm also wondering if there have been changes to emerge that could make a difference. I run the latest unstable non * version. I sorta like having all the new improvements. I'm just not sure if that affects the issue here is all. Dale :-) :-)
Re: [gentoo-user] Returning to chrooted environment?
On 19/12/2014 21:18, German wrote: > During installation, just before running genkernel all, pressed something by > mistake in screen and that got me out of chroot. I have screen split up > horizontally and now whatever I type appears on two terminals simultaneously. > How do I enter in a stage where I left off and try to finish installation? > Thanks a lot > Repeat your earlier steps in the same order up to the point where you started installing stuff (you don't need to do that again) and pick up where you left off. The steps you must do are things like copy resolv.conf, mount stuff inside the chroot and of course run chroot itself -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] Returning to chrooted environment?
During installation, just before running genkernel all, pressed something by mistake in screen and that got me out of chroot. I have screen split up horizontally and now whatever I type appears on two terminals simultaneously. How do I enter in a stage where I left off and try to finish installation? Thanks a lot
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
Mick [14-12-19 17:12]: > On Friday 19 Dec 2014 15:53:53 meino.cra...@gmx.de wrote: > > Mick [14-12-19 16:52]: > > > On Friday 19 Dec 2014 15:23:58 meino.cra...@gmx.de wrote: > > > > Peter Humphrey [14-12-19 16:12]: > > > > > On Friday 19 December 2014 11:18:34 Mick wrote: > > > > > > I run fix_libtool_files.sh after a new gcc > > > > > > is installed, BEFORE I remove the old version. I made a bit of a > > > > > > habit of this, but I don't know if modern ebuilds of gcc actually > > > > > > run the same script post install. > > > > > > > > > > I've found that emerge -c gcc runs fix_libtool_files.sh > > > > > automatically. This has been true for quite a while now. > > > > > > > > Hi Peter, > > > > > > > > that implies that running fix_libtool_files.sh right after installing > > > > gcc is ok before removing the old gcc. This is the opposite from > > > > previous mail. > > > > > > > > By the way: I could'n find optino "-c" for emerge in the manpages... > > > > > > Meino, to avoid misunderstandings: > > > > > > 1. Emerge the new gcc package. > > > > > > 2. Use gcc-config to change to the new gcc version. > > > > > > 3. Run 'env-update && source /etc/profile'. > > > > > > 4. Run fix_libtool_files.sh, although I would think that this is > > > redundant these days. > > > > > > 5. Unmerge the old gcc version. > > > > Hi Mick, > > > > thanks for makeing things clear! :) > > One man - one word - one gcc version! :)) > > > > THX! > > You're welcome. Peter's right the '--depclean --verbose' options will warn > you if something you have already installed depends on the old gcc version. > > -- > Regards, > Mick Hi, backup done! now... gcc-4.8.3 is installed, gcc-config points to the new compiler, the environment is updated (I logged out and in again) and I checked /etc/env.d/04gcc-armv7a-hardfloat-linux-gnueabi for using the new compiler. So everything is fine...except... If I would remove the old compiler now, my system would again be broken. I run the following little loop (zsh) "(.)" means: "only files"): for i in /sbin/*(.) /bin/*(.) /usr/sbin/*(.) /usr/bin/*(.) do ldd $i | grep -q -s '/usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libgcc_s.so.1' if [[ "$?" == "0" ]] ; then echo $i >> /tmp/gccfiles6.txt ; fi done I did find 1033 executables still linked against /usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libgcc_s.so.1 and may be there are more being linked against other libs of the old compiler. Should I rebuild Gentoo? This would take a very very long time on this little system... How to proceed now? Best Meino
Re: [gentoo-user] New PC, new boot concepts
* Mick [141219 11:13]: > On Friday 19 Dec 2014 15:46:43 Todd Goodman wrote: > > * Mick [141219 10:22]: > > [SNIP] > > > > > I am trying to find out what is considered good practice as far as > > > UEFI/MBR and boot management goes. > > > > FWIW, I've built recent machines with UEFI/GPT but I mostly build recent > > machines using BIOS-mode/GPT or MBR. It usually depends on how well the > > mobo I'm using works with either. > > > > Some of the mobos I've used have some seriously crummy UEFI > > implementations that look like they installed Windows and that worked so > > didn't bother testing any further. > > > > I don't dual-boot windows so BIOS/GPT works OK (I believe windows still > > assumes UEFI == GPT and BIOS == MBR but I don't know.) > > > > Obviously I'm not using secure boot if I'm running in BIOS mode. > > > > Just my $.02, > > Thanks Todd, > > Are you saying that there is no benefit in moving to UEFI for Linux usage, if > the MoBo can boot in conventional BIOS mode? I guess what I'm saying is that I've had problems with some mobos running UEFI (and also BIOS) with any non-windows OS. So I don't usually bother with UEFI mode anymore as I find it more hassle than it's worth for me. Someone else may (probably) has some reasons why running UEFI is more beneficial, but I haven't noticed any. But these machines are not booting any other OS aside from Gentoo. If I were dual-booting Windows then I'd go UEFI/GPT for sure. Todd
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
On Friday 19 Dec 2014 16:06:46 Dale wrote: > Mick wrote: > > Meino, to avoid misunderstandings: 1. Emerge the new gcc package. 2. > > Use gcc-config to change to the new gcc version. 3. Run 'env-update && > > source /etc/profile'. 4. Run fix_libtool_files.sh, although I would > > think that this is redundant these days. 5. Unmerge the old gcc version. > > I don't recall ever running fix_libtool_files.sh after switching gcc > versions. Usually when I see a gcc upgrade, I emerge it, switch to it > and the usual profile thing, run emerge -e world JUST to be safe, then > unmerge the old gcc. That's all I usually do here. I have skipped the > emerge -e world a time or two. > > Am I just lucky, not likely as some may know, or does emerge -e world > catch it or what? Now I'm curious. I don't recall having run emerge -e world following a gcc update since about 2005, on at least half a dozen gentoo installations. This is because I do not have a need to have ALL my systems and their applications rebuilt with the very latest gcc version. Bear in mind that some packages may not even use gcc, so you're remerging them unnecessarily. Since electricity is not free in my household, I only emerge what I need. Of course, YMMV. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
Dale [14-12-19 17:08]: > Mick wrote: > > Meino, to avoid misunderstandings: 1. Emerge the new gcc package. 2. > > Use gcc-config to change to the new gcc version. 3. Run 'env-update && > > source /etc/profile'. 4. Run fix_libtool_files.sh, although I would > > think that this is redundant these days. 5. Unmerge the old gcc version. > > I don't recall ever running fix_libtool_files.sh after switching gcc > versions. Usually when I see a gcc upgrade, I emerge it, switch to it > and the usual profile thing, run emerge -e world JUST to be safe, then > unmerge the old gcc. That's all I usually do here. I have skipped the > emerge -e world a time or two. > > Am I just lucky, not likely as some may know, or does emerge -e world > catch it or what? Now I'm curious. > > Dale > > :-) :-) > > Hi Dale, I started compiling the new gcc this morning about ~7:00 AM...just a few minutes ago stage3 finishes. Now ... before doing anything else... I am makeing a backup of all that, so...if anything fails...I am able to reinstall the status quo. I will keep you informed, what happens to my little embedded system... Best Meino
Re: [gentoo-user] New PC, new boot concepts
On Friday 19 Dec 2014 15:46:43 Todd Goodman wrote: > * Mick [141219 10:22]: > [SNIP] > > > I am trying to find out what is considered good practice as far as > > UEFI/MBR and boot management goes. > > FWIW, I've built recent machines with UEFI/GPT but I mostly build recent > machines using BIOS-mode/GPT or MBR. It usually depends on how well the > mobo I'm using works with either. > > Some of the mobos I've used have some seriously crummy UEFI > implementations that look like they installed Windows and that worked so > didn't bother testing any further. > > I don't dual-boot windows so BIOS/GPT works OK (I believe windows still > assumes UEFI == GPT and BIOS == MBR but I don't know.) > > Obviously I'm not using secure boot if I'm running in BIOS mode. > > Just my $.02, Thanks Todd, Are you saying that there is no benefit in moving to UEFI for Linux usage, if the MoBo can boot in conventional BIOS mode? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
On Friday 19 Dec 2014 15:53:53 meino.cra...@gmx.de wrote: > Mick [14-12-19 16:52]: > > On Friday 19 Dec 2014 15:23:58 meino.cra...@gmx.de wrote: > > > Peter Humphrey [14-12-19 16:12]: > > > > On Friday 19 December 2014 11:18:34 Mick wrote: > > > > > I run fix_libtool_files.sh after a new gcc > > > > > is installed, BEFORE I remove the old version. I made a bit of a > > > > > habit of this, but I don't know if modern ebuilds of gcc actually > > > > > run the same script post install. > > > > > > > > I've found that emerge -c gcc runs fix_libtool_files.sh > > > > automatically. This has been true for quite a while now. > > > > > > Hi Peter, > > > > > > that implies that running fix_libtool_files.sh right after installing > > > gcc is ok before removing the old gcc. This is the opposite from > > > previous mail. > > > > > > By the way: I could'n find optino "-c" for emerge in the manpages... > > > > Meino, to avoid misunderstandings: > > > > 1. Emerge the new gcc package. > > > > 2. Use gcc-config to change to the new gcc version. > > > > 3. Run 'env-update && source /etc/profile'. > > > > 4. Run fix_libtool_files.sh, although I would think that this is > > redundant these days. > > > > 5. Unmerge the old gcc version. > > Hi Mick, > > thanks for makeing things clear! :) > One man - one word - one gcc version! :)) > > THX! You're welcome. Peter's right the '--depclean --verbose' options will warn you if something you have already installed depends on the old gcc version. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
Mick wrote: > Meino, to avoid misunderstandings: 1. Emerge the new gcc package. 2. > Use gcc-config to change to the new gcc version. 3. Run 'env-update && > source /etc/profile'. 4. Run fix_libtool_files.sh, although I would > think that this is redundant these days. 5. Unmerge the old gcc version. I don't recall ever running fix_libtool_files.sh after switching gcc versions. Usually when I see a gcc upgrade, I emerge it, switch to it and the usual profile thing, run emerge -e world JUST to be safe, then unmerge the old gcc. That's all I usually do here. I have skipped the emerge -e world a time or two. Am I just lucky, not likely as some may know, or does emerge -e world catch it or what? Now I'm curious. Dale :-) :-)
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
Mick [14-12-19 16:52]: > On Friday 19 Dec 2014 15:23:58 meino.cra...@gmx.de wrote: > > Peter Humphrey [14-12-19 16:12]: > > > On Friday 19 December 2014 11:18:34 Mick wrote: > > > > I run fix_libtool_files.sh after a new gcc > > > > is installed, BEFORE I remove the old version. I made a bit of a habit > > > > of this, but I don't know if modern ebuilds of gcc actually run the > > > > same script post install. > > > > > > I've found that emerge -c gcc runs fix_libtool_files.sh automatically. > > > This has been true for quite a while now. > > > > Hi Peter, > > > > that implies that running fix_libtool_files.sh right after installing > > gcc is ok before removing the old gcc. This is the opposite from > > previous mail. > > > > By the way: I could'n find optino "-c" for emerge in the manpages... > > Meino, to avoid misunderstandings: > > 1. Emerge the new gcc package. > > 2. Use gcc-config to change to the new gcc version. > > 3. Run 'env-update && source /etc/profile'. > > 4. Run fix_libtool_files.sh, although I would think that this is redundant > these days. > > 5. Unmerge the old gcc version. > > -- > Regards, > Mick Hi Mick, thanks for makeing things clear! :) One man - one word - one gcc version! :)) THX! Best Meino
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
On Friday 19 Dec 2014 15:23:58 meino.cra...@gmx.de wrote: > Peter Humphrey [14-12-19 16:12]: > > On Friday 19 December 2014 11:18:34 Mick wrote: > > > I run fix_libtool_files.sh after a new gcc > > > is installed, BEFORE I remove the old version. I made a bit of a habit > > > of this, but I don't know if modern ebuilds of gcc actually run the > > > same script post install. > > > > I've found that emerge -c gcc runs fix_libtool_files.sh automatically. > > This has been true for quite a while now. > > Hi Peter, > > that implies that running fix_libtool_files.sh right after installing > gcc is ok before removing the old gcc. This is the opposite from > previous mail. > > By the way: I could'n find optino "-c" for emerge in the manpages... Meino, to avoid misunderstandings: 1. Emerge the new gcc package. 2. Use gcc-config to change to the new gcc version. 3. Run 'env-update && source /etc/profile'. 4. Run fix_libtool_files.sh, although I would think that this is redundant these days. 5. Unmerge the old gcc version. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New PC, new boot concepts
* Mick [141219 10:22]: [SNIP] > I am trying to find out what is considered good practice as far as UEFI/MBR > and boot management goes. FWIW, I've built recent machines with UEFI/GPT but I mostly build recent machines using BIOS-mode/GPT or MBR. It usually depends on how well the mobo I'm using works with either. Some of the mobos I've used have some seriously crummy UEFI implementations that look like they installed Windows and that worked so didn't bother testing any further. I don't dual-boot windows so BIOS/GPT works OK (I believe windows still assumes UEFI == GPT and BIOS == MBR but I don't know.) Obviously I'm not using secure boot if I'm running in BIOS mode. Just my $.02, Todd
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
On Friday 19 December 2014 16:23:58 meino.cra...@gmx.de wrote: > Peter Humphrey [14-12-19 16:12]: > > On Friday 19 December 2014 11:18:34 Mick wrote: > > > I run fix_libtool_files.sh after a new gcc > > > is installed, BEFORE I remove the old version. I made a bit of a > > > habit > > > of this, but I don't know if modern ebuilds of gcc actually run the > > > same script post install. > > > > I've found that emerge -c gcc runs fix_libtool_files.sh automatically. > > This has been true for quite a while now. > > that implies that running fix_libtool_files.sh right after installing > gcc is ok before removing the old gcc. This is the opposite from > previous mail. I don't know about that, but it's consistent with what you quote from Mick, above, and it works for me - though I see Mick has had a problem recently. > By the way: I could'n find optino "-c" for emerge in the manpages... It means "depclean." -- Rgds Peter.
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
On Friday 19 Dec 2014 15:09:37 Peter Humphrey wrote: > On Friday 19 December 2014 11:18:34 Mick wrote: > > I run fix_libtool_files.sh after a new gcc > > is installed, BEFORE I remove the old version. I made a bit of a habit > > of this, but I don't know if modern ebuilds of gcc actually run the same > > script post install. > > I've found that emerge -c gcc runs fix_libtool_files.sh automatically. This > has been true for quite a while now. Peter, I thought that this was the case, but recently I had to run fix_libtool_files.sh manually. I removed the old gcc thinking all is good, after I had switched to the new gcc with gcc-config, but I ended up with errors. I had to reinstall the old gcc, run fix_libtool_files.sh and then unmerge it again before the errors went away. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
Peter Humphrey [14-12-19 16:12]: > On Friday 19 December 2014 11:18:34 Mick wrote: > > I run fix_libtool_files.sh after a new gcc > > is installed, BEFORE I remove the old version. I made a bit of a habit > > of this, but I don't know if modern ebuilds of gcc actually run the same > > script post install. > > I've found that emerge -c gcc runs fix_libtool_files.sh automatically. This > has been true for quite a while now. > > -- > Rgds > Peter. > > Hi Peter, that implies that running fix_libtool_files.sh right after installing gcc is ok before removing the old gcc. This is the opposite from previous mail. By the way: I could'n find optino "-c" for emerge in the manpages... Best Meino
[gentoo-user] New PC, new boot concepts
Old dogs and new tricks springs to mind. I am building a new PC and what with UEFI, APUs and SSDs, it feels like that the world has moved a long way since the last time I had to install gentoo. I'll be taking my time to google, read and make appropriate selections, so please bear with me while I start relevant threads as necessary to complement my sparse knowledge in these topics. Starting from the top, with this thread I am trying to find out what is considered good practice as far as UEFI/MBR and boot management goes. The MoBo is capable of booting in CMS mode, but I am not sure if there are any benefits in creating a 2MB partition for a conventional MBR bootloader, or I should forego MBR altogether and go directly with a GPT FAT32 EFI System Partition (ESP). If the latter is the way to go and I forget all things I ever learned about MBR, does the 550MB FAT32 ESP partition have to be at the beginning of the drive? Is it beneficial to install a Linux boot loader/manager like GRUB2, or rEFInd, etc., or should I just use the kernel EFI Boot Stub to boot gentoo with? The PC will single boot in Gentoo, although I may drop in a sysrescuecd image for recovery purposes and would be nice to be able to boot this straight off the disk, without having to burn it on a CDROM. Is it simply a matter of adding the LiveCD iso in the ESP with a .efi suffix, or will I need to use efibootmgr to inform the UEFI about *any* kernel images in the ESP other than the default EFI/BOOT/bootx64.efi? Finally, what's your opinion on 'secure boot'? I'm mostly thinking of its benefit as a pre-boot malware protection utility, but I don't want to introduce too much complexity which may make recovery of my data difficult in the future. I've heard some horror stories resulting from NVRAM corruption, or flashing with new UEFI firmware rendering the PC unbootable, etc. but don't know if this is due to user error. If you have experience using secure boot what is your preferred method? Any other pointers and gotchas I should be careful with? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
On Friday 19 December 2014 11:18:34 Mick wrote: > I run fix_libtool_files.sh after a new gcc > is installed, BEFORE I remove the old version. I made a bit of a habit > of this, but I don't know if modern ebuilds of gcc actually run the same > script post install. I've found that emerge -c gcc runs fix_libtool_files.sh automatically. This has been true for quite a while now. -- Rgds Peter.
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
Mick [14-12-19 12:20]: > On Friday 19 Dec 2014 07:22:30 meino.cra...@gmx.de wrote: > > Bill Kenworthy [14-12-19 08:00]: > > > On 19/12/14 13:39, meino.cra...@gmx.de wrote: > > > > Hi, > > > > > > > > (this happens on a embedded system) > > > > > > > > I ran into a problem I think... > > > > > > > > As adviced I run > > > > > > > > emerge --depclean -v -p > > > > > > > > after a greater update to world. > > > > (by the way: Updateing the world is generally to a bad idea...;) > > > > > > > > Beside other things, gcc-4.7.3 was slated for removal. As > > > > gcc-4.8.3 was already installed and gcc-config shows that it > > > > is active, I started the above command without "-p" > > > > And it screws up the whole thing badly: > > > > There were many, many applications (the shell for example...) > > > > which were directly linked to > > > > /usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libgcc_s.so.1 > > > > and/or > > > > /usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libstdc++.so.6 > > > > > > > > After clearing the sdcard and reinstalling the backup I started > > > > to emerge all affected ebuilds by hand...only to find, that they > > > > were again linked against the old libs. > > > > > > > > I checked again with gcc-config and found: > > > > > > > > beagleboneblack:/root>gcc-config -L > > > > /usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.8.3 > > > > beagleboneblack:/root>gcc-config -c > > > > armv7a-hardfloat-linux-gnueabi-4.8.3 > > > > beagleboneblack:/root>gcc-config -E > > > > export > > > > PATH="/usr/armv7a-hardfloat-linux-gnueabi/gcc-bin/4.8.3:/lib/rc/bin:/b > > > > in:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bi > > > > n:/usr/local/sbin:/bin/:/opt/bin:/usr/armv7a-hardfloat-linux-gnueabi/gc > > > > c-bin/4.8.3:/usr/games/bin:/root/bin" export GCC_SPECS="" > > > > > > > > > > > > What is going on here? Why still the old compiler and its libraries > > > > are used? How can I convince Gentoo to finally switch ti gcc-4.8.3? > > > > > > > > What do you think? > > > > > > > > Best regards, > > > > Meino > > > > > > Did you run fix_libtool_files.sh? - you have to do it manually after > > > switching gcc to a bew version. > > > > > > BillK > > > > Hi Bill, > > > > Thanks for your help and hint! :) > > > > In the meanwhile I found a trace of a bad install of version 4.8.3: > > /etc/env.d/*gcc* was not updated. > > > > Currently I am reinstalling the whole gcc-4.8.3. - suit and after > > that I will call fix_libtool_files.sh. > > > > Hope it will fix it! > > Best regards, > > Meino > > This caught me out once too. I run fix_libtool_files.sh after a new gcc is > installed, BEFORE I remove the old version. I made a bit of a habit of this, > but I don't know if modern ebuilds of gcc actually run the same script post > install. > > -- > Regards, > Mick Hi Mick, if call fix_libtool_files.sh needs to be run AFTER the installation of gcc AND after removeing the old...then I never get rid of the old one, cause there are still vital (system ) applications are build against libs of the old gcc and will fail, if the old one has been removed (or better: fail /while/ the old gcc is being removed). A cat bits into its own tail, it seems... So again: how can I get out of this "circle of death and system corruption" ? Best Meino
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
On Friday 19 Dec 2014 07:22:30 meino.cra...@gmx.de wrote: > Bill Kenworthy [14-12-19 08:00]: > > On 19/12/14 13:39, meino.cra...@gmx.de wrote: > > > Hi, > > > > > > (this happens on a embedded system) > > > > > > I ran into a problem I think... > > > > > > As adviced I run > > > > > > emerge --depclean -v -p > > > > > > after a greater update to world. > > > (by the way: Updateing the world is generally to a bad idea...;) > > > > > > Beside other things, gcc-4.7.3 was slated for removal. As > > > gcc-4.8.3 was already installed and gcc-config shows that it > > > is active, I started the above command without "-p" > > > And it screws up the whole thing badly: > > > There were many, many applications (the shell for example...) > > > which were directly linked to > > > /usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libgcc_s.so.1 > > > and/or > > > /usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libstdc++.so.6 > > > > > > After clearing the sdcard and reinstalling the backup I started > > > to emerge all affected ebuilds by hand...only to find, that they > > > were again linked against the old libs. > > > > > > I checked again with gcc-config and found: > > > > > > beagleboneblack:/root>gcc-config -L > > > /usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.8.3 > > > beagleboneblack:/root>gcc-config -c > > > armv7a-hardfloat-linux-gnueabi-4.8.3 > > > beagleboneblack:/root>gcc-config -E > > > export > > > PATH="/usr/armv7a-hardfloat-linux-gnueabi/gcc-bin/4.8.3:/lib/rc/bin:/b > > > in:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bi > > > n:/usr/local/sbin:/bin/:/opt/bin:/usr/armv7a-hardfloat-linux-gnueabi/gc > > > c-bin/4.8.3:/usr/games/bin:/root/bin" export GCC_SPECS="" > > > > > > > > > What is going on here? Why still the old compiler and its libraries > > > are used? How can I convince Gentoo to finally switch ti gcc-4.8.3? > > > > > > What do you think? > > > > > > Best regards, > > > Meino > > > > Did you run fix_libtool_files.sh? - you have to do it manually after > > switching gcc to a bew version. > > > > BillK > > Hi Bill, > > Thanks for your help and hint! :) > > In the meanwhile I found a trace of a bad install of version 4.8.3: > /etc/env.d/*gcc* was not updated. > > Currently I am reinstalling the whole gcc-4.8.3. - suit and after > that I will call fix_libtool_files.sh. > > Hope it will fix it! > Best regards, > Meino This caught me out once too. I run fix_libtool_files.sh after a new gcc is installed, BEFORE I remove the old version. I made a bit of a habit of this, but I don't know if modern ebuilds of gcc actually run the same script post install. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] BluRay reproduction
Understood... I'll look for that. 2014-12-18 17:44 GMT-02:00 Neil Bothwick : > > On Thu, 18 Dec 2014 16:37:15 -0200, Fábio Emilio Costa wrote: > > > Someone had already played BD Video discs > > > > I bought a Pioneer BD player/recorder and I want to play BD films on it, > > but the things I found in net were (a) badly documented, (b) confusing > > and/or (c) Ubuntu oriented. > > You need to install MakeMKV. Then you can either rip BD-ROM discs or > stream the content and play it with something like VLC. > > > -- > Neil Bothwick > > Capt'n! The spellchecker kinna take this abuse! > -- Obrigado! Fabio Emilio Costa São Bernardo do Campo - SP - Brazil fabiocosta0...@gmail.comLinux User #416439(counter.li.org) ICQ #:173799674 Twitter:@HufflepuffBR Google+: http://plus.google.com/+FabioEmilioCosta Facebook: http://facebook.com/fabiocosta0305 Blog: hogwartslinux.wordpress.com "Copie. Seja Legal. Não seja trouxa! Use Software Livre!"
Re: [gentoo-user] No burners are currently available
Joseph wrote: > I've tried to burn a dvd from a command line: > cdrecord -v -eject -dao speed=4 dev=0,0,0 dvd.iso > > but I got a generic error message that it is not possible. Not sending the message does not help. BTW: You specified dev=0,0,0, why did you do that? Since 2004, cdrecord automatically finds the drive in case that there is no more than one available drive in the system. Cdrecord may better know it's address. Jörg -- EMail:jo...@schily.net(home) Jörg Schilling D-13353 Berlin joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'
Re: [gentoo-user] No burners are currently available
Joseph wrote: > When I start Xfburn I get a message: > No burners are currently available > Possibly the disc(s) are in use, and cannot get accessed. > > How to check which program is using the DVD drive? > "ps fax" is not showing that any program is using it. There is no useful SCSI locking on Linux, so there must be a different problem. Try to call "cdrecord -scanbus" Jörg -- EMail:jo...@schily.net(home) Jörg Schilling D-13353 Berlin joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'
