Re: Problem Mounting New Drives
On Sun, Aug 19, 2018 at 09:10:10PM +0200, john doe wrote: > On 8/19/2018 8:59 PM, Stephen P. Molnar wrote: > > > > > > On 08/19/2018 02:28 PM, Reco wrote: > > > Hi. > > > > > > On Sun, Aug 19, 2018 at 02:04:39PM -0400, Stephen P. Molnar wrote: > > > > > > Note that second field is a mountpoint in fstab(5), as one of the stock > > > records show: > > > > > > > UUID=8f4eeaae-a055-4262-bebb-cf99abe982a5 /var ext4 defaults > > > > 0 2 > > > Yours have a block device name instead of mountpoint: > > > > > > > UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /dev/sdb1 ext4 > > > > errors=remount-ro 0 > > > > 1 > > > > UUID=d65867da-c658-4e35-928c-9dd2d6dd5742 /dev/sdc1 ext4 > > > > errors=remount-ro 0 > > > > 1 > > > > UUID=007c1f16-34a4-438c-9d15-e3df601649ba /dev/sdc2 ext4 > > > > errors=remount-ro 0 > > > > 1 > > > So even a stock mount(1) should refuse to mount these. > > > > > > > > > > When I rebooted the computer the OS didn't like the new > > > > fstab and gave me a > > > > number of, at least to me, obscure messages. > > > systemd-mount can be cryptic, I agree. > > > > > > > > > > Obviously, I missed something important. My question is what? > > > It's a kind of dumb question, but where do you need your sdb1, sdc1 and > > > sdc2 mounted? Your fstab(5) does not mention that. > > > > > > Reco > > > > > > > > Well, that's another red faced forehead slapper! > > > > It merely reinforces that I don't know what I'm doing as far as > > hardware is concerned. > > > > It's a good thing that I'm an Organic Chemist and not an IT person. > > > > Instead of trying your new changes in '/etc/fstab' by rebooting, you > could also try 'mount -a'. Or # findmnt -x > https://linux.die.net/man/8/mount > > -- > John Doe Regards -- Felipe Salvador
Re: Is Debian Linux protected against the Meltdown and Spectre security flaws?
On Fri, Feb 23, 2018 at 03:05:18PM +0100, mlnl wrote: > Hi, > > > Can it be true? A version of gcc that runs on stretch that will > > compile the latest fancy spectre fixes etc? > > with latest vanilla kernel 4.15.4 and updated gcc-6: > > CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1' > * Mitigated according to the /sys interface: YES (kernel confirms that > the mitigation is active) > * Kernel has array_index_mask_nospec: YES (1 occurence(s) found of 64 > bits array_index_mask_nospec()) > > STATUS: NOT VULNERABLE (Mitigation: __user pointer sanitization) > > CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2' > * Mitigated according to the /sys interface: YES (kernel confirms that > the mitigation is active) > * Mitigation 1 > * Kernel is compiled with IBRS/IBPB support: NO > * Currently enabled features > * IBRS enabled for Kernel space: NO > * IBRS enabled for User space: NO > * IBPB enabled: NO > * Mitigation 2 > * Kernel compiled with retpoline option: YES > * Kernel compiled with a retpoline-aware compiler: YES (kernel > reports full retpoline compilation) > * Retpoline enabled: NO ^^ I get the same result. I wonder why reptoline is disabled. > > STATUS: NOT VULNERABLE (Mitigation: Full generic retpoline) > > CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3' > * Mitigated according to the /sys interface: YES (kernel confirms that > the mitigation is active) > * Kernel supports Page Table Isolation (PTI): YES > * PTI enabled and active: YES > * Running as a Xen PV DomU: NO > > STATUS: NOT VULNERABLE (Mitigation: PTI) > > grep bugs /proc/cpuinfo > bugs: cpu_meltdown spectre_v1 spectre_v2 > model name : Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz > > > > stepping: 3 > > > > microcode : 0x22 > > -- > mlnl -- Felipe Salvador
Re: Causes, cures and prevention of orphaned inodes?
On Sun, Feb 04, 2018 at 11:06:21PM -0200, Henrique de Moraes Holschuh wrote: > On Sun, 04 Feb 2018, Stephen P. Molnar wrote: > > I am running Debian Stretch on am eight thread AMD GPU platform. > > Lately, it seems if I have been plagued by surfeit of orphaned nodes. > > That means: > > 1. "unlinked" files or directories were still open when the filesystem >had to be shutdown/made read-only. Uncommon, unless you did something >like breaking the system by having /run on something other than >tmpfs, etc. > > 2. Filesystem corruption, most likely due to bad RAM. > > 3. Really unusual workload and usage (or *mis*usage ?) pattern that >results in (1), perhaps involving VMs. Could it be due to an undersized(or faulty) power supply? Could a barely sized power supply, on a heavy load scenario, lead to file system corruption? Thank you > This assumes XFS or ext3/ext4, which seems to be your case. > > > At first I though it might be impending hard drive failure as I started > > receiving warning messages from the OS, but installing a brand new > > drive has not solved the problem, They seem to happen when I am > > running four or more apps at the same time. I have 8GB of RAM in the > > system. > > Test that RAM. > > > Model name:AMD FX(tm)-8320 Eight-Core Processor > > Ensure you are running the latest AMD microcode on that processor: > Update the motherboard firmware (BIOS/UEFI) to the latest version > available from your vendor, and *also* install package amd64-microcode > from non-free. Unless you're on the latest AMD microcode on the > FX-8300, you cannot even run VMs safely. Who knows what else could be > broken... > > -- > Henrique Holschuh Regards -- Felipe Salvador
Re: Stretch - bash crash when reach ulimit file size
On Fri, Jan 26, 2018 at 11:05:09AM -0500, Greg Wooledge wrote: > Yes, it's a bug in his script. Not in bash. > > Resource limits are quite low-level; they are implemented as kernel > system calls (see setrlimit(2)). Processes which violate a resource > limit are signalled by the kernel. > > In the case of RLIMIT_FSIZE: > > This is the maximum size of files that the process may create. > Attempts to extend a file beyond this limit result in delivery > of a SIGXFSZ signal. By default, this signal terminates a > process, but a process can catch this signal instead, in which > case the relevant system call (e.g., write(2), truncate(2)) > fails with the error EFBIG. > > If the OP wants the script to exit gracefully, then a signal trap > must be set up. Otherwise, the shell is simply terminated. Well, actually it doesn't exit, nor terminated at all, it crash. I don't know if it is correct to define crash as an ungraceful exit. Trapping SIGXFSZ whit a break resolve the bug in my script; $ trap break SIGXFSZ; while true; do echo a>>a; done bash: echo: errore in scrittura: File troppo grande Thank you PS. this happen only when I run the script "on line", the same does it work if placed in a .sh file. -- Felipe Salvador
Stretch - bash crash when reach ulimit file size
Hi list, setting ulimit -f 1024 and running (for example) $ while true; do echo a>>a; done makes bash crash when file size is reached Warning: Program '/bin/bash' crashed. $ du a 1024/home/felipe/a I would expect an error or something else (exit?) Is it a bug? bash:amd64/stretch 4.4-5 uptodate Thank you Regards -- Felipe Salvador
Re: history issue - bug?
On Sun, Jan 14, 2018 at 06:24:27PM +0100, Felipe Salvador wrote: > On Sun, Jan 14, 2018 at 02:07:01PM +0100, Hans wrote: > > Hi folks, > > > > try this: > > > > 1. login as normal user > > > > 2. become root with "su -" > > > > 3. delete history with "history -c" > > Then run "history -w" to "write the current history to the history > file" Maybe you could fill a bug report in order to ask if it is possible change the history behaviour about -c and -w switches, actually it doesn't accept this combination, you cannot use $history -c -w or $history -cw You have to run separately $history -c AND $history -w Though I don't think this is a bug. Regards -- Felipe Salvador
Re: history issue - bug?
On Sun, Jan 14, 2018 at 02:07:01PM +0100, Hans wrote: > Hi folks, > > try this: > > 1. login as normal user > > 2. become root with "su -" > > 3. delete history with "history -c" Then run "history -w" to "write the current history to the history file" > 4. Check history, history is gone > > 5. logout from root by "CTL + D" or "exit" > > 6. relogin as root with "su -" > > 7. Check history, voila, it appears again. > > What is wrong? Is it a bug or am I doing the wrong way? > > Any comment will help. > > Best regards > > Hans Regards -- Felipe Salvador
Re: neofita
On Wed, Jan 03, 2018 at 06:24:57AM -0500, Gpat wrote: > Buongiorno, vorrei provare Debian e mi domando quanto spazio su hard disck > necessito?, Due GB di ram e un processore Intel Core 2 Quad Q6600 possono > essere sufficienti? > attualmente uso photoshop essential e qualche altro programma di disegno, + > vlc > Consigli? > Grazie > Gpat Ciao, questa è la lista debian-user, supporto in lingua inglese per gli utenti Debian. Se vuoi seguitare a utilizzare debian-user dovrai necessariamente scrivere in inglese, altrimenti puoi chiedere aiuto su debian-italian[1]. [1] https://lists.debian.org/debian-italian/ -- Felipe Salvador
Re: Cumulative internet data transfer {up AND down}
On Fri, Nov 17, 2017 at 08:52:00AM -0600, Richard Owlett wrote: > I'm interested in investigating cumulative data to/from the internet > for selected interval ranging from an hour to a week. > My only connection is a device connected thru a USB port. > My web search turned up only discussion of measuring throughput RATE. > Suggestion of keyword(s) for search? > Suggested software? > TIA I'm using pmacct in order to produce periodic (say every if-up/if-down) report about cumulative data in each session. http://www.pmacct.net/ Regards -- Felipe Salvador
plasma-discover (packagekit) and apt-listchanges integration
Hi list, when I see update notifications I use apt-get to update the system, in this way a get news and changelogs via email by apt-listchanges. Is there a mode to get news and changelogs using plasma-discover (kde update manager) when you perform an update? Debian GNU/Linux 9.1 (stretch) Regards -- Felipe Salvador
Re: moderncv class does not compile in Debian Stretch
On Mon, Jul 17, 2017 at 08:29:46PM +, Andrea Neroni wrote:
>
>
>
> > Is it really required?
>
>
> Don't know, that's why I'm asking.
>
> > I have no such lines in my .tex file, I'm starting to wondering "Is it
> > your (or mine!) template up to date?" or "Did your template contain
> > something that prevents compilation". I've found mine here:
> >
> > www.ivanbortolin.it/?p=200
> >
> > It still works well, please give a try
>
>
> I tried it and it compiles correctly. But if you change
> \moderncvtheme[blue]{classic}
> in
> \moderncvtheme[blue]{banking}
> it gives the very same error as mine. So it seems like a problem (a bug?)
For clarity, let's use template from
texlive-latex-extra-doc:
/usr/share/doc/texlive-doc/latex/moderncv/examples/template.tex.gz
I attach the template and related .log, I've edited the template in
order to use blue color scheme whit banking style and utd8x package to
provide unicode support.
> in the banking style, the one I'm using. I can change it to another one,
> but I would like to keep the cv consistent with previous versions.
And you should not
>
> Andrea
--
Felipe Salvador
This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian)
(preloaded format=pdflatex 2017.4.11) 18 JUL 2017 15:44
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
**curriculum.tex
(./curriculum.tex
LaTeX2e <2017/01/01> patch level 3
Babel <3.9r> and hyphenation patterns for 31 language(s) loaded.
(/usr/share/texlive/texmf-dist/tex/latex/moderncv/moderncv.cls
Document Class: moderncv 2015/07/28 v2.0.0 modern curriculum vitae and letter d
ocument class
(/usr/share/texlive/texmf-dist/tex/latex/base/size11.clo
File: size11.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
)
(/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty
Package: etoolbox 2017/01/02 v2.4 e-TeX tools for LaTeX (JAW)
\etb@tempcnta=\count79
)
(/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty
Package: ifthen 2014/09/29 v1.1c Standard LaTeX ifthen package (DPC)
)
(/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
Package: xcolor 2016/05/11 v2.12 LaTeX color extensions (UK)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg
File: color.cfg 2016/01/02 v1.6 sample color configuration
)
Package xcolor Info: Driver file: pdftex.def on input line 225.
(/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def
File: pdftex.def 2017/01/12 v0.06k Graphics/color for pdfTeX
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty
Package: infwarerr 2016/05/16 v1.4 Providing info/warning/error messages (HO)
)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty
Package: ltxcmds 2016/05/16 v1.23 LaTeX kernel commands for general use (HO)
)
\Gread@gobject=\count80
)
(/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty
Package: colortbl 2012/02/13 v1.0a Color table columns (DPC)
(/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty
Package: array 2016/10/06 v2.4d Tabular extension package (FMi)
\col@sep=\dimen102
\extrarowheight=\dimen103
\NC@list=\toks14
\extratabsurround=\skip41
\backup@length=\skip42
)
\everycr=\toks15
\minrowclearance=\skip43
)
\rownum=\count81
Package xcolor Info: Model `cmy' substituted by `cmy0' on input line 1348.
Package xcolor Info: Model `hsb' substituted by `rgb' on input line 1352.
Package xcolor Info: Model `RGB' extended on input line 1364.
Package xcolor Info: Model `HTML' substituted by `rgb' on input line 1366.
Package xcolor Info: Model `Hsb' substituted by `hsb' on input line 1367.
Package xcolor Info: Model `tHsb' substituted by `hsb' on input line 1368.
Package xcolor Info: Model `HSB' substituted by `hsb' on input line 1369.
Package xcolor Info: Model `Gray' substituted by `gray' on input line 1370.
Package xcolor Info: Model `wave' substituted by `hsb' on input line 1371.
)
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty
Package: ifxetex 2010/09/12 v0.6 Provides ifxetex conditional
)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty
Package: ifluatex 2016/05/16 v1.4 Provides the ifluatex switch (HO)
Package ifluatex Info: LuaTeX not detected.
)
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
Package: fontenc 2017/02/22 v2.0g Standard LaTeX package
(/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def
File: t1enc.def 2017/02/22 v2.0g Standard LaTeX file
LaTeX Font Info:Redeclaring font encoding T1 on input line 48.
))
(/usr/share/texmf/tex/latex/lm/lmodern.sty
Package: lmodern 2009/10/30 v1.6 Latin Modern Fonts
LaTeX Font Info:Overwriting symbol font `operators' in version `normal'
(Font) OT1/cmr/m/n --> OT1/lmr/m/n on input line 22.
LaTeX Font Info:Overwriting symbol font `letters' in version `normal'
(Font) OML/cmm/m/it --> OML/lmm/m/
Re: moderncv class does not compile in Debian Stretch
On Sat, Jul 15, 2017 at 06:53:44PM +, Andrea Neroni wrote:
> Hello everybody,
> I used to have a personal cv written using the moderncv class from the
> package texlive-latex-extra,
> compiled using pdflatex. After upgrading to Stretch it seems that moderncv
> class is using
> /usr/share/texlive/texmf-dist/tex/latex/fontawesome/fontawesome.sty
Correct
> that in turn uses
> /usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty
I don't find any evidence of such dependency in .log file
> that can only be compiled in XeLateX or LuaLatex. Fine.
> Installed texlive-xetex and compiled using xelatex. This error now pops up
I have not such packages in my stretch:
$ dpkg -l | grep -i latex
ii fonts-mathjax 2.7.0-2
all JavaScript display engine for LaTeX and MathML (fonts)
ii kile 4:2.1.3-4+b1
amd64KDE Integrated LaTeX Environment
ii libjs-mathjax 2.7.0-2
all JavaScript display engine for LaTeX and MathML
ii libpod-latex-perl 0.61-2
all module to convert Pod data to formatted LaTeX
ii libreoffice-writer2latex 1.4-1
all Writer/Calc to LaTeX converter extension for LibreOffice
ii preview-latex-style 11.90-1
all extraction of elements from LaTeX documents as graphics
ii prosper 1.00.4+cvs.2007.05.01-4.1
all LaTeX class for writing transparencies
ii texlive-latex-base2016.20170123-5
all TeX Live: LaTeX fundamental packages
ii texlive-latex-base-doc2016.20170123-5
all TeX Live: Documentation files for texlive-latex-base
ii texlive-latex-extra 2016.20170123-5
all TeX Live: LaTeX additional packages
ii texlive-latex-extra-doc 2016.20170123-5
all TeX Live: Documentation files for texlive-latex-extra
ii texlive-latex-recommended 2016.20170123-5
all TeX Live: LaTeX recommended packages
ii texlive-latex-recommended-doc 2016.20170123-5
all TeX Live: Documentation files for
texlive-latex-recommended
ii tipa 2:1.3-20
all system for processing phonetic symbols in LaTeX
> LaTeX Warning: You have requested package `moderncvheadiii',
>but the package provides `moderncvheadiii'.
>
> ) (/usr/share/texlive/texmf-dist/tex/latex/moderncv/moderncvbodyiii.sty
>
> LaTeX Warning: You have requested package `moderncvbodyiii',
>but the package provides `moderncvbodyiii'.
>
> ! Undefined control sequence.
> \tiny \faCircleO
>
>
> Now, to my questions. Why is Xelatex now required, what changed in the class?
Is it really required?
> How can I solve the latter error? I believe it could be a bug in the moderncv
> class,
> should I report it to package maintainers?
>
>
> Thanks in advance to anybody answering!
>
>
> Andrea
On Sun, Jul 16, 2017 at 01:33:24PM +, Andrea Neroni wrote:
>
>
> > Where did you found this error? pdflatex output or *.log?> I have the same
> > error in the *.log file but it is not prevent pdflatex
> > form building the related .pdf.
>
> Thanks for the answers.
>
> The error is in pdflatex output, the pdf is never generated. I looked
> at an old log from previous compilations and it seems that in the former
> version if pdflatex was used, the class fall back to use the marvosym
> symbols that do not require XeLatex. According to the documentation is
> possible to use
> \moderncvicons{marvosym}
I have no such lines in my .tex file, I'm starting to wondering "Is it
your (or mine!) template up to date?" or "Did your template contain
something that prevents compilation". I've found mine here:
www.ivanbortolin.it/?p=200
It still works well, please give a try
> to choose the old icon set instead of the fontawesome, but it is not
> working.
>
>
>
> Andrea
--
Felipe Salvador
Re: moderncv class does not compile in Debian Stretch
On Sat, Jul 15, 2017 at 06:53:44PM +, Andrea Neroni wrote: > Hello everybody, > I used to have a personal cv written using the moderncv class from the > package texlive-latex-extra, > compiled using pdflatex. After upgrading to Stretch it seems that moderncv > class is using > /usr/share/texlive/texmf-dist/tex/latex/fontawesome/fontawesome.sty > > that in turn uses > /usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty > > that can only be compiled in XeLateX or LuaLatex. Fine. > Installed texlive-xetex and compiled using xelatex. This error now pops up > > LaTeX Warning: You have requested package `moderncvheadiii', >but the package provides `moderncvheadiii'. > > ) (/usr/share/texlive/texmf-dist/tex/latex/moderncv/moderncvbodyiii.sty > > LaTeX Warning: You have requested package `moderncvbodyiii', >but the package provides `moderncvbodyiii'. > > ! Undefined control sequence. > \tiny \faCircleO Where did you found this error? pdflatex output or *.log? I have the same error in the *.log file but it is not prevent pdflatex form building the related .pdf. > Now, to my questions. Why is Xelatex now required, what changed in the class? > > How can I solve the latter error? I believe it could be a bug in the moderncv > class, > should I report it to package maintainers? > > > Thanks in advance to anybody answering! > > > Andrea -- Felipe Salvador
Re: How to find out the current display manager?
On Mon, Jan 16, 2017 at 11:46:05AM -0500, kamaraju kusumanchi wrote: > On Mon, Jan 16, 2017 at 6:00 AM, Felipe Salvador > <felipe.salva...@gmail.com> wrote: > > 0;115;0cIn-Reply-To: > > <cabpbyae5e3sdonsx328ugmmxj9yh88ljuyk6r_nu7tw7hqo...@mail.gmail.com> > > > > 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 > > No, that is not what I mean. I came across this while searching in > google. But this shows the desktop session and not the display > manager. For example, I am running lightdm display manager but the > DESKTOP_SESSION points to plasma. Ok, sorry. I'm on a stretch/sid, did you have this file? /etc/X11/default-display-manager[1] [1] https://www.debian.org/doc/manuals/debian-reference/ch07.en.html#_starting_the_x_window_system -- Felipe Salvador
Re: How to find out the current display manager?
0;115;0cIn-Reply-To: <cabpbyae5e3sdonsx328ugmmxj9yh88ljuyk6r_nu7tw7hqo...@mail.gmail.com> 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 ? > Google tells me that /etc/X11/default-display-manager will show the > default display manager. But I want the display manager that is > currently running (which can be different from the default). Is that > possible? > > thanks > raju -- Felipe Salvador
WINS - name resolution error
Hi, starting from 2016-11-07 whit the daily upgrade (detail attached) I spot these errors: ~$ ping google.com ping: debian.com: Errore di sistema # literally "System error" and, in the attempt to download email: mpop: cannot locate host pop.*.com: File o directory non esistente # file or directory not found These errors seems to be related to wins, a workaround I found is to remove or move back "wins" in /etc/nsswitch.conf, form: hosts: files wins dns mdns4_minimal [NOTFOUND=continue] mdns4 to hosts: files dns mdns4_minimal [NOTFOUND=continue] wins mdns4 I have tired, without success, to edit STATUS>ACTION field as follow: hosts: files wins [UNAVAIL=continue] dns mdns4_minimal [NOTFOUND=continue] mdns4 I would open a bug report but cannot figure out who is the culprit, it must be among the upgraded packages, among these I suspect libwbclient0, I've done some tests whit strace and ldd, but I'm not sure. Regards -- Felipe Salvador Start-Date: 2016-11-07 10:14:55 Commandline: apt-get upgrade Upgrade: publicsuffix:amd64 (20160826-1, 20161028-1) python-samba:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1) libgstreamer1.0-dev:amd64 (1.8.3-1, 1.10.0-1) libwbclient0:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1) gstreamer1.0-tools:amd64 (1.8.3-1, 1.10.0-1) gstreamer1.0-plugins-good:amd64 (1.8.3-1+b1, 1.10.0-1) samba:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1) samba-dsdb-modules:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1) python3-pip:amd64 (8.1.2-2, 8.1.2-3) gstreamer1.0-plugins-base:amd64 (1.8.3-1, 1.10.0-1) gstreamer1.0-pulseaudio:amd64 (1.8.3-1+b1, 1.10.0-1) samba-libs:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1) winbind:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1) samba-common:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1) libnss-winbind:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1) libdevel-globaldestruction-perl:amd64 (0.13-1, 0.14-1) libgstreamer-plugins-base1.0-0:amd64 (1.8.3-1, 1.10.0-1) samba-vfs-modules:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1) gstreamer1.0-x:amd64 (1.8.3-1, 1.10.0-1) gir1.2-gst-plugins-base-1.0:amd64 (1.8.3-1, 1.10.0-1) python3-gst-1.0:amd64 (1.8.3-1, 1.10.0-1) libsmbclient:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1) smbclient:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1) samba-common-bin:amd64 (2:4.4.6+dfsg-2, 2:4.4.7+dfsg-1) gstreamer1.0-libav:amd64 (1.8.3-1, 1.10.0-1) lsb-release:amd64 (9.20161016, 9.20161101) lsb-base:amd64 (9.20161016, 9.20161101) gir1.2-gstreamer-1.0:amd64 (1.8.3-1, 1.10.0-1) libgstreamer1.0-0:amd64 (1.8.3-1, 1.10.0-1) python-pip-whl:amd64 (8.1.2-2, 8.1.2-3) gstreamer1.0-plugins-ugly:amd64 (1.8.3-1, 1.10.0-1) End-Date: 2016-11-07 10:15:13
Re: parted is ALMOST suitable
On Mon, Nov 07, 2016 at 07:59:56AM -0700, Joe Pfeiffer wrote:
> Felipe Salvador <felipe.salva...@gmail.com> writes:
>
> > On Mon, Nov 07, 2016 at 06:37:53AM -0600, Richard Owlett wrote:
> >> On 11/7/2016 6:20 AM, Felipe Salvador wrote:
> >> > On Mon, Nov 07, 2016 at 06:11:50AM -0600, Richard Owlett wrote:
> >> > > *HOWEVER* parted requires root privileges. That is not acceptable.
> >> > > Suggestions?
> >> > > TIA
> >> >
> >> > lsblk -fr ?
> >> >
> >>
> >> Debian is perverse ;{
> >> man page suggested good things.
> >> However when run as other than root, there is a column heading "FSTYPE".
> >
> >> It is blank for all partitions.
> >> They are present when run as root.
> >> Thanks for trying.
> >
> > I don't see this behaviour
> >
> > ~$ lsblk -fr
> > NAME FSTYPE LABEL UUID MOUNTPOINT
> > sda
> > sda1 ext2 ... /boot
> > sda2 ext4 ... /
> > sda3 ext2 ... /tmp
> > etc etc etc
> >
> > or
> >
> > file -s /dev/sda{1..5} | awk '{print $5}'
>
> I was just about to post a very similar followup when I discovered a
> gaping security hole (really, about as big as it gets) on my machine:
>
> snowball:404$ ls -l /dev/sda2
> brw-rw-rw- 1 root root 8, 2 Nov 7 07:54 /dev/sda2
>
> You might want to check your permissions as well
brw-rw 1 root disk 8, 0 nov 7 11:00 /dev/sda
I'm in the disk group
--
Felipe Salvador
Re: parted is ALMOST suitable
On Mon, Nov 07, 2016 at 04:09:24PM +, Brian wrote:
> On Mon 07 Nov 2016 at 09:27:47 -0600, Richard Owlett wrote:
>
> > On 11/7/2016 8:19 AM, Felipe Salvador wrote:
> > >
> > >I don't see this behaviour
> > >
> > >~$ lsblk -fr
> > >NAME FSTYPE LABEL UUID MOUNTPOINT
> > >sda
> > >sda1 ext2 ... /boot
> > >sda2 ext4 ... /
> > >sda3 ext2 ... /tmp
> > >etc etc etc
> > >
> > >or
> > >
> > >file -s /dev/sda{1..5} | awk '{print $5}'
> >
> > richard@full-jessier:~$ lsblk -fr
> > NAME FSTYPE LABEL UUID MOUNTPOINT
> > sda
> > sda1
> > sda2
> > sda5
> > sda6
> > sda7
> > sda8[SWAP]
> > sda9/
> > sda10
> > sda11
> > sda12
> > sdb
> > sdb1
> > sr0
>
> I get the same as you on Debian 8.6. On unstable the command 'lsblk -f'
> shows all the fields populated. I wonder what Felipe Salvador is using?
~$ apt-show-versions util-linux
util-linux:amd64/testing 2.28.2-1 uptodate
~$ cat /etc/debian_version
stretch/sid
--
Felipe Salvador
Re: parted is ALMOST suitable
On Mon, Nov 07, 2016 at 06:37:53AM -0600, Richard Owlett wrote:
> On 11/7/2016 6:20 AM, Felipe Salvador wrote:
> > On Mon, Nov 07, 2016 at 06:11:50AM -0600, Richard Owlett wrote:
> > > *HOWEVER* parted requires root privileges. That is not acceptable.
> > > Suggestions?
> > > TIA
> >
> > lsblk -fr ?
> >
>
> Debian is perverse ;{
> man page suggested good things.
> However when run as other than root, there is a column heading "FSTYPE".
> It is blank for all partitions.
> They are present when run as root.
> Thanks for trying.
I don't see this behaviour
~$ lsblk -fr
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
sda1 ext2 ... /boot
sda2 ext4 ... /
sda3 ext2 ... /tmp
etc etc etc
or
file -s /dev/sda{1..5} | awk '{print $5}'
--
Felipe Salvador
Re: parted is ALMOST suitable
On Mon, Nov 07, 2016 at 06:11:50AM -0600, Richard Owlett wrote: > *HOWEVER* parted requires root privileges. That is not acceptable. > Suggestions? > TIA lsblk -fr ? -- Felipe Salvador
