Search Results for 'boot from iso'

Forum Forums Search Search Results for 'boot from iso'

Viewing 13 results - 1,561 through 1,573 (of 1,573 total)
  • Author
    Search Results
  • #1696
    Member
    Richard

      Write up for Permission question?

      A hearty thank you to BitJam, Skidoo and jdmeaux,
      for your forebearance. Your suggestions led me
      to resolve my problem and learn a bit more about
      antiX, fstab and permissions.

      antiX 17 is very nicely thought out, loaded with
      utilities, SpaceFM and I’ve always liked how fast
      IceWM boots; espeacially on the 32bit netboook.
      I add Double Commander because I’m lazy and love
      the convenience.

      Below is the write-up of information that you all deserved
      in the beginning. Not being able to do everything I needed
      on antiX in my limited access to wifi, led me to abuse your
      good nature and attempt to ask a question via Android without
      access to my antiX install, inxi, /etc/fstab, etal nor internet.

      1) Equipment: Acer Aspire One netbook

      $ inxi -Fxz
      System:    Host: Cucuta Kernel: 4.10.5-antix.1-486-smp i686 bits: 32 gcc: 6.3.0
                 Desktop: IceWM 1.4.2 Distro: antiX-17_386-full Heather Heyer 24 October 2017
      Machine:   Device: other-vm? System: Acer product: AOA150 v: 1 serial: N/A
                 Mobo: Acer model: N/A serial: N/A BIOS: Acer v: v0.3301 date: 05/09/2008
      Battery    BAT1: charge: 25.2 Wh 100.0% condition: 25.2/45.5 Wh (55%)
                 model: SIMPLO UM08B74 status: Full
      CPU:       Single core Intel Atom N270 (-HT-) arch: Bonnell rev.2 cache: 512 KB
                 flags: (pae sse sse2 sse3 ssse3) bmips: 3192
                 clock speeds: max: 1600 MHz 1: 1066 MHz 2: 1600 MHz
      Graphics:  Card: Intel Mobile 945GSE Express Integrated Graphics Controller bus-ID: 00:02.0
                 Display Server: X.Org 1.19.2 drivers: intel (unloaded: modesetting,fbdev,vesa)
                 Resolution: 1024x600@60.00hz
                 OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 version: 2.1 Mesa 13.0.6 Direct Render: Yes
      Audio:     Card Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
                 Sound: Advanced Linux Sound Architecture v: k4.10.5-antix.1-486-smp
      Network:   Card-1: Realtek RTL8101/2/6E PCIE Fast/Gigabit Ethernet controller
                 driver: r8169 v: 2.3LK-NAPI port: 3000 bus-ID: 02:00.0
                 IF: eth0 state: down mac: <filter>
                 Card-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express)
                 driver: ath5k bus-ID: 03:00.0
                 IF: wlan0 state: down mac: <filter>
      Drives:    HDD Total Size: 160.0GB (3.1% used)
                 ID-1: /dev/sda model: Hitachi_HTS54321 size: 160.0GB
                 ID-2: /dev/mmcblk0 model: N/A size: 15.8GB
      Partition: ID-1: / size: 8.6G used: 2.8G (34%) fs: ext4 dev: /dev/sda6
                 ID-2: swap-1 size: 2.20GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
      Sensors:   System Temperatures: cpu: 58.0C mobo: N/A
                 Fan Speeds (in rpm): cpu: N/A
      Info:      Processes: 137 Uptime: 17 min Memory: 99.1/990.5MB
                 Init: SysVinit runlevel: 5 Gcc sys: 6.3.0
                 Client: Shell (bash 4.4.121) inxi: 2.3.40

      2) Installed antiX-17_386-full.iso, again, to a clean partition,
      to eliminate the changes that I had made earlier.

      I wanted to convert a couple of scripts for rsync to be able
      to use antiX in the same manner that I use MX16 on my netbook.
      Because of my lack of internet at home, I carry the netbook
      to a friends house for limited use of wifi, then rsync certain
      folders to a pendrive, then rsync the pendrive to my desktop.

      3) In order to run the scripts on my /media/DATA partition,
      I modified fstab, similar to what I use in MX. I made good
      use of BitJam’s comments about permissions. The modifications
      are as follows:

      # /etc/fstab, antiX-17: static file system information
      # Created by make-fstab on Mon Oct 30 15:53:42 -04 2017
      
      # <file system>                            <mount point>   <type>   <options>                   						<dump/pass>
      #-> /dev/sda6                     label=AX17p6
      UUID=34a06da8-ef8e-4985-9362-b9a955727fdc  /               ext4     defaults                        							1 1
      #-> /dev/sda5  		          label=SWAP
      UUID=b695ee48-617c-457c-a448-e5ee69de3e82   swap           swap     defaults                        							0 0
      
      #-> /dev/sda1  		          label=WINX
      UUID=12C2EBC7C2EBAD63      /media/WINX     ntfs-3g  noauto,noexec,uid=1000,gid=users,dmask=002,fmask=113,users  0 0
      #-> /dev/sda2  		          label=MX160p2
      UUID=f9a4d786-1eb1-4f98-91a9-5d62c3458f90  /media/MX160p2  ext4     exec,users			    0 0
      #-> /dev/sda3  		          label=DATA
      #UUID=12FD732748AE8979     /media/DATA     ntfs-3g  noauto,noexec,uid=1000,gid=users,dmask=002,fmask=113,users 0 0
      UUID=12FD732748AE8979      /media/DATA     ntfs-3g  exec,uid=1000,gid=users,dmask=002,fmask=113,users  			0 0
      #-> /dev/sda7  		          label=AX17p7
      UUID=a6087ad6-4c0b-48e0-929f-f980b9d82971  /media/AX17p7  ext4     noauto,exec,users               							0 0

      4) Set up to run the following test shell script to rsync data from netbook to pendrive:

      #!/bin/bash
      ## Usync.sh:  uses rsync copy certain data folders to pendrive. 
      #
      ## -a, --archive = archive mode; equals -rlptgoD (no -H,-A,-X)
      #   	-r, --recursive = recurse into directories
      #			-l, --links     = copy symlinks as symlinks
      #			-p, --perms     = preserve permissions
      #			-t, --times     = preserve modification times
      #			-g, --group     = preserve group
      #			-o, --owner     = preserve owner (super-user only)
      #			-D		= same as --devices --specials
      ## -v, --verbose = increase verbosity
      ## -u, --update	 = update files
      #
      echo ""
      echo "rsyncing to USB..."
      rsync -avu --progress /home/richard/0-New-stuff/	/media/BLAKDAT/0-New-stuff
      rsync -avu --progress /home/richard/0-ToDo/			/media/BLAKDAT/0-ToDo
      # rsync -avu --progress /DATA/archives/				/media/BLAKDAT/archives
      rsync -avu --progress /home/richard/Documents/		/media/BLAKDAT/Documents
      rsync -avu --progress /home/richard/Downloads/		/media/BLAKDAT/Downloads
      # the rest removed for testing
      #
      echo ""
      echo "rsync completed."

      5) And it executes as expected.

      6) Summary:

      I use a separate /DATA partition that is mounted in MX with full permissions.
      At install, antiX put them all in /media/DATA with “noauto,noexec..” which
      was what I had overlooked, in the contents of /etc/fstab above, the drastic changes
      I had made to my MX fstab.

      Changing these allows the rsync scripts to run via urxvt directly.
      No root access needed.

      I understand that these are non-standard changes
      and do not reccomended them for production systems.
      Nor for anyone else.
      I’m sure there exists a better way to accomplish this,
      as regards permissions.

      Thanks, again, for your comments and suggestions.
      Richard.

      Note: direct [code][/code] don’t seem to work in new antiX forum. rh

      • This reply was modified 5 years, 6 months ago by Richard.

      ASUSTeK 900 EeePC; RAM: 1.96 GiB;
      antiX19.3; 4.9.235-antix.1-486-smp;
      HDD: Super Talent STT 30.08 GiB
      +SD & External HDD.

      #1579
      Forum Admin
      rokytnji

        Credit goes to Jens

        My old computer for testing has 96MB Ram. If I run X I can just run one program at a time.

        The antiX-15-V_386-core-libre.iso needs less Ram to install antiX then antiX-16. I booted the CD without splash, w/o quiet and with textmode (vga=ask). I installed the base and updated the software and always updated the config files to the new maintainer version. The kernel 4.0.5-gnu-antix.1-486-smp didn’t have the right firmware file(s) available for internet connection (core-libre CD?) , so I used a USB stick for copying the 4.4.10 kernel and firmware packages.
        The sound chip needs a non-free file and I used the tutorial from https://wiki.debian.org/snd-cs46xx .

        Sometimes I drive a crooked road to get my mind straight.
        Not all who Wander are Lost.
        I'm not outa place. I'm from outer space.

        Linux Registered User # 475019
        How to Search for AntiX solutions to your problems

        #1352

        In reply to: GRUB

        Forum Admin
        BitJam

          @boombaby, the bootloader screen you are describing sounds like it may be our live UEFI bootloader or maybe our installed bootloader. I’ve attached a screenshot of what the live UEFI bootloader looks like. We use Grub for the live UEFI bootloader and the installed bootloader. It doesn’t have the function key menu at the bottom.

          Also, your problems with getting the system started seem to be mainly a problem with the graphics driver. We do copy over whatever you did on the live system to the installed system since doing anything else tends to cause extra problems when booting the installed system that didn’t happen on the live system. If you got to X on the live system then by copying that over, you should be able to also get to X on the installed system. Anyway, when you get that blank screen with the blinking cursor, you should be able to get to a virtual console where you can log in with .

          Also, have you tried making a live-usb? If you can boot the live-dvd to the command line (see above) then the live-usb-maker program can clone the live system you are running to a usb stick without needing the iso file. It should be very easy.

          Attachments:

          Context is worth 80 IQ points -- Alan Kay

          #1350

          In reply to: GRUB

          Member
          boombaby

            Hello, Anticapitalista…

            Hmmm.

            Using k3b and the same ISO I burnt another Antix17. md5 checked OK first.

            On boot, same thing. “Live” desktop is complete (stars and all) but below “Memory Test” option all the buttons/options and textbox are non-existent.

            So I downloaded another ISO. MD5 checked OK. Burnt another DVD. Booted. SAME OUTCOME. Everything below the Mem Test option aren’t there.

            EDIT Just tried Brasero – with same failure.

            What now?

            Regards,
            boombaby

            • This reply was modified 5 years, 6 months ago by boombaby.
            #1271

            In reply to: GRUB

            Forum Admin
            anticapitalista

              Check the md5sum of the iso. Check the integrity of the disk.(You can do this at the live boot menu – F4 – checkmd5)

              Also post the inxi -Fxz output so we know about your hardware.

              Philosophers have interpreted the world in many ways; the point is to change it.

              antiX with runit - leaner and meaner.

              #1245

              In reply to: GRUB

              Member
              boombaby

                No, Anticapitalista…

                I am now on 64-bit laptop system, so I used the 64-bit ISO.

                As far as UEFI goes I can use the laptop EFI menu to boot to either Mageia or Mint (or other distros) but after that it will “fall through” to the last used Grub Menu. In other words I typically use the Mint Menu (or the Mageia Menu or Antix Menu). In this circumstance Antix won’t start.

                When you say “update-grub” do you mean I type that in Grub’s command line, or in Linux’s CLI ?

                boombaby

                #1233

                In reply to: GRUB

                Member
                boombaby

                  Hello, Each…

                  I was going to start a new post with a problem, BUT, I believe that I may be see the same problem as macondo.

                  Since Antix 16.2 was so good I have been hanging out for the new Antix-17. Maybe I was greedy (and wanted everything) because I downloaded the “FULL” version. [Antix is so good that I wanted to “pig-out” on it – a lot.]

                  My HP Pavillion laptop is 64 bit, and has a number of partitions – Windows; Swap; and several Linux distros. [Windows is not used.]

                  When I ran the new DVD (burnt with iso) it got to the install menu but it would not go through to a running system. Not quite correct. The only part I could use was to go into the live menu “Advanced” section and then choose “Failsafe”. Then I got to the “live” desktop and used the “Install” to complete the installation.

                  Using this method I installed Antix 17 into the old 16.2 partition (formatting it as I went).

                  On this first try I installed with Grub in an EFI boot-up.

                  Boot was NO GO. (That is to say, no boot into Antix17. Seemed to complete the install properly but the boot stops after selecting Antix from menu.)

                  Note that the old multi-boot distro menu (both Mageia and Mint) does not have Antix17 but still shows the old Antix16.2 version – which (of course) won’t boot.

                  So I tried installing again in 3 different ways (no Grub + EFI; Grub + EFI; Grub on root) but Antix won’t boot. Menu option still shows 16.2

                  [For background, before my laptop and using 32bit PC, I used Grub pretty well. UEFI and Grub 2 is a little different – and I haven’t spent any time to understand it yet.]

                  Any advice to complete/fix/redo install?

                  Regards,
                  boombaby

                  Forum Admin
                  BitJam

                    I think your original instincts to stay with full were correct. If you can boot from a dvd or a usb stick then the extra space taken up by full does you very little harm. OTOH, if you want to tailor a system to have only the stuff you want on it then it’s better and easier to start out too small and add things as you miss them or need them.

                    I view full, base, and core as starting points for people to create their own custom systems. While not perfect, our live tools are very good. Once you’ve customized the system to your liking, you are just a live-remaster or an iso-snapshot away from making it your own. You’ll have your customized system on live media. You can use it to install on other machines, use it as a snapshot/backup of your system, use it as a rescue boot device, or use it to take your system with you in your pocket.

                    Context is worth 80 IQ points -- Alan Kay

                    #1119

                    In reply to: antiX-17 released

                    Member
                    ohh

                      On my ancient IMAC 5.1 after converting the full iso so that it would boot the cd on the imac5.1 to run live, would only start in safe mode, then installed ran update-grub on my antix16 install and now boots perfectly. Great job guys so far no blips. If anyone is interested in the conversion of the iso let me know and I will post a link to the info.

                      cheers,
                      ohh

                      ohh@antix17:~
                      $ inxi -F
                      System:    Host: antix17 Kernel: 4.10.5-antix.3-amd64-smp x86_64 bits: 64
                                 Desktop: IceWM 1.4.2 Distro: antiX-17_x64-full Heather Heyer 24 October 2017
                      Machine:   Device: desktop System: Apple product: iMac5 1 v: 1.0 serial: N/A
                                 Mobo: Apple model: Mac-F4228EC8 v: DVT serial: N/A
                                 BIOS: Apple v: IM51.88Z.0090.B09.0706270921 date: 06/27/07
                      CPU:       Dual core Intel Core2 T7400 (-MCP-) cache: 4096 KB
                                 clock speeds: max: 2167 MHz 1: 1000 MHz 2: 2000 MHz
                      Graphics:  Card: Advanced Micro Devices [AMD/ATI] RV530/M56-P [Mobility Radeon X1600]
                                 Display Server: X.Org 1.19.2 driver: vesa Resolution: 1400x1050@60.00hz
                                 OpenGL: renderer: Gallium 0.4 on llvmpipe (LLVM 3.9, 128 bits)
                                 version: 3.3 Mesa 13.0.6
                      Audio:     Card Intel NM10/ICH7 Family High Def. Audio Controller driver: snd_hda_intel
                                 Sound: Advanced Linux Sound Architecture v: k4.10.5-antix.3-amd64-smp
                      Network:   Card-1: Marvell 88E8053 PCI-E Gigabit Ethernet Controller driver: sky2
                                 IF: eth0 state: up speed: 100 Mbps duplex: full mac: 
                                 Card-2: Broadcom Limited BCM4321 802.11a/b/g/n driver: b43-pci-bridge
                                 IF: wlan0 state: down mac: 
                      Drives:    HDD Total Size: 500.1GB (10.9% used)
                                 ID-1: /dev/sda model: Hitachi_HDS72505 size: 500.1GB
                      Partition: ID-1: / size: 55G used: 3.1G (6%) fs: ext4 dev: /dev/sda4
                                 ID-2: /home size: 44G used: 295M (1%) fs: ext4 dev: /dev/sda6
                                 ID-3: swap-1 size: 20.00GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
                      Sensors:   System Temperatures: cpu: 44.0C mobo: N/A
                                 Fan Speeds (in rpm): cpu: 867
                      Info:      Processes: 160 Uptime: 1 day Memory: 663.3/2995.4MB
                                 Client: Shell (bash) inxi: 2.3.40
                      • This reply was modified 5 years, 6 months ago by anticapitalista. Reason: fixed broken code tags

                      Every matter requires prior knowledge.

                      - Du Mu
                      The Art of War

                      Forum Admin
                      SamK

                        md5sum OK
                        ISO burned to CDROM

                        X server fails to start
                        demo user does not log-in automatically
                        boot stops at cli when log-in should occur showing message “For command line install…”

                        Manual log-in as demo leaves user at /

                        Attached archive contains, cmdline, inxi, Xorg.0.log

                        #931

                        In reply to: System Backup (Solved)

                        Forum Admin
                        BitJam

                          1) Everything for you live system is in the directory /live/boot-dev/antiX/. You can do a perfect backup (as root) with:

                          cp -a /live/boot-dev/antiX /live/boot-dev/backup-01

                          Currently, normal users can’t read the /live directory but that may change in the next iteration. You can add entries to your bootloaders to boot from that backup. Here is an example for syslinux.cfg:

                          LABEL backup-01
                              MENU LABEL antiX-17_x64_backup-01
                              KERNEL /antiX/backup-01/vmlinuz
                              APPEND bdir=backup-01 quiet splash=v disable=lx
                              INITRD /antiX/backup-01/initrd.gz

                          The non-obvious part is the “bdir=backup-01” cheat. We call that the “boot directory” and it is at the core of the design of our live system.

                          2) Doing a live-remaster (which requires more cpu than the simple copy because we rebuild the linuxfs file) is another way to back up. When you do repeated remasters we offer to archive the older linuxfs files for you. The “rolllback” cheat will get back to the previous system after a remaster but we don’t have an automatic way of going back more than one. If you choose to archive your linuxfs files, it is pretty easy to retrieve them via the command line. Often, the combination of root persistence and live-remaster (with the “rollback” cheat) will suffice.

                          3) You can use the snapshot program to create an iso file backup but it is just as expensive cpu-wise as a remaster.

                          4) The live-usb-maker program will “clone” your live system to a new live-usb. The clone won’t include your rootfs or homefs files but it will include your bootloader customizations. This is much faster than snapshot or remaster because it doesn’t rebuild the linuxfs (squashfs) file.

                          I hope you get a chance to explore several of these options.

                          PS: code tags didn’t work.

                          • This reply was modified 5 years, 6 months ago by BitJam.
                          • This reply was modified 5 years, 6 months ago by rokytnji.
                          • This reply was modified 5 years, 6 months ago by rokytnji.

                          Context is worth 80 IQ points -- Alan Kay

                          #897
                          Forum Admin
                          anticapitalista

                            I would advise against a shared /home with Ubuntu since there *might* be some config files (dotfiles) that conflict. Of course, there might not be.
                            Instead I would install antiX with its own home on the root partition and use sym links to the Ubuntu /home. You will need to make changes to antiX (and Ubuntu if you want to access antiX home) /etc/fstab.

                            When you boot the live iso, at the boot menu press F4 and highlight wicd. This will put an icon in the tray and it will carry over on install.
                            If you do not see the F menus at boot menu, you will have to add wicd manually.

                            Philosophers have interpreted the world in many ways; the point is to change it.

                            antiX with runit - leaner and meaner.

                            #893
                            Anonymous

                              Thanks for antiX-17_64-full. iso

                              Installation without GRUB in a multi-boot system
                              The focus was for me:
                              will all changes made to the live system be included in the installation?

                              Answer: perfect! 😉
                              slim. conf –> Desktop fluxbox; user male
                              fluxbox –> toolbar.height; toolbar.widthPercent; style-antiX
                              conky

                            Viewing 13 results - 1,561 through 1,573 (of 1,573 total)