Re: Write *once* storage (was Re: write only storage)
Steve McIntyre writes: > In article > you write: >>I would like to have some WORM memory for my backups. At the moment >>they're copied to an archive machine using a chrooted unprivileged user >>and then moved via a cron job so that that user cannot delete them >>(other than during a short window). > > Sorry to butt in, but I used to be a filesystem developer in a > previous life, working on archive storage for things like medical and > financial data. Pet peeve: > > WORM is Write *Once* , not Write *Only* > > "Write only" storage is easy and fast - just throw things at /dev/null > and they can never be altered (or read back). Ah, yes... http://www.ganssle.com/misc/wom1.jpg http://www.ganssle.com/misc/wom2.jpg
Re: Development permissions
"Paul M. Foster" writes: > Folks: > > This is probably a stupid question for many of you, but I've been > struggling with it since I started using Linux in 1996. > > Say you have a directory in which there are development files. A > number of users will be creating, deleting and modifying the files > there. This is the type of situation which might have been common on > old Unix university systems. (Users might be accessing files via > Samba, NFS, or locally.) > > Just to make this more concrete, assume the development tree is in > /var/www/html/website. > > Without setting directory and file permissions to 777, how do you > allow the above? What combinations of groups, directory > owners/permissions and file owners/permissions might make this > possible? > > Paul This situation is exactly what version control systems, especially like svn and git, were created to handle.
Re: Privacy and defamation of character on Debian public forums
Chuck Zmudzinski writes: > I was accused in public of wrongdoing on the > Debian bug tracking system which is hosted > on a public, Debian website in response to a > bug report I made. Bug number?
Re: Privacy and defamation of character on Debian public forums
The Wanderer writes: > On 2021-09-24 at 14:00, Joe Pfeiffer wrote: > >> Chuck Zmudzinski writes: >> >>> I was accused in public of wrongdoing on the Debian bug tracking >>> system which is hosted on a public, Debian website in response to >>> a bug report I made. >> >> Bug number? > > Based on what I've found in digging earlier, as well as the name > mentioned by Andy Smith in his reply, I think it's probably > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994899 - specifically. > the first reply (comment 10). > > The key to finding it was learning that you can search bugs.debian.org > by submitter E-mail address, and trying > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?submitter=brchuckz%40netscape.net > > based on the address used for posting here. Ah, thank you. I looked briefly for a way to search by submitter and didn't find that.
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot
Tim Woodall writes: > On Fri, 1 Oct 2021, Reiner Buehl wrote: > >> On 01.10.2021 16:11, Felix Miata wrote: >>> Mine (old) is like so: >>> # head -n3 /etc/mdadm.conf >>> HOMEHOST >>> DEVICE containers partitions >>> ARRAY /dev/md0 metadata=1.0 name=msi85:0tmp UUID=... >> I tried changing the HOMEHOST from to but that did >> not help. >> >> > > I've solved this but I don't recall how. Same here... FWIW my /etc/mdadm/mdadm.conf contains the line ARRAY /dev/md/1 metadata=1.2 UUID=67d3c233:96a0737c:5f88ed9b:936ea3ae name=snowball:1 and my array is indeed /dev/md1 (I've got *no* recollection why I didn't make it md0!). Is it possible you need to update your init ramdisk? Maybe your changes to your mdadm.conf aren't being seen?
Re: New mdadm RAID1 gets renamed from md3 to md127 after each reboot
Reiner Buehl writes: > On 02.10.2021 01:32, Joe Pfeiffer wrote: >> Is it possible you need to update your init ramdisk? Maybe your changes >> to your mdadm.conf aren't being seen? > > I do run update-initramfs -u after each change. Shouldn't that be > enough to to update the mdadm.conf in the init ramdisk? That's not it then... googling "md127" I found a *bunch* of possible causes.
Re: Don't try this at home kids
David Wright writes: > On Mon 29 Nov 2021 at 17:47:24 (-0500), Jude DaShiell wrote: >> sudo doesn't ask me for my password and I didn't even touch /etc/sudoers >> to do it. A file placed in /etc/sudoers.d with permissions of 0440 having >> any name you choose and contents like: >> user ALL=(ALL) NOPASSWD:ALL >> in it with user being the account name will do it. > > As /etc/sudoers already contains the line: > > %sudo ALL=(ALL:ALL) ALL > > one should be able to achieve the same effect by > adding the user to the sudo group. Near as I can tell from my experience, that doesn't work around the password requirement.
Re: Don't try this at home kids
Paul Johnson writes: > On Mon, Nov 29, 2021 at 11:57 PM Joe Pfeiffer wrote: > > David Wright writes: > > > On Mon 29 Nov 2021 at 17:47:24 (-0500), Jude DaShiell wrote: > >> sudo doesn't ask me for my password and I didn't even touch /etc/sudoers > >> to do it. A file placed in /etc/sudoers.d with permissions of 0440 having > >> any name you choose and contents like: > >> user ALL=(ALL) NOPASSWD:ALL > >> in it with user being the account name will do it. > > > > As /etc/sudoers already contains the line: > > > > %sudo ALL=(ALL:ALL) ALL > > > > one should be able to achieve the same effect by > > adding the user to the sudo group. > > Near as I can tell from my experience, that doesn't work around the > password requirement. > > Make sure you log out and log back in after you do 'adduser joe sudo' (or > whatever your username is). Group permissions are generally only effective as > they were at the time of that session's login. While you're right about need to log out and back in again after changes to /etc/sudoers, my /etc/sudoers files have had the %sudo ALL=(ALL:ALL) ALL line for *years*. Do you by any chance have your system set up so you can login without a password? That's a guess at something that might explain the difference.
Re: Usenet access.
I've been using eternal-september.org for well over a decade.
Re: Usenet access.
songbird writes: > pe...@easthope.ca wrote: >> Hi, >> >> Can anyone suggest an alternative to Google Groups for access to >> sci.electronics.repair. I'd be happy to pay a small subscription for >> access without tedious complications. > > i really liked individual.net and gladly paid them for > the service, it wasn't much, but then they stopped taking > overseas payments so i had to find another service. > > eternal-september works well for my use now, but it does > have hiccups here or there. so it's good to be patient > and go read a book or something here or there. What sort of hiccups? It's been years and years since I've noticed any sort of outage.
Re: Subject: Mr. Dan Ritter, why is it that you appear to be posting your POV on my posts? Are you a covert agent of the anti-FSF cabal, trying to subvert something "positive for FSF, but detrimenta
Dan Ritter writes: > Laura Smith wrote: >> On Wednesday, March 31st, 2021 at 18:28, Dan Ritter >> wrote: >> >> > That was the subject line of a message I just received from a >> > - I am not a covert agent of an anti-FSF cabal [...] >> >> Unless you were a very bad covert agent, you would say that, wouldn't you ;). > > Correct. > > However, one might decide to look at my blog, my history of (I > hope) helpful posts in debian-user, or indeed my career -- and > find quite a bit of counter-evidence. So deeply undercover you don't recognize it yourself.
Re: Firefox HTTPS-only mode breaks sites that return 404 for HTTPS connections
Kenneth Parker writes: > On Wed, Apr 14, 2021 at 10:16 PM Celejar wrote: > > On Wed, 14 Apr 2021 22:57:01 +0100 > piorunz wrote: > > > On 14/04/2021 17:19, Celejar wrote: > > > Hi, > > > > > > I recently switched to Firefox's native HTTPS-Only mode from the > > > HTTPS Everywhere extension, and I've just made the nasty discovery that > > > a bunch of links that had been returning 404, which I had been assuming > > > were dead links, were actually perfectly valid pages, which Firefox had > > > been "upgrading" to HTTPS, and then getting 404s from web servers that > > > weren't offering them via HTTPS (but still apparently accepting > > > connections via HTTPS). Clicking on the little lock icon and turning > > > HTTPS-Only mode off for the website doesn't seem to have any effect - > > > the only thing that lets me actually access these pages is turning off > > > HTTPS-Only mode via the general Settings page (or about:config). > > > > > > When the website doesn't offer HTTPS at all, then Firefox offers to > > > connect via HTTP, after a warning, and that's fine. But having pages > > > become completely inaccessible is intolerable - I now have to check > > > every 404 I get by turning off HTTPS-Only mode and seeing if the > > > page is actually there. Am I missing something here, or is HTTPS-Only > > > mode just badly broken? > > > > It certainly works fine for me. I use https only mode for many months > > now. Can you bring an example of a page which returns good page on http, > > but 404 error on https? > > http://www.daat.ac.il/ > https://www.daat.ac.il/ > > Celejar > > Indeed: A "Universe Site" that I host on Linode doesn't use https. So, > https://eyeblinkuniverse.com -- doesn't work: "Problem loading page - > Unable to connect" > http://eyeblinkuniverse.com-- Works properly on my version of Firefox: > Firefox 78.9.0esr (64-bit) on Debian Bullseye. > > Does this mean that I can look forward to this failure, when the new Firefox > comes out? Why can't people still make simple, text-based web > pages that can be read to a Blind Person? See, I don't do forms, data entry, > or anything on my opening screens. For that, it links to a > Blogspot, which uses some of Google's Bells and Whistles. > > In other words, is this the end of the "Simple Web"? https has nothing to do with "simple web" -- I term I don't remember having seen before, but I like. All the TLS negotiation is handled by the web server and browser, and it's easy enough to set up with letsencryupt that there's really no excuse for not doing it (says the guy who hasn't gotten it set up yet for a shotgun club web site he manages... really need to do that...).
Re: Is there any way to snoop on a USB port?
"Martin McCormick" writes: > I have a Windows box that has software on it which programs > two-way radios and it would be nice to know what the radio and > computer are saying to each other. > > After trying a Windows application that reportedly can > capture serial port traffic, I find that it doesn't appear to > work with usb ports and unix/linux is my preferred world anyway > so is there any sort of hardware that would pass through a USB > connection from the Windows box to the radio and let me siphon > off the traffic to a linux system and log it? > > The Windows app I tried to use has been around for a > decade or more and probably works well with RS-232 ports but the > traffic I need to grab comes from a usb device that creates > /dev/ttyACM0 if plugged in to a Linux box and comm2 on the > Windows system > > When I tried it today, it did nothing but complain that > it was not connected. It finally dawned on me that it probably > sees no serial ports at all as it is supposed to automatically > find and log all port I/O and this is a relatively new HP > Pavilion desktop computer which has no native RS-232 ports or > parallel ports on it and, even if it did, the connection from the > radio to the usb port is a usb plug with the usb hardware in it > and a cable that plugs in to the radio that would most likely > not be practical to tap. First, I assume the software isn't CHIRP, since that also runs under Linux (and is open source besides). When I faced a similar problem (reverse engineering the protocol used to talk to a hobby rocket altimeter), I put Windows on a virtualbox VM on my Linux machine, and then used wireshark to watch the protocol.
Re: "ls -d" OK, but not "ls"
Vincent Lefevre writes: > On a Debian GNU/Linux 10 (buster) machine: > > $ ls -ld /etc/systemd > drwxr-xr-x 3 root root 0 2021-04-19 09:40:41 /etc/systemd > $ ls /etc/systemd > ls: cannot open directory '/etc/systemd': No such file or directory > > Any explanation??? snowball:776$ ls -ld /etc/systemd drwxr-xr-x 5 root root 4096 Jun 17 11:20 /etc/systemd/ snowball:777$ ls /etc/systemd journald.conf logind.conf network/ networkd.conf pstore.conf resolved.conf sleep.conf system/ system.conf user/ user.conf snowball:778$ stat /etc/systemd File: /etc/systemd Size: 4096Blocks: 8 IO Block: 4096 directory Device: 901h/2305d Inode: 16517453Links: 5 Access: (0755/drwxr-xr-x) Uid: (0/root) Gid: (0/root) Access: 2021-06-23 11:04:12.898744989 -0600 Modify: 2021-06-17 11:20:15.302495478 -0600 Change: 2021-06-17 11:20:15.302495478 -0600 Birth: 2012-10-03 22:45:10.910122061 -0600 I'm with the people guessing you've got FS corruption.
z-wave?
I'm interested in trying out z-wave, and I'd like to start with a simple command line utility so I can experiment with a switch, and control it through cron. I'm aware of Home Assistant, which is likely to be the direction I go in the long term. I'd prefer not to try to set it up just to try out a switch! Any recommendations would be welcome.
movemail fails to get lock
After some upgrades, when I try to use VM to read my mail from within
emacs, movemail has been unable to get my mail. I've added some
switches to it to try to get a better picture of what it's doing;
currently I've got
'(vm-movemail-program-switches '("-vvv" "--debug-level=99" "--debug-line-info"))
When I try to fetch my mail with these switches, I get the messages
movemail: mboxrd.c:89: mboxrd_mailbox_init_stream:mu_mapfile_stream_create
(/home/joseph/INBOX.crash): No such file or directory
movemail: mboxrd.c:96: mboxrd_mailbox_init_stream:mu_file_stream_create
(/home/joseph/INBOX.crash): Success
movemail: mailbox `/home/joseph/INBOX.crash': cannot lock: Lock file check
failed
movemail exited with code 1
in the *output of movemail /var/mail/joseph /home/joseph/INBOX.crash* buffer.
Does anyone have any idea what could be wrong here? Much googling has
not given me any ideas...
Re: movemail fails to get lock
Dan Ritter writes: > > You should confirm that /home/joseph/INBOX.crash exists and has > the right ownership and permissions. After that, make sure that > it's not mounted via NFS or some other odd filesystem that has > locking issues. It creates the destination file if it doesn't exist. But yes, it turns out encfs has locking -- or, I suspect, race condition -- issues (see my own followup to my original post).
Re: movemail fails to get lock
Joe Pfeiffer writes:
> After some upgrades, when I try to use VM to read my mail from within
> emacs, movemail has been unable to get my mail. I've added some
> switches to it to try to get a better picture of what it's doing;
> currently I've got
> '(vm-movemail-program-switches '("-vvv" "--debug-level=99"
> "--debug-line-info"))
>
> When I try to fetch my mail with these switches, I get the messages
>
> movemail: mboxrd.c:89:
> mboxrd_mailbox_init_stream:mu_mapfile_stream_create
> (/home/joseph/INBOX.crash): No such file or directory
> movemail: mboxrd.c:96:
> mboxrd_mailbox_init_stream:mu_file_stream_create
> (/home/joseph/INBOX.crash): Success
> movemail: mailbox `/home/joseph/INBOX.crash': cannot lock: Lock file
> check failed
>
> movemail exited with code 1
>
> in the *output of movemail /var/mail/joseph /home/joseph/INBOX.crash* buffer.
>
> Does anyone have any idea what could be wrong here? Much googling has
> not given me any ideas...
Something I didn't realize was relevant when I posted: my home
directory is encrypted with encfs. I'm pretty sure at this point my
issue is a race condition in encs.
I rebuilt mailutils (which includes movemail) from source so I could run
it under gdb. It turns out the way they do file locking is to create a
file with a nearly-random name, create hard link to it with the
requested file name, and then do a stat on both to see if their
parameters match (I don't immediately see the advantage over just
creating the lock file with O_EXCL, but it's not my code). The two
stats are not matching. When I step through using gdb, it works.
So, I'll be filing a bug report against encfs when I get a chance. In
the meantime, using movemail to move the mail to a file on a
non-encrypted filesystem, and then mv'ing it to INBOX.crash, works.
random usernames in attempts to break in to my machine?
This isn't really debian-specific, but I don't know a better place to ask... recently, I've been having servers make a large number of attempts to access my mail host using what appear to be random strings as usernames -- it looks like this: Apr 4 03:04:30 snowball saslauthd[1179]: pam_unix(:auth): check pass; user unknown Apr 4 03:04:30 snowball saslauthd[1179]: pam_unix(:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= Apr 4 03:04:33 snowball saslauthd[1179]: : auth failure: [user=1b391vovbh@pfeifferfamily.net] [service=] [realm=] [mech=pam] [reason=PAM auth error] They all have the same form: .f...@pfeifferfamily.net I'm trying to understand the point; it's not like there's any chance any of those usernames will be valid. This isn't they usual attempts using usernames like root, admin, test1, scan... those I understand. So, anybody have any ideas what's up here?
Re: random usernames in attempts to break in to my machine?
Nicholas Geovanis writes: > On Mon, Apr 4, 2022 at 9:06 AM Joe Pfeiffer wrote: > > This isn't really debian-specific, but I don't know a better place to > ask... recently, I've been having servers make a large number of > attempts to access my mail host using what appear to be random strings > as usernames -- it looks like this: > > Apr 4 03:04:30 snowball saslauthd[1179]: pam_unix(:auth): check pass; user > unknown > Apr 4 03:04:30 snowball saslauthd[1179]: pam_unix(:auth): authentication > failure; logname= uid=0 euid=0 tty= ruser= rhost= > Apr 4 03:04:33 snowball saslauthd[1179]: : auth failure: > [user=1b391vovbh@pfeifferfamily.net] [service=] [realm=] [mech=pam] > [reason=PAM auth error] > > They all have the same form: .f...@pfeifferfamily.net > > I'm trying to understand the point; it's not like there's any chance any > of those usernames will be valid. This isn't they usual attempts using > usernames like root, admin, test1, scan... those I understand. > So, anybody have any ideas what's up here? > > That's "normal". Just looking for a response that doesn't return "user > unknown", then they've got a valid > username they can attempt password attacks on. That's the thing, and why it doesn't look like a dictionary attack. It isn't reasonable words or combinations of reasonable words. Using all the strings including things like "1b391vovbh" would be looking at many, many usernames than necessary, and ending all of them with ".fsf" pretty much guarantees they'll never get a hit. The idea that these are message IDs that got mistaken for usernames when something got scraped looks more likely, but they don't really look like message IDs either (the message IDs I see are much longer, and include the FQDN of the source host). > So here's the thing: What parts of the internet are you expecting logins > from, to your mail server? > If the answer is none, then you should be using kernel packet filtering to > prevent those incoming > messages from reaching your mail server's software. I could reasonably see an email come in from anywhere. I've now put fail2ban on the case... I'm still curious what's happening.
Re: random usernames in attempts to break in to my machine?
Nicholas Geovanis writes: > On Mon, Apr 4, 2022 at 12:27 PM Joe Pfeiffer wrote: > > It's software written by folks who sometimes know what they're doing. > There are only so many Kevin Mitnick's and Phyber Optik's in the world at > time > :-) For which we're all grateful! > > So here's the thing: What parts of the internet are you expecting logins > from, to your mail server? > > If the answer is none, then you should be using kernel packet filtering to > prevent those incoming > > messages from reaching your mail server's software. > > I could reasonably see an email come in from anywhere. > > That depends on who you pay for email (SMTP) service. > I see you're at a .edu, it's probably a different use-case. It's more "I'll > accept an > incoming connection from some where". At home and in the corporate world > that's different. > You will have specific upstream mail providers and separate mail front-end > (say POP) servers. I'm actually running my own mail server at home. The email address I use on usenet dates back to when my university did provide usenet access, which ended decades ago. But yes, just yesterday I had some perfectly legitimate email come in from Formosa. If this were on campus, I'd never see it, it would be IT's problem!
gnome2/keyrings/login.keyring.temp-nnnnnnnnn
I just noticed I have over a million files lurking in $HOME/.gnome2/keyrings/ with names of the form login.keyring.temp-n where n is a nine digit number. Literally over a million: ls ~/.gnome2/keyrings/ | wc 1695549 1695549 50118672 >From the names, I assume these are temporary files that are being created but not delete as they should be. Is there an accepted way to keep them from accumulating like this?
Re: gnome2/keyrings/login.keyring.temp-nnnnnnnnn
Charles Curley writes: > On Wed, 27 Jul 2022 17:50:42 -0600 > Joe Pfeiffer wrote: > >> I just noticed I have over a million files lurking in >> $HOME/.gnome2/keyrings/ with names of the form >> login.keyring.temp-n > >> Is there an accepted way to >> keep them from accumulating like this? > > You can probably cobble something together for logrotate. With the number of gnome users out there there's got to be something more standard than that.
Re: Can I install Debian operating systems for money?
Roger Price writes: > On Wed, 10 Aug 2022, Andy Smith wrote: >> I had a negative experience with LPI about 15 years ago where I >> signed up for one of their tests at a conference (FOSDEM) just out >> of interest and then in the weeks afterwards I was bombarded with >> marketing emails. > > My apologies for an off-topic comment, but this convinces me of the > value of having multiple e-mail addresses, with specific addresses for > people like LPI. > > Roger I run bogofilter, which catches almost all my spam, and have a .procmailrc file with black and white lists. A cron job every morning emails me the email addresses and subject lines of everything that wound up in the spam folder the day before so I can scan for false positives.
Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...
rhkra...@gmail.com writes: > On Tuesday, September 08, 2020 04:39:05 PM David Christensen wrote: >> Neither the string "2 MiB" nor the string "2 M" appear on page you have >> cited. > > That is correct, that's is what I have not found on that page. > >> Please provide a URL that advocates "start the first partition at 2 MIB" > > Maybe I misinterpreted what David Wright said in an email responding to one > of > my questions back in June. > > > Subject: Re: Advice on encrypted filesystem > Date: Friday, June 26, 2020, 09:25:49 AM > From: David Wright > To: debian-user@lists.debian.org > > ---< snip >--- > > If encrypting an entire disk, scramble the disk first, then partition. > If only encrypting a partition, partition the disk first. > *Alignments should be at least 2M (4096 x 512B sectors).* > Scramble any sensitive pre-existing contents: > > > I took that to mean that the first partition should start at 2 MiB. That doesn't follow -- 0 is 2 MiB-aligned (it's also aligned on whatever other size boundary you care to name, of course).
Re: Why start the first partition at 2 MIB, why not at any multiple of 4096 bytes ...
David Wright writes: > On Wed 09 Sep 2020 at 08:53:20 (-0600), Joe Pfeiffer wrote: >> rhkra...@gmail.com writes: >> > On Tuesday, September 08, 2020 04:39:05 PM David Christensen wrote: >> >> Neither the string "2 MiB" nor the string "2 M" appear on page you have >> >> cited. >> > >> > That is correct, that's is what I have not found on that page. >> > >> >> Please provide a URL that advocates "start the first partition at 2 MIB" >> > >> > Maybe I misinterpreted what David Wright said in an email >> > responding to one of >> > my questions back in June. >> > >> > >> > Subject: Re: Advice on encrypted filesystem >> > Date: Friday, June 26, 2020, 09:25:49 AM >> > From: David Wright >> > To: debian-user@lists.debian.org >> > >> > ---< snip >--- >> > >> > If encrypting an entire disk, scramble the disk first, then partition. >> > If only encrypting a partition, partition the disk first. >> > *Alignments should be at least 2M (4096 x 512B sectors).* >> > Scramble any sensitive pre-existing contents: >> > >> > >> > I took that to mean that the first partition should start at 2 MiB. >> >> That doesn't follow -- 0 is 2 MiB-aligned (it's also aligned on whatever >> other size boundary you care to name, of course). > > Care to explain how you align the first partition with the start of the disk? Ah, of course.
Re: How to run AppImage file
Fred writes: > On 11/25/20 12:30 PM, Reco wrote: >> Hi. >> >> On Wed, Nov 25, 2020 at 12:13:03PM -0700, Fred wrote: >>> fred@ragnok:~$ ./ClipGrab-3.9.2-x86_64.AppImage --help >>> bash: ./ClipGrab-3.9.2-x86_64.AppImage: cannot execute binary file: Exec >>> format error >> >> uname -m >> >> Reco >> > > fred@ragnok:~$ uname -m > i686 > fred@ragnok:~$ file ClipGrab-3.9.2-x86_64.AppImage > ClipGrab-3.9.2-x86_64.AppImage: ELF 64-bit LSB executable, x86-64, > version 1 (SYSV), dynamically linked, interpreter > /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, stripped Your uname says you are running a 32-bit system (686 is 32 bit). The output from the file command says it's a 64 bit executable. You can run a 32 bit executable on a 64 bit system, but you can't run a 64 bit executable on a 32 bit system.
Re: How to run AppImage file
Fred writes: > On 11/26/20 9:04 AM, Joe Pfeiffer wrote: >> Fred writes: >> >>> On 11/25/20 12:30 PM, Reco wrote: >>>>Hi. >>>> >>>> On Wed, Nov 25, 2020 at 12:13:03PM -0700, Fred wrote: >>>>> fred@ragnok:~$ ./ClipGrab-3.9.2-x86_64.AppImage --help >>>>> bash: ./ClipGrab-3.9.2-x86_64.AppImage: cannot execute binary file: Exec >>>>> format error >>>> >>>> uname -m >>>> >>>> Reco >>>> >>> >>> fred@ragnok:~$ uname -m >>> i686 >>> fred@ragnok:~$ file ClipGrab-3.9.2-x86_64.AppImage >>> ClipGrab-3.9.2-x86_64.AppImage: ELF 64-bit LSB executable, x86-64, >>> version 1 (SYSV), dynamically linked, interpreter >>> /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, stripped >> >> Your uname says you are running a 32-bit system (686 is 32 bit). The >> output from the file command says it's a 64 bit executable. You can run >> a 32 bit executable on a 64 bit system, but you can't run a 64 bit >> executable on a 32 bit system. >> > > Yes, I see that now. I thought I was running 64 bit. > > fred@ragnok:~$ lscpu > Architecture:i686 > CPU op-mode(s): 32-bit, 64-bit > This seems to say the cpu will run 64 bit software. I suspect (so I'm not sure) that that this means you've got a cpu that is physically capable of running in 64 bit mode, but you installed a in i686 operating system so only the 32 bit mode is actually available to you. It would be interesting to run uname as uname -a and see what it tells you. In my case I get Linux snowball 5.8.0-2-amd64 #1 SMP Debian 5.8.10-1 (2020-09-19) x86_64 GNU/Linux I'll hazard a guess that the places that say amd64 and x86_64 will say things related to i686 instead.
Re: Can't print to CUPS printer on my server
Gary Dale writes: > I'm running Debian/Bullseye on my workstation and Debian/Buster on my server. > I have an old HP CP-1215 color laserjet attached to the server by a USB > cable. I can print a CUPS test > page from the server but not from my workstation. When I try to print > anything from my workstation to that printer, I get "No suitable destination > host found by cups-browsed." > > I've deleted and re-added the printer on the server and rebooted my > workstation but I still get the same problem. > > The printer is using the foomatic drivers. CUPS reports that it is 2.3.3op1 > on my workstation and 2.2.10 on my server. Did you set the printer to be shared?
Re: Label printer Debian compatible
Tom Browder writes: > Has anyone had any success driving a mailing label printer for mailing labels > from either a LAN or direct connection with a Linux box? > > I can print sheets of mailing labels from my main printer, but I would love > to be able to print single labels from my adress db with a suitable specialty > printer and a suitable Linux driver. > > Thanks, and Happy New Year to all! I have had good success with a Dymo LabelWriter 450.
Re: Label printer Debian compatible
Tom Browder writes: > On Mon, Jan 4, 2021 at 12:57 PM Joe Pfeiffer wrote: >> I have had good success with a Dymo LabelWriter 450. > > USB connection? Yes.
Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Gene Heskett writes: > On Monday 27 May 2019 03:42:52 pm Jonas Smedegaard wrote: > >> Quoting Gene Heskett (2019-05-27 19:42:46) >> >> > On Monday 27 May 2019 03:46:00 am Curt wrote: >> > > On 2019-05-27, wrote: >> > > > If Network Manager is giving you grief, please go bark up /that/ >> > > > tree (I can't say much about N-M, because I banned it from my >> > > > boxes about ten years ago: I was at a customer's, in his LAN via >> > > > an Ethernet, when N-M suddenly saw a WLAN out there, out the >> > > > window and said "oh, let's go online over there" and obliterated >> > > > my network setting in favor of some seedy captive portal. That >> > > > was when I decided that N-M and me, we aren't made for each >> > > > other). >> > > >> > > This is a grave bug. I suppose we can assume from your description >> > > that the seedier the wifi portal, the more likely it is to >> > > spontaneously occur, despite any and all user configuration or >> > > intervention. >> > >> > This would appear to be more common, but as far as filing a bug >> > report, I logged in to do something in 2015, creating a new account >> > at the time, so now it refuses to let me in because the username >> > content rules have been changed and my username is now invalid. And >> > because it knows my email address, it won't let me create a new >> > account. So its the classic chicken v egg. I am locked out, so I >> > rant on this list. >> >> Account? You need no account to report bugs in Debian: >> https://www.debian.org/Bugs/Reporting >> > So that indicates I should have apt install reportbug, so I did. > Configured it on 1st run. then became me and ran it again. It never > heard of NetworkManager or Network-Manager. WTH? Debian package names are all lower case, and for better or worse the package management software is case-sensitive. snowball:532$ reportbug Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. If you don't know what package the bug is in, please contact debian-user@lists.debian.org for assistance. > network-manager *** Welcome to reportbug. Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Joe Pfeiffer ' as your from address. Getting status for network-manager... Checking for newer versions at madison... Your version (1.14.6-2) of network-manager appears to be out of date. The following newer release(s) are available in the Debian archive: experimental: 1.18.0-1 Please try to verify if the bug you are about to report is already addressed by these releases. Do you still want to file a report [y|N|q|?]? (at which point I entered a ^C since I didn't actually want to report a bug)
Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Curt writes: > On 2019-05-28, Joe Pfeiffer wrote: > >> experimental: 1.18.0-1 >> Please try to verify if the bug you are about to report is already >> addressed by these releases. Do you still want to file a report >> [y|N|q|?]? > > Think I might've entered 'q' here on the off chance it represented the word > quit. Maybe it means "'q'ueue the report for further reflection," though. > > ;-) No, it does mean 'quit' >> (at which point I entered a ^C since I didn't actually want to report a >> bug) >> > > 'N' also seems a reasonable alternative. 'y' is first in line, but 'N' > is upper case, and there must be a reason for that, so I'm thinking if > you just hit enter the default would be to do nothing (no). I don't remember... I don't think I've ever taken the default option! > On a more serious note, as exim is set up to deliver only local mail on > many machines (default installation), what happens when you cannot hand > your bug report over to a sendmail-like MTA? The exim4 installation provides a symbolic link snowball:558$ ls -l /usr/sbin/sendmail lrwxrwxrwx 1 root root 5 May 7 11:44 /usr/sbin/sendmail -> exim4*
Re: Replacing Pulseaudio with Alsa alone
humbert.olivie...@free.fr writes: >> If you don't use PulseAudio then only one application can use >> an ALSA device at the same time on your computer. > > This is untrue. ALSA provides dmix for mixing different audio flows. > > Olivier What's more, the default device uses dmix. And I find it a lot easier to do this mixing in raw audio than in PA. ALSA itself is capable enough that I don't see the point of an audio server like pulseaudio.
Re: useless languages
David Christensen writes: > On 7/12/19 4:03 AM, Pierre Frenkiel wrote: >> hi, >> when installing some packages (chromiun for example), I get a lot of >> useless languages (task-marathi-desktop task-nepali-desktop ...) >> Is there a way to get rid of them? >> >> best regards, > > I added the following line to my root .profile to prevent apt-get from > downloading and installing 'recommended' packages; > > alias apt-get='apt-get --no-install-recommends' There is currently a lengthy thread discussing why this is a bad idea with the subject "Re: Don't disable recoomends by default" Even if it were a good idea, the way to do it would be in the apt configuration, not by aliasing a command.
Re: Easiest way to do VGA to Text
deloptes writes: > Martin McCormick wrote: > >> I have 4 older PC's that generally work well running >> debian but Right now, 3 of them need varying degrees of attention >> to their BIOS setups as Dell motherboards and possibly other >> brands will occasionally modify their boot sequences for some >> reason and the only way one can boot from a CDROM is to get in to >> the BIOS setup and yank the boot order back to one where the CD >> drive is ahead of the hard drive or put an unbootable hard drive >> in. Six or eight months later, one will suddenly discover that >> the boot sequence has fallen back to the useless one where the >> floppy drive is first, followed by the hard drive followed by the >> CDROM. > > I have not heard so far of working OCR free under linux. I would buy > commercial software that can work as screen reader. You can pipe the images > from the linux PC to that software and hear the text. > > This is not only the OCR part, but also the reading and what I have seen > under Linux is all BS. There were very good projects 10-15y ago, but I have > not heard of a break through in any of them. For example ViaVoice a STT > program used to run on linux and was dropped when IBM and Phillips stopped > the project cause DARPA stopped the funding. Festival is good as TTS, but > is far away from commercial quality and so on. > > Making a good reader program is very complex and sophisticated thing and > there are many unsolved problems to deal with. This means you can not just > OCR the screen and dump it to the reader - you must preprocess it and often > go to semantics, which makes it pretty difficult. I used tesseract-ocr, mentioned previously, a couple of years ago with very good success. Also, the problem he's trying to solve is much simpler than the general OCR problem; he's got the actual correct pixels (rather than a scan), and maybe even have knowledge of what fonts are used. That makes a huge difference. > If you have time to waste, keep us posted of your progress. Last time I did > research on the topic was 10+y ago, when I wrote my thesis on dialogue > systems, so please, correct me if I am wrong and if there is a useful > software out there. Honestly I doubt it, cause people massively got dumber > in the past 10y, of course except the readers of this list :) > > best regards
Re: Easiest way to do VGA to Text
deloptes writes: > Joe Pfeiffer wrote: > >> I used tesseract-ocr, mentioned previously, a couple of years ago with >> very good success. Also, the problem he's trying to solve is much > > what means very good success? You had to proof read it at the end - time > spent. For me either something works or it doesn't none of them worked even > close to good Yes, I did have to proofread, and of course that took time. But if you're setting perfection as the only acceptable performance level, no OCR software will ever achieve it. Human eyes don't meet that standard. I wasn't keeping track of statistics (I wasn't conducting an experiment, I had a pamphlet that needed to be recreated and then edited), but the results were very very close to 100% I certainly spent a lot more time on reformatting and editing than I did proofreading. >> simpler than the general OCR problem; he's got the actual correct pixels >> (rather than a scan), and maybe even have knowledge of what fonts are >> used. That makes a huge difference. >> > > I doubt it - really! Let me know at the end. I am curious. > > regards
Re: How free is Debian
Shahryar Afifi writes: > With respect to all the contributors, developers, hobbyist and users, > who made GNU/Linux and Debian and all other distributions possible, > here lies a humble, ignorance and yet curious question. > > Are all binaries in the kernel code were writing from scratch? Are > there any binary blobs in the kernel that it was given to developers? > If amd64 license is not free, how is it that we have amd64 microcode in > the debian free? and if they are not the same, are we using the full > potential of our hardware? > > I apologize in advance for my ignorance. > Thank you. Typically the binary blobs are not free. If you get the source for a package that includes a blob (for instance, amd64-microcode) you'll see where the blob came from. In the case of that package, it's all just binary -- no source code for the microcode. The LICENCE.amd-ucode file includes the paragraph: You may not reverse engineer, decompile, or disassemble this Software or any portion thereof. So... not free at all.
Re: How free is Debian
John Hasler writes: > Joe Pfeiffer writes: >> The LICENCE.amd-ucode file >> includes the paragraph: > >>You may not reverse engineer, decompile, or disassemble this >>Software or any portion thereof. > > Quite unenforceable, of course. When discussing questions like "how free is this software", the question is all about what's legal -- not what's practical or enforceable.
Re: webmail and email from command line
loredana writes: > On Wed, Aug 14, 2019 at 3:00 PM wrote: > >> [...] > >> Note that what Google calls there "less secure applications" is just >> marketing mumbo-jumbo to nudge users off their non-browser clients. > > I know. But knowing it, and perhaps blaiming it, is not a solution. > >> Is changing mail provider an option for you? > > Yes, not an easy one, 'though. Image writing to all your contacts, > human and automatic ones, and convince them to write to a new email > address. For exactly that reason, years ago I bought my own domain (no, this isn't it -- mostly out of inertia, I still post to usenet using my old NMSU address) and run my own email server. That way I only had to do it one last time, and won't need to change again. > Moreover, is this going to be a solution? > > Which provider would you suggest? There are multiple providers out there that will work fine. I'm on netfirms.com; I'm webmaster for a shotgun club (mesillavalleyshotgunsports.com) that uses godaddy.com.
Re: Looking for suggestions of a "modern" desktop that runs Debian
Rogério Brito writes: > Dear people, > > As all my computers are quite old so far (including the ones that I > use to develop my packages and contribute to Debian), I would like to > get a "modern" desktop that is able to keep up with compiling stuff > and doing basic web surfing/web and typing texts in Emacs. > > Unfortunately, I have assembled computers way, way, way back then and > I don't know which processors should go with which motherboards and so > on. > > I would gladly appreciate some help choosing a computer (or computer > parts) that has a configuration along the following lines: > > * Is able to run Debian without any problems (I am willing to use > something that requires firmware from non-free, but not proprietary > drivers) > * Is a budget system (I'm short on money, unfortunately) > * Is silent, with as little fans as possible > * Has the ability to have 16GB or 32GB of memory (this is one of the > parts where I am willing to focus spending the money) > * Has a processor like a modern AMD Ryzen 5 or whatever is similar in > Intel-land (the 2nd part where I am willing to focus spending the > money) > * I don't care too much about video cards; As long as it can drive a > Full HD monitor, I am satisfied. Integrated card with the CPU is > perfectly ok with me (and, actually, preferred if that would make the > final cost of the computer lower). > > Any recommendations are more than welcome, > > Rogério Brito. Don't underestimate how quiet a fan can be -- I recently switched the fan/heatsink that came with my CPU for a "be quiet! BK010 Shadow Rock Slim" CPU cooler, and my machine is now nearly silent. My air conditioning vents are louder (but, I'll mention that since I live in the desert I have evaporative air conditioning, so my AC vents have to move quite a bit of air).
python3 modules -- apt vs pip?
I've been using apt (and friends) to maintain my systems, including python. Today I discovered the Debian version of the more-itertools module is on version 4.2.0 and is three years old. Meanwhile, the version documented on pypi.org is at version 8.2.0, and has at least one recipe whose arguments are in a different order from the Debian packaged version (grouper, whose order of arguments changed in version 6.0.0). This causes problems, as you might imagine, with other modules! So... do people generally use pip to maintain their python libraries, rather than apt? What's the recommended best practices here?
Re: python3 modules -- apt vs pip?
Alex Mestiashvili writes: > On 4/3/20 11:54 PM, Joe Pfeiffer wrote: >> I've been using apt (and friends) to maintain my systems, including >> python. Today I discovered the Debian version of the more-itertools >> module is on version 4.2.0 and is three years old. Meanwhile, the >> version documented on pypi.org is at version 8.2.0, and has at least one >> recipe whose arguments are in a different order from the Debian >> packaged version (grouper, whose order of arguments changed in version >> 6.0.0). This causes problems, as you might imagine, with other modules! >> >> So... do people generally use pip to maintain their python libraries, >> rather than apt? What's the recommended best practices here? >> > > I'd say the right course of actions would be to open a bug report that > there is a new upstream version available for python3-more-itertools. Good point -- just did it. > In general there are tons of modules which will never be packaged. So > depending on your needs you might need to maintain local modules. > > Python provides virtualenv, plus one can install most of the modules > locally with pip3 install --user which will install the modules > in ~/.local/lib and tools in ~/.local/bin, so don't forget to add this > to your PATH. > > I'd also say that one shouldn't use sudo pip3 since there are high > chances to mess up packages and system. > > Also should be careful with names of python packages since mistyping can > lead to installation of malicious software and with sudo it makes it > even more fun - google for "python malicious packages" Thanks for the warning!
Re: Debian man pages have annoying feature(sic)
Richard Owlett writes: > I the recent thread about returning a Debian installation to its > original state "popularity-contest" was mentioned. > > I wished to compare it to other tools mentioned in that thread. > Obvious stating point -- read the man page. > As I never installed its package I went to > https://manpages.debian.org/buster/popularity-contest/popularity-contest.8.en.html > . > > It did not explicitly answer my question. > However, under "SEE ALSO" it stated: >> Additional documentation is in /usr/share/doc/popularity-contest/. > > *PROBLEM* > As package is not installed, that directory does *NOT* exist. > > Where to find required documentation on the web? > > NOTE BENE > This post is about man pages as a class. Asking for a man page to include all of the documentation about a package isn't reasonable -- there are man pages like that (bash comes to mind), and it isn't a page, it's a book. A man page tries to be a succinct summary, so someone can look up details about running a program, or about a file format, in a hurry. If you want the full documentation on something you haven't installed, the man page is the wrong place to look. Googling 'debian popularity-contest' (instead of looking specifically for the man page) points me to https://salsa.debian.org/popularity-contest-team/popularity-contest#:~:text=The%20popularity%2Dcontest%20package%20sets,go%20on%20the%20first%20CD. which has a wealth of information.
Re: Issue with disabling Intel turbo boost via systemd
l0f...@tuta.io writes: > Hi, > > I have frequent warning/4 entries in my journalctl like this one (dozens/day): > kernel: mce: CPU[X]: Package temperature above threshold, cpu clock throttled Lucky you! My laptop just went ahead and went into thermal shutdown before the system noticed it was getting hot. This doesn't directly address your questions involving controlling turbo boost with the OS, but I was able to disable it in the UEFI.
Re: Fwd: lists.debian.org has received bounces from you
I assume the list is using mailman? I haven't found a setting to tell a subscriber their email is bouncing -- where is it?
Re: any gui for lm-sensors?
Long Wind writes: > i want a small app that show cpu temperature > which package shall i install? > Thanks! I've been using gkrellm to show quite a bit of system information (including temperatures) for years and years now.
Re: what calculator do you use?
kaye n writes: > Hello Friends, > Correct me if I'm wrong, but I don't see any calculator app in my Debian os. > What do you guys use? I'm having trouble with Galculator. > Thank you! M-x calc, from inside emacs.
Re: VPN suggestions?
Dennis Wicks writes: > Greetings; > > I want to set up a VPN for several computers in my house > that are all on a local network. > > And suggestions, hints, warnings? Your question as stated doesn't really explain why you want a VPN, and what you're planning to do with it. All you've mentioned is a private network; if that's all you're doing, there's no reason to have a virtual private network on top of it. FWIW, I've got a few machines at home that are networked, but get in remotely from my laptop using a VPN. It's hosted on one of my machines, and I'm just using openvpn.
Re: VPN suggestions?
Doug writes: > On 07/10/2018 10:59 PM, Joe Pfeiffer wrote: >> Dennis Wicks writes: >> >>> Greetings; >>> >>> I want to set up a VPN for several computers in my house >>> that are all on a local network. >>> >>> And suggestions, hints, warnings? >> Your question as stated doesn't really explain why you want a VPN, and >> what you're planning to do with it. All you've mentioned is a private >> network; if that's all you're doing, there's no reason to have a virtual >> private network on top of it. >> >> FWIW, I've got a few machines at home that are networked, but get in >> remotely from my laptop using a VPN. It's hosted on one of my machines, >> and I'm just using openvpn. >> >> > You seem to downplay a free VPN. What about TOR Browser? > Do you know anything about that? I would prefer not to have > the browsed address know who I am. I think (but I'm not sure) > that this is the function of TOR Browser. > Thanx for any info--doug I'm not downplaying a free VPN, I'm saying it's impossible to give advice without knowing what he wants to use one for. Another followup by a different Joe gives several reasons someone might want a VPN; it'll be done differently depending on what the goals are.
Re: Calculator with "tapes"
Ken Heard writes: > Does Debian have a calculator package which has the equivalent of the > tape produced by mechanical machines to show the entire calculation. > I find such "tapes" essential when for example I am adding a long list > of numbers and need to check after the addition is done to verify that > all the numbers were entered correctly. > > Regards, Ken The emacs calculator mode has it.
Re: As seen above: use of su vs sudo
Martin writes: > [...] >>> >>> is new to me, I never knew! And I think it is good approach. >>> Does one actually get pointed to this during install? >> >> ┌───┤ [?] Set up users and passwords >> ├┐ >> │ >>│ >> │ If you choose not to allow root to log in, then a user account will >> be │ >> │ created and given the power to become root using the 'sudo' command. >>│ >> │ >>│ >> │ Allow login as root? >>│ >> │ >>│ >> │ >>│ >> │ >>│ >> >> └─┘ >> >> >> Cheers, >> David. >> > > How cool is that :-) > Actually, I mostly use the graphical installer for manual install. I > just checked: This dialogue is 10 lines long. I usually stooped > reading after "You need do set a password for 'root'...". Though it seems like installing sudo and asking whether the "first user" should be in sudoers would be a better thing to do even if root can log in.
Re: Request for information
Gene Heskett writes: > On Thursday 16 August 2018 18:46:26 Brian wrote: > >> On Thu 16 Aug 2018 at 18:36:52 -0400, Gene Heskett wrote: >> >> [Almost everything snipped - for obvious reasons.] >> >> > Someone who is an actual member of the organization will probably >> > clarify it further, but I didn't want you to think you are being >> > ignored. >> >> Ignoring it would have been the better choice. I do not think you >> would have hurt his feelings by doing so. :) > > From the line of his msg, it was obvious he, and apparently no one else > at his place, had ever heard of the gpl-v2. The main point of that being > that they can't take it and put their own license on it. That battle has > been won in most of the courts on this wet rock already by the gpl being > found valid. But I would expect they will walk away without another word > when they find there is no warranty. People like that have a need for > somebody to sue if it doesn't Just Work, for their definition of works. > They are totally unwilling to accept any liability and will run like > turpentine doused cats to find somebody to blame. And thats one less > thing this camp has to worry about when they do back away. > > Basicly, Brian, IMNSHO, the gpl is saying TANSTAAFL, a concept their MBA > degree professors never explained. I'm afraid I have to chuckle > everytime I see it being enforced. An MBA degree means they've had > common sense beat out of them. And they willingly subjected themselves > to it. > > Take care now Brian. You're giving him too much credit. There's no evidence he even knew he was asking the question of a place that develops software; his query would have made just as much sense delivered to a tennis shoe manufacturer. It looked like a mass email hoping to get some leads for... something...
Re: question about memtest86+
Long Wind writes: > i install memtest86+ of stretch to test memory > i don't see any error msg, but after a few minutes, it shutdown my PC > > does that mean my memory is bad? > i read manual of memtest86+, can't find explaination I see other people have mentioned possible temperature issues, so I'll mention something that may or may not be relevant: a BIOS update pushed by Dell to my laptop enabled a CPU "turbo boost" mode that overclocked the CPU. Under any sort of load (and memtest86+ is certainly a load!) it would go into thermal shutdown in a couple of minutes, without having logged any sort of messages about heat. Disabling the mode in the BIOS gave me a stable system again.
Re: sometimes i go huh (grep result)
What's tripping you up is that some processing is being done by the shell before grep ever sees your pattern. Taking that into account, what grep is seeing is: songbird writes: > me@ant(25)$ env | grep -F "-g" grep -F -g > grep: invalid option -- 'g' > Usage: grep [OPTION]... PATTERN [FILE]... > Try 'grep --help' for more information. > me@ant(26)$ env | grep -F '-g' grep -F -g > grep: invalid option -- 'g' > Usage: grep [OPTION]... PATTERN [FILE]... > Try 'grep --help' for more information. > me@ant(27)$ env | grep -F 'CFL' > CFLAGS=-g grep -F CFL > me@ant(28)$ env | grep '\-g' > CFLAGS=-g grep \-g (I'll note that in this case you need the quotes or the shell would have stripped the \ . I'm guessing this one is doing what you want) > me@ant(29)$ env | grep '-g' grep -g > grep: invalid option -- 'g' > Usage: grep [OPTION]... PATTERN [FILE]... > Try 'grep --help' for more information. > me@ant(30)$ env | grep "-g" grep -g > grep: invalid option -- 'g' > Usage: grep [OPTION]... PATTERN [FILE]... > Try 'grep --help' for more information. > > > songbird
Re: File with weird permissions, impossible to delete
"Thomas Schmitt" writes: > > Something trampled the parent directory or its attached data structures. It appears to be the two inodes, not the parent directory, that got trampled.
Re: File with weird permissions, impossible to delete
Pétùr writes: > Le 11/09/2018 à 19:34, Martin a écrit : >> >> don't get crazy about FS corruption. There is no sign this is the >> case so far. Date and UID's are odd, but valid within ext4. Remove >> the immutable flag (chattr -i), you will be able to alter the files >> as you like. >> >> One hint will be, check if your system time is ok (both, date and >> hwclock!), may be there is a reason for this odd timestamps. > > Thanks for the reassuring words. > > I deleted the file > .cache/shotwell/thumbs/thumbs360/thumb0c5c.jpg > > without issue after chattr -i on this file. > > However, it didn't work for the index.html file which is considered as > a folder. > > > # ls -la .local/share/Trash/expunged/1257950219/ > myfolder/files/fullsize/index.html > total 16 > d-wS--S--T 2 1061270772 2605320832 4096 oct. 7 2412 . > drwx-- 3 petur petur 12288 avril 25 12:21 .. I realize you've almost certainly already thought of this, but I sort of have to point it out -- did you try using rmdir?
Re: [SOLVED] Re: Migrating Debian installation to a new motherboard
local10 writes: > Nov 1, 2018, 1:57 PM by mst...@debian.org: > >> On Thu, Nov 01, 2018 at 05:43:56PM +0100, local10 wrote: >> >> That means it's down. Note that you said enp3so above, that should >> be enp3s0 (zero); which did you put in interfaces? Also, there >> should be either "auto enp3s0" or "allow-hotplug enp3s0". Assuming >> that's all right, try manually running "ifup -v enp3s0". >> > > That was it. I did have "allow-hotplug" but it was still pointing to enp2s0, > not paying attention obviously. After changing "allow-hotplug enp3s0" the > network came back, everything works. > > So my experience indicates that it is quite possible to replace the > motherboard, stick the old hard disk in and the only change that's > required (in my case) was to change "/etc/network/interfaces" to > reflect the new interface name from enp2s0 to enp3s0 . No need to > change NIC MAC address. > > Thanks to everyone who responded. For what it's worth, I'm running network-manager and my ethernet port (enp4s0 in my case) isn't listed in /etc/network/interfaces at all. All that's in there is lo (the loopback interface).
Re: [SOLVED] Re: Migrating Debian installation to a new motherboard
David Wright writes: > On Thu 01 Nov 2018 at 20:03:05 (-0600), Joe Pfeiffer wrote: >> local10 writes: >> > Nov 1, 2018, 1:57 PM by mst...@debian.org: >> >> On Thu, Nov 01, 2018 at 05:43:56PM +0100, local10 wrote: >> >> >> >> That means it's down. Note that you said enp3so above, that should >> >> be enp3s0 (zero); which did you put in interfaces? Also, there >> >> should be either "auto enp3s0" or "allow-hotplug enp3s0". Assuming >> >> that's all right, try manually running "ifup -v enp3s0". >> > >> > That was it. I did have "allow-hotplug" but it was still pointing >> > to enp2s0, not paying attention obviously. After changing >> > "allow-hotplug enp3s0" the network came back, everything works. >> > >> > So my experience indicates that it is quite possible to replace the >> > motherboard, stick the old hard disk in and the only change that's >> > required (in my case) was to change "/etc/network/interfaces" to >> > reflect the new interface name from enp2s0 to enp3s0 . No need to >> > change NIC MAC address. >> > >> > Thanks to everyone who responded. >> >> For what it's worth, I'm running network-manager and my ethernet port >> (enp4s0 in my case) isn't listed in /etc/network/interfaces at all. All >> that's in there is lo (the loopback interface). > > FWIW if it were listed in /e/n/i, then nm would not manage it, would it. > > I expect you've got the interface name stored in nm's connection > profile instead. > > BTW in a network set up like my own, the place where the MAC would be > relevant is in the DHCP server (here, the router) because that is how > the IP number is assigned. An unassigned MAC will get given an IP > address 192.168.1.200+, and it will conect to the Internet, but other > machines on the LAN would not recognise it. (Although the router can > hand out IP numbers, it doesn't run a nameserver.) Though in my case my DHCP server is dnsmasq on another machine, which happily associates hostnames with the IP addresses so my machines can indeed find each other.
Re: Migrating Debian installation to a new motherboard
mick crane writes: > On 2018-11-01 17:57, Michael Stone wrote: >> On Thu, Nov 01, 2018 at 05:43:56PM +0100, local10 wrote: >>> Under enp3so I see only BROADCAST and MULTICAST, no UP or DOWN. Thanks >> >> That means it's down. Note that you said enp3so above, that should be >> enp3s0 (zero); which did you put in interfaces? Also, there should be >> either "auto enp3s0" or "allow-hotplug enp3s0". Assuming that's all >> right, try manually running "ifup -v enp3s0". > > I have to do a double check with "l" and "1" and "0" and "O", there > ought to be some way to avoid that. We live in a world in which our parents' typewriters had no "1" key, since it looked just like "l". We need to adapt to that world, and check.
Re: Why are some Debian bugs ignored for a long time?
Chuck Zmudzinski writes: > On 8/19/2022 6:59 PM, Andy Smith wrote: >> Hello, >> >> On Fri, Aug 19, 2022 at 05:06:38PM -0400, Chuck Zmudzinski wrote: >> > On 8/19/2022 4:44 PM, piorunz wrote: >> > > On 19/08/2022 18:57, Chuck Zmudzinski wrote: >> > > > I have noticed that some Debian bugs are ignored for a long >> > > > time, sometimes even when the person who submitted the bug >> > > > offered a patch. The Debian developers/maintainers sometimes >> > > > don't even reply and therefore never explain why the proposed >> > > > patch cannot be applied. Why is that the case with Debian >> > > > developers/maintainers? >> > > >> > > Hi Chuck, >> > > >> > > Maybe because developers/maintainers are not paid by the hour, but mere >> > > volunteers, don't you think? >> > >> >> > you are saying if a Debian user experiences a bug in Debian >> > software, Debian developers/maintainers do not have to fix it. >> >> That is a direct consequence of the meaning of the term "volunteer"; >> you may as well have said, "water is wet". Volunteers cannot be >> forced to do work, else they are not volunteers. > > The fact that Debian is created by volunteers and therefore the chances are > high that users might run into problems and not get help from the volunteers > who alone have the power to fix the problems is a fact that Debian users, and > all users of free software, need to keep in mind. This is equally true of commercial software: if the company feels it's a low-enough impact bug it won't get fixed. Commercial software has the additional risk that a product may simply be withdrawn from the market. With cloud-based commercial software, this means it could completely fail to function (one that's particularly noticeable is that as companies withdraw from the home automation space, consumers are discovering their smart home has suddenly become completely dumb).
Failure in fuse3 hook prevents initramfs update
I'm trying to do an update to my Debian 11 system, and keep getting the following failure: E: /usr/share/initramfs-tools/hooks/fuse failed with return 1. Trying to get a little more information, I ran update-initramfs -u -v -k all and after many lines of output, got: Adding binary /usr/lib/x86_64-linux-gnu/libe2p.so.2.3 Calling hook fuse Adding binary /sbin/mount.fuse3 E: /usr/share/initramfs-tools/hooks/fuse failed with return 1. I reported this as a bug against fuse3 last Saturday, but to date haven't heard anything from the maintainer. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022252 So... any ideas what's going on? And more importantly what can I do about it?
Re: Failure in fuse3 hook prevents initramfs update
didier gaumet writes: > Le 27/10/2022 à 00:52, Joe Pfeiffer a écrit : >> I'm trying to do an update to my Debian 11 system, and keep getting the >> following failure: >> E: /usr/share/initramfs-tools/hooks/fuse failed with return 1. >> Trying to get a little more information, I ran >> update-initramfs -u -v -k all >> and after many lines of output, got: >> Adding binary /usr/lib/x86_64-linux-gnu/libe2p.so.2.3 >> Calling hook fuse >> Adding binary /sbin/mount.fuse3 >> E: /usr/share/initramfs-tools/hooks/fuse failed with return 1. >> I reported this as a bug against fuse3 last Saturday, but to date >> haven't heard anything from the maintainer. >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022252 >> So... any ideas what's going on? And more importantly what can I >> do >> about it? >> > > Hello, > > I do not know well initramfs but initramfs-tools(7) manpage states: > [...] > KERNEL HOOKS > initramfs-tools includes hook scripts that are called by kernel > packages on installation and removal, so that an initramfs is > automatically created, updated or deleted as necessary. The hook > scripts do nothing if the environment variable INITRD is set to No. > This will be the case for kernel packages built with make > deb-pkg and with CONFIG_BLK_DEV_INITRD not set in the kernel > config, or built with make-kpkg and not using the --initrd option. > [...] That seems pretty specific to kernel packages. Though that man page points me to a command called lsinitramfs, which lets me see the contents of an initrd; the two I currently have out there both have /usr/sbin/mount.fuse3, but no /sbin at all. Tried editing the fuse hook to put the command in /usr/sbin, but no joy. > So I suppose that for whatever reason, fuse3 package has been > uninstalled but the fuse3 hook has not been removed. > > Depending on what you want (fuse3 installed or not), I would suggest > either cleanly purge or reinstall fuse3 package. I have to have it, as other packages depend on it. Tried reinstalling, still no joy. I've also tried both upgrading and downgroading fuse3 and initramfs-tools, still with no success. I can't see how the copy_exec for fuse is any different than the ones for other filesystems... thinking just in case, I also took a look at the next command in the script, which is manual_add_modules fuse in case that's what's actually failing; it doesn't look any different from any of the other manual_add_modules commands in the directory.
Re: Failure in fuse3 hook prevents initramfs update
Further follow-up: the problem appears to be that something else has already put mount.fuse3 in the initramfs. Replacing the failing line with copy_exec /sbin/mount.fuse3 /sbin || true allows me to create the initramfs, and the system boots, but I doubt it's an optimal solution.
Re: librecad
John Hasler writes: > Have you looked at Freecad and Solvespace? Note freecad is 3D, and his needs are apparently 2D. Though I will relate that my (brief) acquaintance with freecad led me to decide to just write Python scripts using python-occ to generate my models.
Re: librecad
John Hasler writes: > Gene writes: >> Solvespace, googling now, downloaded, will take a look. > > No need to download. It's in Debian. Note that he isn't likely to find anything remotely up to date in a repository, as he's still on wheezy.
Re: librecad
Gene Heskett writes: > On Friday 07 December 2018 19:54:56 John Hasler wrote: > >> Joe writes: >> > ...he's still on wheezy. >> >> I wrote: >> > That is easily fixed. >> >> Gene writes: >> > Not until an rtai patched kernel is available for the newer stuffs. >> >> Why would you run your CAD software on your machine controller? > > Why not John? With 6 machines here running 32 bit wheezy, one running > jessie on an R-PI-3B, and one running armbian stretch on a arm64, all > but the arm64 actually running a machine or the card firmware updater, > the only one w/o enough iron to run cad stuff is the pi. > > This machine, with its comfy chair, can run anything installed on the > other 6 machines via ssh -Y logins, and all are or can be mounted over > an sshfs facility for moving files around. Samba/cifs has turned into a > headache precisely because of all the windows crap that been > incorporated in the last years since Andrew T. got a helper. > > NFS, any version is at best a chain with broken links, whereas sshfs Just > Works. > > The machine that will carve the back panel is the best simulator ever for > code that will be run on it, simply by turning off all motor power, I > can run gcode on it, with the gui exported to this machine and its comfy > chair. This allows me to exercise the code, making sure it does exactly > what I had in mind, without carving up a hundred bucks worth of raw > material and putting more wear on a cutting tool. > > alu is the hardest stuff to cut in terms of tool wear there is, only > partially mitigated by a mister directed fog of sealing oil directed at > the back of the cutting tool so the alu is sealed away from the air, > majorly sealing the just cut surface. > > 99% of the heat you get from machining alu is not the cutting tool > friction, but the burning of the alu as it forms a new layer of alu > oxide in the thousandth of a second after the passing cutting edge of > the tool has exposed the alu to the airborn oxygen. That alox layer is > the 2nd hardest substance we have, 2nd to diamond, and asking the tool > to cut thru it with every passing cutting edge is pure hell even on > silicon carbide tooling. At $10 to $50 a tool. > > CAD/CAM may be able to do it faster, but they do not yield editable > gcode. This file I am working with, if exported as gcode from freecad, > would be 5 to 20 megabytes because the cad/cam programs have no clue > about the use of loops and conditionals. I am doing all this, with one > hole of unk size to cut yet, with 199 LOC. 50+ is comments, keeping > track of what I'm doing. And I can fix it with the same editor I used > to write it. geany. > > Biggest problem ATM is I'm one eyed, haven't let the left eye settle long > enough after the surgery Tuesday to be able to write a prescription and > get the correct lens in the frame, so its empty on that side. Since I'm > partial to hard coated Transitions lenses (special order, takes 7 to 9 > days in this neck of the woods), that will be 2 more weeks till I've got > two medium good eyes again. > > Other than that, whats not to like, John? First, because if you *really* need real time response, you shouldn't be running anything else that might be computationally intensive. I'm happy to believe the developers of RTAI are competent, even excellent, programmers. All the same, if I want real time levels of predictable response I don't want to put anything that might decide to be computationally intensive on the same machine. Second, because you're forcing yourself to look for workarounds due to the decision to use an obsolete (as in, not even in LTS since last May) distribution. As we've seen in this thread.
Re: Question on dpkg -l output.
Dan Ritter writes: > Eduardo M KALINOWSKI wrote: >> On 21 de dezembro de 2018 20:24, aprekates wrote: >> > In a new installed system with Debian 9.6 >> > >> > $ dpkg -l >> > >> > will list only packages with 'ii' state and a couple of 'rc'. >> > >> > But if i run: >> > >> > $ dpkg -l w* >> > >> > i will get a dozen also of 'un' packages. >> > >> > So i dont understand the logic of altering the output when >> > i use a pattern . I would expect to see only 'ii' packages starting >> > from the letter 'w' . >> > >> > Also i dont understand why in a new system dpkg would know >> > anything about uninstalled packages! >> >> dpkg -l w* >> will be expanded by the shell (if there is any file starting with w in the >> current directory). >> >> Have you tried >> dpkg -l 'w*' > > Let's see: > > dpkg -l w* > dpkg-query: no packages found matching webplot.txt It's important to keep in mind that if there are no files matching the wildcard expansion, the w* is passed as-is to the command. So if I create an empty directory, enter the directory, and snowball:525$ dpkg -l w* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++----= un w-bassman (no descripti snowball:525$ touch w snowball:526$ dpkg -l w* dpkg-query: no packages found matching w Yes, the OP does want in general to escape the w* as 'w*' (or other methods), but his output is completely reasonable, especially in a fresh install
systemd mdadm spamming my syslog
Since a recent update, my /var/log/syslog is getting spammed with huge numbers of messages of the form Mar 10 14:02:25 snowball systemd-udevd[18681]: Process '/sbin/mdadm --incremental --export /dev/sda3 --offroot /dev/disk/by-id/ata-ST3000DM001-1ER166_Z501MTQ3-part3 /dev/disk/by-partuuid/ad6f31ee-1866-400c-84f8-2c54da6abd2e /dev/disk/by-path/pci-:00:11.0-ata-1-part3 /dev/disk/by-id/wwn-0x5000c50086c86ae8-part3' failed with exit code 1. When I run the command by hand, I get root@snowball:~# /sbin/mdadm --incremental --export /dev/sda3 --offroot /dev/disk/by-id/ata-ST3000DM001-1ER166_Z501MTQ3-part3 /dev/disk/by-partuuid/ad6f31ee-1866-400c-84f8-2c54da6abd2e /dev/disk/by-path/pci-:00:11.0-ata-1-part3 /dev/disk/by-id/wwn-0x5000c50086c86ae8-part3 mdadm: cannot reopen /dev/sda3: Device or resource busy. Which at least gives me a small clue, but really not much of one. I'm not even really clear on whther this is a systemd or mdadm bug. So, some questions: 1) what is this command trying to do? I do understand a little about mdadm, and am running a RAID 1 array on this machine. But this is using an option (--offroot) that doesn't even appear in the man page, and I've got no idea what it's trying to accomplish. 2) how can I make it stop?
Re: systemd mdadm spamming my syslog
Bob Weber writes: > On 3/10/19 5:20 PM, Joe Pfeiffer wrote: > > Since a recent update, my /var/log/syslog is getting spammed with huge > numbers of messages of the form > > Mar 10 14:02:25 snowball systemd-udevd[18681]: Process '/sbin/mdadm > --incremental --export /dev/sda3 --offroot > /dev/disk/by-id/ata-ST3000DM001-1ER166_Z501MTQ3-part3 > /dev/disk/by-partuuid/ad6f31ee-1866-400c-84f8-2c54da6abd2e > /dev/disk/by-path/pci-:00:11.0-ata-1-part3 > /dev/disk/by-id/wwn-0x5000c50086c86ae8-part3' failed with exit code 1. > > When I run the command by hand, I get > > root@snowball:~# /sbin/mdadm --incremental --export /dev/sda3 --offroot > /dev/disk/by-id/ata-ST3000DM001-1ER166_Z501MTQ3-part3 > /dev/disk/by-partuuid/ad6f31ee-1866-400c-84f8-2c54da6abd2e > /dev/disk/by-path/pci-:00:11.0-ata-1-part3 > /dev/disk/by-id/wwn-0x5000c50086c86ae8-part3 > mdadm: cannot reopen /dev/sda3: Device or resource busy. > > Which at least gives me a small clue, but really not much of one. > > I'm not even really clear on whther this is a systemd or mdadm bug. > > So, some questions: > > 1) what is this command trying to do? I do understand a little about mdadm, > and am running a RAID 1 array on this machine. But this is using an > option (--offroot) that doesn't even appear in the man page, and I've > got no idea what it's trying to accomplish. > > 2) how can I make it stop? > > I also have these kind of messages for my 3 raid1 arrays. The messages > started after an update to testing done on 2/26/18 and have continued up to > 3/11/18 > (today). I looked at the terminal logs and I was running udev (240-6) > (installed 2/22) and mdadm (4.1-1) (installed 2/6). My udev is now at 241-1 > and mdadm is still > at 4.1-1. I'm seeing it at those versions, also. > Since the arrays are started correctly as shown by "cat /proc/mdstat" I > haven't paid much attention to these messages. They only occur at boot. The arrays are started correctly, but I'm getting bursts of these messages every five minutes so it's annoying. > My system is running testing and I do an upgrade just about every day. Same here.
Re: [OT] IP address collisions
Dan Purgert writes: > Nicholas Geovanis wrote: >> On Thu, Apr 18, 2019 at 7:57 AM Michael Stone wrote: >> >>> >>> No, the ULA is the IPv6 equivalent of RFC1918 space--you can use it >>> internally without central registration by choosing a subnet from >>> fd00::/8. The space is so much larger that it's much less likely that >>> two sites would pick the same prefix, but there are no guarantees. >>> >> But isn't it irrelevant whether they pick the same prefix or not? Routers >> that respect ULA and RFC1918 shouldn't route any traffic destined to them >> off the logical subnet. Right? > > No. RFC1918 / ULA are merely "unroutable on The Internet" (as in, they > cannot be directly accessed from the public internet). You can freely > route between them on "private" networks to your heart's content. > > For example, I have the RFC1918 subnets > > - 192.168.1.0/24, .2.0/24, .10.0/24, and .20.0/24 (LAN networks) > - 10.90.0.0/16 (VPN[1]) > > [1] way overkill, but lets me move around a bit in case a hotel is using > part of that range. (I only have the server hand out a /24 out of that > range, but the LAN's routing table uses the full /16). I use 192.168.13/24 for my home machines, externally available on my VPN as 10.13.13/24, on the theory that hotels will be sensitive to offending superstitious guests. Haven't had a problem yet!
Re: pkg-config does not see a package that i installed via apt-get (libmypaint)
The Wanderer writes: > $ apt-file search libmypaint.pc > libmypaint-dev: /usr/lib/x86_64-linux-gnu/pkgconfig/libmypaint.pc > > The .pc file for libmypaint is in libmypaint-dev, not in libmypaint-1.3-0. > > Try installing the -dev package. To elaborate on this a little -- In general, a package libfoo includes the library necessary to run a program compiled against that library, but not any files needed to actually compile that program. I find I almost never need to install a library like this directly, since any programs using it will have it as a dependency. The corresponding libfoo-dev package will include the needed header and other files (including libfoo.pc) needed to compile a program making use of the library. It will normally have libfoo as a dependency, so installing libfoo-dev will be all you need to do manually to be able to compile against and use libfoo.
Re: USB Examiner Package? Special USB Kernel Modules?
Kenneth Parker writes: > Here's an interesting one: A Windows friend handed me a USB Dongle, knowing > that I'm a Linux user. He says he got it 3rd hand, with > info that it might be "Very Dangerous". He would be interested, if I find > out something about it. (And, indeed, Google has many hits > on "USB Malware"). Keep in mind "very dangerous" can mean anything up to and including delivering a voltage that will fry some part of your motherboard. Make sure anything you plug it into is cheap enough you won't be upset to lose it.
Re: Advice on upgrading to SSD
Tony van der Hoff writes: > Hi, > I'm currently running Buster on a 5 year old GigaByte motherboard with > a 10-year old Raid-1 array on 2 500GB disks. Although it is running > fine, I'm becoming a bit concerned about the longevity of this > storage, so I'm planning to upgrade it to a 500GB or maybe 1TB SSD > from Crucial. > > My plan would be to install the SSD in the cage, and dd the contents > of the array onto the SSD. I would then change the BIOS to boot from > the SSD, making the RAID array redundant. > > Can someone please tell me whether this plan is feasible, and what > pitfalls I might encounter? I've found the best way to migrate to new disks, especially if I've already got a RAID array, is to put the new disk in, add it to the array, wait for the array to synchronize, remove the old disks from array. Now install grub on the new disk. If the new disk is larger than the old ones were, now resize the filesystem to match. This has worked well enough for me that I've got several one-disk RAID 1 arrays in anticipation of eventual upgrades.
Re: How to get rid of an entry in grub?
David Guntner writes: > Hugo Vanwoerkom grabbed a keyboard and wrote: >> David Guntner wrote: >>> Hmmm. I wonder if the MBR for the drive sill has a loader on it, >>> even though I removed all partitions and repartitioned it? Is there a >>> utility out there that can wipe the MBR of a drive without touching the >>> rest of the contents? >> >> There is http://bootinfoscript.sourceforge.net/ also. > > Ok, I got that, thanks. Ran it and it does look like there's a remnant > of the old 6.0 system that lived on that drive at one time. > > So, how to *wipe* the MBR for that drive without losing everything on > it? :-) Is there a way? > > 'Cause face it, if I get rid of the boot record on the drive, grub won't > see it anymore even without my disabling the probe script. :-) That is the cleanest way to do it! Looking around a bit, I found the following: https://bbs.archlinux.org/viewtopic.php?id=119702 The command to do it was $sudo dd if=/dev/zero of=/dev/sdx bs=446 count=1 Something the poster didn't emphasize strongly enough (IMHO) is that he's only wiping the first 446 bytes of the MBR -- this leaves the partition table alone. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1bli3iyczp@snowball.wb.pfeifferfamily.net
Re: How to get rid of an entry in grub?
David Guntner writes: > Joe Pfeiffer grabbed a keyboard and wrote: >> David Guntner writes: >> >>> Hugo Vanwoerkom grabbed a keyboard and wrote: >>>> David Guntner wrote: >>>>> Hmmm. I wonder if the MBR for the drive sill has a loader on it, >>>>> even though I removed all partitions and repartitioned it? Is there a >>>>> utility out there that can wipe the MBR of a drive without touching the >>>>> rest of the contents? >>>> >>>> There is http://bootinfoscript.sourceforge.net/ also. >>> >>> Ok, I got that, thanks. Ran it and it does look like there's a remnant >>> of the old 6.0 system that lived on that drive at one time. >>> >>> So, how to *wipe* the MBR for that drive without losing everything on >>> it? :-) Is there a way? >>> >>> 'Cause face it, if I get rid of the boot record on the drive, grub won't >>> see it anymore even without my disabling the probe script. :-) >> >> That is the cleanest way to do it! >> >> Looking around a bit, I found the following: >> >> https://bbs.archlinux.org/viewtopic.php?id=119702 >> >> >> The command to do it was >> >> $sudo dd if=/dev/zero of=/dev/sdx bs=446 count=1 >> >> Something the poster didn't emphasize strongly enough (IMHO) is that >> he's only wiping the first 446 bytes of the MBR -- this leaves the >> partition table alone. > > Seems like a good idea. I tried it, but it doesn't look like it worked: > >> # dd if=/dev/zero of=/dev/sdb bs=446 count=1 >> 1+0 records in >> 1+0 records out >> 446 bytes (446 B) copied, 0.000867678 s, 514 kB/s >> # update-grub >> Generating grub.cfg ... >> Found background image: /usr/share/images/desktop-base/desktop-grub.png >> Found linux image: /boot/vmlinuz-3.2.0-4-amd64 >> Found initrd image: /boot/initrd.img-3.2.0-4-amd64 >> Found memtest86+ image: /memtest86+.bin >> Found memtest86+ multiboot image: /memtest86+_multiboot.bin >> Found Debian GNU/Linux (6.0.7) on /dev/sdb1 >> done > > Grub still seems to think there's Linux on /dev/sdb1. That's > aggravating.. I guess I'll just try moving the stuff off of the one > and only partition on that drive to somewhere else temporarily, and then > delete the partition outright and recreate it. Maybe *THAT* will > finally do it! > > --Dave Ah, I missed that it was on a partition (and not the MBR). What *should* work is $sudo dd if=/dev/zero of=/dev/sdb1 bs=512 count=1 More information: http://www.novell.com/documentation/suse91/suselinux-adminguide/html/ch07.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1b4na6lhwy@snowball.wb.pfeifferfamily.net
Re: Thanks
"Thod Motte" writes: > Thanks to debian and Gnome 3 for making my desktop as buggy and unstable as > Windows 95 was in 1997 and less > customizable. > > I'm just going to revert to squeeze, that desktop actually worked. Another vote for xfce. I switched to it quite a while ago, and have been happy since. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1bob8djn8v@snowball.wb.pfeifferfamily.net
Re: strange bash behavior
David Guntner writes: > Darac Marjal grabbed a keyboard and wrote: >> On Mon, Sep 02, 2013 at 08:06:17AM -0700, David Guntner wrote: >>> Matej Kosik grabbed a keyboard and wrote: Hello, This morning I have been puzzled by bash. After typing the following command: for i in `seq 1 5`;do echo $i; test $i = 3 && break; done I see: 1 2 3 Which is OK. However, if the "break" command appears in a subshell: for i in `seq 1 5`;do echo $i; test $i = 3 && (break); done then the "break" command does not seem to have any effect 1 2 3 4 5 I am curious, is this something to be expected? >>> >>> What do you mean by "appears in a subshell?" >> >> From "man 1 bash": >> (list) list is executed in a subshell environment (see COMMAND EXECU‐ >>TION ENVIRONMENT below). Variable assignments and builtin com‐ >>mands that affect the shell's environment do not remain in >>effect after the command completes. The return status is the >>exit status of list. > > Ok, I'm still not following you. > > What, exactly, is it that you are doing at your keyboard, in order to > run it in this "subshell?" I'm assuming that in your main one you're > just typing the expression and hitting enter. So what are you doing > when the second example fails? Based on his post, he is putting 'break' in parentheses in the second case. This causes a new shell (the subshell) to be created, and the break command to be executed in that subshell. The subshell then exits. This is exactly the behavior I would expect: the break command isn't being executed by the same shell as your for-loop. The for-loop has no way of knowing that the subshell executed a break command (note that the break command is a shell built-in command -- it is interpreted and executed by the shell itself, no new process is created for it). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1br4d5mvmi@snowball.wb.pfeifferfamily.net
Re: strange bash behavior
Stephen Powell writes: > > Interesting. If "break" appears out of context, you should get > an error message something like: > >bash: break: only meaningful in a 'for', 'while', or 'until' loop > > You didn't get an error message, so part of bash thinks it is in context. > Yet it did not exit the loop. It seems to me that you should get one > behavior or the other. Either you should get an error message or it > should exit the loop. Good point -- it is odd that it isn't giving the error message. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1bmwntmvfc@snowball.wb.pfeifferfamily.net
Re: please read i am not getting satisfaction from mytablet l got it in april i dont download anything on it and it is slow take long to load so what should i do please tell me thank you.
phillip johnson writes: When your subject line is three lines long (on my display, anyway) maybe you should move it to the body of your post. When the body of your post is empty, you should *definitely* move something in there. Does your table run Debian Linux? If not, why are you asking here? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1bk3iw7ytq@snowball.wb.pfeifferfamily.net
Re: strange bash behavior
William Hopkins writes: > On 09/03/13 at 03:45pm, Joe Pfeiffer wrote: >> Stephen Powell writes: >> > >> > Interesting. If "break" appears out of context, you should get >> > an error message something like: >> > >> >bash: break: only meaningful in a 'for', 'while', or 'until' loop >> > >> > You didn't get an error message, so part of bash thinks it is in context. >> > Yet it did not exit the loop. It seems to me that you should get one >> > behavior or the other. Either you should get an error message or it >> > should exit the loop. >> >> Good point -- it is odd that it isn't giving the error message. > > The loop context is inherited by the subshell, so break thinks it is fine. It > is only that it is totally meaningless to break there, since that signal > cannot > be captured by parent shell environment. How is the context passed to the subshell? And what signal? > This seems to be expected behavior.. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1bd2oo7yqh@snowball.wb.pfeifferfamily.net
Re: Printer brand recommendations
Doug writes: > On 09/09/2013 06:16 PM, David Christensen wrote: >> On 09/09/13 14:42, ken wrote: >>> I've used Epson with success, but won't another one. The cost of the >>> cartridges is so high, it's like I'm buying the printer over and over >>> again every year. >> >> HP cartridges are also very expensive -- $100+. So: >> >> 1. I bought a black-and-white printer (1 cartridge), rather than color >> (4 cartridges). >> >> 2. I buy high capacity generic cartridges (~$30). >> >> >> HTH, >> >> David >> >> > > Another thread that's been running on one of the lists, where someone > in Switzerland was looking for a printer recommendation, pointed out > that HP printers are no longer the Sherman tanks they used to be, and > that they may no longer be built to last; also that HP does not support > any product after they stopped making it for five years. Not at all-- > you may not even find a manual. (OTOH, I can still get replacement toner > units for a 12 year old LaserJet 2200dn, even tho I can't get any info > from HP about it.) I also have an Epson all-in-one, a WP-4530. > It's quick, it prints, copies, faxes, scans, and has usb, Ethernet and > wireless interfaces. (And a phone connection for fax.) Does duplex, of > course. I do a fair amount of printing, and I don't need new cartridges > very often. It uses four cartridges, CMYK, so if you mostly print black, > that will be the only one you need to replace. The color is very good, > both from the net and scanned in. For B&W images, it's about on a par > with the LaserJet. And Epson has Linux drivers on their website for all > their printers and scanners, in both deb and rpm formats. Someone on the > other list found the WP-4530 for $189 on Amazon. > I have no financial or other interest in Epson. I was a strong HP fan for years, to the point that when a printer died I would only look at HP replacements. After a couple of short-lived HPs in a row, I broadened my horizons to take at least a token look at other brands -- and brought home an Epson Workforce 645 all-in-one which is behaving like HPs used to. It's reliable, the cartridges last a long time, the tray holds a *lot* of paper... just a good piece of equipment. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1bob812w6f@snowball.wb.pfeifferfamily.net
Re: endianness (was Re: sysadmin qualifications (Re: apt-get vs. aptitude))
Jonathan Dowland writes:
> On Thu, Oct 17, 2013 at 05:29:33PM +0200, berenger.mo...@neutralite.org wrote:
>> Speaking about endianness, it really is hard to manage:
>>
>> void myfunction( ... )
>> {
>> #ifdef BIG_ENDIAN
>> move_bytes_in_a_specific_order
>> #else
>> move_bytes_in_the_other_specific_order
>> #endif
>> }
>
> Bad way to manage endian in C. Better to have branching based on C
> itself (rather than preprocessor), otherwise you run the risk of never
> testing code outside the branch your dev machine(s) match. E.g. use
>
> char is_little_endian( … ) {
> int i = 1;
> int *p = &i;
> return 1 == *(char*)p;
> }
>
> Or similar. The test will likely be compiled out as a no-op anyway with
> decent compilers (GCC: yes; Sun Workshop: no.)
What's wrong with htonl and other similar functions/macroes?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1bfvrz6v1o@snowball.wb.pfeifferfamily.net
Re: sudo and UNIXes
Reco writes: > Tom H wrote: >> On Fri, Oct 25, 2013 at 9:16 PM, Reco wrote: >> >>> Considering that primary usage of sudo is to provide controlled >> >>> privilege escalation to uid=0, using unsupported (therefore - not >> >>> updated unless local sysadmins care about security) sudo on these OSes >> >>> is basically equivalent to giving everyone uid=0. >> >> >> >> Somewhat exaggerated :) >> > >> > No offense meant, but probably you're living in a some kind of IT >> > paradise ;) 'Nobody does no evil, nobody does any mistakes' kind of >> > paradise. >> >> Not updating/patching sudo isn't equivalent to giving everyone root >> access! It's a BIG leap! > > True, you need to add to the picture that curious user who just read on > Bugtraq or Full Disclosure about fresh vulnerability in sudo. Or that > disgruntled user who needs /etc/system changed right here and now. Or > that developer who needs to do this 'small change, nobody will notice' > on a production server. > And if you don't have such people there - good for you, as here we can > always find such person here. You also have to add to the picture such a vulnerability, and I haven't noticed any. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1b38nmdqfg@snowball.wb.pfeifferfamily.net
Re: sudo and UNIXes
Reco writes: > On Sun, Oct 27, 2013 at 09:28:51PM -0600, Joe Pfeiffer wrote: >> Reco writes: >> > True, you need to add to the picture that curious user who just read on >> > Bugtraq or Full Disclosure about fresh vulnerability in sudo. Or that >> > disgruntled user who needs /etc/system changed right here and now. Or >> > that developer who needs to do this 'small change, nobody will notice' >> > on a production server. >> > And if you don't have such people there - good for you, as here we can >> > always find such person here. >> >> You also have to add to the picture such a vulnerability, and I haven't >> noticed any. > > If we're speaking of public vulnerabilities: > > CVE-2010-0427. Does not permit users outside of those in the sudoers file (or with the root password) to escalate privileges. > CVE-2013-1775 (allows bypass sudoders modification to retain root > privileges). Again -- isn't "basically equivalent to giving everyone uid=0." Permits someone who *has* sudo access to avoid retyping a password. > I have no knowledge about private 0days. > > Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1bvc0hcqqo@snowball.wb.pfeifferfamily.net
Re: sudo and UNIXes
Reco writes: > On Mon, Oct 28, 2013 at 10:19:43AM -0600, Joe Pfeiffer wrote: >> Reco writes: >> >> You also have to add to the picture such a vulnerability, and I haven't >> >> noticed any. >> > >> > If we're speaking of public vulnerabilities: >> > >> > CVE-2010-0427. >> >> Does not permit users outside of those in the sudoers file (or with the >> root password) to escalate privileges. > > Lessens attack surface, but doesn't void the existence of vulnerability. > >> >> > CVE-2013-1775 (allows bypass sudoders modification to retain root >> > privileges). >> >> Again -- isn't "basically equivalent to giving everyone uid=0." Permits >> someone who *has* sudo access to avoid retyping a password. > > Not only that. Permits someone who already has sudo access to continue > having such access indefinitely, ignoring being excluded from sudoers > altogether. You made a specific claim, that sudo without patches is "basically equivalent to giving everyone uid=0". You have yet to say anything that even begins to substantiate that claim. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1b4n7vik0q@snowball.wb.pfeifferfamily.net
Re: sudo and UNIXes
Curt writes: > On 2013-11-02, Joe Pfeiffer wrote: >>>> >>>> Again -- isn't "basically equivalent to giving everyone uid=0." Permits >>>> someone who *has* sudo access to avoid retyping a password. >>> >>> Not only that. Permits someone who already has sudo access to continue >>> having such access indefinitely, ignoring being excluded from sudoers >>> altogether. >> >> You made a specific claim, that sudo without patches is "basically >> equivalent to giving everyone uid=0". You have yet to say anything that >> even begins to substantiate that claim. >> > > How about this bug: > > http://www.sudo.ws/sudo/alerts/sudo_debug.html > > Impact: Successful exploitation of the bug will allow a user to run arbitrary > commands as root. > > Exploitation of the bug does not require that the attacker be listed in the > sudoers file. As such, we strongly suggest that affected sites upgrade from > affected sudo versions as soon as possible. OK, there has been a bug that will cause the claimed behavior if the sysadmin updated his system between February and November 2011 but not since, and you've got a seriously malicious user. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1bvc09paki@snowball.wb.pfeifferfamily.net
Re: sudo and UNIXes
Reco writes: > Hi. > > On Sat, 2 Nov 2013 11:46:48 -0500 > "Cybe R. Wizard" wrote: >> > How about this bug: >> > >> > http://www.sudo.ws/sudo/alerts/sudo_debug.html >> > >> > Impact: Successful exploitation of the bug will allow a user to run >> > arbitrary commands as root. >> > >> > Exploitation of the bug does not require that the attacker be listed >> > in the sudoers file. As such, we strongly suggest that affected sites >> > upgrade from affected sudo versions as soon as possible. >> > >> How valid is that considering that Wheezy is using sudo >> version 1.8.5p2-1+nmu1 ? > > Perfectly valid, considering that this part of thread is about using > sudo in the UNIX environment, not Linux one. > > >> May I assume that there are still a lot of non-upgraded machines out there? > > Depends. For example, AIX 5, 6 and 7 all have sudo-1.6.7p5-3 (the only > version built officially by IBM). Unless you build sudo from the source > - no upgrades for you. > Solaris 11.1 has sudo-1.8.6.7 out of the box. Note that neither of these is subject to vulnerability in the bug report. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1br4axpaik@snowball.wb.pfeifferfamily.net
Re: MIT discovered issue with gcc
Robert Baron writes:
> Aren't many of the constructs used as examples in the paper are commonly used
> in c programming. For example it is very common to see a function that has a
> pointer as a parameter defined as:
>
> int func(void *ptr)
> {
> if(!ptr) return SOME_ERROR;
> /* rest of function*/
> return 1;
> }
>
> Isn't it interesting that their one example will potentially dereference the
> null pointer even before compiler optimizations (from the paper):
>
> struct tun_struct *tun=;
> struct sock *sk = tun->sk;
> if(*tun) return POLLERR;
>
> The check to see that tun is non-null should occur before use, as in - quite
> frankly it is useless to check after as tun cannot be the null pointer (the
> program hasn't crashed):
>
> struct tun_struct *tun=;
> if(*tun) return POLLERR;
> struct sock *sk = tun->sk;
The paper points out that the code contains a bug; the claim in the
paper is that it is a minor bug as written (it only gets past the
tun->sk dereference if page 0 has somehow been made readable), but
becomes a possible privilege escalation after the check has been
optimized away.
> I am under the impression that these problems are rather widely known among c
> programmers (perhaps not the kids fresh out of college). But this is why
> teams need to have experienced people.
>
> Furthermore, it is very common to find code that works before optimization,
> and fails at certain optimization levels. Recently, I was compiling a library
> that failed its own tests under the optimization level set in the makefile but
> passed its own test at a lower level of optimization.
Isn't that, and an analysis of when this can happen, the main point of
the paper?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1bvbzgtj13@snowball.wb.pfeifferfamily.net
Re: MIT discovered issue with gcc
Robert Baron writes: > Second question: > > Doesn't memcpy allow for overlapping memory, but strcpy does not? Isn't this > why memcpy is preferred over strcpy? According to the man page for memcpy, "The memory areas must not overlap. Use memmove(3) if the memory areas do overlap." strcpy will stop copying at the first null byte. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1br4a4tiy3@snowball.wb.pfeifferfamily.net
Re: umask has no man page?
Carl Fink writes: > When I wanted the options for umask, I typed 'man umask' and got the man > page for it as a C header diretive? (I'm not a C programmer, but it seemed > to be for C header files and came from section 2.) > > This is darn confusing for a new user. I have been around long enough > (slink) that I quickly realized it must be a Bash builtin and found that man > page, but how would a beginner know that? Surely a symbolic link could be > set up for umask as well as the others (bg, eval, fg, read, etc.)? > > Should I file this as a bug against Sid? I know there's no chance it will > make it into Wheezy. The underlying problem is that umask isn't a standalone command, it's a shell builtin. So if you look at the bash manpage you can find the (very terse) documention; of course, there's no hint anywhere that you should do that. Just as for (looking at some other builtins) ulimit, unalias, unset -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1b38a1dkq6@pfeifferfamily.net
Re: FW: Time for compassion and the Init GR
Jerry Stuckle writes: > > The tone is subtle, and not necessarily something a native English > speaker would see. But I see it there. Are you seriously claiming that a non-native speaker would be likelier to pick up on subtle, and quite possibly subconcious, cues than a native speaker? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1btx27prvn@pfeifferfamily.net
Re: Joey Hess is out?
Carl writes: > Really? I may have unthinkingly assumed everyone reading was a native > speaker is American English. In my dialect, "out" means "openly > homosexual" far more often than "quitting". The joke had nothing to do > with Mr. Hess and everything to do with mocking my own first reading > of the subject line. FWIW, I recognized your joke as a joke, and it got a chuckle from me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1bppcvprd0@pfeifferfamily.net
Re: [SOLVED] Is my processor 32-bit or 64-bit?
shawn wilson writes: > On Tue, Aug 28, 2012 at 1:34 AM, Bob Proulx wrote: >> Stephen Powell wrote: >>> By the way, there's something I don't understand. A 32-bit processor can >>> only access 4G of "real" (extended) memory, right? So why are there >>> motherboards available for 32-bit processors that support installing >>> more than 4G of RAM? What good is memory that the processor can't address? >> >> With PAE (physical address extensions) the processor *can* address >> more than 4G of ram. A single process is still limited to 32-bits >> which usually works out effectively to 3G of ram but the operating >> system can make use of more than this. It can be used for filesystem >> buffer cache and for multiple 3G programs. A machine with 6G of ram >> for example could run two 3G program at the same time and hold them >> both in memory without swapping. Or run one 3G program and still have >> 3G for the system to use in filesystem buffer cache. With PAE having >> more than 4G of memory is quite useful. >> >> Using PAE does have a small performance impact. It slows things down >> by 2%-3% in my use cases. But the increase in ram for buffers usually >> more than makes up for the differences. >> > > iirc, pae is only 48 bits too. "only" meaning 256 terabytes in this case... I'll be very surprised to ever see a 32 bit processor that can make effective use of that much memory. -- "Erwin, have you seen the cat?" -- Mrs. Shroedinger -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1bligzghqq@pfeifferfamily.net
Re: [SOLVED] Is my processor 32-bit or 64-bit?
Joe Pfeiffer writes: > shawn wilson writes: > >> On Tue, Aug 28, 2012 at 1:34 AM, Bob Proulx wrote: >>> Stephen Powell wrote: >>>> By the way, there's something I don't understand. A 32-bit processor can >>>> only access 4G of "real" (extended) memory, right? So why are there >>>> motherboards available for 32-bit processors that support installing >>>> more than 4G of RAM? What good is memory that the processor can't address? >>> >>> With PAE (physical address extensions) the processor *can* address >>> more than 4G of ram. A single process is still limited to 32-bits >>> which usually works out effectively to 3G of ram but the operating >>> system can make use of more than this. It can be used for filesystem >>> buffer cache and for multiple 3G programs. A machine with 6G of ram >>> for example could run two 3G program at the same time and hold them >>> both in memory without swapping. Or run one 3G program and still have >>> 3G for the system to use in filesystem buffer cache. With PAE having >>> more than 4G of memory is quite useful. >>> >>> Using PAE does have a small performance impact. It slows things down >>> by 2%-3% in my use cases. But the increase in ram for buffers usually >>> more than makes up for the differences. >>> >> >> iirc, pae is only 48 bits too. > > "only" meaning 256 terabytes in this case... I'll be very surprised to > ever see a 32 bit processor that can make effective use of that much > memory. Sorry to follow up my own post -- I hit "send" too fast. My response was given the assumption that PAE gave a 48 bit physical address space; of course it doesn't. It gives 36 bits -- 64 GB, which isn't nearly so outlandish. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1b7gsjndia@pfeifferfamily.net
Re: IA64 or AMD64?
Stan Hoeppner writes: > On 9/20/2012 4:40 PM, Richard Hector wrote: >> On 21/09/12 09:04, Stan Hoeppner wrote: >> >>> You are either: >>> >>> 1. Horribly lazy >>> 2. Incompetent >>> >> >> Or having a bad day, or been dropped in the deep end by the employer, or >> any one of a number of things we don't know about. >> >> Suggesting google or debian.org or whatever is fine, but this is way >> over the top, IMHO. >> >> I'll assume _you're_ having a bad day :-) > > Not at all. > > That box is a couple of generations old, however, it cost over $10K USD > when it was acquired, sans edu etc discounts. It was top of the line. > Anyone working for an organization with that kind of budget, acquiring > this caliber of hardware, should already know the basics of most, if not > all, processor architectures commonly used with Linux, both CISC/RISC, > and VLIW (EPIC). And if not, should be able to find it one click deep > on the website without needing to ask here. > > IA-64 has been with us for just over a decade. x86-64/AMD64/EM64T have > been with us for almost exactly a decade. This should be common > knowledge by now, and especially so for someone working with such machines. Why do you assume he's doing it for work? If he said something about being an experienced sysadmin, I missed it. This could easily be a box he bought as the n'th owner or from ebay or something. Everybody has to start somewhere, and none of us knew what we were doing when we started (sort of by definition). That he's at that stage now doesn't mean he's an idiot. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1bhaqsywua@pfeifferfamily.net
Re: IA64 or AMD64?
T Elcor writes: > - Original Message - > > From: Stan Hoeppner > >> This list, as with most others, is not to be used as a >> primary technical support resource. People should be making at least a >> cursory effort to search for information before asking here. > > Please see the Code of Conduct ( > http://www.debian.org/MailingLists/#codeofconduct ) instead of inventing your > own rules. I am reading this in a Usenet newsgroup (linux.debian.user). A mailing list code of conduct is at best of peripheral relevance. If there is a portal to a mailing some place, it really doesn't make any difference to where I'm reading (and posting). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1bmx0iwz4g@pfeifferfamily.net
Re: ls file exist, but can't access.
lina writes: > $ ls -lrt > total 8 > -rw-r--r-- 1 lina lina 367 Sep 27 00:15 RET > drwx-- 2 lina lina 4096 Sep 27 00:16 auto-save-list > > $ ls -lrt RET > ls: cannot access RET: No such file or directory > > $ cat RET > cat: RET: No such file or directory > > $ rm RET > rm: cannot remove `RET': No such file or directory > > :~/.emacs.d$ ls > auto-save-list RET > > > Is it weird? or this file stored in some weird place. If what you're posting is an exact capture, it looks like RET has some sort of character before the R -- possibly a space? Try ls " RET" and see what happens. > There is another thing, which is isolated from this one, > > FilesystemSize Used Avail Use% Mounted on > /dev/sda1 95G 54G 37G 60% / > /dev/sda3 1.2T 681G 482G 59% /data > tmpfs 12G 1012K 12G 1% /dev/shm > apricot2-local:/vol/ds_vol > 4.6T 1.9T 2.8T 40% /home > /dev/gpfs15.5T 919G 4.6T 17% /gpfs_data > > /dev/gpfs1 is twice faster than /home/lina checked via dd in read and > write speed, but `ls` so slow. > > I don't know how to check, indeed I have thousands of files generated > there. so I could obviously feel the time retard. I assume /ddv/gpfs1 is some sort of local device, while aricot2-local:/vol/ds_vol is being accessed through NFS? If that's the case, the latter is coming across a network which would make it substantially slower (especially depending on what the network looks like). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1bipb0y8xb@pfeifferfamily.net
Dymo 450 ejects label on login
The issue is as above: new machine running xfce4 desktop, with two printers attached. One of them is an Epson Workforce 645, the other is a Dymo 450 label printer. The Epson is, of course, the default printer on the system. When I log in to the desktop, the Dymo ejects one blank label. Any thoughts? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1bzk3nwb5w@new-snowball.wb.pfeifferfamily.net
profile function: not found. Was: Dymo 450 ejects label on login
Darac Marjal writes:
> On Mon, Oct 15, 2012 at 05:47:07PM -0600, Joe Pfeiffer wrote:
>> The issue is as above: new machine running xfce4 desktop, with two
>> printers attached. One of them is an Epson Workforce 645, the other is
>> a Dymo 450 label printer. The Epson is, of course, the default printer
>> on the system.
>
> Is the Dymo attached as a standard printer (that is, you have an entry
> in CUPS and you can print to it from any normal application) or (being a
> label printer), does it just show up as a character device that prints
> out any data sent to that device?
>
> If the former, check the CUPS logs to see if there's a stuck job,
> perhaps. If the latter, something is presumably sending a form-feed to
> the device. Does this happen if you create a new user and log-in to
> their desktop? Does it happen if you log in at a VT and run startx?
Thanks -- that seemed like the direction the problem had to be in -- but
as you will see in a moment, it wasn't related to the printer or CUPS at
all.
>>
>> When I log in to the desktop, the Dymo ejects one blank label.
>>
>> Any thoughts?
I've tracked the problem down now, and found another, stranger (but
easily resolved!) problem.
My .profile defines several bash functions. When logging in from gdm3,
my .xession-errors file was getting a "function: not found" on every one
of them, and executing all of the commands in the function. The
particular symptom I was seeing before came because I had a function
defined as
function label { sed -e 's/^[ \t]*//' | enscript -r -d dymo450 -B -f
Times-Roman12 -M Address ; }
(if your news reader wraps that, it was all one line in the file and in
my post)
Using the alternate syntax
label () { sed -e 's/^[ \t]*//' | enscript -r -d dymo450 -B -f Times-Roman12 -M
Address ; }
works just fine -- no error, and no blank label.
I've got *no* idea why the function keyword wasn't being recognized. I
put an
echo $SHELL
in the file, and it wrote /bin/bash in the .xsession-errors file, so it
isn't the obvious problem...
--
"Erwin, have you seen the cat?" -- Mrs. Shroedinger
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1blif5gkfm.fsf...@new-snowball.wb.pfeifferfamily.net
