Search Results for 'bluetooth'

Hello there,

The About page of antixlinux.com says;

The goal of antiX is to provide a light, but fully functional and flexible free operating system for both newcomers and experienced users of Linux. It should run on most computers, ranging from 256MB old PIII systems with pre-configured swap to the latest powerful boxes.

This is very pleasing and gladdening.

However, I have my doubts. So I am asking this to clarify them.

Can Antix-19.2.1-Base run a couple of VBox VMs smoothly?

I was thinking of installing VBox and a couple of VMs on my Antix-19.2.1-x64-Base system. My system is mid-range and has the space and required system configurations, I suppose. They are as below;

CPU: Intel(R) Core(TM) i3 M 380  @ 2.53GHz
Graphics card: Intel Core Processor Integrated Graphics Controller
Sound: Intel 5 Series/3400 Series Chipset High Definition Audio
Storage: Intel 5 Series/3400 Series Chipset 4 port SATA AHCI Controller
RAM: 3 GB
Network:
  Wireless: Broadcom BCM4313 802.11bgn Wireless Network Adapter
  Ethernet: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
Bluetooth: Broadcom BCM2070 Bluetooth Device
Hard disk: SAMSUNG HM321HI 300 GB
CDROM: Slimtype DVD A DS8A5SH
BIOS: BIOS

Can a combination of this computer, with the above mentioned HW configurations and Antix-19.2.1-x64-Base OS, handle VBox and its couple of guest VMs of Windows 10 and Android?

Thanks & Regards

• This topic was modified 2 years, 9 months ago by anilkagi.

Taking the following assumptions (my observations):
– Hannie Schaft 19.2 antiX became an excellent OS in the current version as long as some missing functionality is added on individual basis, such as SMB, Bluetooth, subjective aesthetics, etc…
– Evolving or supplementing with a full DE has been abandoned by antiX project owner due to time and resource constraints.
– Development Team appears to be relatively small.

Is there a plan, or just a vision of next milestone in antiX evolution?

Not to be misunderstood, antiX is so good as it is that it makes it difficult to implement significant version difference without a decisive change, such as DE….
Just my two cents, not necessarily expecting answers…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member Xecure]

I don’t know if inxi has a problem with PCMCIA cards, as it doesn’t display any information about it.
Your first post informs us that the driver used is orinoco. I have confirmed it is the only driver compatible with your card:
http://linux-wless.passys.nl/query_hostif.php?hostif=PCMCIA

manufacturer 	wlan type 	product ID 	vendor & product code 	chipset 	driver 	works with Linux 	comments
Compaq 	        802.11b 	WL 110 		                        Orinoco 	Wavelan 	green 	http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Orinoco.html

Check to see if the orinoco module is loaded (if it is on the list, then it is loaded)
lsmod | grep orinoco

If it is, check to see if there are any error messages spit out by the kernel:
sudo dmesg | grep orinoco

Next step is to check what the system is able to recognize as wireless (in your first post it seems to believe it is eth1):

ifconfig
iwconfig

The worst possible case is a problem with the driver for the PCMCIA port. Another user with a Compaq armada M300 had some problems with his here (https://www.antixforum.com/forums/topic/wait-it-does-not-work-right-okay-that-was-aimed-at-the-wireless-driver/). Try to find the card reader in:
sudo lspci -k
It should say something like:

00:04.0 CardBus bridge: Texas Instruments PCI1211
        Subsystem: Compaq Computer Corporation PCI1211
        Kernel driver in use: yenta_cardbus
        Kernel modules: yenta_socket

If everything seems to be OK, maybe the problem is connman. We will proceed to remove it. Try to see if my script (attached in previous message) will work for you to Remove connman and set the correct symlink for /etc/resolv.conf
Then you can again try to get wifi to work with ceni.
If the script doesn’t work, try:

anticapitalista wrote:

1. Remove connman and cmst

sudo apt-get remove --purge connman cmst connman-bluetooth-firmware-antix

2. Delete the resolv.conf sym link in /etc/
3. Create a new symlink in etc like this (in a terminal)

sudo ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf

4. Try ceni again

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member olsztyn]

Xecure wrote:

It is a known issue that bluetooth headphones have problems with the ALSA sound system. I have only got mine to work with pulseaudio. If you want to test it out, these are the instructions:

Getting pulseaudio in your system:

Thank you Xecure for this guide. I had done it in the past but it was piecemeal. Your guide is contains everything one needs in one clear document.
Regards.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member Xecure]

First give us info on your hardware. Open a terminal, execute:
inxi -Fxz
then copy the output and paste it on your post with code tags (select the code inside the forum editor and click on the CODE button on top of the textbox.
Though I believe that your problem doesn’t seem to be hardware related.

It is a known issue that bluetooth headphones have problems with the ALSA sound system. I have only got mine to work with pulseaudio. If you want to test it out, these are the instructions:

Getting pulseaudio in your system:

1. Installing pulseaudio:
Open a terminal and execute
sudo apt update && sudo apt-get install pulseaudio pavucontrol pulseaudio-module-bluetooth

2. Make pulseaudio launch on startup
Edit startup file
geany ~/.desktop-session/startup
Uncomment the line related to pulseaudio. It should look like this:

# Uncomment if using pulseaudio (you need to install it)
pulseaudio -D &

Save and exit

3. Making volume-icon use pulseaudio (and manage volume and properties)
right-click the volume icon in your systray and click on Preferences.
Have External mixer execute pavucontrol. It originally says:
External mixer desktop-defaults-run -t alsamixer
Replace it with:
External mixer pavucontrol

4. Reboot your system.
From this moment on, pulseaudio will autlaunch on startup.

5. Configure your Bluetooth headphone with pavucontrol.
Launch blueman as you have before (if you have it set to autolaunch even better).
Go to Bluetooth devices (your second image). Remove your headset (HD 4.50BTNC) from the list (right-click and Remove) because you are going to set it up again.
Get your bluetooth headset to search for devices/sync, hit the “Search” button on the Bluetooth Devices window. When it appears on the list, select it and click on “Trust” and then “Pair”. Finally, right-click on it and select “Audio sync”.
Open pavucontrol (right-click volume icon, then select “Open Mixer”). Go to the “Output Devices” tab and make sure pavucontrol can find your headset. Then try playing an audio file or a video and check that the application is outputing sound to the Bluetooth headset (you will be able to see this in the “Playback” tab in pavucontrol).

6. The end

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

Hi there I am running into error while setting up my bluetooth, the Bluetooth manager gives connection failed: blueman.bluez.errors.dbusfailederror: protocol not available…

I have install ‘full verison’ of 32bit image of antix linux on my complete hdd.I have already jumped an os due to bluetooth issues. Thanks for the help. Please include detailed instructions as i am a newbie.

Thanks alot!

• This topic was modified 2 years, 10 months ago by mynametiger.

Once I have configured a perfect (perfect for me, of course) antiX system, with aesthetic desktop and all important for me functionality working, such as SMB networking, bluetooth, bit fidelity sound, office, firewall, encryption, etc., I am trying to tap into additional potential of antiX, which may not be standing out as mainstream use.
A few of powerful (IMHO) capabilities that are beyond typical use:
– Capable discovery of other bootloaders (whether Linux systems or Windows) and booting into those systems from antiX Live instance. In addition to discovery of bootloaders, such capability of antiX is extended to discovery of grub menus, which could be a superset of bootloaders. Very useful.
– Capability of multiple installs of Frugal systems and selecting which to boot from Grub menu, whether an installed Grub or antiX Live. There are several ways of addressing Frugals – with or without installed antiX.

Having tapped into the above, can someone please suggest other useful capabilities of antiX that can be tapped into?
Thanks in advance for ideas…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

How to setup Antix for going to sleeping mode after closing the lid? it`s not working by default
I found Pm-utils, but it hard to understand, maybe some easiest way ? just need sleep mode or suspend

inxi -Fxx
System:    Host: antix1 Kernel: 4.9.212-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: IceWM 1.6.6 dm: SLiM 
           Distro: antiX-19.2.1_x64-base Hannie Schaft 29 March 2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: ASUSTeK product: K54L v: 1.0 serial: BBN0AS238812457 
           Mobo: ASUSTeK model: K54L v: 1.0 serial: BSN12345678901234567 BIOS: American Megatrends v: K54L.208 
           date: 09/26/2011 
Battery:   ID-1: BAT0 charge: 23.9 Wh condition: 26.4/37.8 Wh (70%) volts: 16.5/14.4 model: ASUSTek K53--27 serial:   
           status: Charging 
CPU:       Topology: Dual Core model: Intel Celeron B800 bits: 64 type: MCP arch: Sandy Bridge rev: 7 L1 cache: 32 KiB 
           L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 5986 
           Speed: 800 MHz min/max: 800/1500 MHz Core speeds (MHz): 1: 800 2: 800 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:0106 
           Display: server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.3.6 compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:1c20 
           Sound Server: ALSA v: k4.9.212-antix.1-amd64-smp 
Network:   Device-1: Qualcomm Atheros AR9285 Wireless Network Adapter vendor: Foxconn driver: ath9k v: kernel port: e040 
           bus ID: 02:00.0 chip ID: 168c:002b 
           IF: wlan0 state: up mac: 60:d8:19:0e:04:b5 
           Device-2: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet vendor: ASUSTeK driver: atl1c v: 1.0.1.1-NAPI port: a000 
           bus ID: 04:00.0 chip ID: 1969:1083 
           IF: eth0 state: down mac: 54:04:a6:3b:ac:da 
           Device-3: Qualcomm Atheros AR3011 Bluetooth type: USB driver: btusb bus ID: 1-1.1:5 chip ID: 0cf3:3005 
Drives:    Local Storage: total: 298.09 GiB used: 20.41 GiB (6.8%) 
           ID-1: /dev/sda vendor: Seagate model: ST9320325AS size: 298.09 GiB speed: 3.0 Gb/s serial: S2W4PHZ4 
Partition: ID-1: / size: 122.61 GiB used: 20.41 GiB (16.6%) fs: ext4 dev: /dev/sda6 
Sensors:   System Temperatures: cpu: 53.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 2100 
Info:      Processes: 160 Uptime: 2h 09m Memory: 3.77 GiB used: 769.3 MiB (19.9%) Init: SysVinit v: 2.93 runlevel: 5 
           default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: roxterm inxi: 3.0.36 

[Member olsztyn]

Brian Masinick wrote:

I have to agree; antiX in ANY form is much better, superior in every possible way, and we have a very small team.

Thanks masinick for the info on Lubuntu… I just want to mention that whether it is Lubuntu or Xubuntu or Kubuntu or Ubuntu, they are not my cup of tea…
When I finally put together my ultimate antiX Live configuration, that supports SMB to NAS servers, host for virtualization software, Bluetooth, bit fidelity audio matching sound quality of that under Windows, and having that burned into USB Cruzer Fit that can be stuck in my wallet to be just plugged into any laptop, nothing like these *Buntus impress me…
This is the strength of the antiX – quite capable Live, that having configured to my requirements I will continue to use for years to come. Probably long after many antiX desktop users will move on…
If antiX does eventually come up with DE edition of antiX, I will be quite interested too though, and I will not be surprised that it may turn out better that all those *Buntus…
Just my two cents…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member olsztyn]

BobC wrote:

I tried MATE recently with NuTyX. Its ok, I guess, stable but not lean.

I would rather LXQT or XFCE.

LXQT is probably going to run leaner than many of the choices, which is important for people on older hardware.

Whatever Desktop antiX will end up choosing I am definitely looking forward to it. Not that I am not happy with current IceWM and Fluxbox. They are great to minimize resource requirements but they require lots of work to make them presentable to make a regular desktop, not speaking of expected nowadays functionality, such as integrated capability of networking SMB shares, integrated bluetooth, etc. Current antiX has this all available in separate unintegrated pieces of software, but not as integrated part of the antiX system.
On top of this aesthetics of DE do play significant role in day to day usability. I believe that something can be done with current IceWM and Fluxbox to match aesthetics of Gnome and derivatives but I was not able find such quality composition of Themes, Styles, Fonts, etc. I guess developers of IceWM or Fluxbox did not have aesthetics as priority.
So I think that such desktop as MATE or others can introduce this aesthetics component and I believe these desktops can be made relatively lean in resource requirements with some work, such as what Intel has done with Clear Linux, which is benchmarked as the fastest out there and has Gnome 3 desktop but uses only 515 M memory.
I think it is an opportunity for antiX to come out with truly lean version of mainstream desktop, while retaining lean system infrastructure.
This strategy would move antiX to the most popular Linux systems out there…
Just some of wishful thinking…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member olsztyn]

anticapitalista wrote:

If you were to add a desktop-environment to antiX, which would you choose and why?
If antiX were to ship a separate iso built with only one desktop-environment, which would you choose and why?

Although I want to rely on far more experienced participants in suggesting the best desktop I just want to mention I have been using Fluxbox and IceWM, with heavily customized themes to make them visually acceptable, and I am pretty much happy with them after modifications.
However if antiX team is looking to further enhance desktop then I have general criteria for consideration:
– Although current desktops are functionally sufficient IMHO, satisfactory visual presentation of them requires heavy (and not easy) customization of themes, toolbars, fonts, etc. Fonts are still difficult and low resolution, although huge improvement in fonts has been accomplished while moving from antiX 17 to antiX 19. In the new desktop it is important that fonts are crisp and high quality, such as seen in Cinnamon or Gnome. Also aesthetics of windows should be matching those in such desktops.
– User friendly handling of network infrastructure and hardware is important, such as better handling of SMB shares, printers, bluetooth, etc.
– While selecting new desktop be conservative on memory requirements they often entail, perhaps due to multitude of various useless stuff they tend to include. E.g. while Cinnamon has visually presentable desktop, why does it have to use so much memory, comparing to IceWM?
– To me such heavy in resource waste desktops as KDE or Gnome are not acceptable. Unless they are made efficient. I read an article, where the author claimed that nowadays KDE is more efficient than XFCE at every point in the article, but looking at benchmark results in that article they were clearly contradicting these claims… Regarding Gnome derivatives, such as Cinnamon I do not think they need to be so resource wasteful. Such as Intel’s Clear Linux does use Gnome by default but memory utilization is kept rather low nonetheless, such as 515M running nothing… With FF or Chrome running, this raises to 700’s initially, before further tabs are opened.
My summary:
Myself not being a fan of any particular desktop, what matters is functionality, aesthetics, user friendliness and infrastructure support. But particularly not being wasteful in resources.
Just MHO….

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

14 June, 2020
Marielle Franco full, spacefm-fluxbox, SysVinit, buster_ 4.9.193-antix.1-amd64-smp x86_64

 Private  +   Shared  =  RAM used	Program

216.0 KiB +  46.5 KiB = 262.5 KiB	gpm
300.0 KiB +  44.0 KiB = 344.0 KiB	acpid
264.0 KiB +  99.0 KiB = 363.0 KiB	cron
296.0 KiB +  74.0 KiB = 370.0 KiB	init
368.0 KiB + 162.0 KiB = 530.0 KiB	dbus-launch
484.0 KiB +  52.5 KiB = 536.5 KiB	rpc.idmapd
392.0 KiB + 147.0 KiB = 539.0 KiB	dundee
408.0 KiB + 133.5 KiB = 541.5 KiB	irqbalance
348.0 KiB + 230.0 KiB = 578.0 KiB	udevil
484.0 KiB + 233.0 KiB = 717.0 KiB	rpcbind
392.0 KiB + 591.5 KiB = 983.5 KiB	avahi-daemon (2)
652.0 KiB + 409.0 KiB =   1.0 MiB	devmon
876.0 KiB + 221.5 KiB =   1.1 MiB	rpc.statd
356.0 KiB + 756.0 KiB =   1.1 MiB	saned (2)
700.0 KiB + 426.0 KiB =   1.1 MiB	desktop-session
632.0 KiB + 530.5 KiB =   1.1 MiB	gconfd-2
808.0 KiB + 489.0 KiB =   1.3 MiB	getty (6)
  1.2 MiB + 305.5 KiB =   1.5 MiB	sudo
  1.3 MiB + 211.0 KiB =   1.5 MiB	sshd
896.0 KiB + 609.0 KiB =   1.5 MiB	dbus-daemon (2)
  1.4 MiB +  92.0 KiB =   1.5 MiB	elogind-daemon
  1.3 MiB + 317.0 KiB =   1.6 MiB	ntpd
996.0 KiB + 735.5 KiB =   1.7 MiB	connman-vpnd
  1.6 MiB + 242.0 KiB =   1.8 MiB	connmand
  1.7 MiB + 185.0 KiB =   1.9 MiB	ofonod
  1.5 MiB + 449.5 KiB =   1.9 MiB	bash
  1.7 MiB + 378.5 KiB =   2.1 MiB	bluetoothd
  1.7 MiB + 438.5 KiB =   2.1 MiB	gnome-keyring-daemon
  2.0 MiB + 131.0 KiB =   2.1 MiB	rsyslogd
  1.9 MiB + 983.5 KiB =   2.9 MiB	cupsd
  1.5 MiB +   1.7 MiB =   3.2 MiB	gksu
  3.2 MiB +  34.5 KiB =   3.2 MiB	haveged
  3.3 MiB + 535.0 KiB =   3.8 MiB	udevd
  2.8 MiB +   1.3 MiB =   4.1 MiB	slim
  3.6 MiB +   1.3 MiB =   4.9 MiB	conky
  4.5 MiB + 680.5 KiB =   5.1 MiB	wpa_supplicant
  4.1 MiB +   1.4 MiB =   5.5 MiB	fluxbox
  2.6 MiB +   3.1 MiB =   5.6 MiB	volumeicon
  8.0 MiB +   5.1 MiB =  13.1 MiB	roxterm
 22.8 MiB +   1.7 MiB =  24.5 MiB	Xorg
 31.2 MiB +   6.0 MiB =  37.2 MiB	spacefm
---------------------------------
                        146.5 MiB
=================================

[Member olsztyn]

Update:
As Virtual Box works kind of Ok for me, at first I gave up on installing VMware Player under antiX some time ago, not able to complete. However this install working just fine under Clear Linux made me re-visit this challenge and another attempt of installing under antiX.
So this is what I did:
– So as to check if by chance this behavior of not reacting to my click on ‘Finish’ button is not similar to what I reported earlier for Fluxbox – not reacting to dropdown menue items for Chrome/Chromium on my nVidia machines, I re-did this on an Intel laptop (no nVidia). The same negative result experienced, both in Fluxbox and IceWM on Intel box. So this case is different as it does not react to click on ‘Finish’ button as the last step of installation of VMware Player regardless of my machine or Fluxbox or IceWM.
– It bugged me that I was not able to finish installation under antiX as I am trying to make my instances of antiX very versatile and useful for variety of tasks after making work such important functions as SMB shares, Bluetooth sound, Host for virtual machines (Virtual Box so far) – taking advantage of low memory use by antiX infrastructure, etc… So taking another chance, tried this:
– As under IceWM and Fluxbox clicking the ‘Finish’ button installing VMware Player was stubbornly ignored I temporarily installed Gnome desktop from the Package Installer from Control Center. I do not like Gnome but this was just an interim plan before I return to IceWM and Fluxbox… To my surprise (well maybe not…) under Gnome desktop the final click on ‘Finish’ button worked just fine and concluded installation of VMware Player. So:
– Neither IceWM nor Fluxbox was reacting to click on ‘Finish’ button but under Gnome it worked fine and VMware Player completed installation and worked fine…

Now, I do expect this will be again brushed off as VMware problem and that IceWM and Fluxbox have nothing to do with non-reaction to click on ‘Finish’ button. I am in no position to insist it is so, but I have a more practical question if someone is so kind as to help me:
Namely –
At first (I think) I was able to log-off from Gnome and switch back to IceWM on the login screen by toggling F1, and verify VMware Player. But upon subsequent re-boots it stubbornly throws me back into Gnome desktop and does not seem to let me go back to IceWM or Fluxbox via F1. Neither from login screen nor from the initial boot menu selecting IceWM desktop (F6) seems to work. Still ends up with Gnome… Since Gnome is not my choice of desktop for antiX, is there any way to switch back into IceWM?
Thanks and Regards…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member Xecure]

Bienvenido, Patxi.

You have to choose.

A. Use Connman
If you want to use connman, delete the wifi information created by CENI in /etc/network/interfaces
sudo geany /etc/network/interfaces
It should look like this:

#------------------------------------------------------------------------------
# /etc/network/interfaces
#
# interfaces(5) file used by ifup(8) and ifdown(8)
# Used by ceni but not by connman
#------------------------------------------------------------------------------

auto lo
iface lo inet loopback

Then try to connect using Connman

B. Use ceni.
You have to remove Connman completely and create a link for resolv.conf
See anticapitalista’s answer:

anticapitalista wrote:

1. Remove connman and cmst

sudo apt-get remove --purge connman cmst connman-bluetooth-firmware-antix

2. Delete the resolv.conf sym link in /etc/
3. Create a new symlink in etc like this (in a terminal)

sudo ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf

4. Try ceni again

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Forum Admin dolphin_oracle]

checking out the /etc/init.d/.depend-stop file after running update-rc.d on the modified umountnfs-alternative.sh init file. note that connman has a dependent stop on umountnfs-alternative.sh

TARGETS = umountnfs-alternative.sh tlp unattended-upgrades gpm haveged irqbalance acpi-support smartmontools bluetooth dundee elogind ofono slim avahi-daemon saned cups alsa-utils brightness resolvconf urandom ufw connman sendsigs rsyslog umountnfs.sh rpcbind nfs-common hwclock.sh umountfs cryptdisks cryptdisks-early udev umountroot halt reboot
avahi-daemon: saned
connman: umountnfs-alternative.sh
sendsigs: connman alsa-utils bluetooth dundee elogind gpm haveged irqbalance ofono saned slim tlp unattended-upgrades avahi-daemon
rsyslog: sendsigs
umountnfs.sh: rsyslog sendsigs connman alsa-utils bluetooth dundee elogind gpm haveged irqbalance ofono saned slim tlp unattended-upgrades avahi-daemon
rpcbind: umountnfs.sh umountnfs-alternative.sh
nfs-common: umountnfs.sh umountnfs-alternative.sh
hwclock.sh: nfs-common rsyslog
umountfs: hwclock.sh rpcbind umountnfs.sh connman alsa-utils bluetooth brightness dundee elogind gpm haveged irqbalance ofono resolvconf saned slim tlp umountnfs-alternative.sh unattended-upgrades urandom avahi-daemon
cryptdisks: umountfs
cryptdisks-early: cryptdisks umountfs
udev: cryptdisks-early
umountroot: udev cryptdisks-early cryptdisks umountfs
halt: umountroot
reboot: umountroot

• This reply was modified 2 years, 11 months ago by dolphin_oracle.