kvm win8 gues audio is terrible.
I created a fresh install of debian stretch amd64. In that I created a qemu/kvm guess install of win8. It only accepted hda as a valid sound card. All others show us without drivers. So, I am limited to only HDA as -soundhw. Further HDA sounds so broken if I try to test with any sound file or youtube video. It is grainy/distorted and outright horrible. Google searches mentions something about MSI and those approaches are simply not accepted by win8. So, I could not use them. I am wondering if there is something fundamentally wrong with windows guests or is there a setting that I missing. Ramesh
debian stretch tigervnc issues
Recently I got a nvme ssd and did a fresh install of debian stretch (amd64). In the new install, tigervnc is acting up. Commands like "vncconfig" and "vncserver" do not always work. Randomly, about half the time, commands just hang waiting for something and at other times they will exit without doing anything. I do not have any idea why this is happening. I usually fire off one vnc for each user account and we simply connect to one of them to use. This has become a pain now. We use a script vnc0 :N below on an xterm to switch between different user's screen and it nolonger works reliably now #!/bin/tcsh -f if ($?DISPLAY) then vncconfig -disconnect set olddisplay = "$DISPLAY" setenv DISPLAY :0 xvncviewer -FullScreen -FullColor $* xvncviewer -FullScreen \ -passwd ~/.vnc/passwd -FullColor $olddisplay >& /dev/null & else echo 'No current $DISPLAY. Trying :0' xvncviewer -display :0 -FullScreen -FullColor $* || \ echo "display :0 not found" endif My older install (jesse, i386) on the very same machine (dual boot) works just fine, although I think it is xvnc4. I need amd64 to install windows 8 guest. So, I am in a bit of a fix. Please help if you know what I am missing in my tigenvnc setup. Ramesh
Programa para Ações
Olá, gostaria de saber se existe algum programa onde se possa lançar as compras de ações e fiis brasileiros , para fazer custo médio e acompanhar estoque das ações. Desde já agradeço a atenção de todos. -- Ricardo Libanio
Re: definir temporalment variable per a l'ordre actual
Hola Eloi, > Lligant-ho amb l'explicació que he fet a l'altre correu i per > completar-la, aquesta construcció (que com bé s'ha dit és > equivalent a executar-les en dues línies separades) crea la > variable *només* a l'entorn del shell actual. Això fa que > funcioni en el cas de l'echo, perquè la substitució la fa el > propi shell, però la variable d'entorn no està disponible per > al procés fill: > > $ foo=1; env | grep ^foo= > > Aquesta combinació no torna res, a menys que es precedeixi > l'assignació amb 'export'. Una alternativa per passar als subshells la variable sense haver de definar-la al shell actual és via env (els detalls al man): $ env foo=1 ... Quant a la pregunta original de l'Ernest, aquesta altra manera alternativa funciona bé perquè el shell actual no interpreta la cadena que conté l'ordre i les variables: $ foo=1 bash -c 'echo $foo' Salut! Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer - log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Re: Strange event handling problem with Xfce/LXDE - which pkg responsible?
Hi, On Wed, 15 May 2019 21:03:40 +0200 Jonas Smedegaard wrote: (...) > Please report the issue as a bug as best as you can - e.g. file it > against either of those involved packages (or both, comma-separated). > > It is easy in Debian's bugtracker to reassign later to another package > as needed. fyi, I now filed a bug report here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929090 Regards Michael .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. Military secrets are the most fleeting of all. -- Spock, "The Enterprise Incident", stardate 5027.4
Re: Age Ranges for contributors was: Salsa vs Github
A bit of searching shows that some international legislation seems to be responsible for the age restrictions. This project cites the GDPR: https://github.com/hypothesis/product-backlog/issues/561 GitHub's ToS says an account holder must be at least 13 and gives US law as the reason in section B(3): https://help.github.com/en/articles/github-terms-of-service And finally, is GitHub's statement on child labor giving UK law as one of the reasons: https://help.github.com/en/articles/github-statement-against-modern-slavery-and-child-labor Of course, IANAL, etc., but the last two links do shed some light on the issue for me after a quick glance. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: http://www.n0nb.us GPG key: D55A8819 GitHub: N0NB signature.asc Description: PGP signature
Re: Age Ranges for contributors was: Salsa vs Github
On 16/05/2019 19:22, Cindy Sue Causey wrote: > On 5/16/19, Paul Sutton wrote: >> Just a specific question from the thread >> >> Further to the comments by nik on the Salsa vs Github thread. >> >> Am I right in thinking that you can be _any_ age to contribute to >> projects hosted on Salsa and contribute to the Debian project in general? >> >> Granted there is probably a minimal age for practicality reasons. > > I don't have a direct answer to your direct question but decided to > respond here instead of the other thread... that was already sitting > in *compose mode*.. > > I'd say *maturity level* is a better gauge rather than physical age. > If kids can communicate without trolling, who knows where they may go > one day with the right mentorships. > > So I tried Debian's Code of Conduct: > > https://www.debian.org/code_of_conduct > > Didn't see a specific mention of age there but DID see a pointer > toward Diversity. Sounded even better than Code of Conduct so: > > https://www.debian.org/intro/diversity > > And they said: > > + BEGIN DEBIAN'S DIVERSITY STATEMENT BLURB + > > The Debian Project welcomes and encourages participation by everyone. > > No matter how you identify yourself or how others perceive you: we > welcome you. We welcome contributions from everyone as long as they > interact constructively with our community. > > While much of the work for our project is technical in nature, we > value and encourage contributions from those with expertise in other > areas, and welcome them into our community. > > + END DEBIAN'S DIVERSITY STATEMENT BLURB + > > One MAJOR problem is... children are preyed upon horrifically across > the Net. That's an important secondary reason why a website might make > the CHOICE to skip that age demographic in their project. If mentors > detect a young protégé, it wouldn't hurt to further mentorship with a > sidestep into childhood self-protection online as part of the > interaction. > > ** Afterthought while proofreading before sending: @MissingKids and > @DHSBlueCampaign on Twitter regularly present information about > preventing related travesty, really for all ages. Maybe they're each a > potential resource for tip ideas if someone was to put together a > template for others to use with respect to children participating in > primarily adult tech communities. > > This is the first time I'd heard something about age over at Github. > It explains a WEIRD, quick interaction I saw couple weeks ago. A new > issue was opened then the Github "owner" responded with a rational > answer. WEIRD was when that answer concluded by saying EVERYONE EXCEPT > the issue poster was welcome to yada-yada. > > Issue poster closed the issue without saying one more word. Issue > poster's profile.. said they were 13-years-old. This Debian thread > finally takes the question mark off of what the flock happened during > that Github exchange. > > Poor kid.. Judging by their communication alone, I didn't know they > WERE a kid until I visited their profile page out of curiosity after > that WEIRD exchange. :) > > Me.. I first touched my own "computer" when I was about 15-years-old. > Something super small with the name "Sears Roebuck" on it. You hooked > little TVs as your monitor. My memory of it is that it basically > worked with about two lines of code at a time. > > Never got it to do much. I take a memory trip back to that thing every > so often. I actively wonder how differently my #Life would have > evolved if I'd found the right mentoring community back then... > mid-1970's... when so many of today's high tier tech folks first > touched their own first computers *hm* :) > > Cindy :) I agree, people should be judged on maturity not age. I am trying to work on something, partly as I have e-safety training in a few weeks and while usual safety advice applies to IRC, mailing lists in the same way, professionals who have not heard of Debian IRC, or salsa may be unsure, so hopefully raising awareness will empower them to support young people in their efforts to contribute, by enforcing the usual safety rules, and being there if they need to talk. I can make people aware of the code of conduct and get some help in coming up with a short training seminar (to be presented by someone who works in workforce development) to come up with something. Maturity level also helps you make choices, why has someone sent me a private e-mail off list (easily done by accident) on IRC. With e-mail myself and Francisco communicated off list to discuss some finer points to do with the presentation, which is fine. Or is there malicious intent somewhere. -- Good idea to side step in to ensuring young people are safe and mentors to enforce that, but empowering people out side of the community who work with young people would be a good thing to. When working with children we have to avoid 1-2-1 situations this protects us as well as the child. So the same could apply to e-mail
Re: definir temporalment variable per a l'ordre actual
El 16/5/19 a les 17:10, Ernest Adrogué ha escrit: > Amb punt i coma és com fer-ho en línies separades, no es destrueix > l'assignació: > > $ echo $foo > > $ foo=1 ; echo $foo > 1 > $ echo $foo > 1 > $ Lligant-ho amb l'explicació que he fet a l'altre correu i per completar-la, aquesta construcció (que com bé s'ha dit és equivalent a executar-les en dues línies separades) crea la variable *només* a l'entorn del shell actual. Això fa que funcioni en el cas de l'echo, perquè la substitució la fa el propi shell, però la variable d'entorn no està disponible per al procés fill: $ foo=1; env | grep ^foo= Aquesta combinació no torna res, a menys que es precedeixi l'assignació amb 'export'.
Re: Age Ranges for contributors was: Salsa vs Github
On 5/16/19, Paul Sutton wrote: > Just a specific question from the thread > > Further to the comments by nik on the Salsa vs Github thread. > > Am I right in thinking that you can be _any_ age to contribute to > projects hosted on Salsa and contribute to the Debian project in general? > > Granted there is probably a minimal age for practicality reasons. I don't have a direct answer to your direct question but decided to respond here instead of the other thread... that was already sitting in *compose mode*.. I'd say *maturity level* is a better gauge rather than physical age. If kids can communicate without trolling, who knows where they may go one day with the right mentorships. So I tried Debian's Code of Conduct: https://www.debian.org/code_of_conduct Didn't see a specific mention of age there but DID see a pointer toward Diversity. Sounded even better than Code of Conduct so: https://www.debian.org/intro/diversity And they said: + BEGIN DEBIAN'S DIVERSITY STATEMENT BLURB + The Debian Project welcomes and encourages participation by everyone. No matter how you identify yourself or how others perceive you: we welcome you. We welcome contributions from everyone as long as they interact constructively with our community. While much of the work for our project is technical in nature, we value and encourage contributions from those with expertise in other areas, and welcome them into our community. + END DEBIAN'S DIVERSITY STATEMENT BLURB + One MAJOR problem is... children are preyed upon horrifically across the Net. That's an important secondary reason why a website might make the CHOICE to skip that age demographic in their project. If mentors detect a young protégé, it wouldn't hurt to further mentorship with a sidestep into childhood self-protection online as part of the interaction. ** Afterthought while proofreading before sending: @MissingKids and @DHSBlueCampaign on Twitter regularly present information about preventing related travesty, really for all ages. Maybe they're each a potential resource for tip ideas if someone was to put together a template for others to use with respect to children participating in primarily adult tech communities. This is the first time I'd heard something about age over at Github. It explains a WEIRD, quick interaction I saw couple weeks ago. A new issue was opened then the Github "owner" responded with a rational answer. WEIRD was when that answer concluded by saying EVERYONE EXCEPT the issue poster was welcome to yada-yada. Issue poster closed the issue without saying one more word. Issue poster's profile.. said they were 13-years-old. This Debian thread finally takes the question mark off of what the flock happened during that Github exchange. Poor kid.. Judging by their communication alone, I didn't know they WERE a kid until I visited their profile page out of curiosity after that WEIRD exchange. :) Me.. I first touched my own "computer" when I was about 15-years-old. Something super small with the name "Sears Roebuck" on it. You hooked little TVs as your monitor. My memory of it is that it basically worked with about two lines of code at a time. Never got it to do much. I take a memory trip back to that thing every so often. I actively wonder how differently my #Life would have evolved if I'd found the right mentoring community back then... mid-1970's... when so many of today's high tier tech folks first touched their own first computers *hm* :) Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
Re: Age Ranges for contributors was: Salsa vs Github
On 16/05/2019 18:32, Dominik George wrote: > Hi, > >> Further to the comments by nik on the Salsa vs Github thread. >> >> Am I right in thinking that you can be _any_ age to contribute to >> projects hosted on Salsa and contribute to the Debian project in >> general? > Yes. This results from the fact that in Debian, noone cares whether you are > old, young, male, female, trans,...,... No questions ask, as long as you > abide by the rules. > >> Granted there is probably a minimal age for practicality reasons. > As head of Teckids, the heade of the free software (and Debian centric) youth > organisation, I can say that we have seen and worked with contributors as > young as 10. > > Thank you for taking this topic serious :)! > > -nik Great stuff, convincing local youth workers etc that anyone 10+ can just join regardless of age, could be a problem (here it is partly down to safeguarding ), I will stick to promotion via the South Devon Tech Jam (which I help run). This is open to any age, never a problem and in fact there is a lot of intergenerational contact too without a problem. While safeguarding is important (working with children in the UK it is something that is really pushed ) we can keep people safe through good education on how to conduct themselves and what to, and not to share online. Does Debian have any specific advice on this?, in relation to services such as salsa, irc and mailing lists, if so, it may be worth making access to this more prominent. I am probably over thinking stuff here. However if this comes up while talking to people who work with children and young people then It is handy to have answers. Nice thing about the free software community it is truly inclusive, something a lot of the offline world could learn from (and fail to grasp fully). But that is the 'hacker (original meaning , ESR' ) way of doing things. No problem about taking this seriously, I can now push the tools that help and not hinder this effort. Paul -- Paul Sutton http://www.zleap.net https://www.linkedin.com/in/zleap/ gnupg : 7D6D B682 F351 8D08 1893 1E16 F086 5537 D066 302D
Re: definir temporalment variable per a l'ordre actual
2019-05-16, 17:21 (+0200); Josep Lladonosa escriu: > El que puc aportar és que si es vol un valor de variable permanent després > de sortir de l'embolcall es fa: > > export foo=1; sh > $ echo $foo > 1 > $ exit > $ echo $foo > 1 Sí, però en aquest cas el que volia és el contrari: modificar l'entorn d'aquella ordre en concret i prou. De totes maneres punts extra per utilitzar la paraula embolcall ;) Salut
Re: Dúvida com o Crontab
Amigo, boa tarde! Desde já muito obrigado por responder. Um colega em outro grupo me indicou um site chamado https://crontab.guru/ Esse site "testa" os agendamentos do crontab. Um grande abraço. Atenciosamente, Henrique Fagundes Analista de Suporte Linux supo...@aprendendolinux.com Skype: magnata-br-rj Linux User: 475399 https://www.aprendendolinux.com https://www.facebook.com/AprendendoLinux https://youtube.com/AprendendoLinux https://twitter.com/AprendendoLinux https://t.me/AprendendoLinux https://t.me/GrupoAprendendoLinux __ Participe do Grupo Aprendendo Linux https://listas.aprendendolinux.com/listinfo/aprendendolinux Ou envie um e-mail para: aprendendolinux-subscr...@listas.aprendendolinux.com Ativado Qui, 16 mai 2019 13:53:07 -0300 Ednardo Lobo escreveu > On 16/05/2019 12:44, Henrique Fagundes wrote: > > Prezado Colegas, > > > > Primeiramente, saudações "pinguianas" e boa tarde! > > > > Estou com uma dúvida boba no Crontab. > > > > No arquivo /etc/crontab, fiz o seguinte agendamento: > > > > 00 622 */3 * root /usr/local/bin/script.sh > > > > Levando em consideração que hoje é dia 16, eu gostaria de saber se o > > crontab vai executar o script no próximo dia 22 (daqui a 6 dias), ou > > somente no dia 22/08 (3 meses depois). > Não estou completamente seguro, pois não testei, mas creio que ele se > comportará da seguinte forma: > > */3, meses: 1 4 7 10 > > 2-12/3, meses: 2 5 8 11 > > ou, escrevendo de outra forma: > > 1,4,7,10 > > 2,5,8,11 > > Portanto, segundo meu entendimento, ele executará seu script em 22/7. > > Recomendo a leitura da página manual nº 5 do contrab: man 5 contrab. > > -- > Ednardo Lobo > > LOBO's NET: www.lobosnet.com > > +55 62 3202-2571 > +55 62 9 8158-9632 (whatsapp) > >
Re: definir temporalment variable per a l'ordre actual
2019-05-16, 18:11 (+0200); Eloi escriu: > En aquest cas no funciona perquè la comanda echo no està realment > accedint a l'entorn sinó que és el propi shell qui fa la substitució > *abans* d'executar la comanda. Sí, exacte... amb aquest exemple que havia posat no es pot veure si es modifica o no l'entorn. Salut.
Re: Age Ranges for contributors was: Salsa vs Github
Hi, >Further to the comments by nik on the Salsa vs Github thread. > >Am I right in thinking that you can be _any_ age to contribute to >projects hosted on Salsa and contribute to the Debian project in >general? Yes. This results from the fact that in Debian, noone cares whether you are old, young, male, female, trans,...,... No questions ask, as long as you abide by the rules. > >Granted there is probably a minimal age for practicality reasons. As head of Teckids, the heade of the free software (and Debian centric) youth organisation, I can say that we have seen and worked with contributors as young as 10. Thank you for taking this topic serious :)! -nik
Age Ranges for contributors was: Salsa vs Github
Hi Just a specific question from the thread Further to the comments by nik on the Salsa vs Github thread. Am I right in thinking that you can be _any_ age to contribute to projects hosted on Salsa and contribute to the Debian project in general? Granted there is probably a minimal age for practicality reasons. Paul -- Paul Sutton http://www.zleap.net https://www.linkedin.com/in/zleap/ gnupg : 7D6D B682 F351 8D08 1893 1E16 F086 5537 D066 302D
Re: Dúvida com o Crontab
On 16/05/2019 12:44, Henrique Fagundes wrote: Prezado Colegas, Primeiramente, saudações "pinguianas" e boa tarde! Estou com uma dúvida boba no Crontab. No arquivo /etc/crontab, fiz o seguinte agendamento: 00 622 */3 * root /usr/local/bin/script.sh Levando em consideração que hoje é dia 16, eu gostaria de saber se o crontab vai executar o script no próximo dia 22 (daqui a 6 dias), ou somente no dia 22/08 (3 meses depois). Não estou completamente seguro, pois não testei, mas creio que ele se comportará da seguinte forma: */3, meses: 1 4 7 10 2-12/3, meses: 2 5 8 11 ou, escrevendo de outra forma: 1,4,7,10 2,5,8,11 Portanto, segundo meu entendimento, ele executará seu script em 22/7. Recomendo a leitura da página manual nº 5 do contrab: man 5 contrab. -- Ednardo Lobo LOBO's NET: www.lobosnet.com +55 62 3202-2571 +55 62 9 8158-9632 (whatsapp)
Re: Install backport during netinstall installation process
On 2019-05-16, Rory Campbell-Lange wrote: > > Consequently I'd be grateful to know if: > > * it is possible to somehow install the backport kernel and dependencies > during the netinstall process > (apt-get install doesn't seem available on the virtual terminals) I guess preseeding is one way of doing it (gleaned from a rapid internet search): https://blog.raymond.burkholder.net/index.php?/archives/899-Debian-Preseed-Backport-Kernel.html > * alternatively, what mount point and commands should I use to make a > root file system (which I've re-raided and decrypted) available to the > buster installer in rescue mode > Thanks very much > Rory > > > ** there is another issue, which is the stretch grub doesn't seem to be > able to decrypt a dm_crypt volume when made from buster. I've reported > that to debian-boot. > > > -- “When he was dry, he believed it was alcohol he needed, but when he had a few drinks in him, he knew it was something else, possibly a woman; and when he had it all — cash, booze, and a wife — he couldn’t be distracted from the great emptiness that was always falling through him and never hit the ground.” – Denis Johnson
Re: Salsa vs Github
Hi, >I am creating levels for the Rocks and Diamonds game ( >https://www.artsoft.org/ ) these are being uploaded to my project >repository on salsa > >https://salsa.debian.org/zleap-guest/rocksndiamondslevels > >I am in the process of updating the README.md files so, hopefully >others >can also be part of this project. > >Questions: > >is it possible to >1. Fork a project between github -> salsa or between salsa -> github ? > >2 As above but issue pull / merge requests between the two? first off, please do *never* use GitHub for free software. Especially not in a project that might be used by one of the groups GitHub discriminates against (potential contributors under 16 years of age in that case). That said: Forking on either platform is nothing more than git clone; git remote add origin; git push. So yes, you can fork any repository to anywhere else. If you want GitHub users to also be able to use the issue tracker, etc., EduGit.org might be an option for a game as well. -nik
Re: definir temporalment variable per a l'ordre actual
El 16/5/19 a les 16:49, Ernest Adrogué ha escrit: > Em pensava que si feies una assignació de variable a línia d'ordres > seguida d'una ordre, aquella assignació només tenia efecte per a l'ordre > en qüestió. Per exemple, segons això, > > $ foo=1 echo $foo > > hauria d'escriure "1". Però estic veient que no fa l'assignació... > > Ha canviat recentment, o és que mai ha funcionat així? > > Salut En aquest cas no funciona perquè la comanda echo no està realment accedint a l'entorn sinó que és el propi shell qui fa la substitució *abans* d'executar la comanda. O sigui, primer fa la substitució de la variable $foo a l'entorn del shell (on no està definida), i després passa a la comanda echo aquesta variable junt amb la resta de l'entorn però que acaba ignorant perquè echo es limita a repetir el que rep per paràmetres. Una forma de veure-ho en funcionament és aquesta: $ foo=1 env | grep ^foo= Aquí igualment definim la variable foo i executem la comanda env, que *sí* consulta el nou entorn i en retorna totes les variables, entre les quals la foo que just hem definit.
Dúvida com o Crontab
Prezado Colegas, Primeiramente, saudações "pinguianas" e boa tarde! Estou com uma dúvida boba no Crontab. No arquivo /etc/crontab, fiz o seguinte agendamento: 00 622 */3 * root /usr/local/bin/script.sh Levando em consideração que hoje é dia 16, eu gostaria de saber se o crontab vai executar o script no próximo dia 22 (daqui a 6 dias), ou somente no dia 22/08 (3 meses depois). Ficarei grato com quem puder esclarecer. Atenciosamente, Henrique Fagundes Analista de Suporte Linux supo...@aprendendolinux.com Skype: magnata-br-rj Linux User: 475399 https://www.aprendendolinux.com https://www.facebook.com/AprendendoLinux https://youtube.com/AprendendoLinux https://twitter.com/AprendendoLinux https://t.me/AprendendoLinux https://t.me/GrupoAprendendoLinux __ Participe do Grupo Aprendendo Linux https://listas.aprendendolinux.com/listinfo/aprendendolinux Ou envie um e-mail para: aprendendolinux-subscr...@listas.aprendendolinux.com BRASIL acima de tudo, DEUS acima de todos!
Salsa vs Github
Hi I am creating levels for the Rocks and Diamonds game ( https://www.artsoft.org/ ) these are being uploaded to my project repository on salsa https://salsa.debian.org/zleap-guest/rocksndiamondslevels I am in the process of updating the README.md files so, hopefully others can also be part of this project. Questions: is it possible to 1. Fork a project between github -> salsa or between salsa -> github ? 2 As above but issue pull / merge requests between the two? I am asking this, as if someone has github, and can do the above they are able to perhaps help, without having to sign up to an account on salsa. Thanks for any help Paul Sutton -- Paul Sutton http://www.zleap.net https://www.linkedin.com/in/zleap/ gnupg : 7D6D B682 F351 8D08 1893 1E16 F086 5537 D066 302D
Re: definir temporalment variable per a l'ordre actual
On Thu, 16 May 2019 at 17:10, Ernest Adrogué wrote: > 2019-05-16, 16:59 (+0200); tictacbum escriu: > > foo=1 ; echo $foo > > > > creac que cal el punt i coma perquè avaluï l'assignació > > Amb punt i coma és com fer-ho en línies separades, no es destrueix > l'assignació: > > $ echo $foo > > $ foo=1 ; echo $foo > 1 > $ echo $foo > 1 > $ > > > si crides un script en comptes de echo si que funciona perquè crea una > > subshell em sembla.. potser algú sap millor que passa realment > > Doncs, sí, tens raó... > > $ foo=1 sh > $ echo $foo > 1 > $ exit > $ echo $foo > > $ > > pot ser que crei un entorn per al procés fill, però com que echo no > s'executa en un altre procés, en aquest cas no fa cap efecte. > El que puc aportar és que si es vol un valor de variable permanent després de sortir de l'embolcall es fa: export foo=1; sh $ echo $foo 1 $ exit $ echo $foo 1 > > Salut > > -- -- Salutacions...Josep --
Re: definir temporalment variable per a l'ordre actual
2019-05-16, 16:59 (+0200); tictacbum escriu: > foo=1 ; echo $foo > > creac que cal el punt i coma perquè avaluï l'assignació Amb punt i coma és com fer-ho en línies separades, no es destrueix l'assignació: $ echo $foo $ foo=1 ; echo $foo 1 $ echo $foo 1 $ > si crides un script en comptes de echo si que funciona perquè crea una > subshell em sembla.. potser algú sap millor que passa realment Doncs, sí, tens raó... $ foo=1 sh $ echo $foo 1 $ exit $ echo $foo $ pot ser que crei un entorn per al procés fill, però com que echo no s'executa en un altre procés, en aquest cas no fa cap efecte. Salut
Re: definir temporalment variable per a l'ordre actual
foo=1 ; echo $foo creac que cal el punt i coma perquè avaluï l'assignació, si crides un script en comptes de echo si que funciona perquè crea una subshell em sembla.. potser algú sap millor que passa realment Missatge de Ernest Adrogué del dia dj., 16 de maig 2019 a les 16:49: > Em pensava que si feies una assignació de variable a línia d'ordres > seguida d'una ordre, aquella assignació només tenia efecte per a l'ordre > en qüestió. Per exemple, segons això, > > $ foo=1 echo $foo > > hauria d'escriure "1". Però estic veient que no fa l'assignació... > > Ha canviat recentment, o és que mai ha funcionat així? > > Salut > >
definir temporalment variable per a l'ordre actual
Em pensava que si feies una assignació de variable a línia d'ordres seguida d'una ordre, aquella assignació només tenia efecte per a l'ordre en qüestió. Per exemple, segons això, $ foo=1 echo $foo hauria d'escriure "1". Però estic veient que no fa l'assignació... Ha canviat recentment, o és que mai ha funcionat així? Salut
Screenshots of Debian software
Hi All Looking at https://screenshots.debian.net/ the Debian project seems to want some screen shots of different applications etc. I have taken some screenshots for various purposes and since seeing this have started to rename, organize and keep them in case the are useful for this part of the project. These are currently stored on Salsa at https://salsa.debian.org/zleap-guest/screenshots Is anyone here, on the team that deals with screenshots please, I am probably far better at taking the screenshots, renaming them etc and uploading them to salsa, where I am happy for someone to download them and upload to the screenshot repository as required. please use which ever license is appropriate. If we need a volunteer to do the uploading to the above site, I am _not_ offering to volunteer as I am trying to do other things relating to the project. I can however promote the position as long as a job spec (as such) can be written that is clear, concise and explicit as to what that person needs to do, skills required etc. Maybe as a sub page of the screenshots page. You need to be clear as to what you are looking for and the skills required. The link to this could be 'want to help please click here.' I can then try and approach people who may be able to help or send out the information to a wider group who may be able to help. Paul -- Paul Sutton http://www.zleap.net https://www.linkedin.com/in/zleap/ gnupg : 7D6D B682 F351 8D08 1893 1E16 F086 5537 D066 302D
Install backport during netinstall installation process
I've been struggling to fully setup some machines with A2SDi-8C-HLN4F motherboards and Intel x553 NICs (which require recent ixgbe support) as Debian stable machines. Thanks to considerable help from this list, I've been able to successfully setup the machines over the net using buster/testing netinstall images, which allow one to select stretch/stable at install time, then reboot into rescue mode on the netinstaller and install kernel-image-4.19.0-0.bpo from backports to provide a stable system and kernel with ixgbe support. However this doesn't work when running root off a RAID1 array with dm_crypt on top. Rescue mode can't both reassemble the array and decrypt the volume. While I can do that from the rescue shell I don't know how to pivot to make the decrypted volume root so I can install the backport kernel. ** Consequently I'd be grateful to know if: * it is possible to somehow install the backport kernel and dependencies during the netinstall process (apt-get install doesn't seem available on the virtual terminals) * alternatively, what mount point and commands should I use to make a root file system (which I've re-raided and decrypted) available to the buster installer in rescue mode Thanks very much Rory ** there is another issue, which is the stretch grub doesn't seem to be able to decrypt a dm_crypt volume when made from buster. I've reported that to debian-boot.
Re: Debian 9.9 failed to install under VirtualBox
On Thu, 16 May 2019 08:08:57 +0300 "Godruma-vihari dasa (Michael A. Golub)" wrote: > Hi, > > I tried to install Debian 9.9 under VirtualBox (6.0.6, the latest) both > using iso-images and with net-installer. It worked fro some time and > then at the step "Installing programs" (or something like that) reported > an invalid distribution. I downloaded the iso-images both via http and > torrent services. They seemed the same. What is wrong? > > I am going to start using Debian in a VM and then move to it completely. What's your host system? Windows? Did you download the correct Debian install ISO for your system? What is your system's hardware? Did you RTFM? It should have been the first thing you did. Just installing VirtualBox by itself is usually insufficient for it to work properly. All is revealed in the user manual. B
Re: icedtea-plugin desaparegut
1. Jo pensava que dels repositoris no s'eliminava les versions anteriors del programari de la mateixa distribució/versió. 2. Hi ha altres navegadors derivats de Mozilla que sí que fan ús d'aquestes extensions. Per posar un exemple, jo he estat instal·lant IceCat 52 a Debian per a utilitzar el complement de Java que requereixen algunes administracions públiques per a signar i presentar documents. __ I'm using this express-made address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 16/5/19 a les 0:08, Alex Muntada ha escrit: > Hola Narcis, > >> «Stop building» no hauria de significar eliminar les versions >> ja empaquetades i publicades (!) >> Això pot trencar dependències d'altre programari, tant a Debian >> com a d'altres publicadors. > > Des del moment en què s'accepta la versió ESR de Firefox a stable > com la millor alternativa, hi acompanyen tots els canvis que això > suposi, trenquin o no altre programari. El plugin de java no és > pas l'únic plugin que ha deixat de funcionar amb les noves > versions de firefox. > > Mantenir versions del icedtea-plugin que no funcionen amb firefox > genera més maldecaps que no en resol per a la majoria d'usuaris. > Per tant jo trobo que té força sentit que no s'ofereixi quelcom > que se sap que no funciona. > > Per a usuaris més avançats que vulguin tenir una foto de l'arxiu > tal com estava en un moment concret existeix snapshot.debian.org. > > Salut! > Alex > > -- > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada > ⢿⡄⠘⠷⠚⠋ Debian Developer - log.alexm.org > ⠈⠳⣄ >
