antiX-19-a2_x64.iso xdelta patch

Forum Forums News Announcements antiX-19-a2_x64.iso xdelta patch

  • This topic has 53 replies, 14 voices, and was last updated Jun 13-2:15 am by eugen-b.
Viewing 15 posts - 31 through 45 (of 54 total)
  • Author
    Posts
  • #22221
    Forum Admin
    BitJam
      Helpful
      Up
      0
      ::

      it says cannot create the directory even though it is ran as sudo.
      Any ideas on the read-only?

      Thank you for testing!

      The file system in a linuxfs (squashfs) file is read-only. Not even root can write to it. I’m not sure why we are getting that error since /tmp exists in the linuxfs file on antiX-19.a2. I can look into it.

      The 2nd error is fatal. I imagine you are trying to chroot into a 64-bit system from a 32-bit system.

      While the Linuxfs file is still mounted try running:

      sudo chroot-rescue --verbose /mnt/iso/sq1

      There should be a line in the output that looks like:
      env HOME=/root XAUTHORITY=/run/chroot-rescue-Xauthority linux64 chroot /mnt/iso/sq1 /bin/bash --rcfile /run/chroot-rescue-bashrc

      If it says “linux32″ instead” of “linux64” then that is mistake I can fix. If it says “linux64” then my code is “right” but you can’t chroot into a 64-bit system. I have some tricks to get around that. I will see if I can apply them to chroot-rescue.

      Thanks for testing. We are busy with the feedback from antiX-19.a2 so IMO we don’t need the 32-bit iso files for testing now. I’m sorry if that locks you out of our testing. OTOH, you could try running an antiX-19.a2 live-usb on your 64-bit stretch system.

      Context is worth 80 IQ points -- Alan Kay

      #22234
      Member
      PPC
        Helpful
        Up
        0
        ::

        Yesterday, for the first time antiX 19 A2 refused to connect to my wifi network. Connman detected the networks, I entered the wifi password, it said it was connected but I had no network. After my second reboot, network started working fine again…
        Suggestion to the devs: to make life easier for new users trying to connect to their network, antiX may come with a quick start icon for connman near the clock (take at look at my screen grab https://www.antixforum.com/wp-content/uploads/2019/05/screenshotA2.jpg). This allows “fast” convient access to network setting without having connman always in ram (ok slower than having connman gui running, but not by much, and it consumes no RAM).

        P.

        #22236
        Forum Admin
        anticapitalista
          Helpful
          Up
          0
          ::

          Yesterday, for the first time antiX 19 A2 refused to connect to my wifi network. Connman detected the networks, I entered the wifi password, it said it was connected but I had no network. After my second reboot, network started working fine again…
          Suggestion to the devs: to make life easier for new users trying to connect to their network, antiX may come with a quick start icon for connman near the clock (take at look at my screen grab https://www.antixforum.com/wp-content/uploads/2019/05/screenshotA2.jpg). This allows “fast” convient access to network setting without having connman always in ram (ok slower than having connman gui running, but not by much, and it consumes no RAM).

          P.

          In my tests, enabling connman-gtk to task bar adds c40MB to RAM according to ps_mem.py

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

          antiX with runit - leaner and meaner.

          #22237
          Moderator
          BobC
            Helpful
            Up
            0
            ::

            If connman-gtk goes in the toolbar on the left it uses no memory unless/until you call it up. It is working well that way on mine. I went to the library to test it.

            PPC, check for microcode errors on the boot. There could be firmware updates that might help you. I don’t know what kind of machine it is.

            Thanks for your efforts anticapitalista, it’s going to be a great release, imo.

            #22247
            Member
            PPC
              Helpful
              Up
              0
              ::

              Yesterday, for the first time antiX 19 A2 refused to connect to my wifi network. Connman detected the networks, I entered the wifi password, it said it was connected but I had no network. After my second reboot, network started working fine again…
              Suggestion to the devs: to make life easier for new users trying to connect to their network, antiX may come with a quick start icon for connman near the clock (take at look at my screen grab https://www.antixforum.com/wp-content/uploads/2019/05/screenshotA2.jpg). This allows “fast” convient access to network setting without having connman always in ram (ok slower than having connman gui running, but not by much, and it consumes no RAM).

              P.

              In my tests, enabling connman-gtk to task bar adds c40MB to RAM according to ps_mem.py

              Sorry anticapitalista, I belive my idea didn’t come across like I wanted.
              BobC came close to understand what I mean- I just have a normal “quick launch” icon near the clock, connman is NOT running in the tray, the icon is just placed near the clock, but it’s just a normal icon like those that are near the start menu. I find that just placing the icon there tricks me (and I hope, most users), because i’m used to see the network indication running there since my windows days. If I click that icon, then it launches connman, if I send connman to the tray, then I’ll have the real connman “tray icon” running there, along side my “connman quickstarter icon”. I also like placing the usb eject button and the exit button near the clock, but they are also just normal icons… I did the same with the volume control once. I didn’t have volumeicon running (saving some megs of precious RAM), just a icon that looked like it. Clicking it launched the volume control application of my choice.
              I believe using a connman icon like this could be a efficient use of ram- users would have no need to have connman-gtk running in the tray all the time, saving system resources…
              In the screen grab I shared, all icons you see (except for volumeicon) are just normal quick launch icons, as you can see in the RAM readout in Conky, that’s a efficient use of RAM, and the bar has most of what a user needs in everyday life, without needing to use the menu (I even have a search icon than runs dmenu to search and execute installed apps- which would be, in my opinion a great addiction to antiX).

              P.

              #22255
              Moderator
              BobC
                Helpful
                Up
                0
                ::

                PPC, icewm comes with a network monitor which would appear over near the clock and if it is turned on you can see how many bytes are going up or down, and if you hover over it, you see more info, but not the ip address, and my suggestion was to make it run connman-gtk if you clicked on it. I will see if i can post a pic of it set up that way. The settings for all that were included in my post a day or two ago.

                If I could suggest, the absolute nicest thing to do would be to check to see if there was an ip address in the startup and if not, then run connman-gtk from the startup so that new users wouldn’t need to figure out what to do, because it would just pop up on yhe screen for them to connect.

                The pic of what it looks like and the settings to do it are here. That doesn’t include the last idea where it pops up on its own. You might need to scroll down to post 22127.

                https://www.antixforum.com/forums/topic/antix-19-a2_x64-iso-xdelta-patch/page/2/#post-22127

                • This reply was modified 3 years, 11 months ago by BobC. Reason: Addig the link to the settings needed
                • This reply was modified 3 years, 11 months ago by BobC. Reason: The network status monitor hint does not include the ip address as i had thought
                #22282
                Forum Admin
                BitJam
                  Helpful
                  Up
                  0
                  ::

                  chroot: failed to run command ‘/bin/bash’: Exec format error

                  It’s not possible to chroot from a 32-bit system into a 64-bit system. If you were running on a 32-bit system then that would cause an error like this. I’ve made a small change to exclude 64-bit systems from the list if you are running on 32-bit.

                  People on 64-bit can test this feature by running:
                  sudo linux32 chroot-rescue-scan

                  You *may* be able to disable it on a 32-bit system with:
                  sudo linux64 chroot-rescue-scan
                  but that won’t let you chroot into a 64-bit system.

                  Context is worth 80 IQ points -- Alan Kay

                  #22284
                  Moderator
                  BobC
                    Helpful
                    Up
                    0
                    ::

                    I think this would be a good way to make it easy for people to connect. I will try a sleep 10 and then call it from my $HOME/.icewm/startup. If not already connected, it runs connman-gtk.

                    #!/bin/sh
                    
                    # check_connection.sh
                    
                    connected_addr=$(ip addr | grep "inet " | sed '/ scope host /d') 
                    if [ -z "$connected_addr" ]; then
                    	echo "No IP addr, run connman"
                    	connman-gtk
                    else 
                    	echo "IP addr: $connected_addr"
                    fi
                    
                    • This reply was modified 3 years, 11 months ago by BobC.
                    #22288
                    Moderator
                    christophe
                      Helpful
                      Up
                      0
                      ::

                      Oooooo. After apt full-upgrade tonight, the fluxbox icons are looking great!

                      confirmed antiX frugaler, since 2019

                      #22289
                      Anonymous
                        Helpful
                        Up
                        0
                        ::

                        thx bitjam,

                        It was a 32-bit boot…I checked my 32-bit iso and isomount, isoumount, and chroot-rescue
                        worked flawlessly. 🙂 pretty cool stuff to play with.
                        Now for 19-a2 this is a clean install on my little e-machine.
                        I was pleased with the new changes in the installer, asking for the
                        grub, name, and passwords while it was copying instead of waiting till the
                        end. My ethernet was automatically working OOB and after a apt-get update/ apt-get upgrade
                        and switching to the patched kernel it seems to run great despite being a really
                        low-end 64-bit cpu and only 1GB ram.
                        very nice.

                        #22292
                        Moderator
                        christophe
                          Helpful
                          Up
                          0
                          ::

                          Uhh, guys. I’ve lost icewm after tonight’s upgrade:

                          Attachments:

                          confirmed antiX frugaler, since 2019

                          #22294
                          Anonymous
                            Helpful
                            Up
                            0
                            ::

                            I just checked and it isn’t on my list either … didn’t notice since
                            I just installed and icewm is default. Does it still show in F1 on
                            slim login?

                            #22295
                            Moderator
                            christophe
                              Helpful
                              Up
                              0
                              ::

                              Yes. slim login to icewm does work 🙂

                              • This reply was modified 3 years, 11 months ago by christophe.

                              confirmed antiX frugaler, since 2019

                              #22297
                              Anonymous
                                Helpful
                                Up
                                0
                                ::

                                somehow the updates wiped it from the
                                /usr/share/desktop-session/wm-menus files . hopefully
                                they will find & fix this.

                                #22298
                                Moderator
                                christophe
                                  Helpful
                                  Up
                                  0
                                  ::

                                  I don’t recall if someone else mentioned, but icewm preferences (on start menu) will not move taskbar to/from top. I adds/removes tick, but upon restart of wm, it goes back to previous on/off state without moving taskbar.

                                  I figured out the above “issue:” I needed to click “save modifications,” THEN restart session. (duh.)

                                  I really like that preferences addition to the icewm menu, by the way.

                                  • This reply was modified 3 years, 11 months ago by christophe.
                                  • This reply was modified 3 years, 11 months ago by christophe.
                                  • This reply was modified 3 years, 11 months ago by christophe.

                                  confirmed antiX frugaler, since 2019

                                Viewing 15 posts - 31 through 45 (of 54 total)
                                • You must be logged in to reply to this topic.