Re: [gentoo-user] New PC, new boot concepts
On 20 December 2014 02:03:41 GMT+00:00, Sid S wrote: > > 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. You can boot an ISO directly with GRUB2, no need to unpack anything I've been doing it for years. I would be interested to know if is is possible with UEFI but without GRUB -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
On Friday 19 December 2014 19:23:36 meino.cra...@gmx.de wrote: > 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... You don't mention env-update. You should do that explicitly - logging out and in won't do it. > If I [removed] the old compiler now, my system would again be > broken. --->8 > How to proceed now? I'd start again from just after emerging the new version of GCC. -- Rgds Peter.
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
On Friday 19 December 2014 17:20:17 meino.cra...@gmx.de wrote: > I will keep you informed, what happens to my little embedded system... Ah. I have a couple of chroots on my workstation for compiling packages for small boxes. I suggest you do the same. As long as you know all the right USE flags, etc., it should be much quicker to build the system in the chroot, then rsync /usr/portage to the target box and install from packages. -- Rgds Peter.
Re: [gentoo-user] Re: Fresh gen too install - unsuccesful
On Saturday 20 Dec 2014 05:28:49 Tomas Mozes wrote: > 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-na > tively > > 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. All of this is good advice, but ONLY IF the MoBo has been configured to boot in CMS/Legacy_BIOS mode. Otherwise, UEFI will bail out at boot time because it does neither read, nor use the MBR bootloader. Depending on the boot options provided by the motherboard, the hard drive can be configured to boot in legacy-BIOS using an MBR, in UEFI mode using an ESP partition, or both depending on the BIOS selection at boot time. -- 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-20 02:47]: > 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 > > :-) :-) > Hi, after a few more non-booting-systems and backup-reinstalls I think I know whats the reason is...but by I dont know how to get out of it: The system becomes inaccessible if I do an env-update and reboot. Reason for that are binaries, in which the path to the old gcc is hardcoded. With the sdcard mounted I checked that with my PC: I did a grep -r '\/usr\/lib\/gcc\/armv7a-hardfloat-linux-gnueabi\/4.7.3' on ALL files of the sdcard and found "thousands" of hardcoded links to the old gcc inside binaries... The new gcc installed but not doing env-update implies that any further compilation will link to the old gcc. Doing env-update implies a system which will not survive the next reboot. What now? Best regards, Meino
Re: [gentoo-user] Re: Fresh gen too install - unsuccesful
That's where I think the problem lies Mick. My system is uefi. Too bad that gen too officially doesn't support it. I just wish gentoo developers take a closer look at the issue and come out with uefi capable minimal installation CD and clear uefi installation documentation Mick wrote: >On Saturday 20 Dec 2014 05:28:49 Tomas Mozes wrote: >> 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-na >> tively >> >> 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. > >All of this is good advice, but ONLY IF the MoBo has been configured to boot >in CMS/Legacy_BIOS mode. Otherwise, UEFI will bail out at boot time because >it does neither read, nor use the MBR bootloader. > >Depending on the boot options provided by the motherboard, the hard drive can >be configured to boot in legacy-BIOS using an MBR, in UEFI mode using an ESP >partition, or both depending on the BIOS selection at boot time. > >-- >Regards, >Mick
Re: [gentoo-user] New PC, new boot concepts
On 12/19/2014 07:22 AM, Mick wrote: > 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. I got myself an Intel NUC some months ago and ran into this problem. I wound up using UEFI+GPT with grub2 and had no issues, other than learning new grub2 syntax. I didn't like the idea of it scanning automatically and adding new entries. > 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). Keep in mind that your motherboard may have to boot in UEFI to get access to features. For example, my NUC's hdmi audio will not work booted in CMS mode. > 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? I found it useful to have grub2 for testing new kernels. I set up this box mostly as an appliance (mythtv frontend) but sometimes booting to recovery etc is useful. Especially since you can boot a Mint ISO with UEFI support when something barfs. > 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? I didn't bother with it. > > Any other pointers and gotchas I should be careful with? Only thing I screwed up with when messing around with my new NUC was I set the grub platform incorrectly. I used pc-x86_64 instead of efi-64 (I think, it's been a while.) Once I had the grub platform set properly the install went well. Dan
Re: [gentoo-user] Re: Fresh gen too install - unsuccesful
On Sat, Dec 20, 2014 at 10:34 AM, German wrote: > That's where I think the problem lies Mick. My system is uefi. Too bad that > gen too officially doesn't support it. I just wish gentoo developers take a > closer look at the issue and come out with uefi capable minimal installation > CD and clear uefi installation documentation Well, while it's not covered in the official side of the install docs, this wiki page was how I handled my system when I first ended up with a UEFI laptop here (Win8 didn't even make it 12hrs for me ;) -- http://wiki.gentoo.org/wiki/UEFI_Gentoo_Quick_Install_Guide It only has one minor issue, and that's the lack of mentioning first and foremost that, to configure UEFI, you have to be UEFI booted already (it does get around to noting it about the halfway mark). Any UEFI compatible linux livecd/usb will work, though. -- Poison [BLX] Joshua M. Murphy
Re: [gentoo-user] Re: Fresh gen too install - unsuccesful
German wrote: > That's where I think the problem lies Mick. My system is uefi. Too bad that > gen too officially doesn't support it. I just wish gentoo developers take a > closer look at the issue and come out with uefi capable minimal installation > CD and clear uefi installation documentation > > Does this help: http://wiki.gentoo.org/index.php?search=uefi&title=Special%3ASearch&go=Go I see a couple links there about it. I'm pretty sure that the docs are moving to the wiki. Don't forget to search there for docs too. Dale :-) :-)
Re: [gentoo-user] New PC, new boot concepts
On Fri, Dec 19, 2014 at 10:22 AM, Mick wrote: > > 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? For refind and gummiboot, you have to enable the efi boot stub because they're boot managers, rather than boot loaders like grub. If you want to use the efi boot stub, whether directly or via gummiboot or refind, you have to have the kernel (and initramfs if it exists) on a fat partition. Unlike with bios firmware, you can have them all co-exist. AFAIK only grub can boot from an iso file. You have to have a "loopback loop path_to_iso_file" line (which I think of as a "mount -o loop ...") in that iso's menuentry stanza. And its "linux ..." line will be dependent on the iso from which you're booting. The systemrescue iso needs either "findiso=..." or "isoloop=...", I've forgotten.
Re: [gentoo-user] New PC, new boot concepts
On Fri, Dec 19, 2014 at 11:12 AM, Mick wrote: > On Friday 19 Dec 2014 15:46:43 Todd Goodman wrote: >> * Mick [141219 10:22]: >> >>> 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.) > > Are you saying that there is no benefit in moving to UEFI for Linux usage, if > the MoBo can boot in conventional BIOS mode? The advantage of efi over bios is that the boot loader doesn't have to embed anything in the mbr, the post mbr gap, or the bios boot partition.
Re: [gentoo-user] Re: Fresh gen too install - unsuccesful
On Sat, Dec 20, 2014 at 10:34 AM, German wrote: > > That's where I think the problem lies Mick. My system is uefi. Too bad that > gen too officially doesn't support it. I just wish gentoo developers take a > closer > look at the issue and come out with uefi capable minimal installation CD and > clear uefi installation documentation http://wiki.gentoo.org/wiki/UEFI_Gentoo_Quick_Install_Guide
[gentoo-user] Re: Making DVD high resolution
On 2014-12-18, Joseph wrote: > On 12/18/14 19:10, J. Roeleveld wrote: >>On 18 December 2014 18:50:09 CET, Joseph wrote: >>>I've used "Imagination" to make VOB and set in preferences resolution >>>1920 x 1080 HD >>>made VOB. How do I check the VOB frame size settings? >>> >>>When I tried to made HD video using DVD Styler the max frame rate I can >>>set to make DVD ISO is 720x480. >>>How to make DVD with higher resolution? >> >>You can't. >> >>The DVD spec doesn't support HD video. > > So what format do I have to burn the disk in, in order to have lets say 1920 > x 1080 HD > Anything that is not DVD-Video. The DVD-Video standard is very strict about which frame sizes and frame rates are allowed, as well as which codecs can be used and their parameters. You can try to save the 1920x1080 video in a normal file using some container and generate an ISO9660 filesystem containing that file (mkisofs can do that), and then you can burn it (cdrecord from cdrtools). Some table DVD-Video players may or may not be able to play a video file in a DVD prepared in this way. But if you want to stick to the DVD-Video standard, you must use the frame sizes and frame rates specified in the standard. -- Nuno Silva Helsinki, Finland
[gentoo-user] ssh -X problem [no help sofar on ssh group]
This properly belongs on the ssh group, but posting there has not gotten
any responses... and the list is quite slow to boot.
I like using ssh -X to other lan remotes but with new versions of openssh
or perhaps the configs, it only works 1 way.
I can `ssh -X' to the gentoo host from a debian host but not the other
way round.
Two different versions of openssh appear to be involved. But not sure
how different they are.
RHOST=a debian HOST
LHOST= Gentoo HOST
ssh -vN $RHOST 2>&1|grep "remote software version"
[...] OpenSSH_6.7p1 Debian-3
ssh -vN $LHOST 2>&1|grep "remote software version"
[...] OpenSSH_6.7p1-hpn14v5
One thing I tried to do was to copy the RHOST sshd_config and ssh_config to
LHOST. Restart and try again... there were a few incompatible bits in
the files so after commenting a few out until no config errors.
However ssh -X still displayed the error and would NOT work when:
ssh -X RHOST from LHOST
({Note that plain ssh LHOST or RHOST works in any direction}
Error outut with ssh -X $RHOST "xterm"
,
| Warning: untrusted X11 forwarding setup failed: xauth key data not generated
| Warning: No xauth data; using fake authentication data for X11 forwarding.
| Invalid MIT-MAGIC-COOKIE-1 keyxterm: Xt error: Can't open display:
localhost:10.0
`
[Full Error output with ssh -vv -X is very lengthy so is attached at the end]
I'm not seeing how to debug this further. So going back to the stock
version of sshd_config ssh_config on gentoo with two changes:
commented out this line:
PasswordAuthentication no
added this:
X11Forwarding yes
--- --- ---=--- --- ---
Full sshd_config on LHOST: sudo grep ^[^#] /etc/ssh/sshd_config
--- --- ---=--- --- ---
UsePAM yes
X11Forwarding yes
PrintMotd no
PrintLastLog no
UsePrivilegeSeparation sandbox# Default for new installations.
Subsystem sftp/usr/lib/misc/sftp-server
AcceptEnv LANG LC_*
--- Config END---
--- --- ---=--- --- ---
Full ssh_config on LHOST: sudo grep ^[^#] /etc/ssh/ssh_config
--- --- ---=--- --- ---
ForwardX11 yes
SendEnv LANG LC_*
--- Config END---
###
Now the same info for RHOST
--- --- ---=--- --- ---
Full sshd_config on RHOST: ssh root@RHOST "grep ^[^#] /etc/ssh/sshd_config"
--- --- ---=--- --- ---
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
AcceptEnv LANG LC_*
ChallengeResponseAuthentication no
IgnoreRhosts yes
HostbasedAuthentication no
KeyRegenerationInterval 3600
LogLevel INFO
LoginGraceTime 120
PermitEmptyPasswords no
PermitRootLogin yes
Port 22
PrintLastLog yes
PrintMotd no
Protocol 2
PubkeyAuthentication yes
RSAAuthentication yes
RhostsRSAAuthentication no
ServerKeyBits 1024
SyslogFacility AUTH
StrictModes yes
Subsystem sftp/usr/lib/misc/sftp-server
TCPKeepAlive yes
UsePAM yes
UsePrivilegeSeparation sandbox
X11Forwarding yes
--- Config END---
--- --- ---=--- --- ---
Full ssh_config on RHOST: ssh root@RHOST "grep ^[^#] /etc/ssh/ssh_config"
--- --- ---=--- --- ---
Host *
ForwardX11 yes
SendEnv LANG LC_*
HashKnownHosts yes
--- Config END---
The only thing more I can think to include is the full lengthy output of
ssh -vv -X
HOST:gv ~
harry > ssh -vv -X harry@dv 'xterm'
OpenSSH_6.7p1-hpn14v5, OpenSSL 1.0.1j 15 Oct 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 20: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to dv [192.168.0.5] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/harry/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/harry/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/harry/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/harry/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/harry/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/harry/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/harry/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/harry/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version st
Re: [gentoo-user] Re: Fresh gen too install - unsuccesful
Thanks Poison. SystemRescueCD is capable of booting in uefi so I can install gen too from it? I have heard good things about it "Poison BL." wrote: >On Sat, Dec 20, 2014 at 10:34 AM, German wrote: >> That's where I think the problem lies Mick. My system is uefi. Too bad that >> gen too officially doesn't support it. I just wish gentoo developers take a >> closer look at the issue and come out with uefi capable minimal installation >> CD and clear uefi installation documentation > >Well, while it's not covered in the official side of the install docs, >this wiki page was how I handled my system when I first ended up with >a UEFI laptop here (Win8 didn't even make it 12hrs for me ;) -- > >http://wiki.gentoo.org/wiki/UEFI_Gentoo_Quick_Install_Guide > >It only has one minor issue, and that's the lack of mentioning first >and foremost that, to configure UEFI, you have to be UEFI booted >already (it does get around to noting it about the halfway mark). Any >UEFI compatible linux livecd/usb will work, though. > >-- >Poison [BLX] >Joshua M. Murphy >
Re: [gentoo-user] Re: Fresh gen too install - unsuccesful
On Saturday 20 Dec 2014 17:07:47 German wrote: > Thanks Poison. SystemRescueCD is capable of booting in uefi so I can > install gen too from it? I have heard good things about it Yes, this is what I am going to use to attempt to install Gentoo in UEFI. I have used it for years now to install Gentoo with a conventional BIOS. PS. Can you please avoid top-posting in this mailing list. It breaks the logical question & answer of the thread. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Fresh gen too install - unsuccesful
Sorry Mick. I am on android tablet and have no clue how to modify message body Mick wrote: >On Saturday 20 Dec 2014 17:07:47 German wrote: >> Thanks Poison. SystemRescueCD is capable of booting in uefi so I can >> install gen too from it? I have heard good things about it > >Yes, this is what I am going to use to attempt to install Gentoo in UEFI. > >I have used it for years now to install Gentoo with a conventional BIOS. > >PS. Can you please avoid top-posting in this mailing list. It breaks the >logical question & answer of the thread. > >-- >Regards, >Mick
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
> On Dec 20, 2014, at 17:56, meino.cra...@gmx.de wrote: > > Dale [14-12-20 02:47]: >> 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 >> >> :-) :-) > > Hi, > > after a few more non-booting-systems and backup-reinstalls I think > I know whats the reason is...but by I dont know how to get out of it: > > The system becomes inaccessible if I do an env-update and reboot. > > Reason for that are binaries, in which the path to the old gcc is > hardcoded. With the sdcard mounted I checked that with my PC: > I did a > >grep -r '\/usr\/lib\/gcc\/armv7a-hardfloat-linux-gnueabi\/4.7.3' > > on ALL files of the sdcard and found "thousands" of hardcoded links > to the old gcc inside binaries... > > The new gcc installed but not doing env-update implies that any > further compilation will link to the old gcc. > > Doing env-update implies a system which will not survive the next > reboot. > > What now? If i understand your situation correctly, do: gcc-config "to set the new version" env-update logout login emerge --deep --update world emerge --depclean revdep-rebuild This will take a long time but will get your system working again. If you don't wan't to do that you can of course tweak the libraries with binary tools. That is easy if you know what you are doing. To prevent this in the future always before world update, update gcc and glibc first if tere is a new version available. Gcc-config is crusial after you have installed a bew version of gcc. -- -Matti
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
Matti Nykyri [14-12-20 19:48]: > > On Dec 20, 2014, at 17:56, meino.cra...@gmx.de wrote: > > > > Dale [14-12-20 02:47]: > >> 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 > >> > >> :-) :-) > > > > Hi, > > > > after a few more non-booting-systems and backup-reinstalls I think > > I know whats the reason is...but by I dont know how to get out of it: > > > > The system becomes inaccessible if I do an env-update and reboot. > > > > Reason for that are binaries, in which the path to the old gcc is > > hardcoded. With the sdcard mounted I checked that with my PC: > > I did a > > > >grep -r '\/usr\/lib\/gcc\/armv7a-hardfloat-linux-gnueabi\/4.7.3' > > > > on ALL files of the sdcard and found "thousands" of hardcoded links > > to the old gcc inside binaries... > > > > The new gcc installed but not doing env-update implies that any > > further compilation will link to the old gcc. > > > > Doing env-update implies a system which will not survive the next > > reboot. > > > > What now? > > If i understand your situation correctly, do: > > gcc-config "to set the new version" > env-update > logout > login > emerge --deep --update world > emerge --depclean > revdep-rebuild > > This will take a long time but will get your system working again. If you > don't wan't to do that you can of course tweak the libraries with binary > tools. That is easy if you know what you are doing. > > To prevent this in the future always before world update, update gcc and > glibc first if tere is a new version available. Gcc-config is crusial after > you have installed a bew version of gcc. > > -- > -Matti Hi Matti, not exactly... The sequence you show looks like this in my case: gcc-config "to set the new version" env-update reboot logina attempt: impossible...system does not respond anymore The reason is, that env-update updates to the new compiler, while some [CENSORED] system tools/application are hardcoded to use the old compiler libraries... If I do a env-update --no-ldconfig then I am able to reboot successfully...but compilation will be done against the old compiler a fear... I am installing the backup the fourth time today and I am curious, when the first bad sectors of my sdcard will hit me... Best regards, Meino
Re: [gentoo-user] ssh -X problem [no help sofar on ssh group]
On 20 December 2014 18:17:57 CET, Harry Putnam wrote:
>This properly belongs on the ssh group, but posting there has not
>gotten
>any responses... and the list is quite slow to boot.
>
>I like using ssh -X to other lan remotes but with new versions of
>openssh
>or perhaps the configs, it only works 1 way.
>
>I can `ssh -X' to the gentoo host from a debian host but not the other
>way round.
>
>Two different versions of openssh appear to be involved. But not sure
>how different they are.
>
>RHOST=a debian HOST
>LHOST= Gentoo HOST
>
>ssh -vN $RHOST 2>&1|grep "remote software version"
>
> [...] OpenSSH_6.7p1 Debian-3
>
>ssh -vN $LHOST 2>&1|grep "remote software version"
>
> [...] OpenSSH_6.7p1-hpn14v5
>
>
>One thing I tried to do was to copy the RHOST sshd_config and
>ssh_config to
>LHOST. Restart and try again... there were a few incompatible bits in
>the files so after commenting a few out until no config errors.
>
>However ssh -X still displayed the error and would NOT work when:
> ssh -X RHOST from LHOST
>({Note that plain ssh LHOST or RHOST works in any direction}
>
>Error outut with ssh -X $RHOST "xterm"
>
>,
>| Warning: untrusted X11 forwarding setup failed: xauth key data not
>generated
>| Warning: No xauth data; using fake authentication data for X11
>forwarding.
>| Invalid MIT-MAGIC-COOKIE-1 keyxterm: Xt error: Can't open display:
>localhost:10.0
>`
>
>[Full Error output with ssh -vv -X is very lengthy so is attached at
>the end]
>
>I'm not seeing how to debug this further. So going back to the stock
>version of sshd_config ssh_config on gentoo with two changes:
>
>commented out this line:
> PasswordAuthentication no
>
>added this:
> X11Forwarding yes
>
>--- --- ---=--- --- ---
>Full sshd_config on LHOST: sudo grep ^[^#] /etc/ssh/sshd_config
>--- --- ---=--- --- ---
> UsePAM yes
> X11Forwarding yes
> PrintMotd no
> PrintLastLog no
> UsePrivilegeSeparation sandbox # Default for new installations.
> Subsystemsftp/usr/lib/misc/sftp-server
> AcceptEnv LANG LC_*
>
>--- Config END---
>
>
>--- --- ---=--- --- ---
>Full ssh_config on LHOST: sudo grep ^[^#] /etc/ssh/ssh_config
>--- --- ---=--- --- ---
>
> ForwardX11 yes
> SendEnv LANG LC_*
>
>--- Config END---
>
>###
>
>Now the same info for RHOST
>
>--- --- ---=--- --- ---
>Full sshd_config on RHOST: ssh root@RHOST "grep ^[^#]
>/etc/ssh/sshd_config"
>--- --- ---=--- --- ---
>
>HostKey /etc/ssh/ssh_host_rsa_key
>HostKey /etc/ssh/ssh_host_dsa_key
>HostKey /etc/ssh/ssh_host_ed25519_key
>AcceptEnv LANG LC_*
>ChallengeResponseAuthentication no
>IgnoreRhosts yes
>HostbasedAuthentication no
>KeyRegenerationInterval 3600
>LogLevel INFO
>LoginGraceTime 120
>PermitEmptyPasswords no
>PermitRootLogin yes
>Port 22
>PrintLastLog yes
>PrintMotd no
>Protocol 2
>PubkeyAuthentication yes
>RSAAuthentication yes
>RhostsRSAAuthentication no
>ServerKeyBits 1024
>SyslogFacility AUTH
>StrictModes yes
>Subsystem sftp/usr/lib/misc/sftp-server
>TCPKeepAlive yes
>UsePAM yes
>UsePrivilegeSeparation sandbox
>X11Forwarding yes
>
>--- Config END---
>
>
>--- --- ---=--- --- ---
>Full ssh_config on RHOST: ssh root@RHOST "grep ^[^#]
>/etc/ssh/ssh_config"
>--- --- ---=--- --- ---
>Host *
> ForwardX11 yes
>SendEnv LANG LC_*
>HashKnownHosts yes
>
>--- Config END---
>
>
>
>
>The only thing more I can think to include is the full lengthy output
>of
>ssh -vv -X
Try "ssh -Y ".
It's what I have been using for a long time now.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] New PC, new boot concepts
> > > The advantage of efi over bios is that the boot loader doesn't have to > embed anything in the mbr, the post mbr gap, or the bios boot > partition. > > I just wanted to say that there is another advantage too! MS WIndows7 support booting from GPT partition tables, only if you are using the UEFI. (I dont know about Windows8) I wanted to use GPT on a dual boot system, so I enabled UEFI on my laptop, and I am using GRUB2 as bootloader. Everything is working great.
Re: [gentoo-user] ssh -X problem [no help sofar on ssh group]
On Sat, Dec 20, 2014 at 2:05 PM, J. Roeleveld wrote: > > Try "ssh -Y ". > It's what I have been using for a long time now. Correct - ssh -X hasn't worked on Gentoo for ages. It has been a while since I looked up the details but I seem to recall it being an upstream issue and that it is actually broken on many (but not all) distros. -- Rich
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
> On Dec 20, 2014, at 21:04, meino.cra...@gmx.de wrote: > > Hi Matti, > > not exactly... > The sequence you show looks like this in my case: > gcc-config "to set the new version" > env-update > reboot > logina attempt: impossible...system does not respond anymore > Did I miss something or why do you reboot in that phase? -- -Matti
[gentoo-user]
Could register at systemrescuecd forums for now, so I thought to ask here. Trying to get systemrescuecd iso on USB stick. There is shell script on to accomplish just that. When I try to run it, it identifies my thumb drive, however reports that it is 0 mb. When disk is mounted, the volume in megabytes just right, about 2 GB. Log file says that is not enough memory to install. Any ideas what might be a problem? And yes, I am about to try to install gen too from rescued USB drive in efi mode
Re: [gentoo-user] Getting rid of gcc-4.7.3...how?
On 21/12/14 03:04, meino.cra...@gmx.de wrote: > Matti Nykyri [14-12-20 19:48]: >>> On Dec 20, 2014, at 17:56, meino.cra...@gmx.de wrote: >>> >>> Dale [14-12-20 02:47]: 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 :-) :-) >>> >>> Hi, >>> >>> after a few more non-booting-systems and backup-reinstalls I think >>> I know whats the reason is...but by I dont know how to get out of it: >>> >>> The system becomes inaccessible if I do an env-update and reboot. >>> >>> Reason for that are binaries, in which the path to the old gcc is >>> hardcoded. With the sdcard mounted I checked that with my PC: >>> I did a >>> >>>grep -r '\/usr\/lib\/gcc\/armv7a-hardfloat-linux-gnueabi\/4.7.3' >>> >>> on ALL files of the sdcard and found "thousands" of hardcoded links >>> to the old gcc inside binaries... >>> >>> The new gcc installed but not doing env-update implies that any >>> further compilation will link to the old gcc. >>> >>> Doing env-update implies a system which will not survive the next >>> reboot. >>> >>> What now? >> >> If i understand your situation correctly, do: >> >> gcc-config "to set the new version" >> env-update >> logout >> login >> emerge --deep --update world >> emerge --depclean >> revdep-rebuild >> >> This will take a long time but will get your system working again. If you >> don't wan't to do that you can of course tweak the libraries with binary >> tools. That is easy if you know what you are doing. >> >> To prevent this in the future always before world update, update gcc and >> glibc first if tere is a new version available. Gcc-config is crusial after >> you have installed a bew version of gcc. >> >> -- >> -Matti > > > Hi Matti, > > not exactly... > The sequence you show looks like this in my case: > gcc-config "to set the new version" > env-update > reboot > logina attempt: impossible...system does not respond anymore > > The reason is, that env-update updates to the new compiler, > while some [CENSORED] system tools/application are hardcoded > to use the old compiler libraries... > > If I do a > > env-update --no-ldconfig > > then I am able to reboot successfully...but compilation > will be done against the old compiler a fear... > > I am installing the backup the fourth time today and I am > curious, when the first bad sectors of my sdcard will hit me... > > > > Best regards, > Meino > > > Nowhere do you say you run the fix utility - even if its run automatically you will need to run it EACH TIME you run gcc-config. Sometimes you wont get a hit, but often it will. You will also need to run it at least ONCE against EVERY version of gcc ever installed in that OS (as it only looks for the old version number you give it.) gcc-config sets the symlinks to point to the version of gcc you want to use. The fix utility changes the library internal gcc libraries to point to the proper gcc lib. There have been non-gcc cases where you have to trawl the lib directories replacing the errant entries where neccessary (libpng anyone :) BillK
Re: [gentoo-user]
Am 20.12.2014 um 23:08 schrieb German: > Could register at systemrescuecd forums for now, so I thought to ask here. > Trying to get systemrescuecd iso on USB stick. There is shell script on to > accomplish just that. When I try to run it, it identifies my thumb drive, > however reports that it is 0 mb. When disk is mounted, the volume in > megabytes just right, about 2 GB. Log file says that is not enough memory to > install. Any ideas what might be a problem? And yes, I am about to try to > install gen too from rescued USB drive in efi mode don't use any scripts. Never gave me a bootable solution. Either burn to cd or do it manually.
Re: [gentoo-user] Re: Fresh gen too install - unsuccesful
On Sat, Dec 20, 2014 at 09:40:26PM +0400, German wrote: > Sorry Mick. I am on android tablet and have no clue how to modify message body By using a proper e-mail client¹. *SCNR* Though I’d like to believe that even the standard Android client should be able to not break message threads. PS.: Our distro is called “Gentoo”, not “gen too”. It’s a cute kind of penguin.² ¹ K-9 comes to mind. Even though it displays the reply below when replying, it sends the mail with the reply below the quote if the relevant option is set. ² http://en.wikipedia.org/wiki/Gentoo_penguin -- Gruß | Greetings | Qapla’ Please do not share anything from, with or about me with any social network. The Computer is the logical advancement of humankind: intelligence without morality. signature.asc Description: Digital signature
Re: [gentoo-user]
On Sun, Dec 21, 2014 at 12:34:55AM +0100, Volker Armin Hemmann wrote: > Am 20.12.2014 um 23:08 schrieb German: > > Trying to get systemrescuecd iso on USB stick. There is shell > > script on to accomplish just that. When I try to run it, it identifies > > my thumb drive, however reports that it is 0 mb. > > don't use any scripts. Never gave me a bootable solution. Either burn to > cd or do it manually. For me, the script that comes on sysresccd always worked (though I’ve never used EFI yet). The script determines the size of the device with "blockdev --getsz /path/to/device" What does that return if called manually and what size is reported in other programs (fdisk, dmesg after plugging it in)? -- Gruß | Greetings | Qapla’ Please do not share anything from, with or about me with any social network. The USA took the path from barbarism to decadence without the detour over culture. signature.asc Description: Digital signature
Re: [gentoo-user] Size usb stick with fdisk
On Sun, 21 Dec 2014 03:37:29 +0100 Frank Steinmetzger wrote: > On Sun, Dec 21, 2014 at 12:34:55AM +0100, Volker Armin Hemmann wrote: > > Am 20.12.2014 um 23:08 schrieb German: > > > Trying to get systemrescuecd iso on USB stick. There is shell > > > script on to accomplish just that. When I try to run it, it identifies > > > my thumb drive, however reports that it is 0 mb. > > > > don't use any scripts. Never gave me a bootable solution. Either burn to > > cd or do it manually. > > For me, the script that comes on sysresccd always worked (though I’ve never > used EFI yet). The script determines the size of the device with "blockdev > --getsz /path/to/device" > > What does that return if called manually and what size is reported in other > programs (fdisk, dmesg after plugging it in)? Hi. I would tell you if I knew how to do it in fdisk for instance. Can you provide me with instructions please? > -- > Gruß | Greetings | Qapla’ > Please do not share anything from, with or about me with any social network. > > The USA took the path from barbarism to decadence > without the detour over culture. -- German
Re: [gentoo-user]
On Sun, 21 Dec 2014 03:37:29 +0100 Frank Steinmetzger wrote: > On Sun, Dec 21, 2014 at 12:34:55AM +0100, Volker Armin Hemmann wrote: > > Am 20.12.2014 um 23:08 schrieb German: > > > Trying to get systemrescuecd iso on USB stick. There is shell > > > script on to accomplish just that. When I try to run it, it identifies > > > my thumb drive, however reports that it is 0 mb. > > > > don't use any scripts. Never gave me a bootable solution. Either burn to > > cd or do it manually. > > For me, the script that comes on sysresccd always worked (though I’ve never > used EFI yet). The script determines the size of the device with "blockdev > --getsz /path/to/device" > > What does that return if called manually and what size is reported in other > programs (fdisk, dmesg after plugging it in)? That's what it reports when /dev/sdd is mounted: sudo blockdev --getsize64 /dev/sdd 2031091712 When not mounted it reports that no medium found. The same log from usb_inst.sh: Installation on /dev/sdd at 2014-12-20_16:47 blockdev: cannot open /dev/sdd: No medium found usb_inst.sh: error: The device [/dev/sdd] is only 0 MB. It is too small to copy all the files, an USB-stick of at least 512MB is recommended But shell script should be run unmounted. Confused. > -- > Gruß | Greetings | Qapla’ > Please do not share anything from, with or about me with any social network. > > The USA took the path from barbarism to decadence > without the detour over culture. -- German
Re: [gentoo-user]
On 21 December 2014 06:27:41 CET, German wrote: >On Sun, 21 Dec 2014 03:37:29 +0100 >Frank Steinmetzger wrote: > >> On Sun, Dec 21, 2014 at 12:34:55AM +0100, Volker Armin Hemmann wrote: >> > Am 20.12.2014 um 23:08 schrieb German: >> > > Trying to get systemrescuecd iso on USB stick. There is shell >> > > script on to accomplish just that. When I try to run it, it >identifies >> > > my thumb drive, however reports that it is 0 mb. >> > >> > don't use any scripts. Never gave me a bootable solution. Either >burn to >> > cd or do it manually. >> >> For me, the script that comes on sysresccd always worked (though I’ve >never >> used EFI yet). The script determines the size of the device with >"blockdev >> --getsz /path/to/device" >> >> What does that return if called manually and what size is reported in >other >> programs (fdisk, dmesg after plugging it in)? > >That's what it reports when /dev/sdd is mounted: > >sudo blockdev --getsize64 /dev/sdd >2031091712 > >When not mounted it reports that no medium found. The same log from >usb_inst.sh: > >Installation on /dev/sdd at 2014-12-20_16:47 >blockdev: cannot open /dev/sdd: No medium found >usb_inst.sh: error: The device [/dev/sdd] is only 0 MB. It is too small >to copy all the files, an USB-stick of at least 512MB is recommended > > >But shell script should be run unmounted. Confused. > >> -- >> Gruß | Greetings | Qapla’ >> Please do not share anything from, with or about me with any social >network. >> >> The USA took the path from barbarism to decadence >> without the detour over culture. Do you try 'umounted' right after inserting the USB before any mount commands are run? Some automounters send an 'eject' command which makes some USB sticks disappear until they are unplugged and plugged back in. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user]
On Sun, 21 Dec 2014 07:20:16 + "J. Roeleveld" wrote: > On 21 December 2014 06:27:41 CET, German wrote: > >On Sun, 21 Dec 2014 03:37:29 +0100 > >Frank Steinmetzger wrote: > > > >> On Sun, Dec 21, 2014 at 12:34:55AM +0100, Volker Armin Hemmann wrote: > >> > Am 20.12.2014 um 23:08 schrieb German: > >> > > Trying to get systemrescuecd iso on USB stick. There is shell > >> > > script on to accomplish just that. When I try to run it, it > >identifies > >> > > my thumb drive, however reports that it is 0 mb. > >> > > >> > don't use any scripts. Never gave me a bootable solution. Either > >burn to > >> > cd or do it manually. > >> > >> For me, the script that comes on sysresccd always worked (though I’ve > >never > >> used EFI yet). The script determines the size of the device with > >"blockdev > >> --getsz /path/to/device" > >> > >> What does that return if called manually and what size is reported in > >other > >> programs (fdisk, dmesg after plugging it in)? > > > >That's what it reports when /dev/sdd is mounted: > > > >sudo blockdev --getsize64 /dev/sdd > >2031091712 > > > >When not mounted it reports that no medium found. The same log from > >usb_inst.sh: > > > >Installation on /dev/sdd at 2014-12-20_16:47 > >blockdev: cannot open /dev/sdd: No medium found > >usb_inst.sh: error: The device [/dev/sdd] is only 0 MB. It is too small > >to copy all the files, an USB-stick of at least 512MB is recommended > > > > > >But shell script should be run unmounted. Confused. > > > >> -- > >> Gruß | Greetings | Qapla’ > >> Please do not share anything from, with or about me with any social > >network. > >> > >> The USA took the path from barbarism to decadence > >> without the detour over culture. > > Do you try 'umounted' right after inserting the USB before any mount commands > are run? The thing here is that my usb stick is automaunted by the system. I am running Lubuntu. I unmount it simply by clicking on it in a LXDE. > > Some automounters send an 'eject' command which makes some USB sticks > disappear until they are unplugged and plugged back in. Do you think it would make sense to mount stick manually and then unmount it? Thanks > > -- > Joost > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > -- German
Re: [gentoo-user]
On Sun, 21 Dec 2014 07:20:16 + "J. Roeleveld" wrote: > On 21 December 2014 06:27:41 CET, German wrote: > >On Sun, 21 Dec 2014 03:37:29 +0100 > >Frank Steinmetzger wrote: > > > >> On Sun, Dec 21, 2014 at 12:34:55AM +0100, Volker Armin Hemmann wrote: > >> > Am 20.12.2014 um 23:08 schrieb German: > >> > > Trying to get systemrescuecd iso on USB stick. There is shell > >> > > script on to accomplish just that. When I try to run it, it > >identifies > >> > > my thumb drive, however reports that it is 0 mb. > >> > > >> > don't use any scripts. Never gave me a bootable solution. Either > >burn to > >> > cd or do it manually. > >> > >> For me, the script that comes on sysresccd always worked (though I’ve > >never > >> used EFI yet). The script determines the size of the device with > >"blockdev > >> --getsz /path/to/device" > >> > >> What does that return if called manually and what size is reported in > >other > >> programs (fdisk, dmesg after plugging it in)? > > > >That's what it reports when /dev/sdd is mounted: > > > >sudo blockdev --getsize64 /dev/sdd > >2031091712 > > > >When not mounted it reports that no medium found. The same log from > >usb_inst.sh: > > > >Installation on /dev/sdd at 2014-12-20_16:47 > >blockdev: cannot open /dev/sdd: No medium found > >usb_inst.sh: error: The device [/dev/sdd] is only 0 MB. It is too small > >to copy all the files, an USB-stick of at least 512MB is recommended > > > > > >But shell script should be run unmounted. Confused. > > > >> -- > >> Gruß | Greetings | Qapla’ > >> Please do not share anything from, with or about me with any social > >network. > >> > >> The USA took the path from barbarism to decadence > >> without the detour over culture. > > Do you try 'umounted' right after inserting the USB before any mount commands > are run? > > Some automounters send an 'eject' command which makes some USB sticks > disappear until they are unplugged and plugged back in. Thanks Joost. I wrote to usb stick just fine after I umount /dev/sdd1 manually. Those damn automounters. > > -- > Joost > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > -- German
