Re: cannot rename with mv - SOLVED

On Tue, January 17, 2017 12:39 am, Reco wrote: > EBUSY The rename fails because oldpath or newpath is a directory > that is in use by some process (perhaps as current working directory, or as > root directory, or because it was open for reading) or is in use by the > system (for example as m

Re: cannot rename with mv

On Mon, January 16, 2017 11:08 pm, David Christensen wrote: > It's probably a permissions issue. > > Please paste this command into a terminal (as any user) and then paste > the command and output into a reply: > > $ ls -d -l / /backup > > Have you set ACL's, SELinux, or any such thing? I am runni

Re: cannot rename with mv

Hi. On Mon, 16 Jan 2017 22:17:24 -0600 rlhar...@oplink.net wrote: > I wish to rename the directory "/backup" to "/backup.new". > > / is on a 452G partition with 54% in use. > / is owned by root. > /backup is owned by normal user "rh". > > The command "$ mv /backup/ /newbackup/" fails wi

Re: cannot rename with mv

On 01/16/17 20:17, rlhar...@oplink.net wrote: I wish to rename the directory "/backup" to "/backup.new". / is on a 452G partition with 54% in use. / is owned by root. /backup is owned by normal user "rh". The command "$ mv /backup/ /newbackup/" fails with " cannot move ... Permission denied".

Re: cannot rename with mv

On Mon, January 16, 2017 11:23 pm, Doug wrote: > if /backup is actually in the root directory, you need to su (or sudo) to > root and then rename the file: > > [name@pcname]$ su > Password: > [root@pcname name]# mv /backup /newbackup I did this; it did not work. > if this doesn't work, try ./ i

Re: cannot rename with mv

On 01/16/2017 11:17 PM, rlhar...@oplink.net wrote: I wish to rename the directory "/backup" to "/backup.new". / is on a 452G partition with 54% in use. / is owned by root. /backup is owned by normal user "rh". The command "$ mv /backup/ /newbackup/" fails with " cannot move ... Permission den

Re: cannot rename with mv

On Mon, January 16, 2017 11:06 pm, rlhar...@oplink.net wrote: > On Mon, January 16, 2017 10:45 pm, Armando Cerna wrote: > >> You might want to be sure to double verify that fact nothing is >> accessing that directory using lsof ex: lsof | grep backup > > > lsof indicates no opened files for the dir

Re: cannot rename with mv

On Mon, January 16, 2017 10:45 pm, Armando Cerna wrote: > You might want to be sure to double verify that fact nothing is > accessing that directory using lsof ex: lsof | grep backup lsof indicates no opened files for the directory

Re: cannot rename with mv

You might want to be sure to double verify that fact nothing is accessing that directory using lsof ex: lsof | grep backup -- Armando Cerna arma...@cerna.ca On Mon, Jan 16, 2017, at 08:17 PM, rlhar...@oplink.net wrote: > I wish to rename the directory "/backup" to "/backup.new". > > / is

cannot rename with mv

I wish to rename the directory "/backup" to "/backup.new". / is on a 452G partition with 54% in use. / is owned by root. /backup is owned by normal user "rh". The command "$ mv /backup/ /newbackup/" fails with " cannot move ... Permission denied". The command "# mv /backup/ /newbackup/" fails wi

Re: Dell BIOS

Mirko Parthey composed on 2017-01-17 00:36 (UTC+0100): The BIOS clock could still have the correct time despite a dead battery because the Linux system gets the time from an NTP server and writes it to the BIOS clock on shutdown. The clock then runs on ATX standby power and will only lose its m

Re: intel_pstate vs acpi-cpufreq freq scale

Dear Luis, Many thanks for your input and guidance here. 'Have you tried to see if this happens with debian's official kernel?' Doh! Of course. Yes I have now, and intel_pstate is active - yay. Complete newb with any kind of kernel config/tweaking/rebuilding - need to do some reading-up. Thanks

Re: Dell BIOS

On Mon, Jan 16, 2017 at 11:52:48AM -0600, Martin McCormick wrote: > change the boot sequence order from floppy-C:-CDROM to > CDROM-floppy-C: or CDROM-C:-floppy which prevents the hard drive > from grabbing the boot sequence each time. There may be a function key that brings up a BIOS boot menu. Fo

Re: Dell BIOS

Joe writes: > The ones I saw were Japanese components in Japanese television > cameras, many of them broadcast. This was from the mid-90s onwards. Japanese companies can get suckered by something that looks like a good deal just like anyone else. > And silent leakage of copper-dissolving electrol

Your best source for personal finance knowledge

Your best source for personal finance knowledge

Re: Dell BIOS

On Mon, 16 Jan 2017 15:54:05 -0600 John Hasler wrote: > Joe writes: > > The electrolyte used in these [Japanese] capacitors > > They were Chinese knockoffs of a Japanese design. However there was a > proprietary trick that the Chinese missed and so they made and sold a > vast number of caps t

Re: Dell BIOS

Joe writes: > The electrolyte used in these [Japanese] capacitors They were Chinese knockoffs of a Japanese design. However there was a proprietary trick that the Chinese missed and so they made and sold a vast number of caps that turned out to be defective. Electrolytics usually have burst memb

Re: Dell BIOS

On Mon, 16 Jan 2017 14:53:33 -0600 "Martin McCormick" wrote: > Felix Miata writes: > > What models are they? If of approximately 2002 to 2007 vintage, > > they could be victims of the bad capacitor plague: > > > > http://en.wikipedia.org/wiki/Capacitor_plague > > Interesting article. T

Re: How to find out the current display manager?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jan 16, 2017 at 11:42:17AM -0500, kamaraju kusumanchi wrote: > On Mon, Jan 16, 2017 at 4:42 AM, wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > On Sun, Jan 15, 2017 at 09:47:40PM -0500, kamaraju kusumanchi wrote: > >> How

Re: Low Level Format of 1.4 Mb Floppy Isn't Happening Solved.

On Sun, 15 Jan 2017 23:04:14 + Brian wrote: > On Sun 15 Jan 2017 at 15:36:08 -0600, Martin McCormick wrote: > > [A trip down Memory Lane snipped] > > For those who may want to use Plop boot manager, it is far quicker and > more reliable to do so from GRUB on the hard disc. The Plop website h

Re: Dell BIOS

Felix Miata writes: > What models are they? If of approximately 2002 to 2007 vintage, they could > be victims of the bad capacitor plague: > > http://en.wikipedia.org/wiki/Capacitor_plague Interesting article. These dells could possibly be in that group as one has a BIOS date of August 1

Re: Re: grub has stopped booting windows 10

Thank you very much! As you suggested, typing c at the grub menu, followed by set root=(hdo,msdos1) chainloader +1 boot took me to Windows. I suspect that there must be a way to fix my grub menu, but don't know how. The output from os-prober: /dev/sda1:Windows Recov

Re: How to seperate grub devices?

Le 16/01/2017 à 11:56, Darac Marjal a écrit : BIOS will typically only boot from one drive (That said, both BIOS and UEFI often have mechanisms to choose what that drive is). UEFI behaves differently. It mostly uses boot entries pointing at EFI executable files which can be located on any dri

Re: Dell BIOS

Martin McCormick composed on 2017-01-16 11:52 (UTC-0600): I don't know how common this is but the BIOS' of two Dell Optiplexes plus the BIOS of another Dell Dimension don't stay set the way one would like them to. As a computer user who happens to What models are they? If of approximat

Dell BIOS ( was Low Level Format of 1.4 Mb Floppy Isn't Happening)

Brian writes: > Does the machine you are booting use GRUB as the boot manager? Surprisingly enough, yes. I wasn't sure but it certainly does. Here's an explanation with a hope for a workable solution. I don't know how common this is but the BIOS' of two Dell Optiplexes plus the

Re: How to find out the current display manager?

On Mon, Jan 16, 2017 at 11:42:17AM -0500, kamaraju kusumanchi wrote: > Background on why I need this: > I am developing a script[1] that gathers relevant system information > depending on what issue a debian-user is facing. That's pretty ambitious. Good luck. > Thanks. It looks like all I need i

Re: How to find out the current display manager?

On Mon, Jan 16, 2017 at 6:00 AM, Felipe Salvador wrote: > 0;115;0cIn-Reply-To: > > > On Sun, Jan 15, 2017 at 09:47:40PM -0500, kamaraju kusumanchi wrote: >> How can I find out the display manager currently running on a machine >> from the command line? > > I'm not sure, did you mean something li

Re: How to find out the current display manager?

On Mon, Jan 16, 2017 at 4:42 AM, wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Sun, Jan 15, 2017 at 09:47:40PM -0500, kamaraju kusumanchi wrote: >> How can I find out the display manager currently running on a machine >> from the command line? > > Hm. How do you know there aren'

Re: intel_pstate vs acpi-cpufreq freq scale

On lunes, 16 de enero de 2017 1:13:09 (CET) Julian Brooks wrote: > Hi all, Hi Julian, > Fresh install of Sid, with > liquorix 4.9-3 (2017-01-07) x86_64 kernel (for RT audio work). > Have also installed linrunner's TLP. Have you tried to see if this happens with debian's official kernel? > My un

Re: How to seperate grub devices?

Hi, Hans wrote: > > If you do not understand me yet, take this discussion as closed. Mark Fletcher wrote: > No, mate, we UNDERSTOOD you from the beginning, the problem is that > _what you are describing is impossible_. To be exacting: It obviously goes beyond the imagination of the people here,

Re: How to seperate grub devices?

On Mon, Jan 16, 2017 at 12:45:51PM +0100, Hans wrote: > It makes a grub.cfg on PHYSICAL harddrive ONE and > a second one on PHYSICAL harddrive TWO and both are identical. > > But as both shall be different, according to the drive I want start from. > > If you do not understand me yet, take this d

Re: How to seperate grub devices?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jan 16, 2017 at 12:45:51PM +0100, Hans wrote: > It makes a grub.cfg on PHYSICAL harddrive ONE and > a second one on PHYSICAL harddrive TWO and both are identical. > > But as both shall be different, according to the drive I want start from. >

Re: How to seperate grub devices?

It makes a grub.cfg on PHYSICAL harddrive ONE and a second one on PHYSICAL harddrive TWO and both are identical. But as both shall be different, according to the drive I want start from. If you do not understand me yet, take this discussion as closed. Thanks for the try. Best Hans

Re: How to find out the current display manager?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jan 16, 2017 at 12:00:22PM +0100, Felipe Salvador wrote: > 0;115;0cIn-Reply-To: > > > On Sun, Jan 15, 2017 at 09:47:40PM -0500, kamaraju kusumanchi wrote: > > How can I find out the display manager currently running on a machine > > from the

Re: How to seperate grub devices?

On Mon, Jan 16, 2017 at 12:05:06PM +0100, Hans wrote: You all did not understand me, maybe caused by my bad English. update-grub is ALWAYS changing grub.cfg on BOTH drives, same from which system it is started. And I want it only have changed on THAT DRIVE, I am running AT THE MOMENT. The other

Re: grub has stopped booting windows 10

On Sun, Jan 15, 2017 at 06:36:36PM -0600, Charles E. Blair wrote: I have been running version 7.11 of Debian for several years on a desktop with a dual boot of windows and linux via grub. I upgraded to windows 10 roughly 8 months ago, and the system continued to work. On January 9, I notice

Re: How to seperate grub devices?

You all did not understand me, maybe caused by my bad English. update-grub is ALWAYS changing grub.cfg on BOTH drives, same from which system it is started. And I want it only have changed on THAT DRIVE, I am running AT THE MOMENT. The other drive shall be then stayed untouched! Hope this makes

Re: How to find out the current display manager?

0;115;0cIn-Reply-To: On Sun, Jan 15, 2017 at 09:47:40PM -0500, kamaraju kusumanchi wrote: > How can I find out the display manager currently running on a machine > from the command line? I'm not sure, did you mean something like: ~$ echo $DESKTOP_SESSION /usr/share/xsessions/plasma ? > Googl

Re: How to seperate grub devices?

On Sat, Jan 14, 2017 at 10:50:47AM +0100, Hans wrote: Hi list, this is the situation: I have debian installed on my first harddrive and kali-linux on my second harddrive. When a new kernel version is installed, update-grub is always editing both harddrives. Is there a way, to avoid this? So,

apt-listbugs and apt.conf

I'm still running apt-cacher-ng on wheezy (my "plumbed-in" server) and have at various time switched to backports and backports-sloppy in order to get error-free running. The main problem has been cache expiration and at the moment it fails because of: Problem with debrep/dists/jessie/main/bina

Re: How to find out the current display manager?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Jan 15, 2017 at 09:47:40PM -0500, kamaraju kusumanchi wrote: > How can I find out the display manager currently running on a machine > from the command line? Hm. How do you know there aren't two running? Or fifteen? Yes, I know the question s