-
Search Results
-
Given my rash of problems with bad “burns” or “read” causing errors when booting/installing, I’m asking if an “Integrity Check” or “Check for Defects” option could be added to the boot menu on the flashdrive, cd or dvd, that would run an md5sum of the media and compare it to the expected md5sum value to tell me if it burned correctly and if it is readable correctly by the system its being booted in.
I found in all cases that my downloaded md5sum of the iso itself was correct, but that in some cases not even the system that had created it could read it correctly, and in other cases, other machines couldn’t read it correctly. Of course I spent a lot of time installing and then trying to figure out (and asking dumb questions) about weird errors, like IceWM tray missing, or Wpa_Gui won’t run, later, only to find the root cause was a bad burn or read of the image, some caused by insufficient power to the USB and others unknown.
I noticed that Ubuntu and its children have a “Check for Defects” option, and Linux Mint has an “Integrity Check” option, which I assume is similar. I tried to investigate how to add the option, but have been unsuccessful so far, and to be honest, couldn’t figure out what determines how the AntiX boot menu comes up or what is in it, but I think it would save lots of headaches if it were available and used. I’m hoping it would be easy to add and compact enough to not worry about its size, but I guess someone that knows how it works would need to answer that.
Thanks
BobC- This topic was modified 5 years, 1 month ago by BobC.
Topic: multiboot usb grub iso loop
i wanted to make a multiboot usb on linux, without any additional programs, just grub and gparted (for formatting)
this is the only thing i still keep a windows hdd around, now im free 🙂grub, the bootloader on many linux distros has the ability to mount iso files and boot them
so we need an empty flash drive with a single partition, for convenience use gparted to delete the partitions and make a single ext2 partitions
now we’ll use the terminaluse “lsblk” to identify the flash drive
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 149.1G 0 disk ├─sda1 8:1 0 29.3G 0 part / └─sda3 8:3 0 119.8G 0 part /media/sda3 sdb 8:16 1 14.8G 0 disk └─sdb1 8:17 1 14.8G 0 part /media/sdb1-usb-Multiple_Card_Remy usb device is sdb – 14.8gb
take note ‘sdb’ is the device, ‘sdb1’ is the partitions (very important)my partition is already mounted,
but we’ll mount it on another mountpoint: /media/usb
create the mountpoint “sudo mkdir usb”
mount it “sudo mount /dev/sdb1 /media/usb”
now we install the bootloader “sudo grub-install –force –removable –boot-directory=/media/usb/boot /dev/sdb”note we are using /dev/sdb – wich is the device
make sure you replace sdb with your own device, it can be sdc,sde, whatever
next we must put the grub.cfg file in ‘/media/usb/boot/grub’
grub.cfg is attachednow just copy your iso files to the root of your flash drive
these are the latest versions downloaded tonight, if you get the iso files right now, they will work without modifications
as time goes on, new versions will come out, some filenames will change, and grub.cfg must be modified accordinglymost of the boot entries i got from the isos themselves, you can open them in mc and look for grub.cfg or something similar, and just added $isofile
the manjaro boot entry i got from their forumhope this will be of use to someone, i wanted this for so long
- This topic was modified 5 years, 1 month ago by zpimp.
Topic: Hello from Ottawa …
…Canada, not Kansas 🙂
Been using Linux since Kernal 1.5 and been through Redhat(pre-Canonical), Mandrake, Suse,Ubuntu Xbian, Mint and MX (best general-pupose desktop ever)before deciding to try Antix to breathe some life into my old laptop.
They each had pros and cons and it has been fun watching Linux become a dull-fledged desktop system.
The target machine is a 10 year old beast with the screen dangling from broken hinges that I still use with a similarly outdated external monitor
My main machine is an HP Elitebook on which I will continue to.enjoy MX Linux.
Thanks for se great diatro! I think the Systemd Borging of Linux is sad, and I plan to stay clear of it as long as possible – so thanks for not falling down that well.
Sadly my efforts to get Antix 17 up on the old beast have not been successful, so far. The bios won’t support USB boot and a burned ISO won’t boot on either of my machines
I tested both of them with Xubutu live with no issue, but the DVD drive hates Antix.
Will post diagnostics later.
It does boot from USB on my contempprary laptop and is brilliant for older hardware – so I am not giving up yet.
Thanks to the team and community
Randy
Topic: Live antiX-core
I used Live-usb Maker and created a live-usb of antiX-17.1_386-core.iso (32-bit). I booted into it with static persistence.
I have watched dolphin_oracle’s “Setup up your Desktop Environment!” video.
On this video, d_o runs as root this command:
apt-get install xserver-xorg x11-xserver-utils xfonts-base x11-utils lightdm lightdm-gtk-greeter xfce4 xfce4-goodiesThen he reboots into the Desktop Environment.
I don’t want to install xfce4, but icewm. I don’t know which packages are needed. After updating, I tried this:
apt-get install xserver-xorg x11-xserver-utils xfonts-base x11-utils slim xauth scrot icewm desktop-defaults-icewm-antixSlim gave this error:
Setting up slim (1.3.6.9+nmu1) ... [....] Reloading system message bus config... Failed to open connection to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory invoke-rc.d: initscript dbus, action "reload" failedNo GUI after reboot. I tried:
$ icewm icewm: Can't open display: <none>. X must be running and $DISPLAY set. $ startx -bash: startx: command not foundI decided to try with xfce4, as d_o did. I installed lightdm (lightdm-gtk-greeter was also installed automatically) xfce4, xfce4-goodies. Lightdm gave the same error as slim:
Failed to open connection to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory invoke-rc.d: initscript dbus, action "reload" failedThe newest version of dbus appears to be already installed. But there was not a dbus folder in /var/run. I created myself a /var/run/dbus/ folder and a /var/run/dbus/system_bus_socket file, but I suppose it doesn’t help.
