You are not logged in.
- Topics: Active | Unanswered
#1576 Re: Installation » Xfe + isomount question » 2019-12-04 18:42:32
Hello:
... don't understand why you need to mount the isos.
To tell the truth, neither do I.
So I tried to recall how that came about and then it came back to me: I was trying out mounting (in general) with Xfe.
I was having the issues I have mentioned with USB drives and was also having problems mounting CD/DVDs.
So I then tried an *.iso I had at hand in /home/snapshot.
That is what happened and ho it came about.
Sorry ...
... planning to do frequent editing of the iso's boot menu?
No, not really.
I can do that before generating it in refractasnapshot.conf, right?
You are (as usual) right and I stand corrected: the title of the post should have been different.
But the issue is common to mounting an *.iso, a USB drive or system drives are similar or the same.
According to the xfe docs ...
Yes, read them.
... mount filesystems with ctrl-M and unmount with ctrl-U.
What I can't figure out is how/where you find these unmounted filesystems.
Right.
That is exactly what I need to find out how to do.
... don't see anything in the preferences about volume management or devices.
Neither do I.
... adds custom mount / unmount commands ...
Yes, it was a feature someone asked for and the author implementes a couple of years later.
And that's what I want to use but I can only select to mount something Xfe can see/show as available.
Maybe it has to look in /etc/fstab?
I have two mount points /media/cdrom and /media/usb but my /etc/fstab only has rootfs / rootfs rw 0 0.
Thanks and sorry for the *.iso confusion.
Best,
A.
#1577 Re: Installation » Xfe + isomount question » 2019-12-04 09:04:39
Hello:
... Xfe is recognizing that the /home/groucho/Desktop/Example1 is a separate mount point.
... why it is giving you options (that don't work ...
Yes, if I mount the *.iso with the script as user and then open another instance of Xfe as root, I am able to unmount the *.iso with the icon from there.
I can also mount the *.iso with the script (mounts in /root/Desktop) but not with the the icon as it is also greyed out when as running as root.
Command line mounting of the iso on /media/cdrom is only possible as root.
groucho@devuan:/home/snapshot$ sudo mount snapshot-20191203_1428.iso /media/cdrom
mount: /dev/loop0 is write-protected, mounting read-only
groucho@devuan:/home/snapshot$groucho@devuan:/home/snapshot$ sudo umount snapshot-20191203_1428.iso /media/cdrom
umount: snapshot-20191203_1428.iso: not mounted
groucho@devuan:/home/snapshot$ Can you write a custom xfe function to fusermount -u the selected directory?
I'm sorry but my scripting abilities are non-existent so I'd need a more detailed explanation.
The isounmount script uses fusermount and is called from Xfe by selecting the *.iso file and right-click -> scripts -> isounmount
#fxe script iso-umount
#!/bin/bash
FILE=$(basename "$1")
MOUNTPOINT="$HOME/Desktop/$FILE"
fusermount -u "$MOUNTPOINT"What I don't understand is why the mount icon does not go 'live' when I select the *.iso file with the pointer.
ie: Xfe is not identifying it as 'mountable' but then it does identify it as 'unmountable' once it is mounted.
Similar thing happens ith a USB stick:
I can mount it as root via command line and then the unmount icon is 'live' but the operation is not permitted.
Xfe is highly configurable, maybe this is all related to Edit -> Preferences -> Programs where Volume management is configured?
Mount: mount
Unmount: umount
Thanks for your input.
Cheers,
A.
#1578 Re: Installation » Xfe + isomount question » 2019-12-04 00:44:13
Hello:
... commands are correct ...
Yes ...
I thought so too, because ...
... one thing I tried actually worked? ;-D
Why do you want to mount the isos?
If you recall, this live Devuan ascii *.iso will live inside my box in a small capacity USB plugged into a motherboard USB port and will be used as a sort of rescue installation.
The drive will also have one or maybe two separate logical partitions inside an extended partition to hold a few *.iso files which I may need.
This is why I consider it important to be able to mount an *.iso image from within the live installation.
eg: imagine a rig with disabled boot drive and a failing CD/DVD unit with the backups/images in another drive in the box or on a portable external drive.
That said, why the difference in behaviour I mentioned earlier?
ie: Why can I mount and unmount an *.iso made with Refractasnapshot using the scripts I set up as the logged in user but cannot unmount it from Xfe?
On a related subject:
My Devuan ascii 2.0.0 installation works with four internal SAS drives, a DVD drive and four additional USB/FireWire ports, all of which I have to be to be available in Xfe to mount as needed via the live.iso.
It would have to be always there, to be awakened if I have a problem.
This means it has to be oblivious as to which drives are living inside the box when booted or to the ID any of the USB/FireWire drives that could be plugged in at any time.
ie:
When I boot the live.iso and start Xfe, I need to see the on-board drives present in the box at that time and any USB/FireWire drive I plug in so I can mount any of them.
Just like with my main Devuan ascii installation, where I can see all my drives in Thunar and mount/unmount them (w/pw) as needed.
How can I get that done?
With autofs?
Thanks in advance,
A.
#1579 Installation » Xfe + isomount question » 2019-12-03 23:44:45
- Altoid
- Replies: 10
Hello:
Continuing with my ongoing tune up of a minimal Devuan ascii live *.iso, I am stuck ith the issue regarding automounting the drives.
While trying to see how to mount an *.iso image, I installed the isomount package as it had a much smaller footprint then other available options.
I found a couple of adequate scripts on the isomount project page which I set up in /home/groucho/.config/xfe/scripts:
#fxe script iso-mount
#!/bin/bash
FILE=$(basename "$1")
MOUNTPOINT="$HOME/Desktop/$FILE"
fuseiso -p "$1" "$MOUNTPOINT"
and
#fxe script iso-umount
#!/bin/bash
FILE=$(basename "$1")
MOUNTPOINT="$HOME/Desktop/$FILE"
fusermount -u "$MOUNTPOINT"Now I can right-click on an *.iso file and do scripts -> mount or scripts -> unmount.
The surprise was that doing a right-click on the image mounted in /Desktop also showed me a greyed out Mount and an Unmount option, the latter bringing up a pop-up that said Permisison denied when clicked on.
So I can mount and unmount an *.iso made with Refractasnapshot using the scripts I set up as the logged in user but cannot unmount it from Xfe.
I cannot mount it either as the Mount and Unmount icons in the bar are greyed out and the Unmount icon appears only if I have previously mounted the *.iso file with the isomount script.
Same thing happens if I change the ownership of the *.iso file to the logged in user.
What am I missing here?
Thanks in advance.
A.
#1580 Re: DIY » ascii VM to ascii live *.iso » 2019-11-30 12:49:06
Hello:
Let me know if you need more information.
Problem solved.
Modified the settings.
Now the Details screen reads:
Display
Video Memory: 70MN
Remote Desktop Server: Disabled
Video Capture: Disabled
Machine -> Settings -> Display
Enable 3D Acceleration -> unticked
Enable 2D Acceleration -> unticked
Saved, remade the snapshot and burned to USB.
The error I reported earlier is not there anymore and both Synaptic and Pluma work as expected.
It seems that there is a bug in Vbox with 3D acceleration and it does not work properly.
https://forums.virtualbox.org/viewtopic.php?f=3&t=85589
Cheers,
A.
#1581 Re: DIY » ascii VM to ascii live *.iso » 2019-11-30 11:32:47
Hello:
... don't understand the error ...
... shouldn't need 3D acceleration ...
Not that I understand much, but the same thought crossed my mind.
I mean, a permissions issue I can see but ...
... never gotten 3D to work in vbox.) How are you starting synaptic?
I can start it through the OB menu or through the terminal.
I can only see the error message via the terminal.
The OP command (from Obmenu) is lxterminal -e sudo synaptic.
Works perfectly well in the VM.
With respect to 3D in the VM ...
The Details screen reads:
Display
Video Memory: 70MN
Acceleration: 3D
Remote Desktop Server: Disabled
Video Capture: Disabled
Machine -> Settings -> Display
Enable 3D Acceleration -> ticked
Enable 2D Acceleration -> unticked
I can untick Enable 3D Acceleration but if I then tick save the setting and tick Enable 2D Acceleration, I get an error message at the bottom that reads Invalid settings.
This is the installed VBox version:
groucho@devuan:/$ vboxmanage --version
5.2.24_Debianr128122
groucho@devuan:/$ groucho@devuan:~$ sudo dmesg | grep -i video
[ 0.758742] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[ 1.505705] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 1.506254] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input3
[ 6.221301] vboxvideo: loading out-of-tree module taints kernel.
[ 6.525508] vboxvideo 0000:00:02.0: fb0: vboxdrmfb frame buffer device
[ 6.540221] [drm] Initialized vboxvideo 1.0.0 20130823 for 0000:00:02.0 on minor 0
groucho@devuan:~$ groucho@devuan:~$ cat /proc/modules | grep -i video
vboxvideo 36864 2 - Live 0xffffffffc069f000 (O)
ttm 98304 1 vboxvideo, Live 0xffffffffc062d000
drm_kms_helper 155648 1 vboxvideo, Live 0xffffffffc0653000
drm 360448 5 vboxvideo,ttm,drm_kms_helper, Live 0xffffffffc05d4000
video 40960 0 - Live 0xffffffffc0220000
groucho@devuan:~$ More data that may be useful:
groucho@devuan:~$ glxinfo -i | grep render
OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW
direct rendering: Yes
OpenGL renderer string: Chromium
groucho@devuan:~$ groucho@devuan:~$ glxinfo -i | grep direct
OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW
direct rendering: Yes
groucho@devuan:~$ groucho@devuan:~$ glxinfo -i | grep openGL
OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW
groucho@devuan:~$ But GLX gears will run (I see it on the screen) albeit with the same OpenGL Warning:
groucho@devuan:~$ glxgears
OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 1669 requests (1669 known processed) with 0 events remaining.
groucho@devuan:~$ groucho@devuan:~$ glxgears -info
OpenGL Warning: vboxCall failed with VBox status code VERR_BUFFER_OVERFLOW
GL_RENDERER = Chromium
GL_VERSION = 2.1 Chromium 1.9
GL_VENDOR = Humper
GL_EXTENSIONS = GL_EXT_texture_compression_s3tc GL_EXT_draw_range_elements GL_EXT_framebuffer_object GL_EXT_compiled_vertex_array GL_ARB_depth_texture GL_ARB_fragment_program GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_shadow GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_EXT_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_EXT_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_IBM_texture_mirrored_repeat GL_ATI_texture_mirror_once GL_ARB_texture_non_power_of_two GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object GL_ARB_pixel_buffer_object GL_ARB_vertex_program GL_ARB_window_pos GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_func_separate GL_EXT_blend_subtract GL_EXT_texture_env_add GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_EXT_texture_object GL_EXT_texture3D GL_IBM_rasterpos_clip GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_texgen_reflection GL_NV_texture_rectangle GL_ARB_texture_rectangle GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_SGIS_generate_mipmap GL_ARB_shading_language_100 GL_ARB_shader_objects GL_ARB_vertex_shader GL_ARB_fragment_shader GL_EXT_texture_sRGB GL_EXT_framebuffer_blit GL_EXT_blend_equation_separate GL_EXT_stencil_two_side GL_ARB_texture_float GL_ARB_draw_buffers GL_ARB_shader_texture_lod GL_CR_state_parameter GL_CR_cursor_position GL_CR_bounding_box GL_CR_print_string GL_CR_tilesort_info GL_CR_synchronization GL_CR_head_spu_name GL_CR_performance_info GL_CR_window_size GL_CR_tile_info GL_CR_saveframe GL_CR_readback_barrier_size GL_CR_server_id_sharing GL_CR_server_matrix GL_EXT_stencil_two_side
VisualID 33, 0x21
302 frames in 5.0 seconds = 60.305 FPS
301 frames in 5.0 seconds = 60.014 FPS
301 frames in 5.0 seconds = 60.179 FPS
301 frames in 5.0 seconds = 60.045 FPS
288 frames in 5.0 seconds = 57.418 FPS
301 frames in 5.0 seconds = 60.013 FPS0
--- snip ---Not much acceleration there, no?
groucho@devuan:~$ xvinfo
X-Video Extension version 2.2
screen #0
no adaptors present
groucho@devuan:~$ Let me know if you need more information.
Best,
A.
#1582 DIY » ascii VM to ascii live *.iso » 2019-11-29 11:00:11
- Altoid
- Replies: 4
Hello:
Just to test making a snapshot, I made one of the modified basic ascii VM downloaded from the repository.
I thinned it down a bit and it is working perfectly:
https://files.devuan.org/devuan_ascii/v … box.vdi.xz
I have tried testing the few applications I have installed on the VM, but when I try to run Synaptic (which will not be in the final version) I get this message:
OpenGL Warning: Failed to connect to host. Make sure 3D acceleration is enabled for this VM.This warning does not appear when running the VM in my Devuan installation.
This is the package list from the refractasnapsot files in the *.iso
(is there a better way to add this data to a post?)
groucho@devuan:~$ cat /home/groucho/virtual-drives/1/pkglist_snapshot-20191129_0109/package_list
Name
acetoneiso
adduser
adwaita-icon-theme
alsa-utils
apt
apt-utils
at-spi2-core
audacious
audacious-plugins:amd64
audacious-plugins-data
avfs
base-files
base-passwd
bash
binutils
bsdmainutils
bsdutils
btrfs-progs
btrfs-tools
build-essential
busybox-static
bzip2
ca-certificates
cdrdao
clearlooks-phenix-darkpurpy-theme
consolekit
coreutils
cpio
cpp
cpp-6
cron
curl
darkpurpy-icon-theme
dash
dbus
dbus-x11
dconf-gsettings-backend:amd64
dconf-service
dctrl-tools
debconf
debian-archive-keyring
debian-goodies
debian-keyring
debianutils
deborphan
desktop-base
desktop-file-utils
devuan-baseconf
devuan-keyring
dh-python
dialog
dictionaries-common
diffutils
dkms
dmidecode
dmsetup
dmz-cursor-theme
docbook-xml
dosfstools
dpkg
dpkg-dev
e2fslibs:amd64
e2fsprogs
eject
elogind
emacsen-common
enchant
eudev
exfat-fuse
exfat-utils
fake-hwclock
fakeroot
fbterm
file
findutils
firmware-linux-free
fontconfig
fontconfig-config
fonts-dejavu-core
fuse
fuseiso
g++
g++-6
gawk
gcc
gcc-6
gcc-6-base:amd64
gcr
gdisk
genisoimage
gettext-base
giblib1:amd64
glib-networking:amd64
glib-networking-common
glib-networking-services
gnome-extra-icons
gnome-icon-theme
gnome-icon-theme-extras
gnome-keyring
gnome-themes-standard:amd64
gnome-themes-standard-data
gnupg
gnupg-agent
gnupg2
gparted
gpgv
grep
grub-common
grub-pc
grub-pc-bin
grub2-common
gsettings-desktop-schemas
gstreamer1.0-plugins-base:amd64
gstreamer1.0-plugins-good:amd64
gstreamer1.0-pulseaudio:amd64
gstreamer1.0-x:amd64
gtk-update-icon-cache
gtk2-engines:amd64
gtk2-engines-pixbuf:amd64
gtkhash
gtkhash-common
gvfs:amd64
gvfs-backends
gvfs-common
gvfs-daemons
gvfs-fuse
gvfs-libs:amd64
gzip
hddtemp
hicolor-icon-theme
hostname
hunspell-en-us
i965-va-driver:amd64
ifupdown
init
init-system-helpers
initramfs-tools
initramfs-tools-core
initscripts
insserv
intel-microcode
inxi
iproute2
iptables
iputils-ping
irqbalance
isc-dhcp-client
isc-dhcp-common
iso-codes
isolinux
iucode-tool
jed
jed-common
keyboard-configuration
klibc-utils
kmod
less
libaa1:amd64
libaacs0:amd64
libacl1:amd64
libalgorithm-diff-perl
libalgorithm-diff-xs-perl
libalgorithm-merge-perl
libao-common
libao4
libapparmor1:amd64
libapt-inst2.0:amd64
libapt-pkg5.0:amd64
libarchive13:amd64
libasan3:amd64
libasound2:amd64
libasound2-data
libaspell15:amd64
libassuan0:amd64
libasyncns0:amd64
libatasmart4:amd64
libatk-bridge2.0-0:amd64
libatk1.0-0:amd64
libatk1.0-data
libatkmm-1.6-1v5:amd64
libatomic1:amd64
libatspi2.0-0:amd64
libattr1:amd64
libaudcore3:amd64
libaudgui3:amd64
libaudio2:amd64
libaudit-common
libaudit1:amd64
libaudqt0:amd64
libaudtag2:amd64
libauthen-sasl-perl
libavahi-client3:amd64
libavahi-common-data:amd64
libavahi-common3:amd64
libavahi-glib1:amd64
libavc1394-0:amd64
libavcodec57:amd64
libavformat57:amd64
libavutil55:amd64
libbdplus0:amd64
libblas-common
libblas3
libblkid1:amd64
libbluray1:amd64
libbs2b0:amd64
libbsd0:amd64
libburn4:amd64
libbz2-1.0:amd64
libc-bin
libc-dev-bin
libc-l10n
libc6:amd64
libc6-dev:amd64
libcaca0:amd64
libcairo-gobject2:amd64
libcairo-perl
libcairo2:amd64
libcairomm-1.0-1v5:amd64
libcap-ng0:amd64
libcap2:amd64
libcap2-bin
libcc1-0:amd64
libcddb2
libcdio-cdda1:amd64
libcdio-paranoia1:amd64
libcdio13:amd64
libcdparanoia0:amd64
libchromaprint1:amd64
libcilkrts5:amd64
libck-connector0:amd64
libcolord2:amd64
libcomerr2:amd64
libcroco3:amd64
libcrystalhd3:amd64
libcue1
libcups2:amd64
libcurl3:amd64
libcurl3-gnutls:amd64
libdatrie1:amd64
libdb5.3:amd64
libdbus-1-3:amd64
libdbus-glib-1-2:amd64
libdconf1:amd64
libdebconfclient0:amd64
libdevmapper1.02.1:amd64
libdns-export162
libdouble-conversion1:amd64
libdpkg-perl
libdrm-amdgpu1:amd64
libdrm-intel1:amd64
libdrm-nouveau2:amd64
libdrm-radeon1:amd64
libdrm2:amd64
libdv4:amd64
libedit2:amd64
libegl1-mesa:amd64
libelf1:amd64
libelogind0:amd64
libenchant1c2a:amd64
libencode-locale-perl
libepoxy0:amd64
libept1.5.0:amd64
libestr0
libeudev1:amd64
libevdev2:amd64
libevent-2.0-5:amd64
libexif12:amd64
libexpat1:amd64
libfaad2:amd64
libfakeroot:amd64
libfastjson4:amd64
libfdisk1:amd64
libffi6:amd64
libfftw3-single3:amd64
libfile-basedir-perl
libfile-desktopentry-perl
libfile-fcntllock-perl
libfile-listing-perl
libfile-mimeinfo-perl
libflac8:amd64
libfluidsynth1:amd64
libfm-data
libfm-extra4:amd64
libfm-gtk-data
libfm-gtk4:amd64
libfm-modules:amd64
libfm4:amd64
libfont-afm-perl
libfontconfig1:amd64
libfontenc1:amd64
libfox-1.6-0:amd64
libfreetype6:amd64
libfuse2:amd64
libgail-common:amd64
libgail18:amd64
libgbm1:amd64
libgcc-6-dev:amd64
libgcc1:amd64
libgck-1-0:amd64
libgcr-3-common
libgcr-base-3-1:amd64
libgcr-ui-3-1:amd64
libgcrypt20:amd64
libgd3:amd64
libgdata-common
libgdata22:amd64
libgdbm3:amd64
libgdk-pixbuf2.0-0:amd64
libgdk-pixbuf2.0-common
libgfortran3:amd64
libgif7:amd64
libgl1-mesa-dri:amd64
libgl1-mesa-glx:amd64
libglade2-0:amd64
libglapi-mesa:amd64
libglew2.0:amd64
libglib-perl
libglib2.0-0:amd64
libglib2.0-data
libglibmm-2.4-1v5:amd64
libglu1-mesa:amd64
libgme0:amd64
libgmp10:amd64
libgnutls30:amd64
libgoa-1.0-0b:amd64
libgoa-1.0-common
libgomp1:amd64
libgpg-error0:amd64
libgphoto2-6:amd64
libgphoto2-l10n
libgphoto2-port12:amd64
libgpm2:amd64
libgraphite2-3:amd64
libgsm1:amd64
libgssapi-krb5-2:amd64
libgstreamer-plugins-bad1.0-0:amd64
libgstreamer-plugins-base1.0-0:amd64
libgstreamer1.0-0:amd64
libgtk-3-0:amd64
libgtk-3-bin
libgtk-3-common
libgtk2-perl
libgtk2.0-0:amd64
libgtk2.0-bin
libgtk2.0-common
libgtkmm-2.4-1v5:amd64
libgtksourceview-3.0-1:amd64
libgtksourceview-3.0-common
libgudev-1.0-0:amd64
libguess1:amd64
libharfbuzz-icu0:amd64
libharfbuzz0b:amd64
libhogweed4:amd64
libhtml-form-perl
libhtml-format-perl
libhtml-parser-perl
libhtml-tagset-perl
libhtml-tree-perl
libhttp-cookies-perl
libhttp-daemon-perl
libhttp-date-perl
libhttp-message-perl
libhttp-negotiate-perl
libhunspell-1.4-0:amd64
libhyphen0:amd64
libice6:amd64
libicu57:amd64
libid3tag0:amd64
libidn11:amd64
libidn2-0:amd64
libiec61883-0:amd64
libimlib2:amd64
libimobiledevice6:amd64
libinput-bin
libinput10:amd64
libio-html-perl
libio-socket-ssl-perl
libip4tc0:amd64
libip6tc0:amd64
libipc-system-simple-perl
libiptc0:amd64
libisc-export160
libisl15:amd64
libisoburn1:amd64
libisofs6:amd64
libitm1:amd64
libiw30:amd64
libjack-jackd2-0:amd64
libjavascriptcoregtk-4.0-18:amd64
libjbig0:amd64
libjpeg62-turbo:amd64
libjson-glib-1.0-0:amd64
libjson-glib-1.0-common
libjte1
libk5crypto3:amd64
libkeyutils1:amd64
libkf5windowsystem-data
libkf5windowsystem5:amd64
libklibc
libkmod2:amd64
libkrb5-3:amd64
libkrb5support0:amd64
libksba8:amd64
liblapack3
liblcms2-2:amd64
libldap-2.4-2:amd64
libldap-common
libldb1:amd64
liblirc-client0:amd64
libllvm3.9:amd64
liblocale-gettext-perl
liblogging-stdlog0:amd64
liblognorm5:amd64
liblsan0:amd64
libltdl7:amd64
liblua5.2-0:amd64
liblwp-mediatypes-perl
liblwp-protocol-https-perl
liblxqt-l10n
liblxqt0:amd64
liblz4-1:amd64
liblzma5:amd64
liblzo2-2:amd64
libmagic-mgc
libmagic1:amd64
libmailtools-perl
libmenu-cache-bin
libmenu-cache3:amd64
libmhash2:amd64
libmms0:amd64
libmng1:amd64
libmnl0:amd64
libmodplug1:amd64
libmount1:amd64
libmp3lame0:amd64
libmpc3:amd64
libmpdec2:amd64
libmpfr4:amd64
libmpg123-0:amd64
libmpx2:amd64
libmtdev1:amd64
libmtp-common
libmtp-runtime
libmtp9:amd64
libnautilus-extension1a:amd64
libncurses5:amd64
libncursesw5:amd64
libneon27-gnutls:amd64
libnet-dbus-perl
libnet-http-perl
libnet-smtp-ssl-perl
libnet-ssleay-perl
libnetfilter-conntrack3:amd64
libnettle6:amd64
libnewt0.52:amd64
libnfnetlink0:amd64
libnfs8:amd64
libnghttp2-14:amd64
libnl-3-200:amd64
libnl-genl-3-200:amd64
libnotify4:amd64
libnpth0:amd64
libnspr4:amd64
libnss3:amd64
libntfs-3g871
libnuma1:amd64
liboauth0:amd64
libobrender32v5
libobt2v5
libogg0:amd64
libonig4:amd64
libopenjp2-7:amd64
libopenmpt0:amd64
libopts25:amd64
libopus0:amd64
liborc-0.4-0:amd64
libp11-kit0:amd64
libpam-cap:amd64
libpam-elogind:amd64
libpam-gnome-keyring:amd64
libpam-modules:amd64
libpam-modules-bin
libpam-runtime
libpam0g:amd64
libpango-1.0-0:amd64
libpango-perl
libpangocairo-1.0-0:amd64
libpangoft2-1.0-0:amd64
libpangomm-1.4-1v5:amd64
libpangoxft-1.0-0:amd64
libparted-fs-resize0:amd64
libparted2:amd64
libpci3:amd64
libpciaccess0:amd64
libpcre16-3:amd64
libpcre2-8-0:amd64
libpcre3:amd64
libpcsclite1:amd64
libperl4-corelibs-perl
libperl5.24:amd64
libpipeline1:amd64
libpixman-1-0:amd64
libplist3:amd64
libpng16-16:amd64
libpolkit-agent-1-0:amd64
libpolkit-backend-1-0
libpolkit-backend-consolekit-1-0:amd64
libpolkit-gobject-1-0
libpolkit-gobject-consolekit-1-0:amd64
libpolkit-qt5-1-1:amd64
libpopt0:amd64
libprocps4:amd64
libprocps6:amd64
libproxy1v5:amd64
libpsl5:amd64
libpulse0:amd64
libpython-stdlib:amd64
libpython2.7:amd64
libpython2.7-minimal:amd64
libpython2.7-stdlib:amd64
libpython3-stdlib:amd64
libpython3.5-minimal:amd64
libpython3.5-stdlib:amd64
libqt4-dbus:amd64
libqt4-network:amd64
libqt4-opengl:amd64
libqt4-xml:amd64
libqt4-xmlpatterns:amd64
libqt5core5a:amd64
libqt5dbus5:amd64
libqt5gui5:amd64
libqt5multimedia5:amd64
libqt5network5:amd64
libqt5opengl5:amd64
libqt5svg5:amd64
libqt5widgets5:amd64
libqt5x11extras5:amd64
libqt5xdg2:amd64
libqt5xdgiconloader2:amd64
libqt5xml5:amd64
libqtcore4:amd64
libqtdbus4:amd64
libqtgui4:amd64
libqtwebkit4:amd64
libquadmath0:amd64
librarian0
libraw1394-11:amd64
libreadline7:amd64
librest-0.7-0:amd64
librsvg2-2:amd64
librsvg2-common:amd64
librtmp1:amd64
libsamplerate0:amd64
libsasl2-2:amd64
libsasl2-modules:amd64
libsasl2-modules-db:amd64
libsdl2-2.0-0:amd64
libsecret-1-0:amd64
libsecret-common
libselinux1:amd64
libsemanage-common
libsemanage1:amd64
libsensors4:amd64
libsepol1:amd64
libsgutils2-2
libshine3:amd64
libshout3:amd64
libsidplayfp4:amd64
libsigc++-2.0-0v5:amd64
libsigsegv2:amd64
libslang2:amd64
libslang2-modules:amd64
libsm6:amd64
libsmartcols1:amd64
libsmbclient:amd64
libsnappy1v5:amd64
libsndfile1:amd64
libsndio6.1:amd64
libsoup-gnome2.4-1:amd64
libsoup2.4-1:amd64
libsoxr0:amd64
libspeex1:amd64
libsqlite3-0:amd64
libss2:amd64
libssh-gcrypt-4:amd64
libssh2-1:amd64
libssl1.0.2:amd64
libssl1.1:amd64
libstartup-notification0:amd64
libstdc++-6-dev:amd64
libstdc++6:amd64
libswresample2:amd64
libsystemd0:amd64
libtag1v5:amd64
libtag1v5-vanilla:amd64
libtalloc2:amd64
libtasn1-6:amd64
libtdb1:amd64
libtevent0:amd64
libtext-charwidth-perl
libtext-iconv-perl
libtext-wrapi18n-perl
libthai-data
libthai0:amd64
libtheora0:amd64
libtie-ixhash-perl
libtiff5:amd64
libtimedate-perl
libtinfo5:amd64
libtsan0:amd64
libtwolame0:amd64
libtxc-dxtn-s2tc:amd64
libubsan0:amd64
libudisks2-0:amd64
libunistring0:amd64
liburi-perl
libusb-1.0-0:amd64
libusbmuxd4:amd64
libustr-1.0-1:amd64
libutempter0:amd64
libuuid1:amd64
libv4l-0:amd64
libv4lconvert0:amd64
libva-drm1:amd64
libva-x11-1:amd64
libva1:amd64
libvdpau-va-gl1:amd64
libvdpau1:amd64
libvisual-0.4-0:amd64
libvorbis0a:amd64
libvorbisenc2:amd64
libvorbisfile3:amd64
libvpx4:amd64
libvte-2.91-0:amd64
libvte-2.91-common
libvte-common
libvte9
libwacom-bin
libwacom-common
libwacom2:amd64
libwavpack1:amd64
libwayland-client0:amd64
libwayland-cursor0:amd64
libwayland-egl1-mesa:amd64
libwayland-server0:amd64
libwbclient0:amd64
libwebkit2gtk-4.0-37:amd64
libwebp6:amd64
libwebpmux2:amd64
libwrap0:amd64
libwww-perl
libwww-robotrules-perl
libx11-6:amd64
libx11-data
libx11-protocol-perl
libx11-xcb1:amd64
libx264-148:amd64
libx265-95:amd64
libx86-1:amd64
libxapian30:amd64
libxatracker2:amd64
libxau6:amd64
libxaw7:amd64
libxcb-dri2-0:amd64
libxcb-dri3-0:amd64
libxcb-glx0:amd64
libxcb-icccm4:amd64
libxcb-image0:amd64
libxcb-keysyms1:amd64
libxcb-present0:amd64
libxcb-randr0:amd64
libxcb-render-util0:amd64
libxcb-render0:amd64
libxcb-shape0:amd64
libxcb-shm0:amd64
libxcb-sync1:amd64
libxcb-util0:amd64
libxcb-xfixes0:amd64
libxcb-xinerama0:amd64
libxcb-xkb1:amd64
libxcb1:amd64
libxcomposite1:amd64
libxcursor1:amd64
libxdamage1:amd64
libxdmcp6:amd64
libxext6:amd64
libxfixes3:amd64
libxfont1:amd64
libxfont2:amd64
libxft2:amd64
libxi6:amd64
libxinerama1:amd64
libxkbcommon-x11-0:amd64
libxkbcommon0:amd64
libxkbfile1:amd64
libxml-parser-perl
libxml-twig-perl
libxml-xpathengine-perl
libxml2:amd64
libxmu6:amd64
libxmuu1:amd64
libxpm4:amd64
libxrandr2:amd64
libxrender1:amd64
libxshmfence1:amd64
libxslt1.1:amd64
libxss1:amd64
libxt6:amd64
libxtables12:amd64
libxtst6:amd64
libxv1:amd64
libxvidcore4:amd64
libxvmc1:amd64
libxxf86dga1:amd64
libxxf86vm1:amd64
libzvbi-common
libzvbi0:amd64
linux-base
linux-compiler-gcc-6-x86
linux-headers-4.9.0-11-amd64
linux-headers-4.9.0-11-common
linux-headers-amd64
linux-image-4.9.0-11-amd64
linux-image-amd64
linux-kbuild-4.9
linux-libc-dev:amd64
live-boot
live-boot-doc
live-boot-initramfs-tools
live-config
live-config-doc
live-config-sysvinit
live-tools
lm-sensors
login
logrotate
lsb-base
lsb-release
lsof
lsscsi
lxappearance
lxde-settings-daemon
lxinput
lxmenu-data
lxqt-policykit
lxqt-policykit-l10n
lxterminal
lynx
lynx-common
madebits-pca
make
manpages
manpages-dev
mate-desktop-common
mawk
mc
mc-data
mesa-utils
mesa-va-drivers:amd64
mesa-vdpau-drivers:amd64
mime-support
mlocate
mount
mtools
multiarch-support
nautilus-gtkhash
ncurses-base
ncurses-bin
ncurses-term
net-tools
netbase
notification-daemon
ntfs-3g
ntp
obconf
obmenu
openbox
openssh-client
openssh-server
openssh-sftp-server
openssl
os-prober
p11-kit
p11-kit-modules:amd64
p7zip
p7zip-full
parted
passwd
patch
pciutils
pcmanfm
perl
perl-base
perl-modules-5.24
perl-openssl-defaults:amd64
pinentry-curses
pinentry-gnome3
pinentry-qt
pinentry-qt4
pluma
pluma-common
policykit-1
procps
psmisc
python
python-cairo
python-glade2
python-gobject-2
python-gtk2
python-minimal
python-numpy
python-pkg-resources
python-talloc
python-xdg
python2.7
python2.7-minimal
python3
python3-minimal
python3.5
python3.5-minimal
qdbus
qt-at-spi:amd64
qt5-gtk-platformtheme:amd64
qtchooser
qtcore4-l10n
rarian-compat
readline-common
refractasnapshot-base
refractasnapshot-gui
rename
rsync
rsyslog
samba-libs:amd64
screen
scrot
scsitools
sed
sensible-utils
sg3-utils
sgml-base
sgml-data
shared-mime-info
slim
slsh
squashfs-tools
startpar
sudo
synaptic
syslinux
syslinux-common
sysv-rc
sysvinit
sysvinit-core
sysvinit-utils
tar
tcpd
tint2
tmux
trash-cli
tzdata
ucf
udisks2
unzip
usbmuxd
usbutils
user-setup
util-linux
uuid-runtime
va-driver-all:amd64
vdpau-driver-all:amd64
wget
whiptail
wireless-tools
wpasupplicant
x11-common
x11-utils
x11-xkb-utils
x11-xserver-utils
xarchiver
xauth
xbitmaps
xdg-user-dirs
xdg-utils
xfe
xfe-i18n
xfe-themes
xfonts-base
xfonts-encodings
xfonts-utils
xkb-data
xli
xml-core
xorriso
xserver-common
xserver-xorg
xserver-xorg-core
xserver-xorg-input-all
xserver-xorg-input-libinput
xserver-xorg-input-wacom
xserver-xorg-legacy
xserver-xorg-video-all
xserver-xorg-video-amdgpu
xserver-xorg-video-ati
xserver-xorg-video-fbdev
xserver-xorg-video-nouveau
xserver-xorg-video-radeon
xserver-xorg-video-vesa
xserver-xorg-video-vmware
xterm
xxd
xz-utils
yad
zenity
zenity-common
zlib1g:amd64
groucho@devuan:~$ The VM is up to date and apt-get install -f does not show anything missing.
Now, is there something missing or did I skip a step somewhere in the process from VM to *.iso?
Thanks in advance.
A.
#1583 Re: Installation » Thinning down the ascii installation » 2019-11-27 18:32:16
Hello:
If you can devote 1 GB of that usb stick ...
Sure, but the idea is to get the slimmest possible live *.iso.
Have you seen this guide for minimal install?
Yes, I recall trying to use it once for a different project but I had some issues with it.
This time I decided to start with the ascii VM downloaded from the Devuan repository and trim down.
Like you said, it's much easier than installing and it's coming along quite well.
... better luck with the command-line tools ...
... instead of synaptic.
Yes, I'm slowly getting to be more proficient in cmd line but still lacking.
Using apt/apt-get is one area where I'd rather stick to synaptic for the time being.
But I was going to uninstall synaptic before running the snapshot as I won't need it in the live system.
... remove the locales package ...
Good, I'll try that and see what happens.
Still need to know how to weed out the compilers and the themes I don't wan't.
Any suggestions?
Thanks in advance,
A.
#1584 Re: Installation » Thinning down the ascii installation » 2019-11-27 15:37:48
Hello:
removing git should be ok unless ...
OK.
I have not seen any dependency for git.
Like I mentioned, this starts off with the ascii 2.0.0 VM hich I understand is as basic as can be.
... dont know much about git then?
Not really, never used it.
I am not a programmer nor do I know how to compile.
I'm still struggling with understanding basic scripts.
The live install provides me with basic tools to get the rig back up when/if I screw it up.
Practically all my installed applications are from the Devuan repository
Thanks a lot for your input.
Cheers,
A.
#1585 Re: Installation » Thinning down the ascii installation » 2019-11-27 14:31:34
Hello:
g++-6 depends on libc6 ...
Same with libllvm3.9.
OK
Git is always good to have imo. Ive many adhoc programs .,..
Yes ...
But this is a live emergency "as thin as possible" installation I am building.
Being live and non-persistent, I will not be updating anything.
It will reside on a USB drive inside my box, plugged into a USB socket on the motherboard and any updates/upgrades will be done (as needed) to the VM where it is coming from.
I am still on the fence wrt the convenience of having a full scale browser.
It's basically a quick go-to OS I can boot to through my BIOS w/F8 in case something goes awry.
I had a CorePlus installation for a few years for the same purpose, it saved my installation more than once.
But one day I got a pair NVidia FX580 cards and additional monitors.
As TC does not officially support nouveau or have proprietary legacy NVidia drivers available in their repository, I am building this live *.iso which is much better than having to compile a TC kernel or the NVidia drivers.
That said, is it correct to assume that git can be removed?
Thanks for your input.
Cheers,
A.
#1586 Installation » Thinning down the ascii installation » 2019-11-27 13:18:53
- Altoid
- Replies: 9
Hello:
While in the process of thinning down my live ASCII 2.0.0 *.iso project, I've been looking at what has been installed in the base VM I used and then by me.
I have tried to be as frugal as I can but I see there are a few applications I could probably remove.
I'm especially interested in removing those I will not use or do will not use, however small, as in the end, it all sums up.
All this within the strict boundaries imposed by the need to keep from breaking something ... 8^;
I ask this here because I do not entirely trust Synaptic's optional label.
A quick look at the 'size ordered' list Synaptic offers on 'Installed' packages, I see there are 895.
And some are quite hefty.
eg:
themes
Looking through the file manager and aside from the one labeled Default, there are 25 other folders in /usr/share/themes.
Opening obconf I realise that I don't like/need 90% of them and would eventually keep just the default option.
Depending on the size, maybe look for and install a different one as an alternative to default.
How can I get rid of all these themes and still keep the default one?
tools
One of them is the git package weighing in at a hefty 29.1 MB.
Do I need to have it if I will not use this live *.iso to compile anything?
Same question would apply to g++-6 (24.5 MB), gcc-6 (25.7 MB) and libllvm3.9 (46.0 MB).
man pages
/usr/share/man has 36 folders but I can manage with english.
Which ones do I have to keep for english language only?
xserver-org-video-XXX drivers.
I use twin logacy NVidia cards, so I can manage with the nouveau drivers for the purpose of this live *.iso, so I removed the ones that would not drag the xserver-xorg-video-all metapackage along with it.
ie:
xserver-xorg-video-intel
xserver-xorg-video-qxl
Anything else that could also be removed?
Thanks in advance,
A.
#1587 Re: Installation » Display Manager question » 2019-11-27 10:45:42
Hello:
Slim works with Openbox in ASCII.
Thanks.
Yes, I can confirm it works properly with Openbox in ASCII
At least with the default SLiM theme.
I think the ASCII VM I am using as a base uses elogin (?)
Cheers,
A.
#1588 Installation » Display Manager question » 2019-11-26 22:34:01
- Altoid
- Replies: 3
Hello:
In the process of thinning down my live *.iso project, I had a look at the Release_notes.txt file from https://files.devuan.org/devuan_ascii/Release_notes.txt
### Session management and policykit backends
--- snip ---
Each of the 5 DEs available in Devuan comes with a recommended default
combination of login manager (either slim or lightdm) and session
management system:- XFCE: slim + consolekit
- Cinnamon: lightdm + elogind
- KDE: lightdm + elogind
- LXQT: lightdm + elogind
- MATE: slim + consolekit
--- snip ---The default pairings listed above are known to work well
and do not require user intervention, but other combinations are
possible.
I recall having a problem once when using the wrong combination.
Now I'm using openbox and LightDM, will SLiM work also?
Maybe using just startx would be even better?
Thanks in advance,
A.
#1589 Re: Installation » Strange Synaptic issue » 2019-11-26 15:20:00
Hello:
It's because I did something sneaky ...
Aha !
... and you did something you don't remember.
That's for sure ... =-/
... no refractasnapshot-gui in ascii because ...
... I pulled it before the first release of ascii.
OK
If you installed from the 2.1 desktop-live ...
I don't think I have anything 2.1 installed.
My HD install started off as jessie more than two years ago and my VM is the one I mentioned in my OP.
... you got it from the same place you got refracta2usb, which is not in any devuan repo.
I see.
What Synaptic is telling me is that it is installed in my system, not that it is available in the repository.
Sounds like something that could be added to the UI.
The Installed (local or obsolete) Status list shows only two:
refracta2usb 2.3.6
refractasnapshot-gui 10.0.2.
The Installed (manual) Status list shows all five:
refracta2usb 2.3.6
refractainstaller-base 9.5.3
refractainstaller-gui 9.5.3
refractasnapshot-base 10.1.1
refractasnapshot-gui 10.0.2
... latest versions from sourceforge or download the beowulf or ceres packages and use them in ascii.
Use same version of -base and -gui.
OK.
Thanks for the knowledge shared.
Cheers,
A.
#1590 Installation » Strange Synaptic issue » 2019-11-26 14:16:57
- Altoid
- Replies: 2
Hello:
I have two devuan installations on my rig.
The one on my hard drive/s ...
groucho@devuan:~$ uname -a
Linux devuan 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u2 (2019-11-11) x86_64 GNU/Linux
groucho@devuan:~$ ... and onother on Oracle VM Virtualbox.
groucho@devuan:~$ uname -a
Linux devuan 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u2 (2019-11-11) x86_64 GNU/Linux
groucho@devuan:~$ The first installation started off as jessie a good while ago and is now ascii up to date.
The virtual installation is up to date and was built upon the ascii 2.0.0 VM downloaded here:
https://files.devuan.org/devuan_ascii/virtual/
As I am trying to put together a minimal live ascii to use as a sort of a rescue installaiton, for coherence's sake I use the same /etc/apt/sources.list in both systems:
HD installation:
groucho@devuan:~$ cat /etc/apt/sources.list
## package repositories
# Changed - 20180619
deb http://deb.devuan.org/merged/ ascii main
deb http://deb.devuan.org/merged/ ascii-security main
deb http://deb.devuan.org/merged/ ascii-updates main
# needed x virtualbox backport - enable to update package
deb http://deb.devuan.org/devuan/ ascii-proposed main contrib non-free
deb http://deb.devuan.org/merged/ ascii-backports non-free contrib main
# needed x nvidia non-free drivers installation
deb http://deb.devuan.org/merged/ ascii contrib
deb http://deb.devuan.org/merged/ ascii non-free
groucho@devuan:~$ VM installation:
groucho@devuan:~$ cat /etc/apt/sources.list
## package repositories
# Changed - 20191126
deb http://deb.devuan.org/merged/ ascii main
deb http://deb.devuan.org/merged/ ascii-security main
deb http://deb.devuan.org/merged/ ascii-updates main
# needed x virtualbox backport - enable to update package
deb http://deb.devuan.org/devuan/ ascii-proposed main contrib non-free
deb http://deb.devuan.org/merged/ ascii-backports non-free contrib main
# needed x nvidia non-free drivers installation
deb http://deb.devuan.org/merged/ ascii contrib
deb http://deb.devuan.org/merged/ ascii non-free
groucho@devuan:~$ I was starting to install refractasnapshot-base when I noticed that refractasnapshot-gui was not listed.
But I had seen it.
So I moused over to my HD installation and indeed, synaptic lists five options when I search for refracta:
refracta2usb 2.3.6
refractainstaller-base 9.5.3
refractainstaller-gui 9.5.3
refractasnapshot-base 10.1.1
refractasnapshot-gui 10.0.2
So why should synaptic from my VM show me only these three options?
refractainstaller-base 9.5.3
refractainstaller-gui 9.5.3
refractasnapshot-base 10.1.1
I can't understand how this could be possible, I'm using the same repositories.
Am I missing something here?
Thanks in advance,
A.
#1591 Re: Installation » Configuring persistence » 2019-11-25 17:18:45
Hello:
... think it's all OK, you don't need to fix anything.
... System IDs not having a home dir is not a problem.
... odd that alien-os appears to be logged on to them if you havn't logged on there ...
Thanks for the input. =-)
But I gave up on the Alien-OS live distribution, has too many unknowns for my liking and has not been updated for the past two years.
Also, some unknown (have to see if it reproduces later on) was borking up the USBs filesystem and cause for it to not be recognised at boot by the Ultra24's BIOS.
I heeded fsmithred's sound advice and went for the Devuan ASCII vbox image to which I am adding the basic applications I need to make a very slim live *.iso of my own.
This way I know where it came from and how it got to be.
So there'll be no surprises save those due to my own incompetence. =^)
Cheers,
A.
#1592 Re: Installation » Configuring persistence » 2019-11-24 17:46:04
Hello:
First try cat /etc/passwd and see if there's more than 1 entry for alien-os.
OK.
Alien-OS@groucho╺─╸[~] cat /etc/passwd
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
man:x:6:12:man:/var/cache/man:/usr/sbin/nologin
lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin
mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
news:x:9:9:news:/var/spool/news:/usr/sbin/nologin
uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin
proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
backup:x:34:34:backup:/var/backups:/usr/sbin/nologin
list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin
irc:x:39:39:ircd:/var/run/ircd:/usr/sbin/nologin
gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/usr/sbin/nologin
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
messagebus:x:100:104::/var/run/dbus:/bin/false
avahi-autoipd:x:101:105:Avahi autoip daemon,,,:/var/lib/avahi-autoipd:/bin/false
colord:x:102:108:colord colour management daemon,,,:/var/lib/colord:/bin/false
saned:x:103:109::/var/lib/saned:/bin/false
lightdm:x:104:110:Light Display Manager:/var/lib/lightdm:/bin/false
usbmux:x:105:46:usbmux daemon,,,:/var/lib/usbmux:/bin/false
ntp:x:106:112::/home/ntp:/bin/false
uuidd:x:107:113::/run/uuidd:/bin/false
alien-os:x:1000:1000:,,,:/home/alien-os:/bin/bash
groucho:x:1001:1001:,,,:/home/groucho:/bin/bash
Alien-OS@groucho╺─╸[~] Seems there's only one entry.
Then pwck -r and grpck -r as root to check for errors in the relevant files.
OK.
Alien-OS@root╺─╸[groucho] pwck -r
user 'lp': directory '/var/spool/lpd' does not exist
user 'news': directory '/var/spool/news' does not exist
user 'uucp': directory '/var/spool/uucp' does not exist
user 'www-data': directory '/var/www' does not exist
user 'list': directory '/var/list' does not exist
user 'irc': directory '/var/run/ircd' does not exist
user 'gnats': directory '/var/lib/gnats' does not exist
user 'nobody': directory '/nonexistent' does not exist
user 'saned': directory '/var/lib/saned' does not exist
user 'usbmux': directory '/var/lib/usbmux' does not exist
user 'ntp': directory '/home/ntp' does not exist
pwck: no changes
Alien-OS@root╺─╸[groucho]Alien-OS@root╺─╸[groucho] grpck -r
Alien-OS@root╺─╸[groucho] ... can delete incorrect entries if run without -r (which means read-only) but read the man pages ...
I'll read about what it does before I use it without -r.
Try ps -ef | grep alien-os to see what tasks are running as it.
Alien-OS@groucho╺─╸[~] ps -ef | grep alien-os
alien-os 2885 2763 0 17:27 tty5 00:00:00 -bash
alien-os 2886 2760 0 17:27 tty2 00:00:00 -bash
alien-os 2887 2762 0 17:27 tty4 00:00:00 -bash
alien-os 2888 2761 0 17:27 tty3 00:00:00 -bash
alien-os 2889 2764 0 17:27 tty6 00:00:00 -bash
alien-os 2890 2759 0 17:27 tty1 00:00:00 -bash
groucho 3469 3408 0 17:33 pts/0 00:00:00 grep alien-os
Alien-OS@groucho╺─╸[~] There they are ...
Six tasks.
One for each of the alien-os users.
Alien-OS@groucho╺─╸[~] users
alien-os alien-os alien-os alien-os alien-os alien-os groucho
Alien-OS@groucho╺─╸[~] It's all over my head.
No idea what to make of it.
Thanks for your input. =-)
Best,
A.
#1593 Re: Installation » Configuring persistence » 2019-11-24 02:48:02
Hello:
The solution may be (?) in ...
I managed to (sort of) fix things.
I was able to drop to a shell and by means of sudo su become root.
Then I gave root a new password and added a user with his own password.
So, now I was able to log-in both as root with administrative privileges and as user.
Certain that I could log-in under both IDs, I tried to get rid of user alien-os, whose password I did not know and name I did not like.
Unfortunately, that was not possible as it was working with some process.
Alien-OS@root╺─╸[~] userdel alien-os
userdel: user alien-os is currently used by process 2890
Alien-OS@root╺─╸[~] So I figured I could keep it in lieu of the newly created user which I would then remove.
No big deal ....
So, as root, changed alien-os' password and the problem would be solved.
Alien-OS@root╺─╸[~] passwd alien-os
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
Alien-OS@root╺─╸[~] I then rebooted and when I logged in as user alien-os with the new password, instead of bringing up the desktop or saying that the password was not valid, LightDM came back like if nothing had happened: I typed the password at least ten times and it came back without logging me in every time.
I logged on as root again to see what was going on ie: see what users were in the system.
It was a surprise of sorts:
Alien-OS@root╺─╸[~] users
alien-os alien-os alien-os alien-os alien-os alien-os root
» Alien-OS@root╺─╸[~] I installed members and used it with groups try to see who was what:
Alien-OS@root╺─╸[~] groups alien-os
alien-os : alien-os cdrom floppy audio dip video plugdev netdev bluetooth
Alien-OS@root╺─╸[~] Alien-OS@root╺─╸[~] members alien-os
alien-os
Alien-OS@root╺─╸[~] I have always read/been told that users have unique names ie: there could only be one user with alien-os for a name.
But (unless I am missing something) in this case we are in front of six users sharing the same name.
This is where I stop and ask if anyone can shed some light into this.
Thanks in advance,
A.
#1594 Installation » Configuring persistence » 2019-11-24 00:29:34
- Altoid
- Replies: 6
Hello:
While on the way to finish configuring a persistent Alien-OS to generate a new live *.iso, I have come across a(nother) problem.
Alien-OS would boot into persistence with user=Alien-OS in the kernel command line by default.
Add persistence to the line and that was it.
From then on, to make any administrative changes you would just sudo them on.
Not my cup of tea but that is how it is set up by default and was planning to change that by adding a password to root and a user, just for reminder's sake if anything.
After doing a major update (this was a jessie from 2 years ago) and removing a number of unneeded things, I rebooted with persistence and was greeted by LightDM asking for a password to log-in as Alien-OS or as Other.
I had not yet set a root password or a new user yet so I'm at a loss here.
It probably has to do with whatever went into the update.
I have root access to the persistence partition and folders via my Devuan installation but don't know what to change or add to be able to log in.
I have tried renaming /persistence/etc/lightdm/lightdm.conf to lightdm.old but that did not work.
The solution may be (?) in /persistence/etc/pam.d/login but I don't know how to deal with that.
Any suggestions?
Thanks in advance,
A.
#1595 Re: Installation » Problems configuring persistence » 2019-11-23 21:04:19
Hello:
... take out the USB ...
... reboot and see what happens when I plug it into one of the external ports ...
Yes, that did it.
I think this was probably some sort of BIOS glitch.
The rig is a Sun Ultra24, excellent hardware and way ahead of its time.
But the BIOS is absolute crap.
Then Oracle came along...
But I digress.
I assume that it could have been a BIOS glitch because when the problem cropped up, the boot screen (which rolls by fast but you can catch it) did not list a Kingston DataTraveller storage device like it usually did.
And then, having pressed F8 to get at the Boot Menu, when it came up it showed me a USB: USB Flash Drive as the first option instead of showing me a USB: Kingston DataTraveller.
Shutting down, unplugging and plugging it in again (on an external port just in case I had to do something) set things right: at reboot the Boot Menu option was the correct one ie: USB: Kingston DataTraveller.
Thanks for your input.
Best,
A.
#1596 Re: Installation » Problems configuring persistence » 2019-11-23 20:12:58
Hello:
... did it include reinstalling grub?
... grub even installed in the live system?
I don't think so. (?)
Mounting the live *.iso image using AcetoneISO shows me three folders:
- isolinux
- live
- pkglist_Alien-OS MNML-20170610_1259
The pkglist includes:
grub-common
grub-pc
grub-pc-bin
grub2-common
... computer boot without the usb stick?
Yes.
No problems with that.
Maybe the flash drive is dying.
I don't think so ...
It's a new/almost no use Kingston DTSE9.
... a reboot will fix it.
Been there, tried that.
... pulling the stick out and plugging it back ...
... probably be /dev/sdf if you do this
Was about to try that after my afternoon espresso.
I have the impression/idea that somehow/for some reason the file system went south.
But no idea how that could have happened.
It is my understanding that whatever was being written to the drive was getting written to /sda2 and there were 3.0Gb available for that.
I'll take out the USB, which lives inside the box in its own socket on the motherboard, reboot and see what happens when I plug it into one of the external ports and then post back.
Thanks for your input.
Best,
A.
#1597 Re: Installation » Problems configuring persistence » 2019-11-23 15:04:03
Hello:
... 'persistence' in the boot command and the filesystem label on the persistent partition ...
... enough space in the persistent partition to hold a big upgrade.
... boot with persistence when you make the snapshot, it will copy the upgraded (running) system.
This morning I went ahead and booted the live *.iso with persistence and then ran Synaptic.
The update took a long time, probably because the *.iso is from two years ago, the list was huge and included linux-image-3.16.0-10-amd64.
When it finished, I shut down and rebooted the live *.iso with persistence, expecting to see it updated.
But alas, something strange happened on the way to persistence .... =^o !
Not only did the live *.iso not boot ie: on selection of the USB drive, it just proceeded to my usual grub screen.
I booted into my main Devuan and to see what had been written into the persistence partition /dev/sda is nowhere to be found.
It has absolutely dissapeared from the system.
- fdisk does not see it:
groucho@devuan:~$ sudo fdisk -l
[sudo] password for groucho:
Disk /dev/sdb: 68.4 GiB, 73407488000 bytes, 143374000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0004a8f4
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 40974335 40972288 19.6G 83 Linux
/dev/sdb2 40974336 139278335 98304000 46.9G 5 Extended
/dev/sdb3 139278336 143372287 4093952 2G 82 Linux swap / Solaris
/dev/sdb5 40976384 45072383 4096000 2G 83 Linux
/dev/sdb6 45074432 139278335 94203904 44.9G 83 Linux
Partition table entries are not in disk order.
Disk /dev/sdc: 279.4 GiB, 300000000000 bytes, 585937500 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x30830f4e
Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 585936895 585934848 279.4G 5 Extended
/dev/sdc5 4096 585936895 585932800 279.4G 83 Linux
Disk /dev/sdd: 68.4 GiB, 73407488000 bytes, 143374000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x68017f5c
Device Boot Start End Sectors Size Id Type
/dev/sdd1 * 2048 40962047 40960000 19.5G 83 Linux
/dev/sdd2 40962048 45058047 4096000 2G 82 Linux swap / Solaris
/dev/sdd3 45058048 143372287 98314240 46.9G 5 Extended
/dev/sdd5 45060096 143372287 98312192 46.9G 83 Linux
Disk /dev/sde: 232.9 GiB, 250056000000 bytes, 488390625 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x85188518
Device Boot Start End Sectors Size Id Type
/dev/sde1 2048 329396223 329394176 157.1G 83 Linux
/dev/sde2 329396224 488388607 158992384 75.8G 83 Linux
groucho@devuan:~$ - parted does not see it either:
groucho@devuan:~$ sudo parted
GNU Parted 3.2
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print devices
/dev/sdb (73.4GB)
/dev/sdc (300GB)
/dev/sdd (73.4GB)
/dev/sde (250GB)
(parted) quit
groucho@devuan:~$ Any idea as to what may have happened?
I find it strange that the device is not available ...
Edit:
... dmesg reports it ...
--- snip ---
[ 3.584672] scsi 7:0:0:0: Direct-Access USB Flash Drive 2.00 PQ: 0 ANSI: 0
[ 3.596655] sd 7:0:0:0: [sda] Attached SCSI removable disk
--- snip ---... but says nothing of /sda2, which is where persistence is/was supposed to live.
lsblk does not see it either.
groucho@devuan:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 68.4G 0 disk
|-sdb1 8:17 0 19.6G 0 part /
|-sdb3 8:19 0 2G 0 part
|-sdb5 8:21 0 2G 0 part /var/log
`-sdb6 8:22 0 44.9G 0 part /home
sdc 8:32 0 279.4G 0 disk
|-sdc1 8:33 0 1K 0 part
`-sdc5 8:37 0 279.4G 0 part
sdd 8:48 0 68.4G 0 disk
|-sdd1 8:49 0 19.5G 0 part
|-sdd2 8:50 0 2G 0 part
|-sdd3 8:51 0 1K 0 part
`-sdd5 8:53 0 46.9G 0 part
sde 8:64 0 232.9G 0 disk
|-sde1 8:65 0 157.1G 0 part /media/backups
`-sde2 8:66 0 75.8G 0 part
sr0 11:0 1 1024M 0 rom
groucho@devuan:~$ lshw sees it:
groucho@devuan:~$ sudo lshw | grep logical
logical name: eth0
logical name: usb1
logical name: usb2
logical name: usb3
logical name: usb9
logical name: scsi7
logical name: /dev/sda
configuration: logicalsectorsize=512 sectorsize=512
logical name: /dev/sda
logical name: scsi8
logical name: /dev/sdb
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=0004a8f4
logical name: /dev/sdb1
logical name: /
*-logicalvolume:0
logical name: /dev/sdb5
logical name: /var/log
*-logicalvolume:1
logical name: /dev/sdb6
logical name: /home
logical name: /dev/sdb3
logical name: /dev/sdc
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=30830f4e
logical name: /dev/sdc1
*-logicalvolume
logical name: /dev/sdc5
logical name: /dev/sdd
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=68017f5c
logical name: /dev/sdd1
logical name: /dev/sdd2
logical name: /dev/sdd3
*-logicalvolume
logical name: /dev/sdd5
logical name: /dev/sde
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=85188518
logical name: /dev/sde1
logical name: /media/backups
logical name: /dev/sde2
logical name: usb7
logical name: usb8
logical name: usb4
logical name: usb5
logical name: usb6
logical name: usb10
logical name: scsi1
logical name: /dev/cdrom
logical name: /dev/cdrw
logical name: /dev/dvd
logical name: /dev/dvdrw
logical name: /dev/sr0
groucho@devuan:~$ Thanks in advance,
A.
#1598 Re: Installation » Problems configuring persistence » 2019-11-23 01:11:46
Hello:
... 'persistence' in the boot command and the filesystem label on the persistent partition ...
... enough space in the persistent partition to hold a big upgrade.
... boot with persistence when you make the snapshot, it will copy the upgraded (running) system.
Good.
Thanks a lot for your help. =-)
Best,
A.
#1599 Re: Installation » Problems configuring persistence » 2019-11-22 23:51:03
Hello:
I was in my Devuan install and rebooted to alien-os to answer your post and ...
It works.
Go figure.
What does your boot command look like? cat /proc/cmdline
Alien-OS@alien-os╺─╸[~] cat /proc/cmdline
BOOT_IMAGE=/live/vmlinuz initrd=/live/initrd.img boot=live persistence vga=795 username=alien-os
Alien-OS@alien-os╺─╸[~] Stanzas persistence and vga=795 were added bz me after Tab to edit the boot command.
Otherwise it boots as a the std live *.iso. (?)
What is in persistence.conf?
Alien-OS@alien-os╺─╸[~] cat /persistence.conf
/ union
Alien-OS@alien-os╺─╸[~] ... don't know Alien-OS.
... a debian-based distro and it uses live-boot and live-config. Is that correct?
Don't know what it uses, have to check/read up.
All I can say is that the DE keyboard (qwerz) layout + the darkish theme are a bitchy combination. =-/
I saw alien-os mentioned here ...
http://dev1galaxy.org/viewtopic.php?id=1811
http://dev1galaxy.org/viewtopic.php?pid=3569#p3569
... and assumed it was Devuan based.
Is the OS 32-bit or 64-bit?
Apparently only 64-bit.
... system directories on the persistent partition ...
Yes, automagically created.
There is a website:
https://www.alien-os.de/
Every boot the installation says there are updates available (a nag) but it is a huge list which includes linux-image-3.16.0-10-amd64.
If I accept and go ahead, do these stay installed on reboot in persistence mode and then get carried on to the new *.iso?
Thanks in advance,
A.
#1600 Installation » Problems configuring persistence » 2019-11-22 21:50:12
- Altoid
- Replies: 8
Hello:
I am attempting to set up alien-os with persistence so as to change a few things and maybe slim it down a bit further to then burn a new *.iso with the changes.
I am using an 8gb pen drive which I have partitioned in this manner:
500Mib for the *.iso image
3,00Gib for the persistence partition
3,78Gib of unallocated space
Alien-OS@alien-os╺─╸[~] sudo fdisk -l
Disk /dev/sda: 7.2 GiB, 7757398016 bytes, 15151168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x062ec9ea
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 64 921599 921536 450M 17 Hidden HPFS/NTFS
/dev/sda2 921600 7219199 6297600 3G 83 Linux
Alien-OS@alien-os╺─╸[~] These are the mount points:
Alien-OS@alien-os╺─╸[~] mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=813044k,mode=755)
/dev/sda1 on /lib/live/mount/medium type iso9660 (ro,noatime)
/dev/loop0 on /lib/live/mount/rootfs/filesystem.squashfs type squashfs (ro,noatime)
tmpfs on /lib/live/mount/overlay type tmpfs (rw,relatime)
tmpfs on /lib/live/mount/overlay type tmpfs (rw,noatime,mode=755)
aufs on / type aufs (rw,noatime,si=4d6addd750f80fe7,noxino)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
pstore on /sys/fs/pstore type pstore (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=1012409,mode=755)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1626080k)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime)
gvfsd-fuse on /home/alien-os/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sda2 on /media/alien-os/persistence type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
» Alien-OS@alien-os╺─╸[~] The persistence partition has (apparently) all that it has to have:
Alien-OS@alien-os╺─╸[~] ls /media/alien-os/persistence
etc home lib lost+found persistence.conf tmp var
Alien-OS@alien-os╺─╸[~] But I think (?) there is probably something wrong with the mount point as persistence is not working.
What did I miss?
Thanks in advance,
A.
Board footer
