You are not logged in.
- Topics: Active | Unanswered
#1651 Hardware & System Configuration » CUPS accounting [Solved] » 2020-02-17 19:55:25
- Altoid
- Replies: 15
Hello:
I'm looking for a way to quickly be able to know how many pages my Samsung M2020W has printed at any point in time.
Although not really at any point, just when I see that the print density is falling.
The original cartdrige lasted for few pages (I know that is the usual thing) and I have had it refilled and would like to keep a tab on how well it works.
There's the log at http://localhost:631/admin/log/page_log which is read from /var/log/cups/page_log but I don't see how to weed out the data without some time consuming editing.
Thanks in advance,
A.
#1652 Re: Devuan » Debian has fallen. What now? » 2020-01-19 15:31:25
Hello:
Hello:
The writing has been on the wall for a long time now.
And it's well past the time to heed the warning.
Just to reinforce what I wrote previously / further illustrate just what is going on Linux/MS wise, I invite members to check out this YouTube chat from almost two years ago by a chap called Lunduke.
https://www.youtube.com/watch?v=TVHcdgrqbHE
... and this other one.
https://www.youtube.com/watch?v=9MflUrykPaY
I think they are worth watching.
Of course, YMMV.
Cheers (?),
A.
#1653 Re: Installation » installing nvidia drivers on ascii 2.1 » 2020-01-09 11:43:36
Hello:
... edited my sources.list file ...
For those (more knowledgeable than I) able to opine, it would probably be important to see the contents/output of cat /etc/apt/sources.list.
Edit:
The output of cat /var/log/Xorg.0.log would be useful also.
Cheers,
A.
#1654 Re: Installation » "Warning": Failed to connect to lvmetad » 2019-12-31 10:45:47
Hello:
Any suggestions ?
I have not come across this and from what I have read, if the system boots without issues, it is just a harmless warning.
Maybe someone else knows better.
Cheers,
A.
#1655 Re: Devuan » Debian has fallen. What now? » 2019-12-29 13:52:44
Hello:
It could have been worse.
Indeed ...
But I fear that (eventually) it will get worse.
To me it's just a question of time.
Why?
Because not enough people are paying attention to what is going on.
I've clocked roughly 20+ years of MS software use, ~5 years as a regular -> advanced user, the rest as first -> second tier support and on-site hardware service when needed, all at the different places where I made a living and from home when out of a job.
So my background is not that of a coder/developer or packager but someone who started late but who has seen all this first hand as a privileged/advanced user, like many others here.
IMO, there is a striking parallel between systemd in Linux and the registry in Windows OSs.
Systemd in Linux brings back memories of my difficult transition from W3.11 to W95, with the end of the familiar and usually well documented *.ini files I understood (and could tweak when things went foul) to the obscure workings of *the registry*, which took me a few years to get a minimal hold of, basically through unending trial and error grief.
After a few years (W95 to XPSP3) I understood what it was all about: a developer sanctioned virus running inside the OS, constantly changing and going deeper and deeper into the OS with every iteration and as a result, progressively putting an end to the possibility of knowing/controlling what was going on inside your box/the OS as it became more and more obscure.
When systemd appeared in Debian (I was already running Ubuntu) and saw what and how it did it, I realised that systemd was nothing more than a registry class virus which was infecting the Linux ecosystem at the behest of the developers involved and the complicity or indifference of most of the others.
So I moved from Ubuntu to PCLinuxOS and then on to Devuan.
Paranoid?
No. Just strongly convinced that there are people both inside and outside IT that actually want this systemd takeover to happen and are quite willing to pay shitloads of money to push that agenda, Poettering being a prime suspect but surely not the only recipient.
I don't see this MS cozying up to / barging into Linux and areas of influence (GitHub acquisition, WSLinux (!), etc.) in various ways as a coincidence: these things do not happen just because or on a senior manager's whim.
What I do see (YMMV) is systemd being a sort of a putsch to generate a convergence Windows with or into Linux, which is not good for Linux and will be its undoing.
But there's really nothing new here: it's just the well known MSbrace at work.
It's been going on for more than 30 years.
And no, I don't have an answer to this problem.
But I do think that it would probably be a good thing that the awesome manpower behind all the Linux projects scattered out there team up to find common ground instead of everyone of them wanting to do their own thing while mindlessly waving the flag of choice, a flag which they are set to lose if they do not react fast enough.
The writing has been on the wall for a long time now.
And it's well past the time to heed the warning.
Of course, nothing but my $0.02 and as always, YMMV.
To all Dev1 members/guests: Have a Happy New Year 2020.
Cheers,
A.
#1656 Re: Installation » Keyboard configuration issue » 2019-12-28 14:37:23
Hello:
... does many things well ...
Like all the other mainsream desktops out there these days.
... fails in some areas ...
I'd say far too many, but as I suffer its shortcomings I cannot be objective enough.
... has the multi monitor display working well ...
Just like Mate or Cinnamon or Gnome (which I have not tried).
But that is probably because X is working reasonably well and when it does not, some *.orx/layouts get it fixed quick enough.
For example: I've been waiting years for Xfce to be able to line up/organise/keep the desktop icons where I bloody put them.
It's the one thing I miss from XP.
I have been seriously thinking about getting rid of Xfce once and for all but never get around to doing so, probably for fear of breaking my Devuan ASCI .
Cheers,
A.
#1657 Re: Installation » Keyboard configuration issue » 2019-12-28 13:27:28
Hello:
... put the command in your autostart file ...
Done.
Applications -> Settings -> Session and Startup -> Application Autostart -> Add
Name: keyboardmap (or whatever)
Description: sets kb layout (or whatever)
setxkbmap latam
Thank you very much for your help.
That this issue is still a problem after so many years is not a good omen, not for Xfce and certainly not for the Linux ecosystem.
Cheers,
A.
#1658 Re: Installation » Keyboard configuration issue » 2019-12-28 12:52:49
Hello:
... tried setxbmap as a workaround ...
Yes, it works.
I can set the layout with setxkbmap.
But it does not survive a reboot.
Where can I set it to make it permanent?
Thanks for your input
Cheers,
A.
#1659 Re: Installation » Keyboard configuration issue » 2019-12-28 11:21:07
Hello:
rant
This is the type of thing that gets on Linux users' nerves: a straightforward configuration glitch in something that (at this stage in Linux time) should not be happening.
After all, how long has Xfce been a desktop option?
/rant
The issue I am having with the keyboard settings in Xfce seems to be related to a well known bug from back in 2010.
Nine (9) years ago and counting ....
https://askubuntu.com/questions/66096/h … er-reboots
Like someone else posted on that thread:
... u understand now why linux share in desktops is ~1%
A simple stupid language switcher applet is bugged for years...
I'll see if I can make one of the workarounds (evidently considered a permanent fix by the developers) work for me.
Cheers,
A.
#1660 Re: Installation » Keyboard configuration issue » 2019-12-27 21:13:46
Hello:
... configure the keyboard with setxbmap ?
Hmm ...
What I want is to be able to configure it via the desktop settings like it should be done.
ie: Applications -> Settings -> Keyboard -> Layout
rant
This is the type of thing that gets on Linux users' nerves: a straightforward configuration glitch in something that (at this stage in Linux time) should not be happening.
After all, how long has Xfce been a desktop option?
/rant
So if it wants to use the system defaults (the previous setting), I guess I'll have to try setting the system defaults to what I want.
Any other ideas?
Thanks for your input.
Cheers,
A.
#1661 Re: Installation » Keyboard configuration issue » 2019-12-27 13:00:36
Hello:
... Xfce?
Yes.
... desktop is overriding your configuration.
Thought that could be the case, so tried Applications -> Settings -> Keyboard -> Layout, un-checked Use system defaults and chose Generic 105-key PC (intl.) with Spanish (Latin American) layout and Spanish (Latin American, no dead keys) variant.
But no, no cigar.
Thanks for your input.
A.
#1662 Installation » Keyboard configuration issue » 2019-12-26 16:40:39
- Altoid
- Replies: 12
Hello:
My Sun 7 keyboard went south, the second one this year.
Nice but not so trusty after all.
So I pulled an old Lenovo backup from the closet: KU-0225 / P/N: 41A5312
It's a standard 105-key Latin American layout keyboard.
But something is not right and I cannot figure out what it is.
I have set the layout with dpkg-reconfigure keyboard-configuration and my /etc/default/keyboard file reads accordingly.
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL="pc105"
XKBLAYOUT="latam"
XKBVARIANT="nodeadkeys"
XKBOPTIONS="lv3:ralt_switch,compose:menu,terminate:ctrl_alt_bksp"
BACKSPACE="guess"It seems that the keyboard configuration setting is being ignored and the keyboard is working as if it were a Spanish layout (like if it had a ç / Ç at the end of the third row).
eg: The key that should give me an accent ` or two types of brackets { or } and [ or ] gives me a ç or a Ç.
Rather annoying.
Any idea what might be happening here?
Thanks in advance,
A.
#1663 News & Announcements » Merry Christmas » 2019-12-24 21:43:46
- Altoid
- Replies: 9
Hello:
A hearty season's geeting (Merry Christmas / other celebrations, etc.) to all here at Dev1, especially to those who keep the Devuan project moving forward.
Cheers,
A.
#1664 Re: Other Issues » [SOLVED] Apt-get show one package per line? » 2019-12-17 02:29:19
Hello:
... always been overwhelmed by the blob of text too.
+1
Yes, it is a pity.
Keeps me from being more confident in using apt-get.
Maybe maintainers could find a way to make the output (more) readable by default, like dnf?
A.
#1665 Re: Installation » Refracta Snapshot VM mount points question. » 2019-12-07 15:15:10
Hello:
I use optical media, too.
... directories under /media that are needed get created automatically. I think udev takes care of that.
OK
... directories you made under /media, take a look at the rsync excludes ...
... comment out one or more of the following lines, as needed.
Like this:#- /cdrom/* #- /media/*Do the same with /usr/lib/refractainstaller/installer_exclude.list
Great ... =-)
To add a line to fstab in the installer, you just need to add this line:
echo -e "/dev/sr0\t/media/cdrom\tauto\tnoauto,owner,ro,users\t0\t0" >> /target/etc/fstab... right after the section that adds the swap line to fstab.
... starts around line 1430 in /usr/bin/refractainstaller and around line 1570 in /usr/bin/refractainstaller-yad.The last two lines in the following code block are what you need to add.
# add entry for swap to fstab if needed if [[ $use_existing_swap = "yes" ]] ; then if [[ $use_uuid = yes ]]; then swap_part="$(/sbin/blkid -s UUID $swap_dev | awk '{ print $2 }' | sed 's/\"//g')" else swap_part="$swap_dev" fi echo -e $"\n Adding swap entry to fstab...\n" echo -e "$swap_part\tswap\tswap\tdefaults\t0\t0" >> /target/etc/fstab else echo -e "/swapfile\tswap\tswap\tdefaults\t0\t0" >> /target/etc/fstab fi # Make entry for cdrom in fstab echo -e "/dev/sr0\t/media/cdrom\tauto\tnoauto,owner,ro,users\t0\t0" >> /target/etc/fstab
Thank you so much for taking the time to explain/write all this up.
I'll try it and see how it goes.
Just in case, this time I'll have a snapshot of the VM available.
Fortunately, I have backintime installled so I did not have to redo all my previous work after I went edit-happy with /ect/fstab.
With respect to seeing the devices in Xfe, I remembered gnome-disk-utility and decided to try it out on the VM and things got easier.
Not too heavy on the file system but certainly dangerous to use without the proper attention.
eg: that readily available delete selected partition button ...
Have a good week-end.
Cheers,
A.
#1666 Re: Installation » Refracta Snapshot VM mount points question. » 2019-12-06 22:55:03
Hello:
fstab is excluded in the rsync copy ...
... gets created when you install with refractainstaller.
OK.
Sort of makes sense.
The live *.iso would take a large portion of boot time figuring out why it was not being able to mount what fastab said was there and may not be.
But what I am referring to is the fact that the mount points I generated in /media ie: /media/cdrom and /media/usb on the VM are not copied over to the *.iso.
ie: there are no files in /media on the live *.iso.
They survive a reboot of the VM and belong to root.
And I can mount a cdrom or usb to them as root.
If they do not get carried over to the live *.iso, I have to generate them everytime I boot the *.iso file.
Make sense?
There's no entry for cdrom.
I haven't needed that in years.
I still have a score or so of DVDs and CDs with data and need to access them every so often.
... you'd need to add a line of code to refractasnapshot.
That's rather over my head.
Would it be possible to (eventually) add an option for that to refractasnapshot.conf?
--- ot ---
One of the very good things that TinyCore linux has is an application called mount tool.
A very simple desktop panel with a button for each of the drives in the system you are booting into.
Click on a drive and it gets mounted, click again, it gets unmounted.
I wonder if it was specially written for TCore or it has its origins in some linux application.
--- ot ---
Thanks in advance,
A.
#1667 Re: Installation » Refracta Snapshot VM mount points question. » 2019-12-06 21:31:57
Hello:
... is that a typo in this post, or a typo in "fstab"?
It's a typo in fstab.
But the cdrom gets automatically mounted in the VM nevertheless.
[Changing it now]
Done.
groucho@devuan:~$ cat /etc/fstab
rootfs / rootfs rw 0 0
/dev/sr0 /media/cdrom auto noauto,owner,ro,users 0 0
groucho@devuan:~$ Thanks for the heads up.
Best,
A.
#1668 Installation » Refracta Snapshot VM mount points question. » 2019-12-06 16:41:42
- Altoid
- Replies: 6
Hello:
I have set up two mount points in my Devuan ascii 2.0.0 VM ...
/media/cdrom and /media/usb, the first one listed in /etc/fstab:
groucho@devuan:~$ cat /etc/fstab
rootfs / rootfs rw 0 0
dev/sr0 /media/cdrom auto noauto,owner,ro,users 0 0
groucho@devuan:~$ ... but when I boot the *.iso image made with RS, the mount points are not there.
Is this how it is supposed to be or am I missing something with respect to Refracta Snapshot's configuration or VMs in general?
Thanks in advance,
A.
#1669 Re: Installation » Xfe + isomount question » 2019-12-05 21:25:55
Hello:
... you could make a hookscript that will run when you boot the live iso and inject the necessary lines into /etc/fstab.
No idea how to do that.
... won't work for a rescue usb that you're booting on some other box.
It's always the same box but as this *.iso (fortunately) is not used with any frequency, the disk configuration is likely to change so to all effects and purposes it is/could well be another box.
... better off doing it manually in a root terminal.
... fdisk, df and blkid to get information ...
... figure out which one you want to mount.
Yes, you might be right.
I have found that doing things in the terminal is helping me become, slowly albeit steadily, a bit more proficient with in use of the command line.
But it is hard to shed years point&click muscle memory and the apparent convenience it brought along.
I'll see what I can rig up.
Thanks for your input.
Best,
A.
#1670 Re: Installation » Xfe + isomount question » 2019-12-04 22:54:55
Hello:
... can set up the boot menu before or when you make the snapshot.
OK
... set up the extra partitions in fstab with 'noauto,user' options, then you can mount/unmount by right-clicking on the mountpoint.
Yes, that should do it.
Excuse my ignorance, but how do I set that up in a live *.iso when I don't know what drives will be in the box when I use it?
If xfe won't do what you want ...
Xfe is really lean, quick and most importantly, desktop agnostic.
I'd rather stay with Xfe.
Thanks for your input, much appreciated.
Best,
A.
#1671 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.
#1672 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.
#1673 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.
#1674 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.
#1675 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.
Board footer
