topic title: antiX-14R-alpha1-full-386 available
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#1
First alpha release of antiX-14 is available for testing. 32 bit, full only.

This is based on Debian Testing and comes with a 3.14.1 custom kernel which, I hope, will work even on old boxes. Latest LibreOffice 4.2 included! Bleed!
Various splash themes are included, let us know what you think.

Download here:


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://sourceforge.net/projects/antix-linux/files/Testing/antiX-14R/"
linktext was:"https://sourceforge.net/projects/antix- ... antiX-14R/"
====================================


Post comments here.

Enjoy!
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#2
The F7 menu in the bootloader lets you adjust the console resolution on system that don't use KMS (kernel mode switching) graphics drivers. The first 3 entries in that menu (after"plain") enable the splash theme. The others do not:

Code: Select all

    S:800×600
    S:1024×768
    S:1280×1024
    800×600
    1024×640
    1024×768
    1152×720
    1280x800
    1280×1024
    1600×1200
    1600×1200*
If you want splash supported on a different resolution than what is provided, please get in touch with me.

In each virtual console you can select the theme with the"splash-select" program. Use Ctrl-Alt-F1 through Ctrl-Alt-F6 to get to the virtual consoles. Use Ctrl-Alt-F7 to get back to X-Windows.

You can disable KMS with the"F5 Video Mode" -->"safe" option. The"vesa" option will also disable KMS.


edit: attached a screenshot of the splash-select program.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#3
There is a bad bug triggered if you make a selection in the F7 menu that does not start with"S:". The screen will fill with error messages and it will not boot. A fix is on the way.
Posts: 1,445
skidoo
Joined: 09 Feb 2012
#4
re: The init routine which creates persistence container, if missing and needed

-- did not recognize kb input from"numeric row of keys". Only keypad keys (w numlock on) are accepted

-- loooong operation begs a clearer"patience, please, this will take several minutes" disclaimer before the blinking cursor
or consider using one of these utilities to output a dynamic progress indicator

"pv"

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://packages.debian.org/jessie/pv"
linktext was:"https://packages.debian.org/jessie/pv"
====================================


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.ivarch.com/programs/pv.shtml"
linktext was:"http://www.ivarch.com/programs/pv.shtml"
====================================


"pipemeter"

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://packages.debian.org/jessie/pipemeter"
linktext was:"https://packages.debian.org/jessie/pipemeter"
====================================


"bar"

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://packages.debian.org/jessie/bar"
linktext was:"https://packages.debian.org/jessie/bar"
====================================


-- choosing custom settings resulted in a"panic" (incessant scrolling lines of red errortext, requiring reboot)
Posts: 1,445
skidoo
Joined: 09 Feb 2012
#5
re: antiX control centre --}"Set Screen Resolution"
resulting dialog window is titled"screen layout editor" (setting resolution is non-obvious, until user digs into the toolbar commands)
and, although probably"correct" behavior when only one monitor is attached... seems inexplicably unresponsive (does nothing)
edit: this gui is a front-end to xrandr?
(I also tested xrandr, arandr, and grandr... and none of those worked to change settings. shrug)
edit2:
monitor is connected via HDMI cable.
Without acpi=off in the boot option (as it was when I reported earlier) I'm now able to use the antixCC"Set Screen Resolution" utility

re: antiX control centre --} Live --}"set up live persistence" --} action: Resize Root Peristence
no progressbar during loooong resize operation.
Upon completion, success msg reports"rootfs.tmp was created" (i don't recall ever seeing that previously) then, click OK and...
...some dialog flashes (immediately closes) and parent dialog is again displayed, with"action:resize root persistence" pre-selected
(what? i just now did that already, right?)
"correct" behavior, but confusing gui

re: gui shutdown dialog (choose"Shutdown")
bug?
No"eject" prompt (non-essential, just a familiar landmark from prior antix versions) nor"system is going down" terminal msg, just a colored dollarsign prompt
ahhhh, maybe not a bug, just different / awkward. Prompt is runlevel 5; must login as root, THEN choose to halt the system.
Last edited by skidoo on 27 Apr 2014, 21:51, edited 3 times in total.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#6
skidoo wrote:re: The init routine which creates persistence container, if missing and needed
-- did not recognize kb input from"numeric row of keys". Only keypad keys (w numlock on) are accepted
Can you give me information about your system that might affect this? Perhaps"lspci -k"?
-- loooong operation begs a clearer"patience, please, this will take several minutes" disclaimer before the blinking cursor
This is because it is *not* a long operation here. Thanks for the feedback I'll try to make this better for you (and many others I'm sure).
or consider using one of these utilities to output a dynamic progress indicator
Yes, we are aware of those and already use them where we can.
-- choosing custom settings resulted in a"panic" (incessant scrolling lines of red errortext, requiring reboot)
Is this the same bug I reported above with settings in the"F7 Console" menu? If not, can you be more specific about the custom settings you are referring to? We know there is a problem with the vga boot parameter.

Thanks for your rapid and incisive feedback!
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#7
skidoo wrote:No"eject" prompt (non-essential, just a familiar landmark from prior antix versions) nor"system is going down" terminal msg, just a colored dollarsign prompt
ahhhh, maybe not a bug, just different / awkward. Prompt is runlevel 5; must login as root, THEN choose to halt the system.
No, this is a bug on our end. I think"sudo chvt 1" is missing in our logout script. Sent you a PM.
skidoo
Posts: 1,445
skidoo
Joined: 09 Feb 2012
#8
red errortext: might have been during the boot in which I added vga=795 to the bootline (didn't use F7 option menu though)

Unless I can pin down the specifics (it's not repeatable when I retested) or someone else encounters the same hiccup,
just disregard"the 'create custom persistence container' did not recognize kb input" error I reported.

resize root persistence (gui)
I read that, for you, container creation is not slooooow. Maybe you are testing in VM?
Here, writing to a class10 USB pendrive, it's slow enough that during testing today I intentionally choose a tiny container size to minimize the delay.
That's what quickly led me to visit the resize gui ~~ save attempt, at shutdown, had reported"not enough space remaining in container".
Anyhow, after resizing then successfully saving then rebooting, changes are preserved but...
...I'm left with a lingering 102Mb"rootfs.bak" file (written during the failed"not enough space remaining" attempt?)
Guessing I can / should manually delete this file. Also wondering whether it should have been cleaned automatically.
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#9
the rootfs.bak file allows for roll backs in the event of something terrible. The liveUSB utility has a function for removing old files, and yes, you can also remove manually.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#10
skidoo wrote:red errortext: might have been during the boot in which I added vga=795 to the bootline (didn't use F7 option menu though)
Sounds like the known bug.
Anyhow, after resizing then successfully saving then rebooting, changes are preserved but...
...I'm left with a lingering 102Mb"rootfs.bak" file (written during the failed"not enough space remaining" attempt?)
Guessing I can / should manually delete this file. Also wondering whether it should have been cleaned automatically.
The progress bars that you requested should be in the GUI app. If not, I can send you a version with the bars.

Oddly enough, I believe those files can be cleaned up in the remaster-live application which I admit is not the right place. There is a navigate option in persist-makefs which makes it rather easy to clean up those files. I agree that we need to handle this better but it might not happen in this iteration.

Part of our design philosophy has been to not automatically delete users' data so there is always a backup to go back to. The idea was to then let the user choose to delete the files in a GUI app. I think the remaster-live app does this quite well (that might be what D.O was remembering). We need to do it in persist-makefs also but have not done so yet.

Yes, I do most of my testing in a VM, and to make matters worse, it is now running on an ssd.

Again, I want to thank you for your testing and feedback. It is most valuable.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#11
@skidoo At the top of any page on this forum it should say you have one new message. Please read it. Thanks.
Posts: 1,445
skidoo
Joined: 09 Feb 2012
#12
problem in antixCC dialog titled"persistence auto-save config":
Text displayed within the dialog states"The default is semi-auto" (I agree this is the preferred default)
BUT the selectbox is pre-populated with"automatic".
If user doesn't carefully read, and just clicks the OK button... the mode gets changed, to automatic. Oops.

question:
In the newly-added"create missing container at boot", why is ext3 the default?
My understanding was that ext2 (no journaling) is preferable, to avoid pendrive write cycle wear.

expanding on the earlier point
"loooong operation begs a clearer"patience, please, this will take several minutes" disclaimer before the blinking cursor":
As is, the onscreen message reads create blah blahblah mumbletygook
(reads like a declarative, as though the user is expected to do something)
Maybe just changing text to creating blah blahblah ellipsis... would suffice.
FWIW, I timed it: creating the container using the default values @68seconds (pendrive is supposedly class10, but izzit really?)

obeservation:
antiX still messes up my hardware clock (whereas most other distros do not)

observation / request:
lean and mean... and a side order of fries and throw in a transmission-deamon and smartmontools...
Are the L/X/M cheatcodes even working?!? edit: yes the cheat codes are working
-=-
consider: apt-get install --no-install-recommends bum (bootup manager gui util)(532kb)
vs
antixCC --} configure startup services --} ...cryptic, non-comprehensive list, truncated names
edit:
After posting, I did consider... and learned that the"status" for each startup item
as displayed by both
sysv-rc-conf (launched via antiC ControlCentre --} System --}"Choose Startup Services")
and bum (bootup manager)
is misleading. Those apps are blind to the"antiX magic" performed during boot by
/etc/init.d/antix-disable-services

Can we get a hardcore barebones cheatcode added, or... maybe refer to it as a"build yer own blacklist" cheatcode?
Aha, the mechanism for setting what (what else) means"lean", in my book, is already in place. Just edit/customize /etc/init.d/antix-disable-services
the rootfs.bak file allows for roll backs in the event of something terrible.
I'll need to test it further. Although do vaguely recall reading"in the case of suchandsuch, check for presence of rootfs.bak", I've never needed a rollback. If"last known good" is saved to that filename (rootfs.bak) seems like overwriting it or using same filename from a failed attempt... seems like that file (in my case 102Mb) would be unusable ~~ it would certainly be problematic to have only some unknown part(s) of the intended savefile layered into a later session. Okay, beating a dead horse here; I hear ya, user has a gui option to find/remove the .bak file.

suggestion:
consider: apt-get install --no-install-recommends lxtask (613kb)

suggestion:
apt-get install --no-install-recommends anacron (tiny)(for a live system, this util adds important functionality)

suggestion:
ship a /root/.synaptic/synaptic.conf which has been edited to include the line
ShowAllPkgInfoInMain="true";

suggestion:
(even if not shipping a mlocate.db file in the iso)
ship a /etc/updatedb.conf file in which /lib/live is declared in the PRUNEPATHS= line

edited to add:
observation:
Per my testing, package"systemd" (4.8Mb) can be purged, without consequence
Last edited by skidoo on 23 Apr 2014, 03:03, edited 1 time in total.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#13
skidoo wrote:In the newly-added"create missing container at boot", why is ext3 the default?
My understanding was that ext2 (no journaling) is preferable, to avoid pendrive write cycle wear.
I'm swamped now so I will just deal with this.

For home persistence and dynamic root persistence there is not the constant writing. You would only get that with static root persistence which is going to be painfully slow on your system anyway.

Our LiveUSB has a feature that most others don't have. We check the filesystems at boot time and will perform fsck when needed. We default to doing it every 30 mounts. IIRC, this works much better with ext3 because the check is faster and the journal makes it possible to actually repair the file system.

I'm more concerned about speed than wear when we persist-save. You can use tune2fs to enable and disable journaling on an ext3 file system. You can do a head to head comparison by going to the /live/boot-dev/antiX directory and making a copy of the rootfs file. Run persist-save with the journaling enabled. Then disable journaling on the copy and swap the files around and run persist-save again and see if there is a speed difference.

AFAIK, those dire warnings about journaling wearing out flash drives were mostly speculation with little to zero hard evidence. People were just twiddling all the knobs they could. Just like the myth that notime is a lot faster than the relatime default. They are both WAY faster than atime but the relative difference is very small and relatime provides a nice benefit. That's what I use even on my ssd. Although I would use notime on the rootfs file [add to todo list] since it is getting written to by rsync.

The reason I choose ext3 as the default:
Quis custodiet ipsos custodes?
I think it makes the LiveUSB much more reliable. ISTM anything that can be unplugged so easily while it is still mounted should be given as much protection as possible. I'm happy to learn more. I'm not certain ext3 is the best default but these are my reasons for choosing it.

BTW: the two commands we use to create the homefs and rootfs files are:

Code: Select all

dd if=/dev/zero of=$full_file bs=1M count=0 seek=$fs_size
mkfs.$fs_type -q -F $full_file
Where $full_file is the name of the file, $fs_size is the size in meg, and $fs_type is ext2, ext3, or ext4.

Why is that so slow? Without the seek, the dd command would be slow because it would have to fill the file with zeros. But with the seek, it should be pretty fast. Maybe you could play with these commands and see where the bottleneck is. If you want. Maybe the speed depends on the underlying file system the file is created on. If I'm always using ext3 and you're always using ext2 maybe that would account for the vast speed difference we see.
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#14
I have not read the thread because it is bed time for me. Just a quick feedback. Running Live USB using Unetbootin on IBM M57 Dual core wireless Desktop.

Code: Select all

demo@antix1:~
$ inxi -Fxz
System:    Host: antix1 Kernel: 3.14.1-antix.1-486-smp i686 (32 bit gcc: 4.8.2) 
           Desktop: IceWM 1.3.7 
           Distro: antiX-14R-alpha1_386-full Killah P 21 April 2014 
Machine:   System: LENOVO product: 6075BHU v: ThinkCentre M57
           Mobo: LENOVO model: LENOVO
           Bios: LENOVO v: 2RKT41AUS date: 03/20/2008
CPU:       Dual core Intel Pentium Dual CPU E2160 (-MCP-) cache: 1024 KB
           flags: (lm nx pae sse sse2 sse3 ssse3) bmips: 7181 
           Clock Speeds: 1: 1800 MHz 2: 1800 MHz
Graphics:  Card: Intel 82Q35 Express Integrated Graphics Controller
           bus-ID: 00:02.0
           Display Server: X.Org 1.15.0.901 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1600x900@60.0hz
           GLX Renderer: Mesa DRI Intel Q35 x86/MMX/SSE2
           GLX Version: 2.1 Mesa 10.1.0 Direct Rendering: Yes
Audio:     Card Intel 82801I (ICH9 Family) HD Audio Controller 
           driver: snd_hda_intel bus-ID: 00:1b.0 
           Sound: ALSA v: k3.14.1-antix.1-486-smp
Network:   Card-1: Ralink RT2561/RT61 802.11g PCI
           driver: rt61pci v: 2.3.0 bus-ID: 11:0c.0
           IF: wlan0 state: up mac: <filter>
           Card-2: Intel 82566DM-2 Gigabit Network Connection
           driver: e1000e v: 2.3.2-k port: 1820 bus-ID: 00:19.0
           IF: eth0 state: down mac: <filter>
Drives:    HDD Total Size: 402.2GB (0.2% used)
           ID-1: /dev/sda model: WDC_WD3200AAKS size: 320.1GB
           ID-2: /dev/sdb model: ST380815AS size: 80.0GB
           USB ID-3: /dev/sdd model: U3_Cruzer_Micro size: 2.1GB
Partition: ID-1: swap-1 size: 1.07GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 106 Uptime: 4 min Memory: 228.0/3028.0MB 
           Init: SysVinit runlevel: 5 Gcc sys: 4.8.2 
           Client: Shell (bash 4.3.81) inxi: 2.1.18
Connected wifi via WICD. Nice touch on including wlan0 in wireless preferences in Wicd. Worked for me. Hope it works out for others.

I am booted on this Desktop to check the USB Install. It would not boot on my Acer I chatted about in chat.
Stuck on"verify DMA success" first line that comes up on boot for that. I used the F12 key to pick boot and know what I am doing (kinda sorta)
so it must be a hardware thingy since The acer is AMD singl;e core P4 and this IBM is Intel dual core.

I guess I'll not blame unetbootin either since it booted up fine on the IBM Also.
One pendrive boot down. I'll try on Netbooks and laptops later, really, laterz.

__{{emoticon}}__

Edit: I love the new look. Speaks to the outlaw Biker in me. Just thought I could not leave that out also.
Nice job, Bros.

Edit: Exact error message on Acer Aspire AST150 USB Boot= Veryfying DMI Pool Data .....................Update Success

Then just sits there with a blinking cursor. Requires a Cntrl+Alt+Del to to reboot. NO hard shutdown required.
Posts: 325
male
Joined: 04 Nov 2011
#15
Here is my report.
After downloading and check the md5sum, was the
ISO brought to the stick.

Code: Select all

dd if=antiX-14R-alpha1_386-full.iso of=/dev/sdc bs=1M
Since my bios can not automatically boot from USB, I must with
F8 to help out.
First I tried with S 1280x1024, but then left it at the default setting.
So, F2> language; F6> Fluxbox and press Enter.

Since everything went smoothly, I decided to install in a multi-boot system to run.
I did not know that they use this time Grub2. this
complained not at all> (sda7 - root) because of the block lists.

Pain-free! All correctly.
- Time
- fstab
- grub.cfg

Code: Select all

$ inxi -f
CPU:       Single core Intel Pentium 4 CPU (-HT-) cache: 512 KB 
           Clock Speeds: 1: 2798 MHz 2: 2798 MHz
           CPU Flags: acpi apic bts cid clflush cmov cx8 de dts fpu fxsr ht mca mce mmx msr mtrr pae pat pbe
           pebs pge pse pse36 sep ss sse sse2 tm tsc vme xtpr

Code: Select all

$ inxi -F
System:    Host: antix14 Kernel: 3.14.1-antix.1-486-smp i686 (32 bit) Desktop: Fluxbox 1.3.5 
           Distro: antiX-14R-alpha1_386-full Killah P 21 April 2014 
Machine:   Mobo: ASUSTeK model: P4P800SE v: Rev 2.xx Bios: American Megatrends v: 080009 date: 01/27/2004
CPU:       Single core Intel Pentium 4 CPU (-HT-) cache: 512 KB 
           Clock Speeds: 1: 2798 MHz 2: 2798 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] RV280 [Radeon 9200]
           Display Server: X.Org 1.15.0.901 drivers: ati,radeon (unloaded: fbdev,vesa)
           Resolution: 1280x1024@60.0hz
           GLX Renderer: Mesa DRI R200 (RV280 5961) x86/MMX/SSE2 TCL DRI2 GLX Version: 1.3 Mesa 10.1.0
Audio:     Card Intel 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller driver: snd_intel8x0 
           Sound: Advanced Linux Sound Architecture v: k3.14.1-antix.1-486-smp
Network:   Card: Marvell 88E8001 Gigabit Ethernet Controller driver: skge
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <Filter>
Drives:    HDD Total Size: 281.8GB (7.2% used) ID-1: /dev/sda model: Maxtor_6L250R0 size: 251.0GB
           ID-2: /dev/sdb model: Maxtor_6E030L0 size: 30.8GB
Partition: ID-1: / size: 20G used: 2.7G (15%) fs: ext4 dev: /dev/sda7 
           ID-2: swap-1 size: 2.19GB used: 0.00GB (0%) fs: swap dev: /dev/sdb6 
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 93 Uptime: 47 min Memory: 333.5/2021.5MB Client: Shell (bash) inxi: 2.1.18

Code: Select all

# blkid -c /dev/null -o list
device                 fs_type    label       mount point                UUID
-------------------------------------------------------------------------------------------------------------
/dev/sda1              ext4       arch        (not mounted)              a9ef9356-c881-4f21-82c2-d6b35ad809b3
/dev/sda2              ext4                   (not mounted)              289721dd-e2ef-4bba-bcc8-74284c740b00
/dev/sda5              ext4                   (not mounted)              06d9e1bf-b5c1-4ae8-b13b-e5eff1b2cc07
/dev/sda6              vfat       DATEN       /media/DATEN               1B84-0566
/dev/sda7              ext4                   /                          c0009a5c-b969-47fa-8df1-b2a42cd6ad1d
/dev/sda8              ext4                   (not mounted)              e7bdb018-fc39-4d07-9cab-c612d6b90407
/dev/sda9              ext4                   (not mounted)              409deada-dd82-476d-848b-a6d64727b5b9
/dev/sda10             ext4                   (not mounted)              106b3fa3-d0c5-42b9-9abd-431471079825
/dev/sda11             ext4                   (not mounted)              bcbb8867-3de0-48a5-94a7-909d0f9eab7f
/dev/sdb1              ext4                   (not mounted)              484077cb-d3e8-4773-b5f5-f4298730fbf4
/dev/sdb5              ext4                   (not mounted)              15ffb655-1b0b-4e79-9dc6-c759fb894732
/dev/sdb6              swap                   <swap>                     04f4f80e-26b7-4da2-b930-38b5b671a019

Code: Select all

# Pluggable devices are handled by uDev, they are not in fstab
UUID=c0009a5c-b969-47fa-8df1-b2a42cd6ad1d / auto defaults,noatime 1 1
proc /proc proc defaults 0 0
devpts /dev/pts devpts mode=0622 0 0
# Added by make-fstab /dev/sda1
UUID=a9ef9356-c881-4f21-82c2-d6b35ad809b3  /media/arch                                 ext4       noauto,exec,users               0 0
# Added by make-fstab /dev/sda2
UUID=289721dd-e2ef-4bba-bcc8-74284c740b00  /media/sda2                                 ext4       noauto,exec,users               0 0
# Added by make-fstab /dev/sda5
UUID=06d9e1bf-b5c1-4ae8-b13b-e5eff1b2cc07  /media/sda5                                 ext4       noauto,exec,users               0 0
# Added by make-fstab /dev/sda6
UUID=1B84-0566                             /media/DATEN                                vfat       auto,uid=1000,gid=users,dmask=002,fmask=113,users  0 0
# Added by make-fstab /dev/sda8
UUID=e7bdb018-fc39-4d07-9cab-c612d6b90407  /media/sda8                                 ext4       noauto,exec,users               0 0
# Added by make-fstab /dev/sda9
UUID=409deada-dd82-476d-848b-a6d64727b5b9  /media/sda9                                 ext4       noauto,exec,users               0 0
# Added by make-fstab /dev/sda10
UUID=106b3fa3-d0c5-42b9-9abd-431471079825  /media/sda10                                ext4       noauto,exec,users               0 0
# Added by make-fstab /dev/sda11
UUID=bcbb8867-3de0-48a5-94a7-909d0f9eab7f  /media/sda11                                ext4       noauto,exec,users               0 0
# Added by make-fstab /dev/sdb1
UUID=484077cb-d3e8-4773-b5f5-f4298730fbf4  /media/sdb1                                 ext4       noauto,exec,users               0 0
# Added by make-fstab /dev/sdb5
UUID=15ffb655-1b0b-4e79-9dc6-c759fb894732  /media/sdb5                                 ext4       noauto,exec,users               0 0
# Added by make-fstab /dev/sdb6
UUID=04f4f80e-26b7-4da2-b930-38b5b671a019  swap                                        swap       defaults                        0 0
# Added by make-fstab /dev/cdrom
/dev/cdrom                                 /media/cdrom                                iso9660    noauto,exec,users,ro            0 0
# Added by make-fstab /dev/fd0
/dev/fd0                                   /media/fd0                                  auto       noauto,exec,users,rw            0 0
# Added by make-fstab /dev/sr0
/dev/sr0                                   /media/sr0                                  auto       noauto,exec,users,ro            0 0
# Added by make-fstab /dev/sr1
/dev/sr1                                   /media/sr1                                  auto       noauto,exec,users,ro            0 0
Because it is a testing version (Rolling Release),
removed the hook at
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://antix.daveserver.info/stable/"
linktext was:"http://antix.daveserver.info/stable/"
====================================


With spacefm * I can not do anything. Everything removed and this
thunar* installed.

I'm sorry, so far I could find no errors. __{{emoticon}}__ The system I have already adjusted my taste.
As always good work! Thank you!

Edit: In fstab I have only the DATA partition of" noauto"
changed to" auto". __{{emoticon}}__